lanman777
asked on
Roaming Profiles - Replacing Windows XP Pro workstations with Windows 7 workstations.
How do I get my Windows 7 workstations to pull down the roaming profiles I as using of Windows XP PRO?
They are not pulling down to my workstation when I log in.
They are not pulling down to my workstation when I log in.
What I would use is the USMT (User State Migration Tool).
http://technet.microsoft.com/en-us/windows/dd671583.aspx
Hope this helps~!
http://technet.microsoft.com/en-us/windows/dd671583.aspx
Hope this helps~!
Are you running 2003 server or 2008? Windows 7 is not compatible with 2003 roaming profiles. When you have these profiles, unless things have changed, they will not communicate together and on the server, you will see 2 profiles, one for XP, another for 7.
Spec should be correct if you are not accessing from both environments. If you have a mixed domain, you will have issues with the profiles not being the same.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We will have 6 workstations with Windows 7 only for a week. After that we will be migrating our Windows 2003 server to Windows 2008. Will that fix the problem?
ASKER
Yes the roaming profiles are in active directory, but are for my legacy Windows XP proffessional workstations.
YOu should be fine then to just use the migration tool on those profiles.
Are your Windows 7 PC's joined to the domain?
When a user signs in on that domain do they a generic desktop? If so go to My Computer\Users and see if there is a TEMP user. I have run into this here on our network, and I had to log into the system as the local admin, and actually copy the entire profile from our file server to their PC and then once they signed in everything worked.
Let me know how that works!
Thanks!!!
When a user signs in on that domain do they a generic desktop? If so go to My Computer\Users and see if there is a TEMP user. I have run into this here on our network, and I had to log into the system as the local admin, and actually copy the entire profile from our file server to their PC and then once they signed in everything worked.
Let me know how that works!
Thanks!!!
Just to clear up some potential confusion. The server OS does not matter when it comes to roaming profiles, only the client OS matters. So upgrading to Server 2008 will *not* resolve your consistency issues.
Windows 2000 and XP use version 1 of the roaming profile design that MS implemented. Vista and Windows 7 use versoin 2 (hence the .v2 at the end of a folder). Since these are stored in discreet folders, they *can* coexist just fine.
Changes to one, however, will not be reflected in the other. So if a user makes a change on an XP machine, that change will roam to all other XP and 2000 machines, but will NOT be present on any Vista or Win7 machine. And vice versa.
Hope that clears things up a bit.
Windows 2000 and XP use version 1 of the roaming profile design that MS implemented. Vista and Windows 7 use versoin 2 (hence the .v2 at the end of a folder). Since these are stored in discreet folders, they *can* coexist just fine.
Changes to one, however, will not be reflected in the other. So if a user makes a change on an XP machine, that change will roam to all other XP and 2000 machines, but will NOT be present on any Vista or Win7 machine. And vice versa.
Hope that clears things up a bit.
Have you got the roaming profiles setup in active directory?
M@