> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-fslogix-containers-best-practices/v21/overview/roaming-user-profiles.md). # Roaming User Profiles This technology was introduced by Microsoft more than 20 years ago. With Roaming User Profiles, the local profile is transferred to a network location so that a user can access it on multiple machines. The disadvantages of this approach are: * Slow login. Large roaming profiles take a long time to download, and sometimes users may need to wait more than a minute, depending on the profile size. * Slow logoff. A roaming profile needs to be uploaded back at logoff, and if this process is interrupted (for example, due to a network failure or power outage) the profile can be corrupted. This results in the creation of a temporary profile and the help of an IT specialist may be required to address the issue for the affected user. * Folder redirection creates a large amount of SMB traffic between the desktop and the file server. Each request to a file is treated as a new connection. * Every issue described above will also result in increased consumption of network resources. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.parallels.com/landing/ras-fslogix-containers-best-practices/v21/overview/roaming-user-profiles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.