What is a roaming profile, and how does it work?

What is a roaming profile?

A roaming profile is very similar to the local profiles that exist on every Windows desktop. The difference is that, rather than being stored locally on the desktop, a roaming profile is stored on a network server. Because the roaming profile is centralized, as opposed to being local to a specific desktop, the profile data can follow the user from one machine to another. This means that the user will have access to all the data that's stored within their profile, regardless of which of the networked Windows PCs they log in to.

How do roaming profiles work?

With a roaming user profile, employees' data follows them from device to device, so long as those devices are part of the same Active Directory (AD) environment and run a Windows OS. These profiles are stored on a network server rather than on a desktop computer. Admins can configure AD so that it associates the roaming user profile with the user's account.

When an employee logs in, Windows copies the user's profile from the network to the local computer that the employee has logged in to. When the employee logs off, Windows copies any updates the user made to profile data from the desktop computer to the network copy of the profile. This process ensures that the roaming user profile contains current data the next time the employee logs in to a virtual desktop or PC.

This copy-in and copy-out process is what makes profile size so important. Large profiles can increase sign-in and sign-out times, especially in virtual desktop environments or locations with slower network connections. Folder redirection and careful profile design can reduce that risk.

If an organization decides to use roaming profiles, then it will need to take steps to control the volume of data that is associated with each profile. Otherwise, the profile can grow to become quite large. This can be a problem because the profile must be copied to the user's computer each time the user logs on, and the profile also has to be copied from the user's desktop to a network server when the user logs off. In some real-world deployments, it can take nearly an hour for users to log in, simply because of the volume of profile data that has to be copied to the user's desktop as a part of the login process.

How to use folder redirection with roaming profiles

The best way to avoid this problem is to use folder redirection. Library folders such as Documents, Pictures and Videos are a part of a user's profile and can accumulate large amounts of data. Many organizations use folder redirection as a way of moving these folders to a network file share, so that they are stored outside of the user's profile. In doing so, the user might have the illusion that documents are still located in their library folders, when the documents are stored on a centrally accessible network share instead.

The most obvious benefit to using folder redirection is that it can reduce the time required for a user to log on or log off. However, another potential benefit is that folder redirection can sometimes make it easier to back up a user's files.

What are the software and hardware requirements for roaming profiles?

For an organization to use roaming profiles, client computers must be domain joined and connected to the AD Domain Services environment that IT manages. Microsoft's current roaming profile deployment documentation applies to Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 11 and Windows 10, though organizations should validate support for their specific client and server mix before deployment.

IT also needs a file server to host the profiles, Group Policy Management and appropriate administrative permissions. Admins should plan storage capacity carefully, because each profile consumes server space, and large profiles can slow sign-in and sign-out.

Mixed Windows environments require extra care. Microsoft recommends using separate profile versions for different operating system versions to avoid unpredictable behavior or profile corruption. Folder redirection can also help keep user files such as documents and pictures outside the roaming profile so they remain available across OS versions and do not increase profile size.

IT should also be aware that some user customizations do not roam cleanly across all Windows scenarios. Microsoft documentation notes, for example, that Start menu customizations can be lost after an in-place OS upgrade when users are configured for roaming profiles and allowed to change Start.

What options are there to manage roaming user profiles?

Roaming profiles have been a standard and cost-effective way to deliver user settings across physical and virtual desktops for years. They are still a good basic option when an organization needs user settings to follow employees across domain-joined Windows environments.

UE-V is an older technology, and IT teams should verify operating system support before considering it for a current deployment.

Microsoft also released User Experience Virtualization, or UE-V, in 2012. UE-V virtualizes user OS and application settings from a settings store on a file server. However, UE-V is an older technology, and IT teams should verify operating system support before considering it for a current deployment.

For many virtual desktop and Azure Virtual Desktop environments, FSLogix profile containers are now a common alternative. FSLogix redirects the user profile into a virtual hard disk stored on a supported storage provider, such as an SMB file share. At sign-in, the profile container attaches to the session so the user profile appears like a local profile. Microsoft positions FSLogix profile containers as the recommended user profile technology for Azure Virtual Desktop.

The best option depends on the environment. Roaming profiles can still fit simpler Windows desktop and virtual desktop needs, but organizations with nonpersistent desktops, Microsoft 365 app data, Azure Virtual Desktop or more complex profile requirements should evaluate FSLogix or another profile management tool.

How to deploy a roaming profile

Before deployment, IT should decide whether roaming profiles are still the right profile management option for the environment. For newer virtual desktop deployments, nonpersistent desktops or Azure Virtual Desktop, FSLogix profile containers might be a better fit.

Setting up roaming profiles tends to be a relatively easy and straightforward process. The first step is to create a share on a file server and to set up the appropriate permissions. Administrators will need full control, and end users -- who will be seen as creator owners -- will require full control over their own profile folders. Users should not have the ability to access someone else's profile folder.

Once the necessary network share is in place, admins can create a Group Policy setting that sets the profile path to the network share that IT created. There are also some other settings that admins can enable at the group policy level to fine-tune the behavior of roaming profiles. This includes folder redirection, but there are other settings related to things like caching or slow link detection.

Editor's note: This article was updated in May 2026 to reflect current Windows profile management considerations, including Windows 11, profile versioning and FSLogix profile containers.

Brien Posey is a former 22-time Microsoft MVP and a commercial astronaut candidate. In his more than 30 years in IT, he has served as a lead network engineer for the U.S. Department of Defense and a network administrator for some of the largest insurance companies in America.