جواب یک سوال امتحان 290-70

[hamed89156]

سلام

من داشتم تست می زدم ، توی یکی از سوالات بدجور گیر کردم.

از برادران ویندوز کار خواهشمند است لطف فرموده و علت جواب این سوال را مختصراً تشریح کنند.

قبلاً از همکاری برادران کمال تشکر را دارد.

You are a network administrator for your company. The corporate network consists of a single Active Directory domain. All servers run Windows Server 2003, and all client computers run Windows XP Professional. A file server named Server1 contains a shared folder named Share1. One day, some users report that they cannot access any files in Share1, while other users do not experience this problem. You try to connect to Share1 from your workstation, but your attempt is unsuccessful. Then, you try to access data in Share1 through a Remote Desktop connection to Server1, and you can view, and modify files in Share1. You must ensure that all users can access data in Share1.

What should you do?

Assign the Allow - Modify NTFS permission for Share1 to the Users group.*
Assign the Allow - Change share permission for Share1 to the Users group.*
Replace the 10-Mbps network adapter on Server1 with a 100-Mbps adapter.*
Add client access licenses to Server1*

جواب صحیح : گزینه د

Explanation: Each shared folder can be configured to allow a specific number of connections. If the number of connections that are allowed for Share1 has been reached, no new connections will be allowed until one of the connected users disconnects from the share. The fact that you have failed to connect to Share1 by using the SMB protocol, but have successfully connected through a Remote Desktop connection, indicates that Server1 does not allow access to data in Share1 through the share, but allows access locally. It appears that the maximum number of allowed connections to Share1 has been reached. To address the problem, you should consider purchasing additional client access licenses and adding them to Server1. After that, you can increase the number of allowed connections to Share1.

The scenario indicates that only some users cannot connect to Share1; thus, the problem cannot be caused by a lack of share or NTFS permissions for Share1 that are assigned to the Users group. If network .bandwidth on your corporate LAN
were insufficient to support the current number of users, then all users would report slow access across the network; however, authorized users would not be denied access to the data for which they are assigned the appropriate permissions.

---

موضوعات مشابه:

• سوال در مورد ویندوز XP و سوئیچ
• سوال در مورد Access point و سوئیج
• چطور تنظيمات يك سوئيج را روس سوئيچ ديگر قرار دهم
• يك سوال (2تا سوئيچ...)؟؟؟

---

[Reza.D]

من هم با این سوالات Licensing مشکل داشتم.شاید دلیلش عدم کاربرد این مبحث در مملکت ما باشه.

زمانیکه ویندوز سرور رو نصب میکنیم یه صفحه داره که mode و تعداد لایسنس رو مشخص میکنه.

این سوال گیرش در همین نقطه است.تعداد Client Access License اون فایل سرور به max مقدار خودش رسیده به همین دلیل اجازه دسترسی به اون سرور ازطریق شبکه و استفاده از منابع share شده داده نمیشه اما همونطور که در توضیح جوابش گفته به صورتlocal میشه منابع رو استفاده کرد و دسترسی داشت.

در مورد licensing بد نیست این رو یه نگاه بندازید شاید بهتر کمک کنه:

http://www.microsoft.com/windowsserv...loverview.mspx

از نظر تستی و به قولی نکته کنکوری هم به سوال نگاه کنید بقیه گزینه ها به راحتی رد میشن.

این چیزیه که به عقل ناقص من میرسه.امیدوارم اشتباه نکرده باشم.

اگر از دوستان کسی نحوه دقیق چک کردن این لایسنس ها رو (در عمل) توضیح بده ممنون میشم.

[patris1]

http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx#tab=1

About Licensing

Client Access Licenses

If the workstations in your organization are networked, you likely depend on network server software to perform certain functions, such as file and print sharing. To legally access this server software, a Client Access License, or CAL, may be required. A CAL is not a software product; rather, it is a license that gives a user the right to access the services of the server.



Licensing software with Client Access Licenses can be complicated due to the technical nature of server products and networks. Microsoft offers a device-based CAL (Device CAL) or a user-based CAL (User CAL) for purchase. In addition, an External Connector (EC) license is offered for some products as an optional alternative to address specific customer scenarios.
This overview is for reference purposes only. Before purchasing, you should visit the "How to Buy" section for each product and consult your Microsoft representative or local reseller regarding your specific licensing needs.

User CALs

With the User CAL, you purchase a CAL for every user who accesses the server to use services such as file storage or printing, regardless of the number of devices they use for that access. Purchasing a User CAL might make more sense if your company employees need to have roaming access to the corporate network using multiple devices, or from unknown devices, or simply have more devices than users in your organization.

