I've seem cross references but no solutions to this in the forums, has anyone encountered and corrected this issue? Note: I intended to use a blend of Win7 and Win XP (32/64) on the domain so hoping to avoid migration which would mean I could not continue to roam between XP machines.
Thanks, migrating servers from 2003 to 2008 for one client is a little hard to justify.
I've downloaded the microsoft whitepaper for supporting XP & Vista clients. From what I've read the Win 7 architecture for roaming is the same as Vista so I'll test it and see how we go.
Question : Would 2008 support blended client architectures out of the box, or would I have to migrate all XP up to Win 7/ 2008, loosing backward compatibility?
I'll update this thread with the findings from the MS whitepaper
lyonrouge: Thanks, migrating servers from 2003 to 2008 for one client is a little hard to justify.
I've downloaded the microsoft whitepaper for supporting XP & Vista clients. From what I've read the Win 7 architecture for roaming is the same as Vista so I'll test it and see how we go.
Question : Would 2008 support blended client architectures out of the box, or would I have to migrate all XP up to Win 7/ 2008, loosing backward compatibility?
I'll update this thread with the findings from the MS whitepaper
I havn't tried the microsoft whitepaper, so keep us posted.
Yes Windows Server 2008 supports XP clients aswell as Vista / 7, I am unsure about 2000 and earlier tho but I presume so.
Downloaded and installed "Remote Server Administration Tools for Windows 7", enabled Group Policy Management and edited teh "Default Domain Policy" for "Folder Redirection" and applied the changes as per the Microsoft whitepaper "Managing Roaming User Data Deployment Guide.doc". the redirection worked for everything except Application Data. Win 7 wants to use AppData causing "%userprofile%\Application Data" to not resolve. I'm assuming this is the root cause of being signed on with a temporary profile, but I'm continuing the investigation.
had to do the same for XP existing profile and, oddly enough, empty the trash. The redireect makes the synchronisation transparent and showed a file lock when processing $RECYCLE, so emptied recycle and fixed that.
it just get worse and worse. Win7 writes redirect files that XP cannot delete. Win7 writes files that even it can not delete. Desktop exists twice. I can see why not a lot of business have made the changed, what a drama.
Roaming profile was such a good feature in XP but Vista / 7 it's catastrophic.
lyonrouge: Thanks, migrating servers from 2003 to 2008 for one client is a little hard to justify.
I've downloaded the microsoft whitepaper for supporting XP & Vista clients. From what I've read the Win 7 architecture for roaming is the same as Vista so I'll test it and see how we go.
Question : Would 2008 support blended client architectures out of the box, or would I have to migrate all XP up to Win 7/ 2008, loosing backward compatibility?
I'll update this thread with the findings from the MS whitepaper
I havn't tried the microsoft whitepaper, so keep us posted.
Yes Windows Server 2008 supports XP clients aswell as Vista / 7, I am unsure about 2000 and earlier tho but I presume so.
Blending Win XP (Roaming Profiles) with Win 7 (redirect) with Server 2003 DC has been a cataclismic disaster. Before I rebuild the domain with 2008, can anyone confirm (from first hand experience) that this will resolve the issue and allow Win XP roaming profile and Win 7 redirect to work together, i.e. not just some users on XT and some on 7, but the same user going between the two?
ps. is there any way to get the Win 7 redirect "enhancement" to work like roaming profile, i.e. not write to the server when users are working on their desktop? Perhaps I can decommission the Win 7 client and try to repair the roaming profile, but I suspect I've gone to far to get rid of it.
Twitter »
Follow us to receive Twitter updates when new discussions are posted in our forums:
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
