Purchase Windows 7 User Profiles on Windows Server

Translate this page
Powered by Microsoft® TranslatorIntroduction:
This blog post comprises a high-level overview of differing types of profiles,Office Professional 2007, considerations for picking out a profile treatment for ones deployment, highlights of new profile functions in Windows Server 2008 R2, and also a most beneficial practices recommendation for deploying roaming person profiles with folder redirection inside of a Remote Desktop Solutions atmosphere.
Terminology
Below are some fundamental definitions for track record comprehension of differing types of profiles and folder redirection.

· Community consumer profiles

A neighborhood user profile is designed the initial time a user logs on to a personal computer. The profile is stored on the computer's nearby tricky disk. Alterations designed towards the community person profile are particular towards the person and also to the home computer on which the modifications are made.

· Roaming consumer profiles

A roaming consumer profile is mostly a duplicate from the community profile that may be copied to,Office 2007 Professional Plus Key, and saved on,Purchase Windows 7, a server share. This profile is downloaded to every personal computer a user logs onto on a network. Changes designed to a roaming user profile are synchronized together with the server copy with the profile when the person logs off. The benefit of roaming user profiles is the fact that customers usually do not should formulate a profile on every single personal pc they use on a network.

· Obligatory consumer profiles

A mandatory consumer profile is definitely a variety of profile that administrators can use to specify settings for end users. Only procedure administrators can make modifications to obligatory user profiles. Improvements made by consumers to desktop settings are lost when the user logs off. Necessary profiles may very well be produced from roaming or regional profiles.

· Momentary consumer profiles

A momentary consumer profile is issued every time an error issue prevents the user's profile from loading. Short-term profiles are deleted on the stop of every session, and improvements crafted by the user to desktop settings and files are misplaced once the user logs off. Temporary profiles are only on hand on computers operating Windows 2000 and later on.

· Folder redirection

Folder redirection can be described as client-side technologies that allows for the capability to improve the target area of predetermined folders observed inside the user profile. This redirection is transparent on the consumer and offers the user a consistent means of saving their info, no matter its storage spot. Folder redirection presents a way for administrators to divide consumer info from profile information. This division of consumer information decreases person logon occasions mainly because Windows downloads much less data. Windows redirects the community folder to a central location, giving the consumer rapid accessibility to their information once they preserve it, regardless of the laptop or computer they're employing. This rapid accessibility removes the need to update the user profile.

There are two main many advantages to Folder Redirection because it applies to profile information:
When implemented with roaming profiles, it may possibly greatly reduce the dimension with the transportable profile information carried around by consumers for logon/logoff. Due to the fact these folders are redirected to network shares, you trade local I/O effects for network/remote I/O affect. This will be particularly helpful on disk-constrained deployments. Working with Folder Redirection with obligatory profiles enables consumers to have some control/persistence of customization this sort of as application configuration settings (AppData) or IE Favorites. Highlights of what’s new in Windows Server 2008 R2 RD farm logon performance advancement
First logon to a device in a server farm is generally slow due to synchronous Group Policy processing, and subsequent logons are swifter when Group Policy is asynchronous. In WS08 R2, the GP cache is roamed in between the servers with the farm so end users have to only expertise the delay through first farm logon and get a a lot quicker logon practical experience for subsequent logons to all members of your farm.
Roaming person profile cache management
An RDS environment can possibly have countless distinct users. Whereas caching of roaming user profiles is enabled for the greater consumer working experience, this profile cache can increase particularly significant and may possibly possibly overrun the available disk space about the server. Controlling the cache dimension of particular person user profiles might possibly not be reliable around the RDSH server, simply because there can be numerous new, distinct users.

A new Group Policy setting is available for RDS in WS08 R2 that limits the dimension for the overall roaming profile cache (situated in %systemdrive%\users directory). If the dimension with the profile cache exceeds the configured size, RDS deletes the minimum not long ago put into use copies of roaming profiles until finally the all round cache goes below the quota. The policy setting is discovered in the subsequent site: Desktop computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Profiles\Limit the dimensions of your complete roaming user profile cache.
User profile hive cleanup shouldn't be needed starting up with WS08 and Vista
Prior to WS08 numerous people downloaded the UPHClean services to prevent profile corruption issues caused by applications and processes keeping connection to registry keys while in the user profile immediately after logoff.

