I'm attempting to integrate my first Vista Business install into my Windows Server 2003 environment. My company uses roaming profiles. The client I'm upgrading is my last Windows 98 user, so they don't have an existing profile to worry about merging. I've set the account in the AD to use our default profile path. The folder that contains the profile has the administrators group as the owner with Everyone granted full access to the share and NTFS permissions.A folder <user name>.v2 gets created in the profiles folder, but it is blank. No other folders are files are copied into it.In my GPEdit.msc I've set the following attributes: Do not check for user ownership of roaming profile folders = enabledPrevent roaming profile changes from propogating to the server = disableOnly allow local user profiles =disableAny noticeable reason nothing is being copied into this profile?

Hey JMTrout, I also had this problem with Windows Vista when I first started integrating it into our systems. The solution that ended up helping us was to create a template of the profile, or to first set the profile as a local profile in AD, log the user in, log the user off, and the set the profile to roaming again. That can get a bit extensive when you are trying to integrate alot of users, so what I would suggest is creating a template. To create a template to be used by the roaming profile service, follow the following steps. 1. Create a user with standard user privilidges. 2. Log in as that user 3. Logoff from that user 4. Login as an administrator 5. Go to the System control applet, and click change settings. 6.Click on the advanced tab, and then click on settings under the user profiles section. 7. On the next window that comes up, click the name of the user you just created. 8. Click Copy To, and fill in the location of where you need the roaming profile create in the Copy Profile To section. 9. Click on change under the Permitted to Use, and type in the username of the user that you want to use it. 10. After that window closes, you should now have that user a template for his or her profile. 11. Attempt to login as that person, and their profile should no longer say that it was not able to load their roaming profile correctly. If this does not solve the problem, I would suggest looking under the System Event Log in the event viewer, and seeing if any log entry from the user profile service is critical. If their is, check to see why it had a fatal error. This should help a lot in trying to solve the problem. Hope this helps!