The replacement computer
If the hard drive on a user's computer fails, all data and user settings saved on that computer will be lost. However, if there is a recent system image backup for this user's computer, then we can replace the failed hard drive and restore the computer to its state before it crashes. However, most businesses do not implement image backups for workstation systems because the amount of hard disk space of all machines is very large, requiring saving up to hundreds or thousands of GB of backup data. . Instead, most businesses focus on ensuring that data is stored on important servers that are backed up regularly. If you execute FR to focus on backing up user data as described above, user data will not be lost when their computer fails.
However, user settings can also be an equally important part, especially if users have customized their applications to help them work more efficiently. So if these users' computers are faulty and you bring them a brand new computer with all the preinstalled applications, this user needs to do a lot of their work, they It may still take hours or more for customizing the applications on your computer, downloading templates, making some personal customization for the operating system such as definition resetting libraries, configuring taskbar properties, etc. And some items such as dictionaries created over time can be very laborious if you have to rebuild from the rubble. The time spent on sorting out such things not only causes frustration for users but also loses productivity for your business.
Fortunately, however, by executing Roaming User Profiles (RUP) together with FR and OF, you can save the user's entire state - both data and user settings - on his file servers. The main purpose of this implementation is to provide users with alternative computers, the working mechanism is as follows:
There are a few things to note about this scenario:
If you have to focus all user settings and data to allow replacement computers, you can use Remote Desktop Services (or Terminal Services) to do that. You can also provide users with session-based desktops with RD Session Host (or terminal server) servers or individual virtual desktops running on the RD Virtualization Host server (workstation's virtualization infrastructure solution). Microsoft). Either way, users will have a complete replacement desktop, which they can access from any computer on the network. However this method may not be suitable for small organizations. In other words, the implementation of RUP can bring many complex issues that you will see in some later parts of this series, so many businesses can be satisfied with computers that are only capable. Sell instead, where FR is used to centralize user data but user settings are not centralized.
Migration workstation
When a certain version of Windows appears for a while, that's when we start our migration process. If your desktop computers are still running Windows XP, this is the time to consider migrating to Windows 7 because Windows XP is close to the end of support. The thing to understand here is that implementing a USV solution can simplify the process of desktop migration. This is because in most cases, user migration from Windows XP to Windows 7 involves using User State Migration Tool (USMT), a user account and operating system migration tool. and application settings from the old system to the new system. Small businesses can use Windows Easy Transfer instead, but most mid-range businesses prefer to use USMT because it is a more powerful utility, able to customize and create scripts.
By executing FR to redirect My Documents and other profile folders where users save their data, you can speed up the migration of the workstation because there is no need to migrate data properly. setting up users. This method also reduces the risk of data loss occurring when doing a wrong step in the migration process, since all enterprise data is now stored on a centralized file server, no Right on user computers. This workstation migration scenario is one reason why you should execute FR in your environment if you don't already have one.
Roaming
Some organizations set up shared computers in semi-public places like receptionists so that employees can use this computer when they need to do something. You can use roaming scripts here because users often work with their assigned computers and only occasionally roam with shared computers.
In this case, it is best to do the following:
If you also use RUP in your environment, you can use Group Policy to delete cached copies of roaming profiles on shared computers when users log out of these computers. In this way, the hard drives of shared computers will not have user profiles. However most organizations do not use RUP and it is not really necessary to support the roaming type that is sometimes described in the above scenario.
Hot Desking
Call centers, help desks or similar environments often have to implement hot desking systems, where employees do not have computers assigned specifically to work. Instead, employees must share a number of shared computers and use whatever machines are available to perform their work. Remote Desktop Service (desktop sessions or virtualized desktops) is the best solution for such environments, but smaller organizations can use customized USV strategies according to their needs. Such environment:
What is RUP? You can use RUP if users need access to their personal Windows workstation when they log on to a shared computer, but it should be noted that the RUP scenario is quite complicated. This is because the call center, the help desk usually only uses a small number of standard applications, and it would be better if you use Group Policy to lock the temporary environment for these employees instead of giving let them roam desktops that they can personalize.
Conclude
The following table summarizes the recommended USV strategies for the five scenarios described in detail above:
ScriptDirectory redirection
Offline File
Roaming User Profiles
Backup centralized user data
For the My Documents and Desktop folders
It is possible for My Pictures folder and other folders
Not used for AppDataRoaming directory
YES
NO
Computer replacement
Use for My Documents and Desktop folders
It is possible for My Pictures folder and other folders
Maybe for the AppDataRoaming folder
YES
YES
Migration workstation
Give My Documents and Desktop
It is possible for My Pictures folder and other folders
Not for the AppDataRoaming folder
YES
NO
Roaming
For the My Documents and Desktop folders
It is possible for My Pictures and other folders
Not for the AppDataRoaming folder
NO - disable OF on shared computers
NO
Hot Desking
Yes for the My Documents and Desktop folders
It is possible for My Pictures folder and other folders
Not for AppDataRoaming
NO - disable OF on shared computers but allow indexing on the file server to be able to perform remote searches.
NO - Use Group Policy instead of locking the client environment to the user.
As suggested in the table above, a redirected directory needs to be further explored as AppDataRoaming in Windows Vista and Windows 7. Therefore in the later part of this series, we will go together to find out at Why does this folder redirect require special considerations when planning a USV strategy for the business?