Client Access License based on user


Device CALs

With a Device CAL, you purchase a CAL for every device that accesses your server, regardless of the number of users who use that device to access the server. Device CALs may make more economic and administrative sense if your company has workers who share devices, for example, on different work shifts.

Client Access License based on device


External Connectors

If you want external users—such as business partners, external contractors, or customers—to be able to access your network, you have two licensing options:

• Acquire CALs for each of your external users.
• Acquire External Connector (EC) licenses for each server that will be accessed by your external users.

External Connector licensing



An external user is a person who is not an employee or similar personnel of the company or its affiliates, and is not someone to whom you provide hosted services. An EC license assigned to a server permits access by any number of external users, as long as that access is for the benefit of the licensee and not the external user. Each physical server that external users access requires only one EC license regardless of the number of software instances running. An "instance" is an installed copy of software.
The right to run instances of the server software is licensed separately; the EC, like the CAL, simply permits access. The decision on whether to acquire CALs or an EC for external users is primarily a financial one.

Server Licensing Not Requiring CALs

Some server products are available to be licensed on a "per processor" or "per instance" basis.

Per Processor Licensing

Under the Per Processor model, you acquire a Processor License for each processor in the server on which the software is running. A Processor License includes access for an unlimited number of users to connect from either inside the local area network (LAN) or wide area network (WAN), or outside the firewall (via the Internet). You do not need to purchase additional server licenses, CALs, or Internet Connector Licenses.

Software licensed by processor



Specialty Server Licensing

Specialty Server licensing is a commonly used model. Specialty Servers are server-only licenses that also do not require CALs. Specialty Servers require a server license for each instance of the server software running on a server. An example of this is Microsoft Office SharePoint Server for Internet Sites. You can run the instance in a physical or virtual operating system environment. By exception, some products provide more specific use rights.

Specialty Server licensing



Other examples of Specialty Server licensing include Windows Web Server 2008 and Microsoft Dynamics CRM 4.0 Workgroup Server.
For a list of Microsoft Server products and their applicable CALs, see the Product CALs tab

[patris1]

http://www.boyce.us/articles/licensing_cals.asp

