【 Weak current College 】 unified Windows desktop configurations to improve operational efficiency

On a day-to-day basis, business users may want to use any intranet, a computer can have its own familiar working environment. In other words, because the work needed (such as a conference room for meetings requires use of temporary computer), employees use a different computer when you log in, the staff is rendered before the user's desktop, shared folders, and other employees in their work environment. In other words, employees use a different computer, as long as the employee's user name is the same, it should use the same profile. To achieve this purpose and is not a myth. Windows operating system provides a method called "roaming user profile" file strategy to achieve this objective.
I. three differential analysis of the configuration file.
In Microsoft's operating system, its default provides three configuration files for local user profiles, roaming user profiles, mandatory user profiles, and so on. These three profiles each have their own uses. As a Microsoft systems engineer, to understand these three profiles features and differences, and then the actual needs of the enterprise, select the appropriate configuration file.
When users first log on to the steering group system, the system will be used to automatically create a "local user profile." That said, the operating system will take the user's desktop, network folder etc configuration is saved in the local user configuration file for use the next time you login. However the local user profile is different for different computers, changing a word that each user on a different computer (even if the user name the same) have different local user configuration file. It is this profile does not meet the above requirements.
Mandatory user profile is the system administrator preconfigured, when the user logs on to the user configuration file take effect. When an employee logs on while it is possible to adjust the desktop settings as needed, but when the user logs off, these changes are not saved to the mandatory user profile. That is, to use mandatory user profiles, each time you log on to the operating system is using fixed desktop settings, the adjustment of its follow-up will be lost. To do this configuration file will not be able to meet these needs.
If the system administrator wants to domain users to the domain of any computer logs on, the system is the user's own work environment, we can use the same configuration file to have the same desktop settings, you need to store on the server a roaming user profile. When an employee logs off from the system, desktop configuration changes (such as adding a link to a network-shared file shortcut) will be automatically saved to roaming user profiles. So the next time you log in again when employees of this operating system, the system will take this changed a roaming user profile to set the desktop environment. This is what I have to recommend a configuration file, it can let the enterprise employees when and where you can have the same working environment.
Second, to domain users specify a roaming user profile.
Typically, system administrators can use two ways for a user-specified roaming user profiles, respectively to the user specified an empty roaming profiles and give the user to specify a preconfiguration of the roaming user profile. Since the two are very much the way the configuration process, so the author "to the user specified an empty roaming user profiles", for example, talk about this specific configuration process.
Suppose now the enterprise has the following requirements. Enterprises have a sales manager in its domain user account as SA001. As a result of its work, the sales manager would like their use of account SA001 in-house any one of your computer when you log in, all want to see is their own desktop environment. To achieve this, the how to configure?
Step 1: first in the file server on one UserShare "shared folders". This shared folder is used to store enterprise within the domain user account of the roaming user profile. At the same time in order to guarantee the user's desktop configuration changes can be saved to the shared folder, the writer also adjusted the associated permissions. Allow the user to this shared folder to change permissions. Because the author is in NTFS file system, so by default on domain users is not change permissions. For this reason the author emphasized that we must allow the user to the contents of this folder. Otherwise, the user's desktop to change configuration will not be able to successfully saved to the server, or even cause the desktop configuration to be lost.
Step 2: create the user information. Shared file set, the system administrator wants to use the domain administrator to log on to the domain controller. Then open the "start" and "management tool" and "Active Directory users and computers" window. And then in the window to create a user account. Account creation is finished select the "Properties", open the configuration file labels. In profile path, specify the store the roaming user profile path, that is just the first step to set the address of the shared file, such as \\192.168.0.3\UserShare\SA001. Where is file server 192.128.0.3 IP addresses as shared folder UserShare, SA001 is the system administrator to specify the name of the folder. In order to facilitate the management, the folder name is a good idea to talk to the same domain user name. This folder does not need pre-existing, only need to specify a folder name. By the time the system will automatically be created.
Step three: roaming user profile initialization. The above two steps to complete, when the Sales Manager to SA001 account to log on to the domain of any computer, the operating system from the second step in the definition of a shared file, create a roaming user profile jacket. This folder name is the name of the folder specified above. Note that the user first logs on, the folder will not have any data. In other words, when the user is the default user profile, not the roaming user profile. If the Sales ManagerRoom for the first time on this computer is logged on, the work environment is the system's default configuration. If the sales manager was previously on this computer, login (set up roaming user profiles before), you use a local user profile. And then when the user logs out of the operating system, its desktop settings (may not have made any changes) will be stored in a roaming profile. After sales manager regardless to the network of any computer to log on to the domain, the system will read the roaming profile and take advantage of this configuration file parameters to initialize the user's work environment. In addition it should be noted that, apart from the user's desktop configuration is saved to a roaming profile, also be saved to the local configuration file. So, even if due to reasons such as network, resulting in a roaming user profile cannot access, users can still use the local user configuration file to initialize the user's desktop environment.
Third, the user's roaming profile usage restrictions.
Because a roaming user profile is stored on a network server, so when users from any domain or computer when you log in, he can read into the configuration file. But when the user logs off, the desktop's changes are automatically saved to the server on roaming user profiles. Business users regardless of which one you next to the computer when you log in, will be to change the settings to configure the working environment. However a roaming user profile environment is not perfect, its main application by three.
A roaming user profile only applies to domain users. That said, only the Microsoft domain environment can use roaming profiles. Local computer user is unable to use a roaming profile. This is mainly because a roaming profile is saved in the domain of a server, and only domain users to the domain of the computer to log on and read the server configuration file in the roaming.
Second, it is only when the user logs off the desktop configuration changes will be saved to the configuration file. If there is a staff now, its just on the desktop, new point to a shared file on the network. In the absence of cancellation before the configuration not saved to the roaming profile. At this point if this employee suppos off to the room for a meeting, then the most recent changes will not be adopted. Because of this change has not yet been saved in the roaming profile.
Third, because roaming profiles are stored on a network server, and not stored locally. So if the corporate internal network instability or heavy, you use a roaming user profile to initialize the user's desktop environment, you may need to take a long time. As this system engineers in the deployment of roaming user profiles, it is a good idea to first assess your network environment. Determine how to provide a fast, stable local-area network.