Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We're planning a migration of several hundred desktops to Windows 7 and hitting a snag in our test lab with roaming profiles. Bit of background:

  • Win 2003 FFL
  • Currently all XP machines
  • Roaming profiles, working fine
  • Win7 test PCs are in Computer container, not in seperate OU so as yet not affected by a myriad of GPO.

We've just started using a few test machines both here in our office and in test. The profile directory is created on the server as username.V2 but contains ALL of the profile, including Local and LocalLow. For many users this consists of many gigs of Outlook cache!

Does anyone have any thoughts? I thought Windows was meant to exclude these dirs by default?

share|improve this question

2 Answers 2

The Local and LocalLow aren't supposed to roam with the user. M$ has said that the data stored in these folders are usually too large to roam. See this:

Word Document

share|improve this answer
Yeah, I've read the articles as well - I know full well that they're not supposed to roam, but they still are. Which is the problem :-) –  George Hewitt Aug 26 '10 at 6:30
Ahh, sorry, I got nothing then. gl –  blsub6 Aug 26 '10 at 20:32

Microsoft likes to do things in certain ways. Maybe the test container for your Win7 is causing this? Maybe there's an implied/embedded/default GPO rule somewhere that you are now bypassing?

Also, have you updated the win2003 server with all the bits needed to support Windows7?

And overall, it might be more cost effective to setup a new Windows 2008 server first.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.