Understanding Client Access Licenses
Microsoft doesn't make all of its money just selling software-it also makes a boat-load selling Client Access Licenses. Whether you are an administrator who manages hundreds of systems or a small business owner just trying to connect a few PCs to a server, understanding Client Access Licenses is the only way to ensure your company doesn't run afoul of Microsoft's End User License Agreements (EULAs).
What's a CAL?
When you buy Windows Server, you receive a server license that allows you to install the operating system on one computer. A server license by itself doesn't give you the legal right to allow others to connect to that computer, whether they work for your company or not. Instead, each user needs a Client Access License, or CAL. You might think that buying a copy of Windows XP or other Windows operating system gives you that CAL, but it doesn't. When you buy a Windows client operating system you have the legal right to install it on a computer and use it, but the Windows license does not give you the legal right to use it to connect to a Windows Server. That's where the CALs come in.
A CAL gives you the legal right to connect to a server application such as Windows Server. Not all CALs are created equal, however. A CAL is targeted to a specific server application.
For example, in order for ten users to connect to a Windows Server to access shared printers and folders, you need to purchase ten Windows CALs. Windows Server keeps track of the connections by computer, so multiple concurrent connections from one computer count only against one license. For example, you could open four shared folders and use two shared printers concurrently, and this would count as one connection rather than six.
Now, let's throw Exchange Server into the mix. If you have 25 users, you need to purchase 25 Exchange Server CALs in addition to 25 Windows CALs for that server. Likewise, other Microsoft server applications such as SQL Server, Project Server, Host Integration Server, and others, require their own CALs. Let's expand the example and say that you have 25 users who need access to the server for printing and file sharing. 20 of those users need access to Exchange Server, and 10 need access to SQL Server. You need 25 Windows CALs, 20 Exchange Server CALs, and 10 SQL Server CALs, for a total of 55 CALs.
Sounds simple enough, doesn't it? In an example like this it is simple, but what if several of your Exchange Server users need to access the server from a desktop computer, a notebook, and a PDA? What if you add a shop floor where 50 employees share 10 computers in different shifts? Now you need to consider licensing modes.
Choose Your Mode
Windows 2000 Server offers two licensing modes: per-server and per-seat. Windows Server 2003 replaces per-seat licensing with per-user / per-device. Let's take per-server first.
When you configure Windows Server for per-server mode, you specify the number of CALs you have purchased for the server and Windows Server allows up to that number of concurrent connections. Configure it for 100 CALs, for example, and Windows Server will support up to 100 concurrent connections. Additional connection attempts after the limit is reached fail. Windows Server counts administrator connections against the total but still allows administrators to connect after the limit is reached to allow them to manage the server (and potentially disconnect users if needed). With per-server licensing therefore, Windows Server actively controls connections based on the number of licenses for which you have configured it.
Per-user / per-seat mode is a bit different. A User CAL (per-user mode) allows a single user to connect to the server with any number of devices. If your users work with a desktop computer, notebook, PDA, and smart phone-all accessing an Exchange Server, for example-the logical choice would be to purchase User CALs. Each user could then connect with as many devices as needed.
A Device CAL allows one device to connect to the server application. For example, assume you have a training lab containing 20 computers that are shared by 200 students throughout the day. Rather than purchase 200 User CALs, you would instead purchase 20 Device CALs. Since User CALs and Device CALs cost the same, your licensing cost is only one-tenth what it would be if you purchased User CALs.
An important distinction between per-server and per-user / per-device licensing is that with the latter, Windows Server does not prevent connections even after the limit is reached. The License Logging service does monitor and report connections for both per-server and per-user / per-device, but only with per-server mode does Windows deny connections after the limit is reached.
I Don't Need No Stinking CAL!
There are a few situations where CALs are not needed. The first is when users access the server anonymously. For example, you don't need CALs to allow users to access your company's Web site. If you add a private area to the site that requires authentication, such as to allow access to key customers or business partners, you do need to add CALs for those users who will be authenticating.
Recognizing that companies might require a large number of customers or clients to access a server or server application, Microsoft introduced the External Connector License. An External Connector (EC) allows an unlimited number of external users to access a particular server application. ECs are not meant to allow company employees to connect remotely-you need traditional CALs for that. Instead, ECs are targeted at customers, clients, and business partners who need authenticated access to your servers and server applications.
ECs can be expensive if you don't have very many customers or partners at the moment who need access. If that's the case, you can purchase CALs and achieve the same legal goal. If the number of external users will grow over time, compare the cost of individual CALs against the cost of an EC to determine which option makes the most sense for your situation.
For more information about CALs and licensing, check out Microsoft's CAL Guide at its Software Asset Management site. You'll also find more information about licensing and license management in an article I wrote for TechRepublic on the subject. Finally, look for more articles here in the future on licensing and license management.
Jim

[patris1]

و نیز برای ترمینال سرور

http://support.microsoft.com/?scid=kb%3Ben-us%3B822134&x=22&y=11

The function of Terminal Server CALs in Windows Server 2003


This article describes the function of client access licenses (CALs) in the Terminal Server Licensing client licensing management system in Microsoft Windows Server 2003.


CALs in Windows Server 2003 are different from CALs in Microsoft Windows 2000. Windows 2000 only uses Device CALs. These CALs are tied to a device. Windows Server 2003 uses Device CALs, and it also uses a new client access license, User CALs. Device CALs in Windows Server 2003 function the same way that Device CALs in Windows 2000 do. User CALs, however, permit access to software by an individual user, instead of by a device.

User CALs allow customers more flexibility when they use Terminal Server in their environments. If a user logs on to more than one client computer, they use one User CAL. The User CAL is not stored in the registry on the client computer the way that a Device CAL is.

User CALs can only be installed on a Windows Server 2003 Terminal Server Licensing server. User CALs cannot be issued to Windows 2000 terminal servers or to clients that access Windows 2000 terminal servers. If the network contains Windows 2000 terminal servers, the Windows Server 2003 Licensing server also has to contain Device CALs, not just User CALs.

Customers do not need a Device CAL and a User CAL to access a terminal server. The terminal server is set in the Terminal Services Configuration tool under Server settings\Licensing as to which type of CAL it will accept. You can set this to Per Device or Per User. This setting can be changed without requiring a restart of the terminal server. One terminal server cannot accept User CALs and Device CALs at the same time.

If the Terminal Server is in Per Device mode and your Licensing server only contains User CALs, you are only issued temporary licenses. When these temporary licenses are close to expiration, you see the following message in a pop-up window: Your terminal services temporary client license will expire in N days. Please contact your system administrator to get a permanent license.
This message also appears in the application event log as:Event Type: Information Event
Source: Application Popup
Event ID: 26
Description:
Application popup: Terminal Services
Warning : Your terminal services temporary client license will expire in N days. Please contact your system administrator to get a permanent license.
To correct this problem, switch the terminal server to Per User mode.