In WS08 and Vista,Windows 7 Starter Key, there is absolutely no need to have for UPHClean since this functionality (and much more) is now done by the Consumer Profile Cleanup Service that's designed into the running program. Thereby you won't be able to locate a model of this tool for Vista/WS08.
Profile considerations and trade-offs
There are three main considerations/trade-offs when deploying person profiles inside of a Remote Desktop Companies environment:
Central management of user data and settings:
It is essential to centrally retail outlet person data and settings in order that customers obtain a regular expertise irrespective of which server on the farm they connect to.
Thus it's not at all highly recommended to deploy regional profiles on the Remote Desktop Session Host, especially if it's going to eventually be piece of a farm deployment. Efficiency:
Synchronous consumer Group Policy processing, substantial profile dimensions, good sized numbers of consumer Group Policies, and slow back links amongst RDS and profile servers will be the most typical issues that considerably slow down logon.
To prevent the overhead of synchronous user Group Policy processing on any logon, turn on asynchronous Group Policy processing as described under. It might consider 2 to 3 logons for new policy settings to consider impact.
To refrain from big profile dimensions, we endorse that you simply configure roaming person profiles for registry settings and folder redirection for all other parts with the user profile. Furthermore, you could set a policy to limit the profile dimensions.
To greatly reduce large amount of Consumer GPs, you could potentially re-scope your policies (e.g. utilize to a a variety of group or OU) to scale back the number of GPs that apply for the server at person logon.
RD Session Host or RD Virtualization Host must have a speedy connection to Lively Directory and to the SMB share where roaming consumer profiles and redirected folders are stored (e.g. in very same datacenter). Application compatibility:
Some programs may affect logon functionality if, for instance, they record a whole lot of info into the registry, bloating the profile dimension. Thereby it truly is often endorsed to arrange folder redirection for your AppData folder as described with the Step-by-step most beneficial practices manual under.
However, some applications may have challenges whenever they are deployed alongside folder redirection. As a result as described below, there are extraordinary concerns for redirecting the AppData folder.
If a problematic software writes information to exterior the ordinary profile places or bloats the dimension of your profile even while the AppData folder cannot be redirected, it is possible to use Microsoft Software Virtualization (App-V) to deploy that software.
Considerations and Trade-Off Summary
 
Central management of user info and settings

Performance

Application compatibility

User info management method
     
Local consumer profiles

Not suitable for RDS farm scenarios

Faster logon experience

Does not introduce app compatibility issues

Roaming user profiles

-User information and settings backed up centrally

-Recommended in RDS farm scenarios

Roaming profile downloaded over network, can slow down logon/logoff

Applications may possibly bloat profile dimension

Mandatory profiles

-Changes to end users settings not preserved given that a regular profile is applied

-Can be useful in locked-down environments

Standard profile size ensures steady logon performance

Does not introduce app compatibility issues

Folder redirection

-User information backed up centrally (but not registry)

-Used in combination with a variety of profile types

Can help improve logon speed when roaming profiles are deployed by reducing the dimension of roaming profile

Redirection of AppData folder may possibly cause software compatibility challenges – details in stage 5 below
Perfect practices for any typical RDS deployment

Step-by-step best practices guide to deploying profiles on RD Session Host:

Configure roaming consumer profiles for registry settings and folder redirection for user and application data folders to improve logon and logoff functionality when centrally managing person info and settings. It is actually most effective to keep the dimensions of roaming user profiles small due to the fact these are downloaded at logon and uploaded back on the server at logoff, increasing logon and logoff instances.
Put together an SMB share on a file server to retail outlet roaming person profiles and ACL it correctly as described on page 28 for the Managing Roaming Consumer Info Deployment Information.
For more effective logon/logoff performance, the file server on which the profiles are saved should really be found within the exact same datacenter as the RDS servers.
Ensure which you flip off Offline Folders for shares exactly where roaming user profiles are stored in order in order to avoid synchronization troubles as per this KB article. Set up RD Session Host roaming profile path
Roaming profiles ought to be configured separately for each RD session farm. They really should not be shared between farms or user’s physical desktops seeing that profile corruption and info loss may very well occur if a consumer is simultaneously logged into two machines that load the exact same user profile.
Configure the following Group Policy around the RD Session Host:
Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Providers -> Remote Desktop Session Host -> Profiles -> Set path for Remote Desktop Services Roaming Profiles Limit the dimensions of total profile cache
Caching roaming user profiles is suggested to improve logon/logoff speeds. Roaming consumer profiles are cached by default. Also, a typical most effective practice is to cache profile info on the separate drive to optimize info access speed.
In a giant deployment with hundreds of end users, leaving these caches around the RD Session Host can cause the server to run out of disk room. 
In WS08 R2, you can find a whole new Group Policy setting for your Remote Desktop Session Host to limit the dimension from the general profile cache on the server
Configure the “Limit the dimensions of the overall roaming user profile cache” policy under Local Personal pc Policy -> Laptop computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Providers -> Remote Desktop Session Host –> Profiles
If you enable this new Group Policy setting you should really not need to delete person profile caches at logoff. Configure track record upload of registry settings
By default, roaming person profiles are saved towards the server only at logoff. Consequently, to ensure that changes to the user profile are saved back to your server (if, one example is, the consumer does not frequently log off) it can be suggested that you simply enable the subsequent Group Policy which is new in WS08 R2:
Computer Configuration -> Administrative Templates -> Technique -> User Profiles -> Background upload of the roaming person profile’s registry file though consumer is logged on Configure Folder Redirection for all user information folders.
Please follow the instructions in this TechNet article to redirect all person data folders listed on page 7 for the Managing Roaming User Data Deployment Manual.
Ensure you set correct permissions on the share as per instructions in this article.
Special factors for AppData\Roaming folder:
If the AppData folder is redirected, some programs may perhaps encounter efficiency problems since they will be accessing this folder over the network. If that is certainly the case, it can be endorsed that you configure the subsequent Group Policy setting to sync the AppData\Roaming folder only at logon and logoff and use the community cache whereas the user is logged on. Whilst this may have an affect on logon/logoff speeds, the person expertise may well be improved as programs will never freeze due to network latency.
User configuration>Administrative Templates>System>Consumer Profiles>Network directories to sync at Logon/Logoff.
If programs continue to practical experience difficulties, you should certainly consider excluding AppData from Folder Redirection – the downside of doing so is it may very well increase your logon/logoff time. Enable asynchronous Group Policy processing
Synchronous Group Policy processing could considerably decrease logon effectiveness, thereby it happens to be endorsed to configure the following policy: 
“Allow asynchronous person Group Policy processing when logging on through Remote Desktop Services” 
It is uncovered under Pc Configuration->Policies->Admin Templates->System->Group Policy
Lockdown with mandatory profiles:
Use mandatory profiles if you have a very locked-down natural environment (as an example, a call center) which does not require preserving user settings. Gains of this approach are that customers will get a swiftly and constant logon/logoff efficiency as well as the same predictable expertise whenever they connect. When utilising mandatory profiles it is actually preferred to also use folder redirection for user info as mentioned in step 5 above. To configure mandatory profiles,Office 2010 Product Key, please follow the instructions on page 30 with the Managing Roaming Consumer Information Deployment Guidebook. Note: Windows only allows for for your overall consumer profile to be obligatory or roaming. There's solutions accessible from RDS partners that offer a lot more flexibility.
Remote Desktop farm concerns:
As mentioned above, it is advisable which you configure separate roaming consumer profiles and folder redirection paths for just about every farm to prevent information loss and corruption troubles if there may be a chance that a person can simultaneously log onto further than one farm. WS08 R2 has farm logon improvement: First logon to a machine is commonly slow as a consequence of synchronous Group Policy processing and subsequent logons are speedier when Group Policy is asynchronous. In WS08 R2, the GP cache is roamed amongst the servers of your farm so end users need to only encounter the delay for the duration of the primary farm logon and get a swifter logon experience for subsequent logons to all members with the farm.
RD Virtualization Host:
Pooled virtual machines: You are able to configure roaming person profiles with folder redirection just as inside the RD Session host case (see above) to centrally manage user settings and information. Personal virtual machines: Configure roaming consumer profiles with folder redirection just as in the RD Session Host scenario or manage consumer data this sort of as on the physical desktop (community consumer profiles could be used depending about the scenario requirements). Please refer to the Managing Roaming Consumer Data Deployment Guidebook for more general information on user information management.