ࡱ> 7 "*bjbjUU 7|7|hl  VVVDLLL(M|Mt$P&JU(rUrUUR[RnLs$R# r%$]VFvZ|[@FvFvĂrUU*4ĂĂĂFvRrUVUĂFvĂĂ 6k4"VUP j{տ;LLz # ^HU&R~r&Ă Operating System User Data and Settings Management White Paper Abstract This white paper describes the IntelliMirror user data and settings management features of the Windows 2000 operating system. These features are key components of change and configuration management. The user data and settings management features can help administrators reduce their organizations Total Cost of Ownership. 2000 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft, Windows, and WindowsNT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 USA 06/00 Contents  TOC \o "3-3" \t "Heading 1,1,Heading 2,2" Introduction  PAGEREF _Toc485535598 \h 1 User Profiles Overview  PAGEREF _Toc485535599 \h 2 Advantages of User Profiles  PAGEREF _Toc485535600 \h 2 User Profile Structure  PAGEREF _Toc485535601 \h 3 Table 1  PAGEREF _Toc485535602 \h 4 Configuration Preferences Stored in the Registry Hive  PAGEREF _Toc485535603 \h 4 Configuration Preferences Stored in Profile Directories  PAGEREF _Toc485535604 \h 5 Table 2  PAGEREF _Toc485535605 \h 7 How Do Users Get Their Profile?  PAGEREF _Toc485535606 \h 7 Enhancements to Roaming User Profiles  PAGEREF _Toc485535607 \h 9 Improved Merge Algorithm  PAGEREF _Toc485535608 \h 9 Non-roaming Folders  PAGEREF _Toc485535609 \h 12 Quotas on Profile Size  PAGEREF _Toc485535610 \h 12 Table 3  PAGEREF _Toc485535611 \h 13 Configuring a Roaming User Profile  PAGEREF _Toc485535612 \h 17 Best Practices for User Profiles  PAGEREF _Toc485535613 \h 17 Folder Redirection Overview  PAGEREF _Toc485535614 \h 19 Advantages of Using Folder Redirection  PAGEREF _Toc485535615 \h 19 Folders that Can Be Redirected  PAGEREF _Toc485535616 \h 20 Default Folder Locations  PAGEREF _Toc485535617 \h 21 Table 4  PAGEREF _Toc485535618 \h 21 Configuring Folder Redirection  PAGEREF _Toc485535619 \h 21 Using Logon Scripts to Redirect Folders  PAGEREF _Toc485535620 \h 23 Complementary Technologies  PAGEREF _Toc485535621 \h 23 Offline Files  PAGEREF _Toc485535622 \h 23 Synchronization Manager  PAGEREF _Toc485535623 \h 24 Best Practices for Folder Redirection  PAGEREF _Toc485535624 \h 25 Table 6  PAGEREF _Toc485535625 \h 26 Table 8  PAGEREF _Toc485535626 \h 28 Common Scenarios and Examples  PAGEREF _Toc485535627 \h 30 The New Hire  PAGEREF _Toc485535628 \h 30 The Laptop User  PAGEREF _Toc485535629 \h 31 Computer Replacement  PAGEREF _Toc485535630 \h 31 A Shared Computer Environment  PAGEREF _Toc485535631 \h 32 For More Information  PAGEREF _Toc485535632 \h 33 Management and Overview Papers  PAGEREF _Toc485535633 \h 33 Technical Papers  PAGEREF _Toc485535634 \h 34  Introduction User data includes the documents, images, spreadsheets, presentations and e-mail messages on a user s computer. User settings include application configurations, preferences, window sizes, toolbar settings and so forth on a user s computer. With the capabilities provided by the IntelliMirror"! management technologies in the Windows 2000 operating system, administrators can manage user data and settings in ways that reduce the Total Cost of Ownership (TCO) for the computing systems. By using IntelliMirror on both the server and client, administrators can protect and manage user data and settings. Non-recoverable data from local workstations can be copied to servers, where it can be easily backed up and centrally managed. Personalized data, applications, and settings can follow each user to different computers throughout the network. Administrators can easily replace faulty computers and restore all user data and settings on a new computer. When fully deployed, IntelliMirror uses the Active Directory"! service and Group Policy in Windows 2000 Server for policy-based management of user desktops. A Windows 2000 Professional desktop can be automatically configured to meet specific requirements of a user s business roles, group memberships, and location. Group Policy and the Active Directory are not necessary for every IntelliMirror feature. Most of the features can be set on the local level or through local polices. An organization can tailor use of IntelliMirror to its needs. When planning to use IntelliMirror, an organization should assess which features it needs and then implement the technology required. This paper discusses two of the key components that provide IntelliMirrors user data and settings management - User Profiles and Folder Redirection. It also provides an architectural overview of these features, and presents sample scenarios that illustrate their use. User Profiles Overview A user profile describes the desktop computing configuration for a specific user, including the users environment and preference settings. A profile is created the first time that a user logs on to a Windows 2000based or Windows NT Workstationbased computer. A user profile is a group of settings and files that defines the Windows 2000based environment that the system loads when a user logs on. It includes all the user-specific configuration settings, such as program items, screen colors, network connections, printer connections, mouse settings, and window size and position. Profiles are not user policies and the user has a profile even if you don't use Group Policy. A user's data can be stored on the local hard disk drive, or IntelliMirror can be set so that the data roams with the user wherever he or she logs on. User data can include shortcuts to executable files, personal files, and user settings, such as a custom dictionary. Depending on how you manage your network, you or a user can define the desktop settings. The following user profiles are available in Windows 2000. 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. You create this profile and store it on a server. This profile is available every time that a user logs on to any computer on the network, and any changes made to a roaming user profile are updated on the server. 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. The mandatory user profile feature is included with Windows 2000 only to provide compatibility with Windows NT 4.0based domains. Note: If you need to provide managed desktop configurations for groups of users or computers, you should use Group Policy in Windows 2000, instead of mandatory profiles. Advantages of User Profiles A primary goal of user profiles is to separate each users settings and data from that of other users and the local computer. Separating each users state provides several advantages: It allows for stateless computers. An organization can configure computers to store all the key user settings and data away from the local computer. This allows for much easier computer replacement and backup. When a computer needs replacing, it can simply be swapped out all of the users state information is safely maintained separately on the network and is independent of a particular computer. When the user logs onto the new computer for the first time, a local copy of the users state is copied to the new computer. It allows a users system and desktop customizations to travel with the user from computer to computer, without requiring the user to reconfigure any settings. When a user logs on to any computer on the network that supports the roaming profile, the users desktop appearsjust as that user left it before logging off. With roaming user support, users can share computers, but each user has his or her personal desktop (both roaming and mandatory profiles support this functionality). User Profile Structure A user profile consists of a registry hive and a set of folders stored in the file system. The registry is a database used to store computer- and user-specific settings. Portions of the registry can be saved as files, called hives. These hives can then be reloaded for use as necessary. User profiles take advantage of the hive feature to provide roaming profile functionality. The user profile registry hive is the NTuser.dat in file form, and is mapped to the HKEY_CURRENT_USER portion of the registry when the user logs on. The NTuser.dat hive maintains the users environment preferences when the user is logged on. It stores those settings that maintain network connections, Control Panel configurations unique to the user (such as the desktop color and mouse), and application-specific settings. The series of profile directories store shortcut links, desktop icons, startup applications, and so forth. Together, these two components record all user-configurable settings that can migrate from computer to computer. The default location of user profiles has been changed for Windows 2000 to allow administrators to secure the operating system folders without adversely affecting user data. On a clean installed Windows 2000 computer, profiles are stored in the %Systemdrive%\Documents and Settings folder. In contrast, on Windows NT 4.0 computers, profiles are stored inside the system directory, at %Systemroot%\profiles folder (typically WINNT\profiles). Note: if you upgrade a computer from Windows NT 4.0 to Windows 2000, the profile location remains %Systemroot%\profiles. Table 1 below shows the location of user profiles for each of the possible installation scenarios: Table 1. Operating system Location of user profileWindows 2000 clean installation (no previous operating system)%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and Settings Windows 2000 upgrade of Windows NT 4.0%SYSTEMROOT%\Profiles; for example, C:\WinNT\ProfilesWindows 2000 upgrade of Windows NT 3.51%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and SettingsWindows 2000 upgrade of Windows 95 or Windows 98%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and Settings Configuration Preferences Stored in the Registry Hive The NTuser.dat file contains the following configuration settings: Windows2000 Explorer settings. All user-definable settings for Windows2000 Explorer, as well as persistent network connections. Taskbar settings. Printer settings. All network printer connections. Control Panel. All user-defined settings made in the Control Panel. Accessories. All user-specific application settings affecting the Windows2000 environment, including: Calculator, Clock, Notepad, Paint, and HyperTerminal, among others. Application Settings. Many applications store some per user settings in the users registry hive (HKEY_CURRENT_USER). An example of these types of settings would be Microsoft Word 2000s toolbar settings. Configuration Preferences Stored in Profile Directories The screenshot in Figure 1 below illustrates the structure of the user profile. Figure 1. User Profile Each users profile contains the following folders: Application data*. Application-specific data, such as a custom dictionary for a word processing program. Application vendors decide what data to store in this directory. Cookies. Internet explorer cookies. Desktop. Desktop items, including files and shortcuts. Favorites. Internet Explorer favorites Local Settings*. Application settings and data that do not roam with the profile. Usually either machine specific, or too large to roam effectively. Application data. Computer specific application data. History. Internet Explorer history. Temp. Temporary files. Temporary Internet Files. Internet Explorer offline cache. My Documents. The new default location for any documents that the user creates. Applications should be written to save files here by default. My Pictures. Default location for users pictures. NetHood*. Shortcuts to Network Neighborhood items. PrintHood*. Shortcuts to printer folder items. Recent. Shortcuts to the most recently used documents. SendTo. Shortcuts to document storage locations and applications. Start Menu. Shortcuts to program items. Templates*. Shortcuts to template items. * These directories are hidden by default. To see these directories, change the View Options. By default, the Local Settings folder, and its subfolders do not roam with the profile. This folder contains application data that is not required to roam with the user, such as temporary files, non-critical settings, and data too large to roam effectively. The Folder Redirection feature of IntelliMirror allows an administrator to redirect the location of certain folders in the user profile to a network location. When these redirected folders are accessed either by the operating system or by applications, the operating system automatically redirects to the location on a network share specified by the administrator. From a user perspective, this is similar to the roaming scenario because users have the same settings regardless of which computers they use. However unlike roaming, these settings actually remain on the network share. Folder redirection can be used with all types of user profiles, local, roaming, or mandatory. Using Folder Redirection with local profiles can provide some of the benefits of roaming profiles (such as having a users data available at any computer, maintaining data on the server) without the need to implement roaming profiles. Remember though, using Folder Redirection with a local profile would only result in the users documents and files being available from all computers. To have settings and configurations move with the user, you would need to use roaming profiles. Combining Folder Redirection with roaming profiles gives the benefit of roaming profiles, while keeping network traffic caused by synchronization of the profile to a minimum. Folder redirection is accomplished using Group Policy. The use of Folder Redirection with roaming profiles is discussed later in this document. Table 2 below lists the folders that roam with the profile by default, and indicates whether they can be redirected using Group Policy. Table 2. Folder NameDescriptionRoams with profile by defaultRedirect with Group PolicyApplication DataPer-user roaming application dataYesYesCookiesUsers Internet Explorer cookiesYesNoDesktopYesYesFavoritesUsers Internet Explorer favoritesYesNoLocal SettingsTemporary files and per-user non-roaming application dataNoNoMy DocumentsUsers documents. YesYesNetHoodYesNoPrintHoodYesNoRecentShortcuts to recently used documentsYesNoSend ToYesNoStart MenuUsers personal start menuYesYesTemplatesPer-user customized templatesYesNoHow Do Users Get Their Profile? The way in which users get their profiles depends on the type of profile theyre configured to use. This section describes this process. Local Profile - New User The user logs on. The operating system checks the list of user profiles located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to determine if a local profile exists for the user. If an entry exists, then this local profile is used. If a local profile is not found, and the computer is part of a domain, the operating system checks if a domain wide default profile exists in a folder named Default User on the domain controllers NETLOGON share. If a domain wide profile exists, it is copied to a subfolder on the local computer with the username under %SYSTEMDRIVE%\Documents and Settings\. For example, a new user with the username JDoe would have a profile created in %SYSTEMDRIVE%\Documents and Settings\JDoe. If a default domain profile does not exist, then the local default profile is copied from the %Systemdrive%\Documents and Settings\Default User folder to a subfolder on the local computer with a username under %Systemdrive%\Documents and Settings\. The users registry hive (NTUSER.DAT) is mapped to the HKEY_CURRENT_USER portion of the registry. When the user logs off, a profile is saved to the local hard disk of the computer Local Profile - Existing User The user logs on. Windows checks the list of user profiles located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to get the path to the users profile. The users registry hive (NTUSER.DAT) is mapped to the HKEY_CURRENT_USER portion of the registry. When the user logs off, the profile is saved to the local hard disk of the computer. Roaming Profile - New User The user logs on. Windows checks the list of user profiles located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to determine if a cached copy of the profile exists. If a local copy of the profile is not found, and the computer is part of a domain, Windows checks to determine if a domain wide default profile exists in the Default User folder on the domain controllers NETLOGON share. If a domain wide profile exists, it is copied to a subfolder on the local computer with their username under %Systemdrive%\Documents and Settings\. If a default domain profile does not exist, then the local default profile is copied from the %Systemdrive%\Documents and Settings\Default User folder to a subfolder on the local computer with their username under %Systemdrive%\Documents and Settings\. The users registry hive (NTUSER.DAT) is copied to the local cached copy of their user profile, and is mapped to the HKEY_CURRENT_USER portion of the registry. The user can then run applications and edit documents as normal. When the user logs off, their local profile is copied to the path configured by the administrator. If a profile already exists on the server, the local profile is merged with the server copy (see merge algorithm later in this paper for more details). Roaming Profile - Existing User The user logs on. Windows checks the list of user profiles located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to get the path to the users profile. The users registry hive (NTUSER.DAT) is copied to the local cached copy of the user profile, and is mapped to the HKEY_CURRENT_USER portion of the registry. The contents of the local cached profile are compared with the copy of the profile on the server, and the two profiles are merged. (See the new merge algorithm later in this paper for more details). The user can then run applications and edit documents as normal. When the user logs off, the local profile is copied to the path configured by the administrator. If a profile already exists on the server, the local profile is merged with the server copy Enhancements to Roaming User Profiles The Windows 2000 user data management and user settings management features provide several enhancements that increase the usability, resilience, and performance of roaming user profiles. Improved Merge Algorithm This section describes how Windows 2000 reconciles local and server copies of a users profile. To improve the experience of users, Windows 2000 roaming profiles have a new algorithm to synchronize copies of a profile. This prevents problems from occurring when a user logs into two different computers simultaneously. The Windows NT 4.0 algorithm worked well in the most common cases where users logged on to only a single computer. However, when a user logged onto multiple computers at the same time, the user sometimes experienced unexpected behavior caused by the assumption that each computer had the master copy of the profile. For Windows 2000, the algorithm was changed to support the merging of user profiles at the file level and to provide support for last writer wins. To illustrate the behavior of the new algorithm, several examples are presented that compare the behavior of Windows NT 4.0 to Windows 2000. Overview of the Windows NT 4.0 Algorithm In Windows NT 4.0, the algorithm is an Xcopy with full synchronization support. That is, it has the ability to mirror a profile from one location to another, and any extra files or directories in the destination location are removed. The algorithm is based on the concept that there is only one master profile at any one time. When the user is logged on, the master profile is on the local computer. When the user is not logged on, the master profile is on the server. The user logs on to computer A, the primary computer. The roaming profile is Xcopied from the server location to the local profile location. The user creates documents, changes colors, and so on. All of these changes are stored in the local profile location. As the user logs off the computer, the profile is Xcopied from the local profile location back to the server location. This is an exact mirroring process. If there are any extra files in the server location, they are deleted to ensure that the server location is a duplicate of the local profile. As mentioned previously, this works well in the majority of cases, where a user logs on to only a single computer; but a user who logs on to multiple computers at the same time might experience unexpected behavior. Examples of Windows NT 4.0 Merge Algorithm Issues When using Windows NT 4.0, a problem arises if the user logs on at two or more computers. Building on the preceding example: The user logs on to computer A. The user logs on to computer B. The user creates a document on computer A and stores it in the user profile. The user logs off of computer A. The user logs off of computer B. The document that the user created in step 3 is deleted because, from the perspective of computer B, the master profile is stored locally. The extra files on the server must be deleted so that the local profile is currently the master server profile. The Windows 2000 algorithm preserves the document because it is able to compare the time the document was created with the time the profile was loaded. If the document was created or modified after the profile load time, the file must be preserved because it came from a different source. A similar problem can occur when files are modified. For example, suppose that the user has a document called Document.doc in his or her My Documents folder in the server copy of the profile: The user logs on to computer A. The user logs on to computer B. The user modifies the document on computer A. The user logs off computer A. The user logs off computer B. The changes made to the document on computer A are lost because when the user logged off computer B, the computer overwrote the new version of the document with the old one; the computer is programmed to recognize that it had the master version of the profile. The Windows 2000 algorithm preserves the changes to the document because it compares the time the document was modified with the time the profile was loaded. This results in a much better experience for the user. Overview of Windows 2000 Merge Algorithm Windows 2000 merges user profiles at the file level. The merged profile contains the superset of files that are in the local computer and server copies of the users profile. In the case where the same file is in both the local and server copy of the profile, the file that was modified most recently is used. This means that new files are not deleted, and updated versions of existing files are not overwritten. When a document or file is updated, the new algorithm compares the timestamp of the destination file with the timestamp of the source file. If the destination file is newer, it is not overwritten. When a user logs on to a computer, the current time is saved; when the user logs off, this timestamp is used to determine which files are new in the server profile and which files have been deleted in the local profile. For example, if the server profile has a document in the My Documents folder called Review.doc and this file does not exist in the local profile, either it is a new file from a different computer, or it was originally in the local profile and the user deleted it. Knowing the time when this new profile was loaded, it is possible to compare it against the timestamp of Review.doc. If Review.doc was created or written to after the profile load time, the file must be preserved because it came from a different source. If the Review.doc timestamp is older than the profile load time, Review.doc must be deleted because it would have been copied to the local computer at load time. In addition, some files might need to be removed from the local cache so that items that were deleted between sessions remain deleted. For example: The user logs on to computer A. The user creates or modifies a document on computer A. The user logs on to computer B. The user logs off computer B; computer B has a copy of the document. The user deletes the document and logs off computer A. To ensure that the files are deleted, the cached version of the profile is synchronized with the profile on the server when a user logs on. All files in the local cache that are not present in the server and that were not modified since the last logoff time are removed. By using these changes, Windows 2000 can merge user profiles. Non-roaming Folders Roaming user profiles are copied from the server to the client when the user logs on, and copied back when the user logs off. However, Windows 2000 includes a per-user local settings folder within the user profile that is not copied during log on or log off sessions. Operating system components and other applications can store non-roaming per-user data in this folder. For example, Internet Explorer can store a user's Favorites in the roaming portion of the user profile and store the temporary Internet files in the local, non-roaming portion of the user profile. By default, the Temp and Temporary Internet Files folders are excluded from the roaming user profile. You can configure additional folders to not roam by using the Group Policy snap-in. If you enable this policy, you can exclude additional folders. However, you cannot use the Exclude Directories In Roaming Profile to include the Temp and Temporary Internet Files folders in a roaming user profile. Quotas on Profile Size The Proquota.exe program is a tool that you can set to monitor the size of a user's profile. If an individuals user profile exceeds the predetermined file limit, the user cannot log off from the computer until the user reduces the size of files. Profile quota size is managed using the Group Policy snap-in. You can use the Limit Profile Size policy, available in the User Configuration\Administrative Templates\System\Logon/Logoff node of the Group Policy snap-in to set the maximum size of the roaming user profile and to determine the systems response when the limit is reached. Click the Explain tab of this policy setting for more details. If you are combining Folder Redirection of the My Documents folder and roaming user profiles, it is best to not use quotas on the profile. The items that would normally be written to the user profile are done so on behalf of the user by the operating system and applications, so the user is not aware of them. Examples of these files include Custom.dic and Favorites. You can also use the policy that removes cached versions of the profile on logoff, if you are concerned with disk size on a multi-user computer for example, a public computer where thousands of users can log on. The policy is called Delete cached copies of roaming profiles, and it is accessed under the Computer Configuration\Administrative Templates\System\Logon node of the Group Policy snap-in. Group Policy Settings Pertaining to Roaming User Profiles Table 3 below lists the available policy settings related to roaming user profiles. For details about these policy settings, click the policys Explain tab. Table 3. PolicyLocation in Group Policy Snap-inDescriptionLimit profile sizeUser Configuration\Administrative Templates\System\Logon/LogoffSets the maximum size of a roaming user profile and determines the system's response when a roaming user profile reaches the limit. Delete cached copies of roaming profilesComputer Configuration\Administrative Templates\System\LogonDetermines whether the system saves a copy of a user's roaming profile on the local computer's hard disk drive when the user logs off. This policy and the related policies in this folder define a strategy for managing user profiles that reside on remote servers. Specifically, they indicate to the system how to respond when a remote profile is slow to load.Slow network connection timeout for user profilesComputer Configuration\Administrative Templates\System\LogonDefines a slow connection for roaming user profiles. If the server on which the user's roaming user profile resides takes longer to respond than the thresholds set by this policy permit, the system considers the connection to the profile to be slow. This policy and related policies in this folder together define the system's response when roaming user profiles are slow to load. PolicyLocation in Group Policy Snap-inDescriptionWait for remote user profileComputer Configuration\Administrative Templates\System\LogonDirects the system to wait for the remote copy of the roaming user profile to load, even when loading is slow. Also, the system waits for the remote copy when the user is notified about a slow connection, but does not respond in the time allowed. This policy and related policies in this folder together define the system's response when roaming user profiles are slow to load.Prompt user when slow link is detectedComputer Configuration\Administrative Templates\System\LogonNotifies users when their roaming profiles are slow to load, letting a user decide whether to use a local copy or to wait for the roaming user profile. If you disable this policy or do not configure it, when a roaming user profile is slow to load, the system does not notify the user. It loads the local copy of the profile. If you have enabled the Wait for remote user profile policy, the system loads the remote copy without prompting the user. PolicyLocation in Group Policy Snap-inDescriptionDo not detect slow network connectionsComputer Configuration\Administrative Templates\System\LogonDisables the slow link detection feature. Slow link detection measures the speed of the connection between a user's computer and the remote server that stores the roaming user profile. When the system detects a slow link, the related policies in this folder tell the system how to respond. If this policy is enabled, the system does not detect slow connections or recognize any connections as being slow. As a result, the system does not respond to slow connections to user profiles and ignores the policies that tell the system how to respond to a slow connection. If this policy is disabled or not configured, slow link detection is enabled; the system measures the speed of the connection between the user's computer and profile server. If the connection is slow (as defined by the Slow network connection timeout for user profiles policy), the system applies the other policies set in this folder to determine how to proceed. By default, when the connection is slow, the system loads the local copy of the user profile. PolicyLocation in Group Policy Snap-inDescriptionWait for remote user profileComputer Configuration\Administrative Templates\System\LogonDirects the system to wait for the remote copy of the roaming user profile to load, even when loading is slow. The system waits for the remote copy when the user is notified about a slow connection, but does not respond in the time allowed. This policy and related policies in this folder together define the system's response when roaming user profiles are slow to load. If this policy is disabled or not configured, then when a remote profile is slow to load, the system loads the local copy of the roaming user profile. The local copy is also used when the user is prompted (as set in the Prompt user when slow link is detected policy), but does not respond in the time allowed (set in the Timeout for dialog boxes policy).Timeout for dialog boxesComputer Configuration\Administrative Templates\System\LogonDetermines how long the system waits for a user response before it uses a default value. The default value is used when the user does not respond to messages explaining that any of the following events has occurred: The system detects a slow connection between users' computers and the server that stores the users' roaming user profiles. The system cannot access users' server-based profiles when users log on or off. Users' local profiles are newer than their server-based profiles. To use this policy to override the system's default value of 30 seconds, type a decimal number between 0 and 600 for the length of the interval.Configuring a Roaming User Profile You can configure a roaming profile by using the following procedure. To configure a roaming profile for users: Create a folder on the server where user profiles will be stored. This will be the top-level folder that contains all the individual user profiles. Configure the folder as a shared folder, and give all users Full Control permissions. Open the Active Directory Users and Computers snap-in and navigate to the individuals User object. Right-click the user's name and click Properties on the shortcut menu. Click the Profile tab. For the Profile Path, type the path to the network share where the user profile is to be stored. For example, for a user whose network name is JDoe, the following path, \\NetworkShare\Profiles\%username%, would create a directory called JDoe in the Profiles share on the server used to store user profiles. You can also populate the profile path by using an Active Directory Scripting Interface (ADSI) script. ADSI provides a single set of interfaces for managing network resources. Administrators can combine ADSI with Visual Basic Scripting Edition (VbScript) or JSCript scripts to manage resources in the directory service such as users, services, and so on. To learn about ADSI and ADSI scripts, see  HYPERLINK "http://msdn.microsoft.com/downloads/sdks/platform/platform.asp" the Microsoft Platform SDK. Best Practices for User Profiles To get the best experience possible from roaming user profiles, it is important that you read all the documentation and plan your implementation thoroughly. This section presents best practices for using roaming user profiles. If Users Roam Between Windows NT 4.0 Clients and Windows 2000 Clients, Set the Profile Path During Install on Windows 2000. Differences in the default profile path may cause problems for users roaming between Windows NT 4.0-based clients and Windows 2000-based clients. To minimize the chance of problems, make sure the path to the profile is the same on both clients. Redirect the Location of the My Documents Folder Outside of the Users Roaming Profile. To decrease initial logon time to a new computer, it is recommended that you redirect the location of the My Documents folder outside of the users roaming profile. By far, the best way to do this is with Folder Redirection. If you dont have Active Directory enabled, you can do this with a logon script or instruct the user to do so manually. Do not use Encrypted File System (EFS) with Roaming User Profiles, Offline Folders, or the File Replication Service (FRS). The Encrypted File System is not compatible with Roaming User Profiles, Offline Folders, or FRS. If you enable EFS on profile folders or files, the users profile will not roam. Dont Set Disk Quotas Too Low for Users with Roaming Profiles. If a users disk quotas are set too low, roaming profile synchronization may fail. Make sure enough disk space is allocated to allow the system to create a temporary duplicate copy of a users profile. The temporary profile is created in the users context as part of the synchronization process, so it debits his or her quota. Dont use Offline Folders on Roaming Profile Shares. Make sure that you turn off Offline Folders for shares where roaming user profiles are stored. If you do not turn off Offline Folders for a users profile, you may experience synchronization problems as both Offline Folders and roaming profiles try to synchronize the files in a users profile. Note: This does not affect using Offline Folders with redirected folders such as My Documents. If Storing Roaming Profiles on the Same Server as redirected folders that have caching enabled, Ensure that Offline Folders are Set to Synchronize at Logon and Logoff. When a share is unavailable, Offline Folders considers the whole server to be unavailable until the offline cache is manually synchronized. Roaming profiles are not synchronized with the server while Offline Folders considers the server to be unavailable. If you are using Offline Folders in conjunction with Folder Redirection and roaming user profiles, for the best experience you should ensure that you leave the default setting of synchronizing Offline Files at logoff enabled. Windows 2000 Roaming Profiles Require Full Control Share Permissions on the Profile Share. If you are using Windows 2000 Professional in an environment where you previously used Windows NT 4.0 roaming profiles, it is important to ensure that users are given Full Control share permissions for the shared folder on the server containing the user profiles. You can still restrict access to the share by using NTFS discretionary access control lists (DACLs). Not having the share permissions set to Full Control results in Windows 2000 profiles not synchronizing. This problem occurs because Change permission does not allow WRITE_DAC access, so the system can't copy DACLs. Windows 2000 roaming profiles copy file and folder DACLs, whereas Windows NT 4.0 profiles do not. Folder Redirection Overview Folder redirection is a feature of Windows 2000 that allows users and administrators to redirect the path of a folder to a new location. The new location can be a folder on the local computer or a directory on a network share. Users have the ability to work with documents on a server as if the documents were based on the local drive. For example, you can redirect the My Documents folder, which is usually stored on the computer's local hard disk, to a network location. The documents in the folder are available to the user from any computer on the network. The My Documents folder is the location on the Windows2000 desktop where the user can save documents and graphic files. Previously, administrators who wanted to redirect folders to the network had to use logon scripts to change registry values. In Windows 2000, the same task can be accomplished by using Group Policy. Advantages of Using Folder Redirection Folder redirection provides a number of advantages. Some of the following benefits relate to redirecting any folder, but redirecting My Documents can be particularly advantageous. Even if a user logs on to various computers on the network, the users documents are always available. The system administrator can use Group Policy to set disk quotas, limiting the amount of space taken up by users' special folders. Data specific to a user can be redirected to a different hard disk on the user's local computer from the hard disk holding the operating system files. This protects the user's data if the operating system needs to be reinstalled. Data stored on a shared network server can be backed up as part of routine system administration. This is safer and it requires no action on the part of the user. You can also combine Folder Redirection and roaming user profiles to decrease logon and logoff times for roaming and mobile users. Besides the improved availability and backup benefits of having the data on the network, users also have performance gains with low-speed network connections and subsequent logon sessions. Because only some of their documents are copied, performance is improved when the users profiles are copied from the server. Not all of the data in the user profile is transferred to the desktop each time the user logs on only the data that user requires. When you combine the use of Folder Redirection and roaming user profiles, you can provide fast computer replacement. If a user's computer needs to be replaced, the data that a user requires can quickly be re-established on a replacement computer. By using Folder Redirection to redirect the My Documents and Application Data folders, in conjunction with roaming user profiles and Group Policy-based deployment of applications, an organization can move the key user state to a network location. This means the users documents, settings, and applications follow them, regardless of which Windows 2000 computer the user logs on to. For increased availability, Offline File technology gives users access to My Documents even when they are not connected to the network. For more information, see the  HYPERLINK \l "_Complimentary_Technologies" Complementary Technologies section later in this paper. This is particularly useful for those who use laptop computers. Folders that Can Be Redirected Application Data, My Documents, My Pictures, Desktop, and Start Menu are the five folders that can be redirected. These were identified as the key folders that an organization would need to redirect to preserve important user data and settings. There are several advantages to redirecting each of these folders. The usefulness of each will vary according to your organizations needs. My Documents. The place in the shell for users to save their documents and pictures. Common dialog boxes in Windows 2000 point to the My Documents folder by default, so there is a greater tendency for a user to save files there. Data stored on a shared network server can be backed up as part of routine system administration, and is safer because it requires no action on the part of the user. My Pictures. The new default location for pictures and images in Windows 2000. It is recommended that you configure My Pictures to follow the My Documents folder. Application Data. Often applications place large data, such as dictionaries, in the Application Data portion of the user's profile, which roams with the user. To improve performance, Application Data was added to the list of folders that can be redirected. This means that users can still have access to Application Data (such as the custom dictionary), but without the need to download the (possibly large) files at every logon. Desktop. Some organizations want to configure computers to use a common look and feel. By redirecting the desktop for a group of users, you can ensure that all users share the same desktop, with the same desktop items. Start Menu. For compatibility with Windows NT 4.0, Windows 2000 allows you to use Folder Redirection to redirect the Start menu folder. You do this by having all users point to the same read-only information. As a best practice for Windows 2000based computers, do not use Folder Redirection to redirect the Start menu folder, use Group Policy to control what appears on the Start menu. Default Folder Locations The default locations for special folders that have not been redirected depend on the operating system that was in place previously, as listed in Table 4 below. Table 4. Operating system Location of special foldersWindows 2000 clean installation (no previous operating system)%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and Settings Windows 2000 upgrade of Windows NT 4.0%SYSTEMROOT%\Profiles; for example, C:\WinNT\ProfilesWindows 2000 upgrade of Windows NT 3.51%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and SettingsWindows 2000 upgrade of Windows 95 or Windows 98%SYSTEMDRIVE%\Documents and Settings; for example, C:\Documents and Settings Configuring Folder Redirection Administrators manage Folder Redirection settings by using the Group Policy snap-in. To configure Folder Redirection: To start the Group Policy snap-in from the Active Directory Users and Computers snap-in, click Start, point to Programs, click Administrative Tools, and then click Active Directory Users and Computers. In the MMC console tree, right-click the domain or the OU for which to access Group Policy, click Properties, and click Group Policy. To create a new Group Policy object (GPO), right-click the domain or OU you want to associate with the GPO, select Properties from the context menu, and then in the domain or OU containers Properties page, click the Group Policy tab. Click New, and type the name to use for the GPO. For example, type Redirect MyDocuments GPO. Click Edit to open the Group Policy snap-in and edit the new GPO. In the Group Policy console, expand the User Configuration, Windows Settings, and Folder Redirection nodes. Icons for the five personal folders that can be redirected will be displayed. To redirect any of these folders, right-click the folder name, click Properties, and then select one of the following options from the Setting drop-down box: Basic - Redirect everyone's folder to the same network share point. All folders affected by this Group Policy object will be stored on the same network share. Advanced - Redirect personal folders based on the user's membership in a Windows 2000 security group. Folders are redirected to different network shares based on security group membership. For example, folders belonging to users in the Accounting group can be redirected to the Finance server, while folders belonging to users in the Sales group are redirected to the Marketing server. In the Target folder location text box, type the name of the shared network folder to use, or click Browse to locate it. In the following example, the environment variable %username% is used; this allows you to use a single policy for multiple users, and have Folder Redirection create a folder for each user based on their username. For example, type \\FolderServer\MyDocumentsFolders\%username%. In the folders Properties dialog box, select the Settings tab, configure the options you want to use, and then click Finish to complete the Folder Redirection. The available options for settings are: Grant the user exclusive rights to My Documents. If selected, sets the NTFS security descriptor for the %username% folder to Full Control for the user and local system only; this means that administrators and other users do not have access rights to the folder. This option is enabled by default. Move the contents of My Documents to the new location. Moves any document the user has in the local My Documents folder to the server share. This option is enabled by default. Leave the folder in the new location when policy is removed. Specifies that files remain in the new location when the Group Policy object no longer applies. This option is enabled by default. Redirect the folder back to the local user profile location when policy is removed. If enabled, specifies that the folder be copied back to the local profile location if the Group Policy object no longer applies. The My Documents Properties page provides two additional options for the My Pictures folder: Make My Pictures a subfolder of My Documents. If selected, when the My Documents folder is redirected, My Pictures remains a subfolder of My Documents. By default, My Pictures automatically follows the My Documents folder. Do not specify administrative policy for My Pictures. If selected, Group Policy does not control the location of My Pictures; this is determined by the user profile. An important point to note is that you should not pre-create the directory defined by username. Folder Redirection will handle setting the appropriate ACLs on the folder. If you choose to pre-create folders for each user, be sure to set the permissions correctly (see the permissions tables in the  HYPERLINK \l "_Best_Practices_for" Best Practices section later in this paper). For more information on using the Group Policy snap-in and the Folder Redirection extension, refer to the  HYPERLINK "http://windows.microsoft.com/windows2000/en/server/help/" Windows 2000 Server online Help, the HYPERLINK "http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp"Step-by-step Guide to Understanding the Group Policy Feature Set, and the  HYPERLINK "http://www.microsoft.com/WINDOWS2000/library/planning/management/userdata.asp" Step-by-step Guide to User Data and User Settings, all of which are available on the  HYPERLINK "http://www.microsoft.com/windows2000/default.asp" Windows 2000 Web site. Using Logon Scripts to Redirect Folders Although using Group Policy to redirect users folders is the recommended method, there are alternate ways to achieve similar results. You can use logon scripts to set the values of the User Shell Folders key in the registry, which will give you basic functionality similar to Folder Redirection. Alternatively, you could use Windows NT 4.0 system policies to set the appropriate values. However if you choose to do this, you loose the advantages of using Group Policy to set folder paths, such as automatic moving of files when the path changes, and the registry settings will persist. Complementary Technologies This section highlights Windows 2000 technologies that complement the Folder Redirection feature. Offline Files Offline Files is a new feature of Windows 2000 that complements Folder Redirection. Offline Files let users disconnect from the network and work as if they were still connected. When the computer is offline, the files and folders appear in the same directory as they did onlineas if they still resided in the same location on the network. This allows the user to edit files when they are disconnected. The next time they connect to the network, the offline changes are synchronized with the network share. By using Offline Files, users can continue to work with a copy of network files even when they are not connected to a network. If your organization has mobile users with portable computers, Offline Files gives them access to their files when they are not connected to the network, and ensures that they are always working with the current version of network files. By using a cached version of the files, users can open and update files even when they are not connected to the network. Offline Files stores the data in the computer's cache to make network files available offline. The cache is a portion of disk space that a computer accesses when it is not connected to the network. The view of shared network items that you have made available offline remains as it is when connected, even if users lose a connection to the network or they remove a portable computer from the docking station. Users can continue to work with the Offline Files as they normally do when online. Users have the same access permissions to those files and folders as when they are connected to the network. When users dock a portable computer and the network connection is restored, any changes they made while working offline are updated to the network. If two users on the network make changes to the same file, they can save their version of the file to the network, or keep the other user's version, or save both. Shared files or folders on a Microsoft Windows 2000 network can be available offline. You can also make files available for offline use from any computer that is sharing files using server message blockbased file and printer sharing, including Windows 95, Windows 98, and Windows NT 4.0. Note: The Offline Files feature is not available on Novell NetWare networks. When configuring a shared folder, you have the option of choosing whether all the files in the folder are automatically available offline, or whether a user must explicitly mark a file to be available offline. Offline Files is a completely stand-alone technology, which means that you don't need to pair it with Folder Redirection and set up and configure network shares, but it works well if you do pair the two technologies. For example, if a shortcut to a file is available offline, that file is made available offline, but if a shortcut to a folder is available offline, the contents of that folder are not available offline. If you pair the two technologies, Offline Files and Folder Redirection, both the shortcut and the folder are available offline. By using the manual caching for documents, users manually specify any files that they want available when they are working offline. Automatic caching for documents is recommended for folders that contain user documents. Opened files are automatically downloaded and made available when users work offline. Older copies of the files are automatically deleted to make room for newer and more recently accessed files. The automatic caching of programs is used for folders with read-only data or run-from-the-network applications. To ensure proper file sharing, the server version of the file is always opened. Synchronization Manager When using Offline Files and folders, users can synchronize all network resources by using the Synchronization Manager. The Synchronization Manager can be set to automatically synchronize some or all resources. For example, users can set certain files and folders to be synchronized every time they log on or off the network. The Synchronization Manager quickly scans the system for any changes, and if it detects changes, the resources are automatically updated. Only resources that have changed are updatedvastly speeding up the synchronization process. Best Practices for Folder Redirection To get the best results from using Folder Redirection, it is important that you read the Windows 2000 Server Group Policy documentation and plan your implementation thoroughly, particularly with respect to Group Policy. To learn more about Group Policy and Folder Redirection, see the HYPERLINK "http://windows.microsoft.com/windows2000/en/server/help/"Windows 2000 Server Online Help, the  HYPERLINK "http://www.microsoft.com/windows2000/library/resources/reskit/samplechapters/dsec/dsec_pol_zbgy.asp" Group Policy chapter of the MicrosoftWindows2000 Server Resource Kit Distributed Systems Guide, the HYPERLINK "http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp"Step-by-step Guide to Understanding the Group Policy Feature Set, and the  HYPERLINK "http://www.microsoft.com/WINDOWS2000/library/planning/management/userdata.asp" Step-by-step Guide to User Data and User Settings, all of which are available on the  HYPERLINK "http://www.microsoft.com/windows2000/default.asp" Windows 2000 Web site. To understand Group Policy requires that you also learn about Active Directory; for more information, refer to the  HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/default.asp" Active Directory services white papers and the  HYPERLINK "http://windows.microsoft.com/windows2000/en/server/help/" Windows 2000 Server Online Help. This section presents best practices for Folder Redirection. Let the System Create Folders for Each User To ensure that Folder Redirection works optimally, create only the root share on the server, and let the system create the folders for each user. If you must create folders for the users, ensure that you have the correct permissions set. Permissions Required for Root Folder and Redirected Folders The tables in this section outline the permissions required to create the root folder and to redirect users folders. Table 5 below lists the NTFS permissions required for creating the root folder. Table 5. User AccountFolder Redirection permission defaultsMinimum permissions requiredCreator OwnerFull Control. Apply to this folder, subfolders and files. Full Control. Apply to this folder, subfolders and files.Local AdministratorFull Control. Apply to this folder, subfolders and files. Full Control. Apply to this folder, subfolders and files.EveryoneFull Control. Apply to this folder, subfolders and files.List Folder/Read data, Create Files/Write Data, Create Folders/Append Data. Apply to this folder only.Local SystemFull Control. Apply to this folder, subfolders and files.Full Control. Apply to this folder, subfolders and files. Table 6 below lists the share level (Server Message Block or SMB) permissions required for the root folder. Table 6. User AccountFolder Redirection permission defaultsMinimum permissions requiredEveryoneFull Control. Use security group that matches the users who will need to put data on share. Table 7 below lists the NTFS permissions required to manage users redirected folders. Table 7. User AccountFolder Redirection DefaultsMinimum permissions required%username%Full Control, owner of folder.Full Control, owner of folder.Local SystemFull Control.Full Control.EveryoneTraverse Folder, Read Attributes, Read Extended Attributes and Read Permissions.Everyone - no permissions. Considerations for Group Policy Removal It is important to consider the behavior of your Folder Redirection policy settings when Group Policy is removed. You specify policy removal options in the selected folders Properties page, shown in Figure 2 below. This is accessed under the User Configuration\Windows Settings\Folder Redirection node of the Group Policy snap-in by right-clicking a folder, and clicking Properties. See  HYPERLINK \l "_Configuring_Folder_Redirection" Configuring Folder Redirection. Figure 2. Specify policy removal in a folder Properties page Table 8 below summarizes what happens to Redirected Folders and their contents when the Group Policy object no longer applies. Table 8. Folder Properties page settings  When policy is removed:State of the Move the contents of special folder to the new location optionSetting selected for the Policy Removal optionEnabledRedirect the folder back to the user profile location when policy is removedThe special folder returns to its user profile location. The folder contents are copied back to the user profile location. The contents are not deleted from the redirected location. The user can continue to access the contents, but only on the local computer.DisabledRedirect the folder back to the user profile location when policy is removedThe special folder returns to its user profile location. Note: In this case, the folder contents are not copied or moved to the user profile location. As a result, the user can no longer see the contents.Either Enabled or DisabledLeave the folder in the new location when policy is removedThe special folder remains at its redirected location. The contents remain at the redirected location. The user continues to have access to the contents at the redirected folder. Use Offline Folder Settings on a Server Share Where the Users Data is Stored This is especially useful for users with laptops. In particular, redirected folders of any type should be coupled with Offline Files. Table 9 below details the recommended configuration to use for Offline Files. Table 9. Redirected FolderRecommended Offline Folder SettingsMy DocumentsAuto-caching for documents or manual caching for documents (if you want users to have to manually make files and folders available offline).My PicturesAuto-caching for documents or manual caching for documents (if you want users to have to manually make files and folders available offline).Application DataAuto-caching for programs.DesktopAuto-caching for programs if the desktop is read only. Incorporate %Username% into Fully Qualified Universal Naming Convention (UNC) Paths By using the %username% environment variable, you allow the operating system to easily create folders for users based on the username. For example, \\server\share\%username%\My Documents. Have My Pictures Follow My Documents It is recommended that you configure the My Pictures folder to follow the My Documents folder, unless you have a compelling reason not to, such as file share scalability. In General, Accept the Default Settings for Folder Redirection If you are storing roaming profiles on the same server as Offline Files is enabled, Redirected Folders ensure that Offline Files are set to synchronize at logon and logoff. When a share is unavailable, Offline Files considers the whole server to be unavailable until the offline cache is manually synchronized. Roaming profiles will not be synchronized with the server while Offline Folders considers the server to be unavailable. If you are using Offline Files in conjunction with Folder Redirection and roaming user profiles, for the best performance you should ensure that you leave the default setting of synchronizing Offline Files at logoff enabled. Common Scenarios and Examples This section presents sample scenarios that illustrate some of the practical uses of IntelliMirrors user data and user data management features. The scenarios present a snapshot of a users computer in its various uses and stages throughout a typical lifecycle. Each of the scenarios fits into an entire picture or can be seen as a separate event and shows how IntelliMirror benefits the entire organization by reducing the time and effort associated with maintaining the computing environment. The following scenarios are included:  HYPERLINK \l "_The_New_Hire" The New Hire  HYPERLINK \l "_The_Laptop_User" The Laptop User  HYPERLINK \l "_Computer_Replacement" Computer Replacement  HYPERLINK \l "_A_Shared_Computer" A Shared Computer Environment The New Hire One of the most critical and time consuming IT tasks is setting up the new hire with a computer. In an organization that is using IntelliMirror, the new hire logs on to a new computer and finds documents and shortcuts already on the desktop. There are shortcuts to common files, URLs and folders that are useful to all employees (for example, the employee handbook, a shortcut to the departmental shared documents store, and a shortcut to the users departmental guidelines and procedures). Desktop options, application configurations, internet settings, and so on, are all configured to the corporate standard, ensuring that if the user needs to call the help desk, the support staff knows the configuration the user started with. In this example, the user gets a pre-configured user profile that was set up for all new users, and was configured before the new hire logged on to the network. The administrator configured a computer to look and behave according to the corporate standard, and then using the User Profile utility built into the System Control Panel application, copied the user profile to a Default User folder on the domain controllers Netlogon share. When the new hire logged onto the network for the first time, Windows 2000 copied this default profile to the local computer and used this profile as the basis for the new hires profile. In addition to configuring the default profile the user received, the administrator also used Group Policy to redirect the users My Documents folder to a network location, so that the users documents are safely stored on a network server and can be backed up regularly. The Laptop User A laptop user working at the office creates several documents and saves them to his or her My Documents folder. After saving documents, the user logs off, unplugs the laptop computer from the network and takes it home. While at home and off the network, the user continues to edit the documents saved earlier in My Documents. The user returns to the office and logs on to the network. Since the user has done some offline work, a dialog box appears advising the user that data in My Documents has changed and is being synchronized with the network copy. In this scenario, the users My documents folder has been redirected to a network server, the documents are transparently saved to the network location and also saved in the local computers cache (because the network folder is setup to be available offline), so that they are available when the computer is disconnected from the network. The whole process can be transparent to the user; the experience is no different than saving documents to the local hard disk. As soon as the user reconnects to the network, IntelliMirror attempts to reconnect to the network location of the redirected folders. When IntelliMirror reconnects, it determines if there are differences in the data between the local copy of the folder and the network copy. In this scenario, the user has made modifications to a document on the local computer. IntelliMirror identifies this change and prompts the user to update the version stored on the network. Computer Replacement The computer that the user is working on suddenly stops working with a complete hardware failure. The user calls the support line, and about 20 minutes later a new computer, loaded only with the Windows 2000 Professional operating system arrives for the user. Without waiting for technical assistance, the user plugs in the new computer, connects it to the network, and boots it. The computer allows the user to log on to the corporate network, and the user finds that the desktop has the same appearance as the original computer that it replaced. It has the same color scheme, the users preferred background picture is on the screensaver, and all the application icons, shortcuts, and favorites are present. More importantly, all the users data files have been restored. In a disaster recovery scenario, IntelliMirror assists in getting the users computer replaced and running quickly and with the minimum of support. In this example, the user was configured to use roaming user profiles, so that a copy of the users working environment was safely stored on a network server. When the new computer arrived, the user was able to log on and the server copy of the users profile was downloaded to the new computer. An administrator could also have used Folder Redirection to redirect the users key folders such as My Documents and Application Data, to ensure that the users documents were safely stored on the server. A Shared Computer Environment In this scenario, a user works in a department where the computer he or she uses may change from day to day - a call center or IT support environment, for example. The user is working on an important document late one night when the shift ends. The user saves the document and logs off the computer. When the user returns to work the next day, he or she logs onto the first available computer a different computer from the one used the previous night. The user logs onto the network, and sees that the desktop has the same look and feel as the original computer. The user opens the My Documents folder on the desktop and finds the document exactly where he or she saved it and continues the work started the previous night. In this example, the user was configured to use roaming user profiles, so that a copy of the users working environment was stored on a network server. When the user logged onto the computer, the users existing preferences, shortcuts and documents were copied to the local computer, so that the user could continue working as if using the original computer. A variation on this scenario is using roaming profiles in conjunction with Folder Redirection. Users can have the same work environment, and access to the same documents on any computer. Changes made on one computer are synchronized with the other computer the next time the user logs on. For More Information For the latest information on Windows 2000 Server, change and configuration management, and IntelliMirror, see the  HYPERLINK "http://www.microsoft.com/windows2000/guide/server/overview/default.asp" Windows 2000 Server Web site. Management and Overview Papers The following table lists a series of papers that introduce the Microsoft Windows management services and change and configuration management. These papers are intended for managers and technical decision makers who need to understand the business requirements for, and the benefits of, management features, as well as the Microsoft management architecture, tools, and solutions. We recommend that you read these in the order listed in Table 10 below. Table 10. TitleContentPoint your browser to:Introduction to Windows Management ServicesAn overview of the management roles and disciplines, as well as the architecture for management solutions that will be available, either as part of the operating system or as an add-on. HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/manageintro.asp" http://www.microsoft.com/windows2000/library/howitworks/management/manageintro.asp.Windows 2000 Desktop Management OverviewAn overview of change and configuration management and an introduction to how Microsoft products, such as Windows 2000 IntelliMirror"!, Remote OS Installation and Systems Management Server address this management discipline. HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/ccmintro.asp" http://www.microsoft.com/windows2000/library/howitworks/management/ccmintro.asp.Introduction to IntelliMirrorAn overview of the features of Windows 2000 IntelliMirror and scenarios for how organizations can benefit from IntelliMirror. HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/intellimirror.asp" http://www.microsoft.com/windows2000/library/howitworks/management/intellimirror.asp.Remote Operating System Installation OverviewAn overview of the features of Remote Operating System Installation and scenarios illustrating how organizations can benefit from IntelliMirror. HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/remoteover.asp" http://www.microsoft.com/windows2000/library/howitworks/management/remoteover.asp.Systems Management Server: Executive OverviewAn overview of the features of Systems Management Server, and discussion of its benefits. HYPERLINK "http://www.microsoft.com/smsmgmt/exec/default.asp" http://www.microsoft.com/smsmgmt/exec/default.asp and  HYPERLINK "http://www.microsoft.com/smsmgmt/default.asp" http://www.microsoft.com/smsmgmt/default.asp.  Technical Papers Table 11 below lists additional technical papers that are or will be available for administrators and Information Technology (IT) managers who are interested in understanding the details of Windows management services features and technologies. Table 11. More information on Will be available in this web site:Active Directory HYPERLINK "http://www.microsoft.com/windows2000/library/technologies/activedirectory/default.asp" http://www.microsoft.com/windows2000/library/technologies/activedirectory/default.asp.Step-by-Step Guide to Understanding the Group Policy Feature Set HYPERLINK "http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp" http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp.Using Group Policy Scenarios HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/grouppolicy.asp" http://www.microsoft.com/windows2000/library/howitworks/management/grouppolicy.asp.Microsoft Windows Installer Service HYPERLINK "http://www.microsoft.com/windows2000/library/howitworks/management/installer.asp" http://www.microsoft.com/windows2000/library/howitworks/management/installer.asp.Software Installation and Maintenance HYPERLINK "http://www.microsoft.com/windows2000/library/operations/management/siamwp.asp" http://www.microsoft.com/windows2000/library/operations/management/siamwp.aspRemote OS Installation Service HYPERLINK "http://www.microsoft.com/windows2000/library/planning/management/remoteos.asp" http://www.microsoft.com/windows2000/library/planning/management/remoteos.asp.User Data and User SettingsHYPERLINK "http://www.microsoft.com/windows2000/library/planning/management/userdata.asp"http://www.microsoft.com/windows2000/library/planning/management/userdata.asp.Windows Management Instrumentation (WMI)HYPERLINK "http://www.microsoft.com/windows2000/library/technologies/management/"http://www.microsoft.com/windows2000/library/technologies/management.Implementing Profiles and Policies for Windows NT 4.0 HYPERLINK "http://www.microsoft.com/NTServer/management/deployment/planguide/prof_policies.asp" http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp.  To access the User Profile utility, click Start, point to Settings, select Control Panel, select System, and then select the User Profiles tab in the System Properties dialog box.   Windows2000 White Paper  PAGE 4 Windows2000 Server White Paper  PAGE 34  EMBED Word.Picture.8  ly   J K W X Y s t u v w x      ! " * + E F G H I J jqUjUjwUCJOJQJaJjUj}U5CJOJQJaJjUaJ mHnHsH mH sH h jUjUmHnHu=8DMPb    x " 0/!0$!xp]p4'#.()*!*" J `  L u 8 #cP(V/01       @ A [ \ ] ^ _ `       + , F G H J K L T U o p q s t u jYUjUj_UjUjeUjUjkUCJOJQJaJjU jUC    2 3 4 6 7 8 _ ` z { | ~  !"#BC]^_abcjA Uj UjG UjUjMU5CJOJQJaJjUaJjSUCJOJQJaJ jUjU@/0JKLNOPvw"#$&'(55CJOJQJaJj)UaJj Uj/ Uj Uj5 Uj Uj; UCJOJQJaJ jUj U@56PQRTUVefg,-.012QRlmnpqrL x!!5\hjUjU5CJOJQJaJjUaJjUjUj#UPJCJOJQJaJjU jU@2rL 7F x!CEƀE5`4/0x!c"#$$j%ywuw4CEƀE CEƀE!c"z"##+0,0D0F00000000121Y1Z11111%2'2]5^55 6 666666666 7&7475777Z7e7777788+8,8F8f8g8s8888889(9/9091929[9d9e9f9g99999::,:5:::::dBeB5] 56\]6]NH 56\6 jUPJ5\Vj%}'c)z)y-/00,0E0ywuuusmm,$If.4CEƀE CEƀE  E0F000001121Z1111&2'2(2^228x4+$Ifk$$Ifl0  :033333333333333333364 lal2#353h3y6CEƀECEƀE CEƀE h33W4$5]55y642(CEƀECEƀECEƀE555666u2CEƀECEƀECEƀE46&777y-L hEƀE^CEƀECEƀE78,8gL hEƀE^L hEƀE^,8g88(9p$L hEƀE^CEƀEL hEƀE^(9[999y6CEƀECEƀECEƀE9:,:U::;y6444CEƀE"CEƀE!CEƀE ;?@@AA B BBB+BIBdB,$If.D5C$EƀDF4 dBeBvBBBBBBBBBBBnhhhhnhhhhnHh+$If$$Ifl\q6:f $8064 lal BBBBBBCCCC(CbCeChh@$$Ifl\q6:f $8064 lal+$If eChCiCvCCCCCCCCCChhDhL$$Ifl\q6:f $8064 lal+$If CCCCCCCCCCCCChhD$$Ifl\q6:f $8064 lal+$If CCCCD!D%D)D*D4DRDVDYDhh$$Ifl\q6:f $8064 lal+$If eBYDZDFFFFI]|]pa|aggOrar{rr\scsssuv6vsv`wgwwwxxRzzv||K~r~FG (̀34GLB^_Qitˌ7BMWyIJ0J jU jUCJOJPJQJ^JaJ56]PJOJQJ5\CJQYDZDzDEEnljh4$$Ifl\q6:f $8064 lalE.E%FFy6CEƀE%CEƀE$CEƀE#FHIbIy6CEƀE&CEƀEoCEƀEobIIIIJw4CEƀE)CEƀE(CEƀE'JJBK]KoKyw4CEƀE,CEƀE+CEƀE*oKMMNy6CEƀEoCEƀEoCEƀE-N4OpPPPyw4CEƀE0CEƀE/CEƀE.PIQQRy6CEƀE3CEƀE2CEƀE1RSSTT%WWFXoXEZ{ZqCEƀE54CEƀE4 {ZZH[[I]|]y6424CEƀE8CEƀE7CEƀE6|]]]^:^mF$ & FIEƀE.F$ & FIEƀE.54:^^^^_q*(4F$ & FIEƀE.F$ & FIEƀE.F$ & FIEƀE._`aaaamF$ & FEEƀE.F$ & FEEƀE.54ab4bRbXcq*(4F$ & FEEƀE.F$ & FEEƀE.F$ & FEEƀE.Xc-dVdef=jjjj+kkF$ & FGEƀE.F$ & FGEƀE.54 +kLkkkmq*(4F$ & FGEƀE.F$ & FGEƀE.F$ & FGEƀE.m+mnp qrsuvvmwvw}wwwC$If.4wwwwxxxxQzRzzz>|?||dvvv|8vvv|vvv|B$If$$IflF&P  06    4 lal ?|A|H|i|u|v|||J~tTnnnB$If$$IflF&P  06    4 lalC$IfJ~K~r~~Gnoqx~xxxx~vpppC$IfB$If$$IflF&P  06    4 lal ̀ }wwwB$If$$IflF&P  0    4 lal 5A~xxxC$If$$IflF,V  0    4 lalAB_s} wwwB$If$$IflF&P  0    4 lalstʈpDEh؋D zzztttzrpn4-$IfB$If$$IflF,V  0    4 lal ؋lŒ'q*F$ & FKEƀE.F$ & FKEƀE.F$ & FKEƀE.'oq*(4F$ & FKEƀE.F$ & FKEƀE.F$ & FKEƀE.>Jܜʝ֝'-HQlx/;#!#/4E̪JKLfg(erepK[İ԰CK)wxӴԴ!#IJ'(PJ0J jU6]5\ jUZא7,ݔY IƗMڛ5ݞkG4G3y6CEƀE;CEƀE:CEƀE9vūeuCEƀE=4CEƀE<Cy6CEƀE@CEƀE?CEƀE>]fxuoo,$IfC.Eƀ!DF4CEƀEAԴ"#J(uvw8x4+$Ifk$$Ifl0pp064 lal(tuv 7[fkp{Է9CO[иڸ%6BNQ!#39K*1BHlɽϽž&.jp:FeiJVW,-1Hv .9W`6]5\5\ CJPJ^JPJ\ ׷]Ho(F$ & FVEƀE.F$ & FVEƀE.F$ & FVEƀE.4Hq*F$ & FVEƀE.F$ & FVEƀE.F$ & FVEƀE.Beu2CEƀEoCEƀEoF$ & FVEƀE.eq.CEƀEoF$ & FVEƀE .F$ & FVEƀE.W-y6-  & F^CEƀE oCEƀE oCEƀEo`h9:_`aop@ABabhimno%&'FGMN#$)*+츳jU]0J CJ0J 6jUjUj#UjUjUj"U0J jU jU5\BiFpywwuwwusqwww4CEƀE oCEƀE o UnCM,$If.4/01bcST ?@C@AHI23abc45SUabop}%&5\ CJPJ^JCJ^JPJjU]0J ]jU] jU]]6j0U0J j#U jUFA{|I{{{({{{{{{{+$If~$$IflFp8  06    4 lal234{yy6C.Eƀ"DF4~$$IflFp8  06    4 lal+$Ifbcd{uuu{ssq.4+$If~$$IflFD8  06    4 lal,$If 5TUbp~{(uuu{uuu{uuu+$If~$$IflF8  06    4 lal,$If 7}}{}4~$$IflF8  06    4 lal&67I @GHaovxy+,fkQRyzoz&'jUCJ^JCJ 5PJ\CJOJQJ^JPJaJ5PJ\aJPJ6]5CJOJQJ\^J0J jU jU5\DHwxIl$$Ifl4066` 064 lal,$IfC.Eƀ#DFxyKtyyyyyy+$If$$Ifl4F_6_  06    4 lal,fR {{{{4{{{{{y4+$If~$$IflF_6_  06    4 lal X-6Hlmzlh+$Ifk$$Ifl0064 lal,$If.4d!F1t4+$Ifk$$Ifl0064 lalt(^w4CEƀEDCEƀECCEƀEB4'()KLM\]^_QbBNGHp |   ?K345HIMN |~^_j$Uj#Uj"Uj!UPJ5\ j0JUj !Uj U0J jU jUFPQb`2HP   UVkT4CEƀEETs7AGOfgM  ^v|pppvpB$If|$$IflFV ( 0    4 laC$If.4 ^^Izdz~$$IflFV ( 0    4 laB$If :;<YZ[]!^!!!!""]"^"""" # #-#.###### $ $i$j$k$$$$$A%B%C%%%%%&&&]&^&}&~&&j-Uj,Uj+Uj*Uj)Uj(Uj'Uj&U0J j%U jUC   !!'!K!|||zxvtnnC$If.45B$If|$$IflFV ( 0    4 la K!L!]!""]"##-### $$$$%%@XdP8B$Ifi$$Ifl0 4 04 la%%`&a&}&)'*'S'''%((((($4i$$Ifl0 4 04 laB$If&&&&'''S'T''''''%(&(((((((()))')0)=)F)L)b)o){))))))))))))))))))******"* j 2Uj;U< OJQJUV mHnHujUmHnHu5\ j0JUj1Uj 0U0J jUj.U7(())))))))))))))))))))***** @4  & F8^8`* *!*"*  & F8^8`$P/R / =!"#$%'P/R / =!"#$%0$P/R / =!p"8#$%. 00&PP/R / =!p"#;$%`!MرtD|h w`)]x=ohJriR$M$Qv8!6`EJ.W7H!*`oBʾ/G3ξ(Oݙ,YQًEe?)~>}4EW?oYyAGGUVѣߣrs'ޓz|EukYmyhQn'dWϲO~⋗_Ⱦ=+ɟN~q'o<:ywŏOdQguq]ʿo篊'zlYs{ɷ9BC ! aKeO\j}q`.smצJ2s狦M=|h]42`gy[`;12gϏ9udi3>sJngvN;22o.!=}Nsa'a.9b= Sas5v7ooaw#^}!LC0G~|T~EŜ~{\ *zȓoM0'<@S,0FuYgC`:Ĥs{!r%>G~ss=7J4?X9#?ȕ CC94\o9H3Y5zڽsr咪^4 >󹭳ϙVh&b9NXW1is^V`s079DB9s9 Po5KN.#?+1I9|9:? zi>8?s0~!#?ȕ |\rasOe0\` 6߼Z:ܲsʞX_Zjk-V3U`n>lsvPYTG`n ۔glYj쪉嬆OftCi愂 s]^o7^Mv#@]#Էnn9œu aJ_{_Ϲ {Jcs~.l9̥UcV4z+PN9DBu4H!w:XkM[_+gQ?kO4Q>x\߶fQwbNG˽9gw`ik8%zgaw;C> k)Մ7g +Wckƺ fx>S!Z !5g2$_{ e1qon.N_ ms݃wʿ0 31]#xs99ϑC3sh6sϡ$|n:9M#?9yP>7F~%y>7v~%s`nr>w~ϡ`"W99!?G)r ss]9KܘM3v=gq~~~~u֟9acNrh>gnjSmjS;oM좩k.//kNOOs\ױ5s \\ ܦ:SL6o( ;9ck39׽ez]zHq'?fus07\~`i`"W99 `u]~ΫiNT/Ժ%dLK">%mkoUFL[i.n~~\o9r%d.]+ [z1봆b.WuS냹|NdυCis}־\;xY:ڑ9:+`.ĩ?s!4QC07ܔ~ s&xܐ18kG5i 䚎tr M١.U|l ɜ\`B27L )*CM綽+a&ɜ9!'Xu][[`fd>u7:.|: w^ҭCFPRC#J!r%9|CϑC4:!''Lן! <_E$b^m]j- E+^v(\Ik\kPOLp(-{x9@X=yz4I~eXanϱ`\ "?`C瘨JݬCl̅?\W8y }.h9kmpG9kM\> sBM|qc|'?gsasSn0G~"W`!|\49D~ܨ9̰f֒?}ٙӴXegNoN̙6g8>Gsnc&|#?< ZN1,%?7t9 #?G~!r%̍(BF_RdN=RťZ՛L$O^160cߺ?;.*tZpZ[1)y]C\kiW)9#s~뷺Z#sZɟ±u zbn?%4sͻmMloBa]2,VOedP9xF<39s9s\ 9b̡>sM?sNlCVsԳh]-=(姡ș.M4-j}uc`.U]fz]3fN[i i~#sGa_>nr\p8&͜Um̈́90rec>LnX`RheK ٙSCJkPzcЎ9bQ\?*~>}4{+.츸xjn#ùS:ǥ$PNG  IHDRogAMA pHYsF IDATx1\Vwՙ}OHd"! !AFDF@3}^m?Z q>:}IH] ~e|r7_~$חS)AG jB w)HSJT s$̔8e]uHn&QPtM`3L.7vf}3l[}ܢ;,ݓ7J)s|D2IIIHJ"$X~iRJ)?1I ?4:?7ȤcDeӞcx9cffIQ.u*D5{+ r 7df7L5skV YJ.5rƇܰjܝsV2)")̏ iÌUb(;Hbsw~_Ԍ19g-+t05t%FIh ZsӃ[swL[s3 ݷyn.qn.qV)~=-.AD* JfQ\p VJ)04rSkw3y 攨$H:w@_KN-$9 ]7wAn9E?87wcw3k5-(l&ڇڀbFRh$!5CfPԊ LBw3OA+.$'\J)w}<)99#O{v:y*"ƌ%@%ڪ.:If.MҀu7sC!^BkDｙzws[q:$V޻ 0q'L R$X] 1@`fy RK /!S`H\$51+:Rʡ$1 8Ƕm=Ưd#^fN}3Rɘ,,t[5'q[b3ABofH74\L͛mzm}E55w V/qZdf&sFD #) JDN_ %F!C)AK=k )#3R3159gpP,[pY f.4$r`fh`[3\hu_2m3\ ޯ$̤$L3"Eej g0Ɉ%.̤0$3V\x_] + T):HbuF8eQe2iy8y>g2i9Հ5)͕K teVG$u;m{[wozZZsIq7w; v\)2FBIHQAZ}R򓸐ƅdDžP rlI }Ӊx&`ɵD6k0 i@w p3_:hfdܴJyۺhAkw{w3֚ۚTG7ZkZkfnqk*le}\!lm1MS N4cI4.p.k,#quaI̼_YJ)xix? >ߟ"|9ipהwufFf3f@N:vl-!̝DߍDsqMdMz3W[3鮋 ̕)4@$#Iw5#*'LhI BV\0%7$KIzS[3Tc)qM\յa&>=n`irx\> n]@\ kfɦ ;Z{tv0޷}[ښ .\qҙ4v_\ %V\nIZDf Xk=\qa=%v`cr}f%U]N2C)Qj %Έ1i|:癳j o$e%.TP($9̜L!H(%рs (C;HbA<{>Y_O{<4nR~HCyf1#3)Tbx)]J)后O_=wVbxj_(#$cf2)͐U9I] \J)GwOy>4b$G4TJ)tσNo|9/=xN rί}?y\{1iu1Rʑ$1N9G`8G$Jj${cuR h[>3tʗ{bq^]~BGlRJv$1<{1y)rO̹KL"$%hpRJ)cy".hBhfV":fZZ(C;8|?/Bsm??zD2k2K)2+݌m(Ϡٛ f_z#HiTdRʑ$1yfpOd0g7{cWq9g]6Æ?l#GIACT JKMRhBҠB4iJEA )!&`cŅ8u޻w9c=/1Իn~Zͻ{|̓L1B5l)&{sO.R:țQDDBpcBMMMf(sMVSdS.#g`8dԧVRՊ1>fW]c{H.͉ɘTqQRUUrrD2ݝTNIG W]USJJD"\r|-Oa`b w2q 5555ѢZ7Sv%HuvNbf"" *O]pifQOa &V,\]#!jjjjj޵ B8Pm)`W$=RWl߾=;)̬j(-xϝ̌cG:+ : 80juRMMMM Fb i/Tmw7K MT4fۺV(h?EPfVղ,˲l>fæM^}@L\u[ $Ma?ﶙ0sn "$QGK,3q,BA"|e ANHDq08jjj6Fbpd͓%D =r>"z=춯 8lqbMbvĸqFdHH@Yܝ`Q"mq~3DN6D 2`;f z{11RFa" BQHP0qGEzBBG0U555D1Lcbl5$svi$qMFb<j0{=F濳; N5?}q=тmZf3ol2tl5sq߸+gNpE3:r+qj O9ux[ /@n_,8eg/|qD ,•AF,G('z@UB>V4T 1@0HOŨ *+AHd.fjjL*,*.:(ឈv@=[(R˅Qϫ|k+m+mYڪe.Ӱm gh۰FB1Lo DK>~'y /U\\xeЃ xoc„ g67؝9~oPᚬPliZ~iҲT"Y,j^%R\ݼTM<ᰡ"cӘskkjjjF B"f@^oY]4~Vvz'/5i\' ;9kTy8Xt?YkW>⶿m7bf @By`j?7eOfip"'μ t[ #Ʌ(2쬪8%u^**p'SuJ sűBNSg#\j!ȾjjjjD1@,;m1<0\؇D\zV%='G:䙘yFj ϔ fWM2cw~;>Es{7a#h6/O8=`'OZpS/ ?gg_ƝæpSuwZ "'p`*]4`&!O1w45"*xp'E8aq)8WOC & LTK_=Hs^QwAUwQFAI$ƨTYda4V,QY5ntPKx([>%+" 3=}sv43$2_O{w}_.efH!r1"" MN"!#DCa ی0I1qC(b\Ya#3Dd~Wd5<:+6'h*$Zׇݧq+vܬAa V\\N' |Hs~=U2mIG&32~lP"t[ rdQVd>伛}~~a4i+KF3\>($!B3=1X;a͡H8beO:ϦW.]7Vv~E.bK3 N3\WM̠2d6d6ef?6?@ *}?(\kHl/ @Kon31x9NF Oߴ铼wEɩT*Hf(ǹq\N)30% (E20i@$ԧz")Ck$cL$1x1lnIC= jYh_6"ΚLkosH:87U}}Z[maOeգO_-7a`u##A[5f3"Q=uj1qEȟ`FI2@Ng";Twj7Mv"!@ $J&E@} ;[77F\xS3LPt]8Nj `̈| w=}aa_Υ״udt:m u$Kk;ڕ 4!ƈӑG##pl6kKQ-o1rٱ%t;av"%,:qeO8E Da h1#.\нϬL&3]%Tuk/B&=/{p\u[[i/^8!HZRL%}6?R9r護ӧz~ X[]SS?#|e㾰4@1C$h?o+**-':Ccء 1RJ1 "(rj3r4rP "E%.b_0W3nM X~Bp핚x8s8?og>"D!A)4=<1w ֈʽ"R)̙؍ IDATL*eQq_O?RV < >u/ oB%a7AA<" CߺoDZ~r<&:8J1*BAuoh >5E>.{e\3+(nM &q3 qyclUn XT a CL@19۵Mۻ=0j1ZrRG+aZR io Ґ;`Ñ='qts`G5,NBOrBXIE٠BC@DcoA AܡSTAnlIE팺IgR)ۈ2N/z?FP{t5Lft`cp7\h+Uƶ$|%Oy@D]~#Rp N:dF0")\Nn$m%ح`S)PQ6h_v9E}­:H_GefQ.(Z!ـ3xLq*==8%~IaFaa;Vf=z?豧{~/ܴujJ)ǍyD<:JQYMWq`=J&k?X_ϾMkѭEcS8S`hm"1 zypcqOHmmMDH.*1Prr6hEN%*}sEX=sϞ:9onn1FO<:bhe4V%< ic6 ./{NXv&uӦ?ݙy\^i_o'M &GqxL.SS1:LBqlۤp#0yo֜gJ4":cwL*GD5ܱcۮ=MM;f1677l6/P#۷w#8&Y. m"ynqJc\Q"jgygaK$rw)Q1D)EH HS"BۇDFV +JX 娏u )6Ϝ=uuӦOy(ԙI/.Zsfݸ7`ɪ5 `~QcъuӦn~``fE٠kg9aYF@ڝx6`'x&`Kr"cqc18*\rkZg)]~$C\fMd2N1LaÇVV 1_~χţn޽~ڴS;gQ9aQLî#yC"r-sDZ>NzbeֲP؄X#7N )6y91\?{^X`g߾yUk˗ {n_@X򍱣.²BL(,H!YcD3pPA`Vtݖw6hbXc"Gh֧\m'f\s4K ÇE?\x'+7z{a[d}Y"a!E&-X-"VO&0oJg"@1Dt ¸Bvk-j55wTy\WU4 V36s|xneUї0hͻ?ꒋ~cˎ;zӇ 7"L2XS%\U{Ӹ!5SDd"1e H(L-I"Z L+ (AD@o/]J`)-"L5n]"ٺ-I`/lP̠ЉŬ3} ?b2k"/ D!BA/E ƘBaas'ت r1;5M6j*?~޶zÏ=L&mšy)Tlmˊ6췿{=n㼗錿|۰.sF{eoD#Bk?"ⰡCmf2v h $&{V0`u )N×PWL'SqAgRJn*4}Ƭ~GSjkr^C/(޷uQ!h@a8vh>X4lkxmڼeזwWWW];[N~gu߹5YcI6Dn.ҕ?@]kՕZ}K /W@EŨA)ce2qFk4qb-uJbJ*NB$NI"`EPD{is_d.E5}ݽ-k}[`I-DwF112vގ! *ՒʻPܒ7ߕKd" 2|V#AU}spC}q5G>jqh}y_4O`Rv CuGK= j(GwDԩSg]t&uttDQYDZKɫ~ cF53zqcX ,]B1,_uaI׾yK%SuiJ0"79|m*LqSC9 2#A듔x@<R1QAU0L"﫪3cpIâ(qvռ}7xk^شｸ~WCm y#wc{؀f?{BFov>ai؀kwv9WLo&׺ )pѥv.܉'4v7 ?nlbh]"Pycq6^!x~j6 \p ^yg0+{ծ|`ջǍuesc$UYl3$寿Ü f& LJ4$鑍Ç%#T_H!Fv+ғT 2FJ@&:|gIr>BA @U!:}€د2M4\v4RO>Mb Y+/:?yp\T vn&Ge#K{Eex67o|ׯ+ 65oDfH5 F fMs&edȐϣ0Q`y(qz~0Qg(v;Ҷ{D݄z sRcm۾=0 6i 2P7\M9v"ؾɿSn㘚SomݱK\>UUǍ(̞$|ϫ*Xc@vƪ&ߪ1"Qc,tRU şb%I_lٲ*Hb7SR^8jZ4'+;ZGNb@!VW5maxQ[: {'}o]?|p^b nw%dݷ[LUtnd>|&Z_<|c<.SKgގ&ah8b @!w?ҏZo8q@P^g*!V#cGy3%js/gipD%W׬Ռ;zSOc1mƖA~u91͡\%HKZvejTFUmN6]cZjbyduR|4$X۪4$ص~k;O\ÝgZSQ' g+t7~Usyf| }觕"Uin<۪yKz`vu͐!ßcҀI< [>ٳ1NBN4[`瞶;;Nm 80a]p|!h[(L*?ɮ=g>rȑ#̀M1Q4 4>])=>ܫo6=,W-chzukՂ$6]g-ΘO+|]Fy|+C Ba 9xg_E&" G1ǟd555qT`]-5p䀠6Ðږ%P QEB!Iڌ?I׿fm3fܱOs]Yc":qzQ2Inj=9C;CwSucbWbDª:ƺﲒcynv2J~©]Du / { q  B`JJDZN=yRU++y%$H3S-2dȐ!Aa DAiP׭?! 0 1GQ~ekx`Uus&7qoqhZBkK$D"ݻDqm*ikk/7l3_ꗮ vޝ{eA;)tUI\exPbd,{dMJ KcɀacmXm1[%ipDd<'zwuٕ.]k%h*2d" 2|zﱣ IӅJ웜@.30ͷ7o= 8 eK[[[8ȄF3jޞQyB@WQ#6uށƎ?naI,}1>OhZS~-":㬳+jl]8 64|ȐUTZckaKL@G39W[%"RX) v?b !fb(:j5i^eIK 5 S*BbоUq;Yc ?|FSr98 :o?ȭ1apzYvH?ٱcǻ6Pۨ>^x5IP"6w[]N?/;':5IIA bFV5FMl&I@F!U[&=6RLn챘Y`" Jࢯj%q"(N"*eX02J K>y'lYPa%C c )6*b*ȕV肵&0I+13O2D4iIa۷j5n_?Ȫ=vHQ!iwpmf aJ6N+ZuctQmԴv 3Ţ~dwq% &Dwryo}?VLgxs={~|·#G_kpǥǏ?~Og;4eYW{@r [Qav\ Z|nsu-}-*P4De9yH[Dc@D`4*C aP+D (5hD(w3?IXQ@zDQVb22yTc?`oRCJ XiiZWc`~ڤ&*Q|,t.8Ds\t^pu_?=<֛ahq߸K7͜5kcǎܻ=;쁟ã{#"r rvx֌cAWW9̌" ׌ H(ZZ[#N"tXa>c%QCePw@ #P,,@h ZBu0h gAAՠ@c&\@D0ŰA$4LA/V Y4)iiA=w .ܽ$<_q_M(*8g+@ۅ IDAT Guv6@d#JtD ]tɓv 'Ŀ_o{#7o .?uIDI/Xx w"(ÁE2q_L U1" aA((hkfQ1 0TD8ma@$Ш$RC>?bh  'yT`DUX  @c :ICwv~}Ekaك+-c[oY /+/-}OwDvsqln̤S<94o]f5/̢BNJ,"EUD ;@Q O/?KFDd[4IT$*fHp=RTiQDiGVcܖMRF :;: {/Wd_"i'ޗ\r|?ۮʫ dk+7[W>mWho5>}FT:>!_n)VKxs"vQws%B#UkQ&|9ZhUWP YUEEXU@PDXHĝpѤ/s&CQ˦LLKՋ |a``?uڹSl6;un>}zq|zr߽nfޑǮ{oC=1zgn|խǏrWGXDB0)sg*O1^D|$U`Lܩ{-}>7x@Đ9"Y Ƃ~7Ͽ6GC4޼k(3nEoS׈5t6=3-hGT򓨺7o\}R-) jyEu]+ÉdYtz]؞Cl* } aꍒ"9 mƀG@% BB1쐬eJ b@HjZ#jT@ `0GDo| Y4"_HAuKim⩹2007YZ7m^FBĻjDrι6[Ej Wmضz/^_e;CM#>򘉡xwAU(3s] ]8KTs>,SN 'UOg_# ݹ,* )5 r XBtb1{w{TVU`E!4T !JZgҾ!52RvZ.]0']  6Ta{"MTpWxɧx򩤽(U{!Kùe#.-vu>xJˏ[(ocٽ5ݾsn{yikV,]b5vo20k~y zн'!QgTAAWU(T~z~͠Z**@ "U ˪UpPfOC(]CIr0_֐f=30 ] 7_/ N,44dp7͏uh=@Di "yϮX~+[#;~o/b&Pz]Qf<CoYU2xW (!E893F$D*LB|J &%ypE Y5^:%}2RK`NZӥxɧzz_Ʋlp&?۫Kxws8DE]:R<}qIIx;Z&BP=[gwiѺ'9}D_wáVQ 4J B cB5Ak/0PZ($EVeA fhE23!Ç膆L&frܸqZZZ4eϙ2+Y/gϞ^xaǎ=ݞ=I_;SΚܳ[܅Hđ%Edθ.VUO KG䝄NB'9D ðJǎ>t#G>tcG;r4?P +Fu,.dB7n0(ޕ6R:JQ8pyTqܺX>zcYf?jQUͪk"LxfSVL-[v٪tKf]K_$yIi;{Z<; e4D"lZMTιw~2ˣݕZ4dPfU<;>&AOy?O&0a:4d Dؠ3H(eGG; Z:^ǏI"0uK.IUf͚5KZxǏc~J'ץU=|XrMQ=&"r)AC^6dNG]9/X^kB0АPƤ1T-]]J*~ڍJ+W(FeFkm(11O_>9ZFT`Tc>_RwaA!(忧{}%# wYҭyǜ9m/_嗉4e>ta:|`L9_qyiovc_ol߶XxeJqD^)a.%j`B# 'd% X_X0䞑:H0D{p@|!"2 ,*,zedC?r *+Eoxݽy)dUwk>S]OÐ޾+'M~fA:ۙ˗\?wv҈Y4P#m)r-^tAKviٓՏu JQK6KPDZ4֚``d2Fdm!R h -IfǍ7a„ֱcr1cr\._;vر>1nܸfKLSSgK>>_uCi2[l6[ݼ$zV2:&Ak X#,C +(z׋!OXK2էJO][QQH/̧dHzSLY1(w$5dvQZK#ɐ5F(RGAFU)E@Z=1dBDCHHR fA( cgQD0D|=o4Ad)i<ߨ8F>}1?5 ZZZ&L{-G8\.wW6mٺ/1*{NCGaQNJRZǀYc3@ٌP@AYKA&dM*` , A&c'6DTPUͱLZzY#>e9O5^AbܵƜuE-)K9XNRUkSF=.)5N7:''".a>I]]8t,.a(Ήsyp}-tOWH4'; gs*}(ycC⺶H$֎"BKMk?X}IIm8ʡrI lJ;ܳZ3GܹoFE\if󭵾WUKG6WB+++ D.JQ8~ٿKcZ"> ]ȓŤ"ƤIוDԨɳxk30ZFdh*uV]]r ՘m DHu5(Lɾ=#_p ]cˣkz7L_=wy8{}OHmZ_M6ǎ6R'w~|_??yUFy/ g fH8ՐJ 4M>_`27r[#~뫬=w]|nj?AE.=w'O~ڙ1JϞ;/PP?׶Kobp䞻l=# İ2hT#?zjë`.*bbԎ/$DeivfCNzU;vvM0(DzzVׄ U31C~ (tPaqBP ̈Ea[+6]hɲߨ4)0=|/*i8~W˷l-':= |EtPz@I#Ӥ"'E D'$Y$怔qߏ>F@FĄӽi6P??'Bh4(1x5c9zDm_[rg*ƏΟ!A 󄠺TMXdGosiڡpoM .!i+1NS x /sWJ9`wxCFOo.{&f5h4*yC';/O-~t#2Wz\gL6+4  '3dY.@5HJEJ&̈ A}$DTaW6rBA&P 2IHDD($KJ4hW_^GmmYe['ObU/"w#MOS-h7=Sv,ޮ͡m:CwX0ѣMqo1PC-Tg~򫵪tj\!80srFP0131w~]V oIyCzy7߼_^y3ԗwh0"$&"UP~ۂB>ROAD&΄} Y鎵q/L Q@Eҿ Ǽd~3]p Ķ]髜W5fFF2/M'lZmY /C7gWrw? ϨVU}Zޤ4e1#(7:;ncۘN샬w(oQβl4ySC/go%#y` a .$ pwIE.zQL&W+E*"'XRSX'',~Tb 4"#"fVMEDR!"%)_ ^m5vTh^ U%z"`*)1DQHܓcZELR XJE"1d %LJH^ 3tםl[jzU6n].ގ"2;e.}>3f Eh/@ a 1#e!1QDC0R1d*6 lffJwk 1VWW/$/+/VH.LR_."^^9I1b~rQL&1Ƥ8j2KILǘyCЌ!2!! )a͊6\_<<} WحsLB;j<%M[6ZhBȲ#YLEH)Bz|>8FIr%&I$J bdK;h$"@uʹka -'dD"+ 0VM=&n(q:YII<9p=z^Ӆ7zw=)EpkBU5RYgˍ$n, " U%&5E1IJK 'WwKvX,d@x/~!!\He}cvߦ[/~:ܗWihܭ3t.[hx̣yY:8h.<t(~yTϳ,xr#:$U-B-&-Ru" t.L f2d"Db$" m%zi'}ޙӅ.lUҰRF@! )f?A Sb>Zt$W f2HUS .zX/*t/>,qm:`!$&ʟmї:QfdfU,n׎f<)$SAIҦ}&IL XLE'E4J3:浄=.0 F?k}U!z]aUnexzv7dj_m`X }m;~^~^zmI)sf.|:v*e'8qH .},,0ƐluG;d8ytXKxW׶S :[9f{8z<뒽5!:ǯ= jSfKH""2" # 2Խj ]8, ]~cyOSњEvajBKhiu˛@TF&QeDl6;W^}eֻ$*m٥xb^^"Xr>ȪtŻZ`s% ̉f"Ylm=5>1(RN`@* jGIFFԺ+))Z=Zk6زhztؑEOwS_',! 3u79 w8sVa9 +r)/ ž՗4KPWa!K<`־*W4$AP -DU !ĖQM#OGfzDDJLpBrNVEf49@x)^ 9aSN 'r{ʫy?] zRIw9Ud{ ٸ.|◮K\KtAj8!Vq@P ϳTm]M=GJ]W,%18ίo4Lp#>Փ4p;V [(W鉸-^!#_iH~TW|k.~7I'ZXTpƚ;(bC7fTJP&SR(h̍Nq i)afЋ2n/!cu;5' a$@$s>@OFo,B &G#{W9aٻr?6jyPt[|߹+:g?ԓ+,xUn{wEO+-}r/=Cх${ !}~wZQ`-qh,i5tC`v煉yF_Ggh{!'Zh)g$<͔g0*@wYfnH3N, @!iLgnLq/Icw!Z1'l>CZk5)VEEdĴMZ S!xFL? Δ]e΋qBNZ%P&wM_Mo _ +o?.>Ǟ~qs̹X-"/+OwpK6͋}oG{3,&'ƅ^s/|pWڥ?\o3ebA3=amdFMeӖ M#?ڑZZSTDRѷĹ+3a73j3 gꉢ-b6A:QB/'O[nm28 )sR9u_BPl"sA/{$m=ԑ̸fHH7zc՝%"v[PmQ8&ZjEK-v#k~fwjMNzv!NF>$Ld1dh&(Z@KssWn5 -b(@Y՛2,뙧xb4Z/}믯2ҡp}=o ӚG8rF簾Q 7L!soW8&KϾxz7-V7zJ׾~ٶO 99B^U/_;.loMh-kXzEw#S51@f)k"3Y +<ٝ%rSyfl 9QhsO8b'[a 5)V& +n=+cWZ)N,2Ko5iCwp6h Zhir֦efhbndDkidm[v#oD?͜٭{f)%EF7?ٵ0(hf=EDH3 ;jqXIWpa9s:-Dθ T)5_o15kd8 -1]D&` ",lHeA4>ck7!Er[pFX*` ö`rBr@R̷9}01­*Č44O%{1S$+Ӆڲ6MDk5N#vZ)n4E)鿁Q>4so! 'euPF pe2Q͝lv2ySи{rDj,]:n@ $$fjLI4Y1"a4@˹r&l)2q.P LQd@Ȕ0G$ 䄅F.8^3/FC!iR,3R|6y&N^qp nxY+:![Jr7Rnm=#i-ŝ=0(Eh6CJ&;ß<@0&fRE?he}FN8CF?uF$ @^e;]911XXN-hLl+cJNzI*Cm ̤[h=BrtMm0Mt/ >̼I)0sPX̋qŐ^"sli 1m{wt&"1SXҢ[K$CJs ~vC8)+7:Nf枰1f8ņNm ^qRA'Sg3CӍZo4 Z[ dRv{r^٢艄&y݇{F /iL ܡ ً,]@HMF91fn(85ЂgDG3[앐lsf T66,j̏ 61rLȌhc Sn -\_ R= r2F@Zf헌>yw$S'Nq^?ŚiN`i>o+ 豙12Zb[YPn'[Q 1fvJJ8&T"`Rdty8qZr =0Lcpa˩0@e9iű]̆b'F'.qcč@M䘩֮WESd6c*j촀Z&kdľu9,¤쳙AK?埓2Rad8A}|0}OqS<ʹ\g)ֈ53h-`QfЀ5Jࣦ{%ZFJB2._h1`,qaH2|LDv1=skbf^apr3MVR&2ۃ#G!*Czg#&v;\"ca;qmnڤ)5~mZm֚f )kj.!UI3dUU%gk pU% Ὓ;$̢E BH"*"PC*H*ieqaNY3=2~ӟ-’k m@arjN$<[q 2"$ 'x(P "IߢRP,Yզ|1r$P%dF:9NOWs``Nj/xꈡx]p+;/޻Bá C͞"Vv!K ' [WPOVSk)ЧsĤRQ WEEUGI.YQLdbP`$ZPi-/dbbH$.N-N;s&Τv ?jɂ͹OB7cXrHJQ97MN9He-+HNi~eV)"DS#UDTSΑڔ[.Ӏj ٍe,UPRrisNI,97y#Fx>QSDT5(o(FzjVTm D$9K9$6]k&MM>jv4kM)6Fsr:)q"zd J0wGp]PǺ­O>>1n{.e6xmXͅƒO%qO]z*um X}$ePju,JWyϪ"RU݃}Ȼ>YEa4TMQM!)Ualz)%;A5q…zc+x {ݔv/^ ٍ%rԤhԮƋll ǠnQ:Xb8GsPUUM))ám֦iڜ֛6UbVESJss&K&9(C.`4 1m{vFɇ |9@c;wkɝl'~^ysr),=̼xl]g]gnovRGO>E)JGY%, aV~w'臭Լӣ Z ӥR N/}}C◓4*"ʔJeۜrT3&天030Ԉx0jP-v~uq=wS?\vgڃwWI?/d.VpMR:$5T0P=ZUDHA܊PܙS۫kN?;ؐ3Ħf!`q=BBTf Gxxq ҦB`RDJkD#]_|}p|1.}ytݸ JWxwŢ/]76뻮E鋙Y)7sw/Ew[cp8" pLKfQ!'wK=^c:-U~Oq0?+I[{.gܓG ;f6%Q#nrYsʩEKʽ4A 'dWBUv:H՛q8 M c@H"4fuK'j#L0"/e єD]O^:܂"{@ʖ^jMWɫ c j%}rO ͑gP!I␛4l93Ӄ|Mdn2f#cp7aV7rON1\M&a_wm+z.k%./vPi6*Kխ1>`( 6ZȠIvSBy=BsG'$K/}"$(<܇G i .[5E}-Pڏ+eh:׮!Bp\'鐴Hi؏5+#PTGsQ(ty4>|]Z"FDHLDbsc 2(T~C]9¥Kfz;ӯpPp˯b Gqi7O43{qMݪp!hpdZ0&-jyZ##hEk`bg<1way 7I&CCr" f6A+A+WqC#ݜ"#s3Bm`#: "\; O!Z:sϟ]Ax%o|[8awwϭp#/ .I\\ȌiyL CbDuKÞ 0aJZ_u-Zת5bKxk3mSs[=.ݓiw]\~tydw񵋋ˋrxvœݼe=$"UB*UU…1hA{8yCinܦ]KS.y^ͻbwq̻2/qC}[Å36\;ي>&+3g.xhy)?!Tuo~UUUETM;VN#hK=8H#ap*><"">K(3|a:"L󰃈x?gkڔZCK`#UW{oIT;Ǽj6%>3g}Mr?}^yڷtDz!<͉#S12+ɠ[2s\Z&S=h`&ijӴmYys-t1ew'˼,]ҲMK4E[<9EDD2Pm0^C#aGvzjou8Q%kO../w˓GnYb7?YfM]['rGL̆hT@1 98zPgھUWϚR/zP1\v@-Br$ vurm$2eaQM,WB/VUzUGbl0| Dз2GcS,mz.tҶ3hEUmw е ٱ9e$(fqDd=̙y}S4QU+?7Sp]nE}g}#2 d#wsޫGzC_~߇dSd.A-yY_i"_ $8d;J6m ?wxgΜ98c_=-逹b5/j…0(7y^'\wu2WsrBÊʌA_\8̙3g|eU>d2r71L2V#W)]0;/~CkW&m)kR;**]VՖEa@l $[k$f^"2Hy f 46 {wq1?6yJq~I-%R,U]:[CCgCq>w1>YVV>J#ld>.H۰Y,/`/x\kXeW)V7,P3ZwzҼ{kl=r> IQх38k2Vks_C0/P11ƫ>Y(VA+77Kͪ`/"zMyvr]IvNft9yQЛ=$P $K&{w"H"P$ؼmwmPNQۈ3q:T qq)L0.߱rKwkUY`3(YeXM\A'_Үic=|hؙ7Q ːJy:>_ȸ./DQФ%.gƧbcWS1|p-v6(ZNn@ev~֗]-Uz8D2AR)ޫh{=7x>Y)n{fFDC*Y]gG"`Dj]%.QeZr=Z?vVb$ ]7~>3zhBI/}"x) @BHT) e}q0(*(t1~gS1|x w@Tdy]U7mҸUPɕ^Xu[++ Q_Wrp乼PEuX{#Z.#3vkcަbp7\|@QU~ý:w\R{{WH{eIial!WenKHZVi\Tp-> P=iO K/$a(;:gg c>E¿|'T,CY7V6B*QRoQ}6`W:M >/MɂH+ :˅8e8v0!^BiD6IeEs11/bdz9W/ ݵ}sZTػ\Be YWفpP;+%{dV^o"+qUz"r ܗ:"y?qO| ,\HjSPE=ts^n"t"\t>1Obd-d;PĵBTo$L HAH"XI^e˦ Y &Tez`8 m,Q}mp0s_tӻloXFkqVavvVc6o&-ۿl4`Y+u~TVqj ̏"g۽<$I&6>m&[?1۩hǾOa$IZ8^P55Jlp\jvaERɣd{e;Jv*Kl*29@ mƢZfў`m ;aQŶ0RFmIw꿹`ک,Ӻڠl?y*CbZl ఱ/^ qvHhюERjm^ywp\_xڏaW98.!&#vN[=|<̆ӭ.vw=Mӯܤ×Z>(t$\uPeI]'X#B%74uE c_PlA+lzӍ3jVPש1FnúZFnzMerLSu<ntL`{&}vsFZ|2X~S `18/SйuNӧȡ M9,W0->\I?G/bOOR/}%KGgHfVJGc$qS.݆G"+([N(B4-&NND~|r߫ ˗H_:śVE+y/smqX xPDwo/A{ċ.;0)Znޥ=6(f5F#N30lCU#y553w]ۧ3a3+͔`ҞywdU'`]QyW˚AM3m AŨM5U2aĻ+"j ċLBYih#dcŞ}.ZfNmnm6h/гfY^`U9eeJ򸎛}W{f7=tP)D67@6ChG0Ĵ^aiZk.1Ł;i|]2@s9Lެ*tȁ79,MŇ` us˱xO&&]ױăߛ5HEvvKg/rѯWrEEvw6\4zL],XK)T݊ܖH8<lnnq&H:|= s4h{û&GH`b{fx!Pǡb϶!މJ6d8{7@}xOUu@Um~SWO>]}7i5= |MwqOG9x/mEMTEf iKSM# =h[J`\˛)/ l$pM>& (l;'ݙ4sEQa+.4s۬4.G3uH🱸Ϗ87/{#7Ӂ>4X}ҍ:,\F pT> %!#+wY{L ~o@!^L%H]8d PމLYʮ^nSJDi#pr\jkJ~.fD 5lRBq(s`B3tQP>FU\_^ymVVDWZfMe ,&چM8'Ԉ uyUy7De<2+(~>"* *CcO慪x;@`${GuA%t8*iȁlU#^+k79 'MACj*{bሊS\YCQFc"+b8- SGf *p\ % ;\tP\^q ⊴^Z,w'Ԛ~Nqjp>aWD8u ac(mom[uXMbTP$biM)μVϸG_bYw{CټGiJ{9r}>sӤgkc/eΊgKCwvßy{l!P ?i ӊ.{_)%), )<@ud\V >9v,5t| $IC R|2W{U$#4ѰǛ*ô!=k,\Յ~99)bMW@|hOa H*oG C쬜g{JSanM2//fɞp› @ /&XCJ6-Wq< L@H?@vb}b$2<6ĻG `iHz$prʠjE2d+K {* g%@5"T*K"/~KEIWH bWZAw͑.vW}4 W#F8 /oa$KO&P*-Ym(F[DE2+F9z/.?FkT\jznɅ~/xht;Jţ:  H{&)x #G0X iR3ˈ$ىQ ^(1'' #`⾨,xI8JvR.NDXRLЉ^{ f BUIYY` NNa+ 񚐔( nF0cH7xEgTP D*m1+dh/&b`&Il*= ZX.DYx/v{=6~l5&^| ׉ 4ieG4 ކ׾=9tnW8Y1B%6Qrw*GS)y"?.6zK%Vם;f*P^ub(JGk 3q ETM*aIKf, Y4{ghx{ "~-` )6T)&JoK0ň vQB+%Nka _&Xq-Qmd-A+B1r m/“'-yP~D+R]&k6;k ;onO!y[zOvf:hJ)](P 7.@5SN )^k尿wqFnkuMuŇG(tr=qYXmlq<o42ء\v8Q O+`CRQ{׍Ңnn:8hnUekCdFCcO27Vv ٘DZcS2?mYh{۷NMGKΐԱ= G 7c,,5I4oxi~_\$3~.7xx{᧹p힩S;W`>?hc}J.GJ6Sҥ~>1 ~]ЃW?TZ7+ޛ;,9f_}M۫{=W<~O*_}8]>Zm~ū|mO>E}Tn~Żާx߫ _t$~/aqqg=K 4rʹ-B|qA<VDv4rč:XiT|.9@C:SD]SӾr ؊rZC:B&gǰ, G*FK<*")5}YXӯuEpXBP삉,2T+*gHP݋~+ bGi[jp@Vc?@HĮ%4Z1H%2 -p,` J0tE rBqF$H䃦n5D - ^V ӻ"$De 0YPaPhrڧ~2QtDYWCFi( -xsH_4(Ɗ4*' mJ` ~uJ3&Е4]E;b.!&CHaꎨ$\_Zlz!p"} h-'z~VV‹q@B i,o Ky5jmD/ *u  "^o]!oѴ+1DڂXWJ&HsoFKvDzVs)@ȼdM ԣPŋVI³"sׂ|P%,O`KD+N,,+@-Gőq >W,$f|`b%%", ^{tѦt<: ^?]a~2t3I'>B{E % !Jw6+W.mJ֪DUH A*Ĺ_`"HUrK'6tAac#6t~E4)%A(EE;LAV)#Wb!DȞD-JBZBQ؈,arKj췛Xmaj FA1AB!r)Qzi`S#*^YQ%tB@b+<}G0! m)BjmduX?B$ HIN̄3 (6-l IT`9) 6vEnY$JIGhSP*FX-Ǻ]5ګ!F,"+=MYig6ފs}q“ޓ)INj0njkCbQ[s(ڙ(`ߴj\΁|P/l _@xǢfi}DSQ.C?nޛ,X!Nk~#_0LNl[Ue.aQǓ ];y ?Mfc}LT\yoHICVaVʮU;3lTdP! D9rB![B+}Y򺺮kz_i%b m3Ÿ]*ｻZBJ^+/x~3{./{__ޯwn/>"l~dmy6!bTf{*=߸}lSŻ"}X[P`ׅ>zʉL m/0- STt%邊2|K6xQ,ې^SP8.*Ϧ4"<E8f,H#rOB d9[ߩ`ш,{gȆ(\ƱV G rXt>&|)n{P 7UQC@{T~Ct zΗ7Nq BmEgE`"" C-貁.58Xi@9VCiwלߋ*O/DZ&We0AOtY NYhи1zoOߋx +(@Ʋ Q%G0ļA-? 6)9H:D2$ˌkh+_G+/=C! q F:wT3zEvVBb@}:{K y+$^{ & ?3', ef]qO& Z~^~lYbɝ@-T.c&ﾯtMAx| :G[CaO}=|^z'&K&=o{mv^.38cz=`{kb{_^Kq2׋ z'=Z9PVi.:KY"]z.'bt̔Ho}1+0`<RMmvR%8>vQŗa!a!(ިR %=;'93wJ6qˌ9Trf_{io}8,|Q9s܄=JCj^K\ :B}NeLj4‰jZˏ-B{THtgb΂C4c@yOt=#~x)FyQ^{0w %¹``@=J4aƐ\@z!>*%(pR&xj0kVx_BF}LPsp'& } GLv0x0 JLTS+,UcO"׀CΙ4^`T{&ϤeDR (c"we*‹e\. ˯-V"*.%EJY "Rc[c7C fAU) +\Oբ""/x6B*)SM*;]褎0*-"jjkpL Aƥ{IƁ|/8,?ϓr[[RƝI["3x"qˉBnaXrg8gSbmJ(,G9%""J4UI\@~MűaܧMk0^g2d9g +~Y3daWRksj=4um!*3 :\/^R cJVu ЋI'] Oi>90yyY=LSGKF^!x,hN8%Yia(ձ6cW Pӱ!.cఒLcbf='Mx>t)zsR(>`M-(6C~] x l‚sŰHqo\6˄r;AT]J{E_RI7Fy#̛%w߻[R #@`JMk8 ])pyai<5TȕE^f"C2 Z+ p#l4f!/D9x R(mÍ-\t`ԽǒtRiKW4h+ $i_n{ t7æd[GHb P&'y8嫕[!(\.1|"Q2Ւ< &K,'͆e|A9D)%~&c-Ϛ-4)qKDJsN؅Ǣwt*bբtRjte+2' p&!~'<8Dxʞ5T=-2@OrQ!j^`=9U}"Y{os&5 4D>M8ɔm[^5\2wT4+|):e; gKppk&*Zm{j1Do{mgYBZ]/G.q+2#M%w(>U6nb{Wm!].%WFCVIFvd2y{S7`z#*Gm>>6s8xT*ΜaO&/Ͳ/}?|kdnN8@yyfPeulDqST6RWvd|x b$7H@zCRJK1npC4 &ɴ T?P*ᮨϠaڡz U!$(ѦH(7TWؤԃn2iR+-SRjL 0VCh 5|/7Ɇ3':?둏Qx(&o  0:QKsZrKmNC`%&L<|C9e 2UMS{Ž .YY=,m)7{KA%8(G2P>]&p,04КXΉ^ ϝl'izCbbn(O>ѐE/~^dQ~ (ck5%^XfK53!x*`U7cVH}] G$y8KxgNKӴ}TK6wK*\ap{@(V |Qæn-P\T Li@V ֞ } \s5pVqxR*eF.gu~o%Sa#t1c8)Լ )&>sI湱8~FZHhe 蜉C#eLt YO"W Jj> 1HֲS^ A Zmڅ!VE{ߋM`]Q 'ن C`[ O9p3@H0DyLoƕ#A^!T "{6 Zr`1lѵ(v*j1[I30=6YٟTyaܣm)!/U>y+c8#E6J=Ҋ 8N?nFt.98"]ڹ޲Nh@>7{/&]h !{ung{r~ΑV2ku~e7w"}Bkޓ3#z5e;'F.rovG~Sg4g6᱈g1+Prgᤩ[X;YdJ ]pեr"uM^NXT5d菷NB^#psS/^Fq15сɈGånbtVo 0n(DV8KinxqgrcTZ}kx]L 42?%;L{;b#4d{4!o~t5+uL#iEfX8Qy@5D^2ZDNSG&B%w)5vn~dD8"2#MxW45`7)ul-nykAc<Ƨ# >P˪S9|Ka~9~aEYT+t;xxF Ȣmr rεٴ׶*Nk{5E|_Rh32)ɼ|m ؊\\I`SNn ׶% ,S pףj c^*̀4"g~Qs~wyIfmqFqlS9h>oɻAxN ^"vA(zɥ|7U$s~Wq Jx MU@&l ⏕tG"e9 peֱ]s'%>"wXƛy*9$my h eW7CЎZYe=r_a8v]^~l}}G=~A -7{}UE7{V}y{z=dV ߒ+˪%-2^rk-}2{jP@u \dayZ*J:Ͽ^#"]ȘeJ 0l G zˢ;dE _E4!Qe+B(2Y4-6:[mh1mU>ԔUO wSP,4p ϦrF۫Ϧ8FSeto]_:H.^Plx9סE{OPםВ8ƇcTXV^%q U Z6ǙhDΩ0׳s/1 QYUPJÙgD\9)9(D Dvv90#ugRK4TT 2qUKϐ.(yA M3#bYsf{4'64%80ĩL[B=L!.D`@'&3Q^1)OMAaqb"r`6RKNe r'N6=R!u,]:{(tH lMEBa/єYbE<!B"װ+%0&W,T3)kQ&}8zڤs6(AL;ORpko7eޝVy.(FԸsĎ"wڣ:i/V|yuƄle=DGOe`ơ'rBZgR^]heuc*R})]- kq/GLUu҈s2DvUAvk/7fsr\7XA{5Hے AKS?zYf(3u̼ۂ-7"Kn>p DԆDE|=n`1d#ВslK hlM$^KcNμ!IЫz{%ޘL)!VȌ=>7%$T.yd^4S1;-&FlFSC΀5[W~|hzE큽@zDes}xPЕO HD@zk4{Ϡ5똽ZANV-Latqځe~6{u?I\uAXFTZ"1xh,u[ #HƵ(sHo5WN#f|w8<ҽ0Vtk7vrwt<~!{$rVkmS:*]~?1<ͷwlվԳ7 QCTEc&WMĔ.:m*U~/#=2D"hcc<Ƙ .7 Oo (݄eʮ{S`w4ȘSe8=+ǹ,ޫh /0M8 F_/DՁ=cfQ&~,өV0TgJ% Ӯ6qy$OL֑pNC@TiZ> BgB9sl3=˙4_tn%9ҭ(k F:!K,<`2$IVr_9WTbJ\&(O =D(hp 4 @DެfZ"PN]/a eY'S||ϲtcA,;QW,1.F47OԻSm}~ p Je=46 C9Ĕ{A1B ☺ ֨!G'{\v)O>WLfLhf4a[_9-Մ$`eJvFT '(8Q0hxK+zSyCP8R9Ģ8jYP)^BU*^"1Zl_ ,#a"ke@Ӌ!8_" q@{wh/_g+ +JB_5)*9̕[P.POMzm:L"W(`RfTlvMH`)./IZīxIm|q<6}WS_>CAP ܇a7nYJ{ƅ՗M"p&"@}1;ՃGGUZI3J4"5@a%`Y`Bq6(!*U~o⏌ C> pxlb&)H{tT(^`uJՖYS^>tG.msOVHyeԸ" hII[c%E LhUO  j* rrB>qDs)^DZe| br1*WAy&J7Lfp xuC p$pIx)S•0\Y1ek55y-HrI9k"ű݃ѐ1x7@r Y&R%?- S צc{" @`dF+tSҙ1]9ju%CJV;;}91Wg{Fqy꥾w4U~&-2hX~\N[Za>ϱyy>~6˞;i~%lS/Í>9>}μN_}-f{i} ߖ$PFV g =ol7I -r3g-K`&f -_zam/nI`|m .VkDR 󵭬6 >l>)-/U tx jؖGIWrqPmyL{\1sʼ-{ @]9U?{t6Ssv\Kmg7cd| ]w?gByrb>QjZD-YN:Q~'˖扞%h_%ik2U Y-S s{O%'ATcH5!8LE x)=)>S2F(U,# <!_|o""qʛ@]MɧrA!Yh#_o( ϸlo$^x{v.툯?_hj*RctqHnc 8%P[N{_D{w#R19Aܵ_G۱xR$P:=;=dtȂxϾ ܂GqYzJru^D5ȇHEz %G 4Q@!ҁs':/_!' 6(Q@bB9c^v)_\Rbu$ދr,|w0y@!Bumz]#:X}Gÿ AfREY. y RqU/W2u²G/IYvKg^h3Dr yeȏ UQ^6V$]C "=#y9DGw^(|t$^(PZq G6asuz:^`X9^;v-ᔂ MBGҾhoU%B If_ X^DIΧ*.TK"d<"c2kW$,o]]@t!5{O[\{Vޮ_cc{Z7Hfy46hTϘ4$ƽ(u$е!DS2:E?~L\чtV~{W-0wA-$bݱ]  a9|f`#>[hŽcq +D}^o&K_Mz̤ys'XI}ߒ[)+C|%_/җ =ţ6$%nZξoJ?xhP>إǓE}9fE3)^p5MTB8ET%[8=5%W<m({d]z5#8DqO34zz1_ #D 9vC-IENDB`}DyK _Toc485535598}DyK _Toc485535599}DyK _Toc485535600}DyK _Toc485535601}DyK _Toc485535602}DyK _Toc485535603}DyK _Toc485535604}DyK _Toc485535605}DyK _Toc485535606}DyK _Toc485535607}DyK _Toc485535608}DyK _Toc485535609}DyK _Toc485535610}DyK _Toc485535611}DyK _Toc485535612}DyK _Toc485535613}DyK _Toc485535614}DyK _Toc485535615}DyK _Toc485535616}DyK _Toc485535617}DyK _Toc485535618}DyK _Toc485535619}DyK _Toc485535620}DyK _Toc485535621}DyK _Toc485535622}DyK _Toc485535623}DyK _Toc485535624}DyK _Toc485535625}DyK _Toc485535626}DyK _Toc485535627}DyK _Toc485535628}DyK _Toc485535629}DyK _Toc485535630}DyK _Toc485535631}DyK _Toc485535632}DyK _Toc485535633}DyK _Toc485535634DyK yK ~http://msdn.microsoft.com/downloads/sdks/platform/platform.aspDyK _Complimentary_TechnologiesDyK _Best_Practices_forDyK yK rhttp://windows.microsoft.com/windows2000/en/server/help/DyK yK http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp DyK yK http://www.microsoft.com/WINDOWS2000/library/planning/management/userdata.aspDyK yK bhttp://www.microsoft.com/windows2000/default.aspDyK yK rhttp://windows.microsoft.com/windows2000/en/server/help/9DyK yK http://www.microsoft.com/windows2000/library/resources/reskit/samplechapters/dsec/dsec_pol_zbgy.aspDyK yK http://www.microsoft.com/windows2000/library/planning/management/groupsteps.asp DyK yK http://www.microsoft.com/WINDOWS2000/library/planning/management/userdata.aspDyK yK bhttp://www.microsoft.com/windows2000/default.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/default.aspDyK yK rhttp://windows.microsoft.com/windows2000/en/server/help/DyK  _Configuring_Folder_Redirection}DyK _The_New_HireDyK _The_Laptop_UserDyK _Computer_ReplacementDyK _A_Shared_ComputerDyK yK http://www.microsoft.com/windows2000/guide/server/overview/default.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/manageintro.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/ccmintro.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/intellimirror.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/remoteover.aspDyK yK dhttp://www.microsoft.com/smsmgmt/exec/default.aspDyK yK Zhttp://www.microsoft.com/smsmgmt/default.aspDyK yK http://www.microsoft.com/windows2000/library/technologies/activedirectory/default.aspDyK yK http://www.microsoft.com/windows2000/library/planning/management/groupsteps.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/grouppolicy.aspDyK yK http://www.microsoft.com/windows2000/library/howitworks/management/installer.asp DyK yK http://www.microsoft.com/windows2000/library/operations/management/siamwp.asp DyK yK http://www.microsoft.com/windows2000/library/planning/management/remoteos.asp DyK yK http://www.microsoft.com/windows2000/library/planning/management/userdata.aspDyK yK http://www.microsoft.com/windows2000/library/technologies/management/DyK yK http://www.microsoft.com/NTServer/management/deployment/planguide/prof_policies.aspYDd? J  C A? "2MرtD|h wv`!MرtD|h w`)]x=ohJriR$M$Qv8!6`EJ.W7H!*`oBʾ/G3ξ(Oݙ,YQًEe?)~>}4EW?oYyAGGUVѣߣrs'ޓz|EukYmyhQn  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvxyz{|}~FRoot Entry  F@$/{տ@Data wyAWordDocument ObjectPool{տ@$/{տ_1012218791 F{տ{տ1TableCompObjhObjInfo i@@@ Normal OJQJ^J_HaJmH sH tH <A@< Default Paragraph Font  @Vl,b$5qDP/O" m@n(  6   AB S  ?? t@3@UnknownGz Times New Roman5Symbol3& z Arial5& z!Tahoma"hǃBfǃBf!@!r0G2 Craig Marl Craig Marl   FMicrosoft Word Picture MSWordDocWord.Picture.89qOh+'00 <H d p | .User Data and Settings Management White Paper.0ser Craig MarlnrairaiObjectPool {տ{տWordDocument(SummaryInformation( DocumentSummaryInformation87 bjbjUU (7|7|l www$ RwU"wwwMw w Yx 0 jj jUmHnHu 1hN N!@!"A!#$%n5qDP/OPNG  IHDR sRGB pHYs+qIDATx^]-w+,0 \ <``(` `AA@@  \` 44Hi.gZSsdiT]ucGQ?XNo?ש΍i$396 !v{.yn s>s.~ p d?'4qD8cԱGp-b>@G/肜3K;&8Ǚ ~s9GD7;ʹ9g!81LK3 ǩk*LqZpq8w pg>NӉa<NL…M 2ƙK*+9n`&H2v)STC3yDƱmD\n@Wzt&\h6BiK9oyN? ZE\~p-q. 9Տ$A*7P\%4EB%R˹s8iOy6֭U΍Six2 @Jd:Wp֙t 98\a+3˵^)3ՄLB56gH~k2L)I{,"9FB\?bff<ĺ,dCq߹pWp!Up.dS劻>UМs^g|͚%u949b\*6qv$8{1mxmTq.7`D1BnڋCi۱oFAiIڅ@7yNwC>޸nGx?Ӌ-A[Jx3}8 S -w(nad_ ̫T=H'j8P 3 PX%qUIVm|QbS[/"WTa,N9_Im pp8ស'y7qUߨstI8W|&ͧ?=]<&s!UrUi"wVRs  ny~2",EW/Hʫ,,` \~xCO/0Ci8Wrݽ?pχ_v_ti,6 jb+s7awׯ?>~"%Y Ӹn>E!̺?yJ`Iҙ\=$6bck|SP\?WlFzWVCynm?5j"ԲkCWX<%1eϙ' ,Y?VkEכ5t)+9oHN6_e|.8}CV;A-%*1~犯<TC!xWGz*:^#jD@s ^/ܻ5VDe)CDc^ >rUG/Jr-y.#F.{Sz -h! ƹijS= girR{5B?Y0'Vȿ :22\VPvN9S{ru),9>zb;1[ށiëδ5]B!]MXFrh CЗv3G%7Ч- vG{̋=7ϕ ƹ+pns{.ϧ"KLsE$y&GctDOFkaV|]^Iw9v9J*:0eV~n&Ƈe TzSTG?sSGxmsdǓ+5sGkE\iBc#.&E{3GXb+f3vw/~|ׇFP0r DǛHܬƿ;ipxa$= ϻaN/i"ͺB/iYu|}j#gA3O/Yy.+;o"agHWS&Kכi.3+޼<`,Tnxg`T$w4稯(14Q;w&ܡ[vϣsy[doA…ozCfG57Nݪ[p>[uV7 Zqz+'%6ƕ؈qn%GTsz9F\89܅uz9]&{6@szLBd=eraSbkt8~NmV8ٟH~8n>Gnso5 [h9cwvpˈp5Y-_=J F@sjS4RrխmtdnAbc+g 5Ch8G@7<;[9ߪNY"v<')M\۲sk\r ~G,ƹgA8Y[9k7bMr{;Ίs 1GbV~'q:C^xA ˸Z:蛔VXq ;WNqͽJ'SY ! 9J6fց\E $h>vutRٲTYެ_Q18S= 6(\_y_J-pْmf8 (%㴵Mڽj9mdVUE?TqfjVϭ7pirf湙c@uS\K1Ω~nn8DeU9&%" ƹdY,)!)s T`/﷾`IU݂Ȳq? C!ֹҮ$ɣjylZs< 9XDF9B:(<%T~Y6Rs ?祝%ȸTΛsP{ 5DCP\s߫ĵ}/RKdV.bp]Xˮ,~e[q7aRmpGFu(i2UݙJ;~o%n}ӱu)83$fr {krV7?ʹ1#D_ǭ n2IENDB`Oh+'0l   ( 4 @LT\dss Craig MarlrairaiNormala Craig Marl2aiMicrosoft Word 9.0@@jx@jx՜.+,0 hp  Microsoft Internal  Title'dWϲO~⋗_Ⱦ=+ɟN~q'o<:ywŏOdQguq]ʿo篊'zlYs{ɷ9BC ! aKeO\j}q`.smצJ2s狦M=|h]42`gy[`;12gϏ9udi3>sJngvN;22o.!=}Nsa'a.9b= Sas5v7ooaw#^}!LC0G~|T~EŜ~{\ *zȓoM0'<@S,0FuYgC`:Ĥs{!r%>G~ss=7J4?X9#?ȕ CC94\o9H3Y5zڽsr咪^4 >󹭳ϙVh&b9NXW1is^V`s079DB9s9 Po5KN.#?+1I9|9:? zi>8?s0~!#?ȕ |\rasOe0\` 6߼Z:ܲsʞX_Zjk-V3U`n>lsvPYTG`n ۔glYj쪉嬆OftCi愂 s]^o7^Mv#@]#Էnn9œu aJ_{_Ϲ {Jcs~.l9̥UcV4z+PN9DBu4H!w:XkM[_+gQ?kO4Q>x\߶fQwbNG˽9gw`ik8%zgaw;C> k)Մ7g +Wckƺ fx>S!Z !5g2$_{ e1qon.N_ ms݃wʿ0 31]#xs99ϑC3sh6sϡ$|n:9M#?9yP>7F~%y>7v~%s`nr>w~ϡ`"W99!?G)r ss]9KܘM3v=gq~~~~u֟9acNrh>gnjSmjS;oM좩k.//kNOOs\ױ5s \\ ܦ:SL6o( ;9ck39׽ez]zHq'?fus07\~`i`"W99 `u]~ΫiNT/Ժ%dLK">%mkoUFL[i.n~~\o9r%d.]+ [z1봆b.WuS냹|NdυCis}־\;xY:ڑ9:+`.ĩ?s!4QC07ܔ~ s&xܐ18kG5i 䚎tr M١.U|l ɜ\`B27L )*CM綽+a&ɜ9!'Xu][[`fd>u7:.|: w^ҭCFPRC#J!r%9|CϑC4:!''Lן! <_E$b^m]j- E+^v(\Ik\kPOLp(-{x9@X=yz4I~eXanϱ`\ "?`C瘨JݬCl̅?\W8y }.h9kmpG9kM\> sBM|qc|'?gsasSn0G~"W`!|\49D~ܨ9̰f֒?}ٙӴXegNoN̙6g8>Gsnc&|#?< ZN1,%?7t9 #?G~!r%̍(BF_RdN=RťZ՛L$O^160cߺ?;.*tZpZ[1)y]C\kiW)9#s~뷺Z#sZɟ±u zbn?%4sͻmMloBa]2,VOedP9xF<39s9s\ 9b̡>sM?sNlCVsԳh]-=(姡ș.M4-j}uc`.U]fz]3fN[i i~#sGa_>nr\p8&͜Um̈́90rec>LnX`RheK ٙSCJkPzcЎ9bQ\?*~>}4{+.츸xj1Table&SummaryInformation(DocumentSummaryInformation8OCompObj j      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEIHJKLMN[PQRSTUVWXYZG\]^_`abcdefghijklmnopqrJ `Lu8 # c  P ( V 2 r m 7Fxcj} c"z"y&()),)E)F)))))1*2*Z****&+'+(+^++#,5,h,,W-$.]....///&0001,1g11(2[2223,3U334?99:: ; ;;;+;I;d;e;v;;;;;;;;;;;;;;;;<<<<(<b<e<h<i<v<<<<<<<<<<<<<<<<<<<<<<<<<=!=%=)=*=4=R=V=Y=Z=z=>>.>%??ABbBBBBCCBD]DoDFFG4HpIIIIJJKLLMM%PPFQoQES{SSHTTIV|VVVW:WWWWXYZZZZ[4[R[X\-]V]^_=cccc+dLdddf+fgi jklnoompvp}ppppppqqqqQsRsss>u?uAuHuiuuuvuuuJwKwrwwGxnyoyqyxyyyyy z ~ ~ ~~5~A~B~_~~stʁpDEh؄l…'o׉7,ݍY IƐMڔ5ݗkG3vŤeC]fxԭ"#J(uvw װ]HBeW-iFpUnCMA{|I234bcd 5TUbp~7HwxyK,fRD iB@B Normal dxOJQJ_HmH sH tH \@\ Heading 1+$$dx @ &#$@& 5CJKHB@B Heading 2,H2$@&OJQJ8@8 Heading 3$@&5<@< Heading 4$@&5CJ<A@< Default Paragraph FontXOX Abstract Text dCJOJQJ_HmH sH tH lOl Abstract Title)d(x$dN]5CJOJQJaJ:O: Bullet 1 & F 1$RO"R Bullet 2 & F 1$^CJOJQJaJZO2Z Bullet 3' & F 81$^8`CJOJQJaJhOBh Caption Large Picture`d8<^`6CJOJQJaJRORR Caption Normald8<6CJOJQJaJ2Ob2 Code dL CJOJQJ:'@q: Comment ReferenceCJaJF@F Comment Text dxCJOJQJaJ8O8 Contents./CJ\TOT Document Typed5CJKHOJQJaJ,@, Header  !TOT Footer-even#  5$dN^55CJTOT Footer-odd& 5$dN^55CJ8&@8 Footnote ReferenceH*L@L Footnote Textdx1$CJOJQJaJ(U@( Hyperlink>*B*VOV Legalese! XdtF0$^6CJOJQJaJdOd Picture1 Small!"$dx1Z  &a$6CJOJQJaJ`O2` Masthead Descriptor#d8^6CJOJQJaJOB Number$ & F (1$>T .Tf^`(BOARB Number after bullet %]^]&)@a& Page Number:Or: Paper Title'h(]hCJ @OR@ Picture2 Med ($ mHnHuLOBLPicture3 Large)$`^` mHnHu>V@> FollowedHyperlink >*B* phBOB Table Body+sd((]sCJBOB Table Bold,d((1$5CJ@O@ Table Bullet- & F].O1. Table Title.xB@BTOC 1/ P d5mHnHu:@:TOC 2 0 PCJmHnHu>@>TOC 31 P^CJmHnHu>@">TOC 42 ^CJmHnHu, @2, Footer 3 !jORj Body-no indent4 d1$] CJOJQJ^J_HmH sH tH FORF Body-indent51$]`CJ6B@b6 Body Text6p]pCJ("@( Caption76]NON caution8ddd[$\$CJOJPJQJ^JaJ8P@8 Body Text 296OJQJ]@@@ TOC 5:d^CJOJQJaJ@@@ TOC 6;d^CJOJQJaJ@@@ TOC 7<d^CJOJQJaJ@@@ TOC 8=d^CJOJQJaJ@@@ TOC 9>d^CJOJQJaJX^@X Normal (Web)?ddd[$\$CJOJPJQJ^JaJVOAV Numbered step&@ hhx]^h`^J<O< CODEA$$dL5CJOJ QJ FO"F Table Body 2Bsd((]sCJ<O2< Table HeadC<5CJOJ QJ "!"!! "!&Ou8DMPbx" X-6Hlmzd!F1t(^PQb`2HP U V k T s 7AGOfgM/^I'KL]]- `a})*S%                    !!!!! !#!(.0#0'0'0'000400040`40!0!0!0!0!0!0!0`!00/0/00000101010101000101010100000/0000000100000001010001010/000000000/0000040`40040 40 40 40 40 050 40 40 40 40  0  0  0 40 0 40 0 00 40c"40c"40c"(.0c",0),0)0)+0)+0)0)+0)+0)0)+0)+0)0)+0)+0)0)40)(0c"40(+ 0(+ 0(+ 0(+ 0(+ 0 (+ 0 (+(0c"(0$.0$.40$. 0 $. 0 $. 0 $. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$. 0$.40$.40$.40$.40$.40$.40$.40$.50$.(.0c",0 ;,0 ;,0 ;,0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;+0 ;+0 ;+0 ;+0 ;0 ;(0c"40Z=80Z= 0> 0> 0> 0> 0> 0> 0 >80Z= 0!B 0"B 0#B 0$B80Z= 0%BD 0&BD 0BD 0BD 0'BD 0(BD80Z= 0)pI 0*pI 0+pI 0,pI 0-pI0 40L(0L40M40M40M80M40FQ 0.FQ 0/FQ 00FQ 01FQ40FQ80M40IV50IVI $0IVI $0IVI $0IVI $0IVI $0IV40IV40IV40IV50IVE $0IVE $0IVE $0IVE $0IVE $0IV40IV40IV80M40-]40-]40-]40-]50-]G $0-]G $0-]G $0-]G $0-]G $0-]40-](0L40f40f(0L40i40i40i40i80i40o(.0LC0mpC0mpC0mp0mpB0mpB0mpB0mp0mpB0mpB0mpB0mp0mpB0mpB0mpB0mp0mp0mpC0mpC0mpC0mp0mpB0mpB0mpB0mp0mpB0mpB0mpB0mpB0mp0mp0mpC0mpC0mpC0mp0mpB0mpB0mpB0mp0mp0mpC0mpC0mpC0mp0mpB0mpB0mpB0mp0mpB0mpB0mpB0mp -0mp -0mp -0mpB0mp0mp0 0E40EK $0EK $0EK $0EK $0EK $0EK $0E40E40E0 4080408040,8040ݍ8040 8040408040M8040ڔ40ڔ040ݗ40ݗ0ݗ40k 02k 03k 04k 05k40k40k40k0ݗ40Ť 06Ť 07Ť 08Ť 09Ť 0:Ť0ݗ40(.0,0],0]0]+0]+0]0]+0]+0]0]+0]+0]0]+0]+0]0]40]0ݗ40w40wV $0wV $0wV $0wV $0wV $0wV $0wV $0w 0w 0wV $0wV $0w 0f 0f 0f 0 f0f 0 f 0 f40f40f0͗40 40 0͗0(0404040404040(040D0͗4040408040o804040(.0,0,0,00+0+0+00+0+0+00+0+0+00+0+0+004040(.0,0,0,00+0+0+004040*.0,0,0,00+0+0+00+0+0+00+0+0+0080804040040*.0,0,0,00,0,0,00+0+0+0+0+0+00+0+0+0+00+0+0+0+0+0040804040*.0,0,00+0+00+0+00+0+00+0+004080408040 804040400404040 0; 0< 0= 0>0404040040;40;40;40;40;04040040404000@ 0@ 40> (.0C0> C0> C0> 0> B0> B0> B0> 0> B0> B0> B0> 0> B0> B0> B0> 0> B0> B0> B0> 0> B0> B0> B0> 0> 50> 0@ 4040C0C00B0B00B0B00B0B00B0B00B0B00B0B00B0B00B0B00B0B00(0400@0 0@40@0@40@0@40@0@40@0@40@40@40@0@40@0@0@40@40@0@0@0 004000 8gggj 5!eB(`&'&"*" x!j%E02h3567,8(99;dBBeCCCYDEFbIJoKNPR{Z|]:^_aXc+kmw?|J~ As؋'GHex tT^K!%(*"*!*JXtv *FH@\^+GJTps 3 6 _ { ~   ! B ^ a   / K N v  # & 5 Q T f  - 0 Q m p IKf9`oAahn&FM#*0bS?&(L\^ 4 H Mn^;Z]] - jB]}&S%"! %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%ĕXXXXXXXXXXXXXXXXXXXXXXXXXtXtXXXXXXXXX*13Zadj!!!:    O2$MرtD|h wb$#ùS:ǥ$ŕ<2$Z8Mx(Rߒ߹b$؋+.`wtda/F@ (   b  C ?3"b  C ?3" ~( P V  C A"VB  C D"t  0A ? ?#" 8   S A http://www.microsoft.com/WINDOWS2000/library/planning/management/images/ud_fig07.gif#" B S  ?]."!"t( + 4' ? , _1%, j0k0k _Toc481822331 _Toc481826445 _Toc481827809 _Toc481895837 _Toc481908331 _Toc481908372 _Toc481908450 _Toc481995296 _Toc481995331 _Toc482008733 _Toc482008769 _Toc482009109 _Toc482515593 _Toc482515701 _Toc482515739 _Toc482517070 _Toc483989082 _Toc485442882 _Toc485535597 _Hlt485535644 _Hlt485535645 _Toc485535598 _Toc396470201 _Toc476986468 _Hlt482515735 _Toc485535599 _Toc485535600 _Toc393446640 _Toc397931373 _Toc476986469 _Toc485535601 _Toc388674172 _Toc393446641 _Toc397931374 _Toc393446642 _Toc397931375 _Toc485535602 _Toc476986470 _Toc485535603 _Toc476986471 _Toc485535604 _Toc485535605 _Toc476986472 _Toc485535606_Enhancements_to_Roaming _Toc476986473 _Toc485535607 _Toc476986474 _Toc485535608 _Toc476986475 _Toc485535609 _Toc476986476 _Toc485535610 _Toc485535611 _Hlt482006937 _Toc476986477 _Toc485535612 _Toc476986478 _Hlt481908365 _Toc485535613 _Hlt481908444 _Toc476986479 _Toc485535614 _Toc476986481 _Toc485535615 _Hlt485447268 _Hlt485447269 _Hlt481984387 _Toc476986482 _Toc485535616 _Toc476986483 _Toc485535617 _Toc485535618 _Toc476986484_Configuring_Folder_Redirection _Toc485535619 _Hlt485447342 _Hlt485447356 _Hlt481989106 _Hlt481997438 _Hlt481997439 _Hlt481989133 _Hlt481989169 _Hlt481989170 _Hlt482009296 _Hlt481989216 _Hlt481989217 _Toc485535620 _Toc476986485_Complimentary_Technologies _Toc485535621 _Toc485535622 _Hlt482515628 _Hlt481995329 _Toc485535623 _Toc476986487_Best_Practices_for _Toc485535624 _Hlt481996448 _Toc485535625 _Hlt482003318 _Hlt482002328 _Hlt482002329 _Hlt485447381 _Toc485535626 _Toc476986488 _Toc485535627 _Hlt482005625 _Hlt485447391 _Hlt482005629 _Hlt485447395 _Hlt482005632 _Hlt485447406 _Hlt482005638 _Hlt485447408 _Hlt482005635 _Toc476986489 _The_New_Hire _Toc485535628_The_Laptop_User _Toc476986490 _Toc485535629 _Toc476986491_Computer_Replacement _Toc485535630 _Toc476986492_A_Shared_Computer _Toc485535631 _Toc448234735 _Toc472485332 _Toc476986493 _Toc485535632 _Toc440964019 _Toc445789055 _Toc450543561 _Hlk472835426 _Hlk472835427 _Hlk472835428 _Hlt472835549 _Hlt472837035 _Hlt477172624 _Hlt482006228 _Hlt472835454 _Hlt472836938 _Hlt474667222 _Hlt482006239 _Toc478446113 _Toc480797465 _Toc485535633 _Hlt482006187 _Hlt482006192 _Hlt482006200 _Hlt482006206 _Toc440964020 _Toc445789056 _Toc450543562 _Toc478446114 _Toc480797466 _Toc485535634 _Hlt482006171 _Hlt482006166 _Hlt482006158 _Hlt477172886 _Hlt477172887 _Hlt482517028 _Hlt482006149 _Hlt482006107 _Hlt482006125 _1012218791@@   c"c"c"c"y&y&y&(()'+(+%.%. ;Z=Z=LLLMMffiimpyEE։ޗޗkkRRSŤŤ]vwwjlPu||UU""TTQRR222V V V V k k k    9 : > @ A B B C T T T tt!#! @@@&'(!" #$%)*+,-./012345@679;@8:@<=>?@@A@B@CDEFGIHJK@L@M@N@O@P@Q@R@S@T@U@VXWYZ[@\@]_^`a@bc@d@e@f@ghik@j@l@m@n@o@p@q@r@tsuvwxzy{}|~@@@@@@@@@@@@@@@@@@@@@@@@@__ -6y"y"y"y")]+]+\.\.\.\.;Z=Z=Z=y=y=LLLMM*f*f j jtpyggՉ։։׉SST֤dwkmQv}}EUl#$UUQaa2FFj j j j : ; ? A B C C D H H H r r r r r r uu!#!Xw!*I$%'(-.1278@_+KTt 7 _   " B b  / O v  ' 5 U f  1 Q q ));;^=_=a=b=g=h=k=l=q=r=tpupIgdeM$45?@M^"]] - ^%    !!! !#!Xw!*I$%'(-.1278@_+KTt 7 _   " B b  / O v  ' 5 U f  1 Q q ));;^=_=a=b=g=h=k=l=q=r=tpupIgdeM$46?AM^"]] - ^%    !!! !#!Xw!*I$%'(-.1278@_+KTt 7 _   " B b  / O v  ' 5 U f  1 Q q ));;^=_=a=b=g=h=k=l=q=r=tpupIgdeM$45?@M^"]] - ^%               !!!!!!!!! !#! Craig MarlKD:\Documents and Settings\craigma\Desktop\UserDataand settings_cnedit1_.docPatty NicholsonLC:\DOCUME~1\a-patrni\LOCALS~1\Temp\UserDataand settings_cnedit1_ craigma.docPatty NicholsonC:\Documents and Settings\a-patrni\Application Data\Microsoft\Word\AutoRecovery save of UserDataand settings_cnedit1_ craigma.asdPatty NicholsonC:\Documents and Settings\a-patrni\Application Data\Microsoft\Word\AutoRecovery save of UserDataand settings_cnedit1_ craigma.asdPatty Nicholson=C:\Whitepapers\Mgmt\UserDataand settings_cnedit1_ craigma.doc***C:\Documents and Settings\a-chrisn\Application Data\Microsoft\Word\AutoRecovery save of UserDataand settings_cnedit1_ craigma2.asd***QC:\DOCUME~1\a-chrisn\LOCALS~1\Temp\UserDataand settings_cnedit1_ craigma2_cn2.doc***YC:\Documents and Settings\a-chrisn\Desktop\UserDataand settings_cnedit1_ craigma2_cn2.doc***YC:\Documents and Settings\a-chrisn\Desktop\UserDataand settings_cnedit1_ craigma2_cn2.doc***7C:\Documents and Settings\a-chrisn\Desktop\settings.docWsQYxPŠQaVίFV$1 < 9 ` g VV "*NPŠQ$a*7 }O`,a\[&vPŠQy,o.  PŠQJ#`9_ (|1&|-1);j$-PŠQ<*.znn.4#/V&C2A0@Ε%v1~m(3B&6H7eY8 u}PC.m,"( jvgV .zV;|лhV~Rлx4.`f|*?ZN:3Kbt&                                                      |2                           RH^4u?uAuHuiuuuvuuuJwKwrwwnyoyqyxyyyyy z ~ ~ ~~5~A~B~_~~stʁDEfxԭ"#J(uvA{|I23bc 5TUbp~Hwxy,R6HlmzAGOfgM/^I'KL]]- `a})*S%  !!! !#!@HX"!@(@4@8@Unknown Craig Marl***G: Times New Roman5Symbol3& : ArialW& ??Arial Unicode MSTahoma7&  Verdana5& z!Tahoma?& Arial BlackE5  Lucida Console3Times="HelvArial?5 z Courier NewA& Arial NarrowA"GenevaArial;Wingdings71Courier"1hcF&kFFF