Similarly, Terminal Server clients that run Microsoft Windows XP or Windows 2000 may receive the following error if the client cannot connect to the Terminal Server:The remote session was disconnected because the local computer client access license could not be upgraded or renewed.


The following event is logged in the application event log on the Terminal Server computer:Event Type: Information
Event Source: TermService
Event Category: None
Event ID: 1011
Date: 10/21/2003
Time: 8:23:13 AM
User: N/A
Description: The terminal server client useraccount has been disconnected because its temporary license has expired. For more information, see Help and Support Center at Microsoft Support.
This problem may occur if the Licensing Mode in Terminal Services is set to Per Device, the Terminal Server Licensing server only has Per User CALS.

To correct this problem, change the Licensing Mode in Terminal Services Configuration to Per User. To do this, follow these steps:

1. Click Start, point to Administrative Tools, and then click Terminal Services Configuration.
2. Click Server Settings, and then double-click Licensing Mode.
3. Change the Licensing Mode to Per User, and then click OK.

Currently, Windows Server 2003 does not manage User CALs. This means that even though there is a User CAL in the license server database, the User CAL will not be decremented when it is used. This does not remove administrators from End User License Agreement (EULA) requirements to have a valid terminal server (TS) CAL for each user. Failure to have a User CAL for each user, if Device CALs are not being used, is a violation of the EULA.

Note To use both User and Device TS CALs simultaneously on the same terminal server, the server must be configured for Per User TS CAL mode.

The following text is from the End User License Agreement (EULA) for Windows Server 2003:Two different TS CALs are available to you: "Device" and "User." Each TS Device CAL permits one Device (used by any User) to conduct Windows Sessions on any of your Servers. Each TS User CAL permits one User (using any Device) to conduct Windows Sessions on any of your Servers. You may use a mix of TS Device CALs and TS User CALs simultaneously with the Server Software in your environment. You can have a Terminal Server request Per User licenses or Per Device (default) but not both simultaneously.




For more information about Windows Server 2003 Terminal Server Licensing, visit...


For more information about Windows Server 2003 Terminal Server Licensing, visit the following Microsoft Web sites:
Guidelines for Deploying Windows Server 2003 Terminal Server (Guidelines for Deploying Windows Server 2003 Terminal Server)
Windows Server 2003 Terminal Server Licensing (Windows Server 2003 Terminal Server Licensing)



APPLIES TO

• Microsoft Windows Server 2003, Standard Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

Keywords:

kbdirservices KB822134

[hamed89156]

اگه جسارت نیست سوال دوم رو هم می پرسم.

You are a network administrator for your company. Your corporate network consists of a single Active Directory domain. All servers run Windows Server 2003, and all client computers run Windows XP Professional. A written company policy defines a standard desktop environment that must be implemented for all users on the network. Each time a user logs on, the desktop environment must be the same, regardless of the changes that the user may have made during previous sessions. If a user makes any changes to his or her desktop environment, those changes must be discarded when the user logs off. You must enforce the company policy.

What should you do?

§ For each user account, configure a profile path to a network share. In each user's roaming profile, rename the NTuser.dat file to NTuser.man.



§ For each user account, configure a profile path to a network share. Assign only the Allow - Read permission for the share to the Authenticated Users group.



§ Rename the NTuser.dat file to NTuser.man in each user's local profile.



§ Configure all user accounts to use the same roaming profile. Configure the Default Domain Policy GPO to prevent changes to roaming profiles.

[hamed89156]

جواب گزینه د درسته در صورتی من الف رو زدم !!!

Please Help

[patris1]

http://technet.microsoft.com/en-us/library/bb490855.aspx

Depending on how you manage your network, you or a user can define the desktop settings.
The following user profiles are available in Windows .NET Server, Windows XP Professional, and Windows 2000 Professional:

• Local User Profile. Created the first time that a user logs on to a computer, the local user profile is stored on a computer's local hard disk. Any changes made to the local user profile are specific to the computer on which the changes are made.
• Roaming User Profile. A copy of the local profile is copied to, and stored on a server share. This profile is downloaded every time that a user logs on to any computer on the network, and any changes made to a roaming user profile are synchronized with the server copy upon logoff.
• Mandatory User Profile. A type of profile that administrators can use to specify particular settings for users. Only system administrators can make changes to mandatory user profiles. Changes made by the user to desktop settings are lost when the user logs off.
• Temporary User Profile. A temporary profile is issued any time that an error condition prevents the users profile from being loaded. Temporary profiles are deleted at the end of each session - changes made by the user to their desktop settings and files are lost when the user logs off.

Note: If you need to provide managed desktop configurations for groups of users or computers, consider using Group Policy instead of mandatory profiles

در ضمن سوال بدبخت هم گفته از Group Policy استفاده شود. You must enforce the company policy

در ضمن شما فقط یک UNC تو Share Folder بدید که کافی نیست، به نظرتون هست!!!

[hamed89156]

. Note: If you need to provide managed desktop configurations for groups of users or computers, consider using Group Policy instead of mandatory profiles

در ضمن سوال بدبخت هم گفته از Group Policy استفاده شود. You must enforce the company policy

1- منظور از managed desktop configuration چیه ؟

2- فکر نکنم چون حالا از عبارت "policy" در سوال استفاده شده ، منظور group policy بوده !

[patris1]

نه عزیز من همیشه که اینطور نیست، ولی بعضی وقتها یکم ظرافت باید بخرج داد.
والا Company Policy یعنی سیاست کمپانی .

[hamed89156]

سوال بعدی !

Dan is the administrator for a Windows Server 2003 computer named Data3. Data3 hosts shared folders on drive F. Shadow Copies of Shared Folders is enabled on the volume. The storage volume is located on drive D. The network segment where Data3 resides is unavailable on Monday while maintenance is being performed on a router. During this time, Dan receives a call from a user who is requesting a previous version of a database file on Data3 named SECustomer.mdb. SECustomer.mdb is located on drive F in the shared SalesData folder. The user requests that a copy of the previous version be delivered to her office on floppy disk as soon as possible. Dan is unable to connect to Data3 from his client computer due to the router maintenance. He cannot log on to other computers on the network segment. He logs onto Data3 using the console and opens the properties for SECustomer.mdb but the Previous Versions tab is not displayed.

Dan contacts you and asks if you know of a way to access the shadow copies directly from the Data3
console
What should you instruct Dan to do?

§ Install the Shadow Copy client on Data3.

§ Open Internet Explorer, and connect to \\localhost\F$.

§ Open a command prompt, and run vssadmin create shadow.

§ Use Computer Management to access the shared folder, and reopen the SECustomer.mdb properties.

[patris1]

http://www.petri.co.il/how_to_use_the_shadow_copy_client.htm

Recovery of Files or Folders

There are three fundamental situations in which most end users find themselves at one time or another when they use their computers. These scenarios include:

• Accidental file deletion, the most common situation.
• Accidental file replacement, which occurs for example, when users forget to use Save As.
• File corruption.

It is possible to recover from all of these scenarios by accessing shadow copies. The process is a little different when accessing a file compared to accessing a folder.

Important: End users should be notified regarding how frequently shadow copies of the selected volume will be made. End users should also be made aware that there is a maximum of 64 shadow copies, after which the earliest copy is purged. Recovering a Deleted File

To recover a deleted file, use the following procedure:

1. Navigate to the folder in which the deleted file had been stored.
2. Position the cursor over a blank space in the folder. If the cursor hovers over a file, that file will be selected.
3. Right-click the mouse and select Properties from the bottom of the menu. Select the Previous Versions tab.
4. Select the version of the folder that contains the file before it was deleted, and then click View.
5. View the folder and select the file that will be recovered.
6. Drag and drop, or cut and paste, the shadow copy to the desktop or folder on the end user’s local machine.

Recovering an Overwritten or Corrupted File

Recovering an overwritten or corrupted file is easier than recovering a deleted file because the file itself can be right-clicked instead of the folder. To recover an overwritten or corrupted file use the following procedure:

1. Right-click the overwritten or corrupted file and click Properties.
2. Select Previous Versions.
3. If you want to view the old version, click View. To copy the old version to another location, click Copy... To replace the current version with the older version, click Restore.

Recovering a Folder

To recover a folder use the following procedure:

1. Position the cursor so that it is over a blank space in the folder that will be recovered. If the cursor hovers over a file, that file will be selected.
2. Right-click the mouse, select Properties from the bottom of the menu, and then, click the Previous Versions tab.
3. Choose either Copy or Restore.
4. Choosing Restore enables the user to recover everything in that folder as well as all subfolders. Selecting Restore will not delete any files

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

دانلود کنید و بخوانید

http://download.microsoft.com/download/f/3/d/f3da10e8-c9fd-454d-9a54-c765d738449d/SCR.doc