bondbill2k2 Posted June 30, 2011 Posted June 30, 2011 Well ive been given the task of sorting out these windows 7 machines for our network and im "trying" to get them working with staffs XP roaming profiles. I have downloaded the quite informative Vista Managing roaming user data deployment guide which is useful but it says to use the Group policy managment console on the vista client (GPMC.MSC) which doesn't exist on 7. From reading around the net I believe im on the right lines having downloaded and installed RSAT but im not sure where to go from here, the server manager tool says it only suports 2008 R2. Sorry if im overlooking the obvious here but its all a learning curve for me at the moment
bondbill2k2 Posted June 30, 2011 Author Posted June 30, 2011 think you want gpedit.msc ;p Thats what I thought but you only get local computer policy with nothing on redirection
ryanmwalker06 Posted June 30, 2011 Posted June 30, 2011 To download RSAT for Windows 7, use these links: Note that you need to choose either a 64-bit or a 32-bit version NOT based upon the OS version of your servers, but based upon the OS version of your Windows 7 workstation(s). 64-bit version of RSAT for Windows 7 (222.1 MB): http://download.microsoft.com/download/4/F/7/4F71806A-1C56-4EF2-9B4F-9870C4CFD2EE/amd64fre_GRMRSATX_MSU.msu 32-bit version of RSAT for Windows 7 (215.1 MB): http://download.microsoft.com/download/4/F/7/4F71806A-1C56-4EF2-9B4F-9870C4CFD2EE/x86fre_GRMRSAT_MSU.msu Please note that the above links are for the RTM versions, and not for the smaller sized RC versions! id try downloading it again did you def download the right bit version??
3s-gtech Posted June 30, 2011 Posted June 30, 2011 RSAT for Windows 7, install that on a Windows 7 client (specifically, not on the server - you'd buy a Windows Server 2008 R2 licence instead). Then build the policies from there. Ideally, upgrade your servers or add a 2008 R2 DC - you'll be doing yourself a massive favour, and it doesn't have to cost much to do (a 64bit server + S2k8R2 licence can be had for a few hundred pounds). Staff members profiles will have to change - many aspects are not interchangeable between XP and 7 but it's admittedly easier with roaming - they can do both at once.
riffleman Posted June 30, 2011 Posted June 30, 2011 (edited) You need to use the GPMC on your 2003 server. Almost all of the settings applied by a 2003 server are used by Windows 7 Clients. You only use the GPMC on a Windows 7 Client if you need to specifiy specific Windows 7 settings, but as you've already found out, most of those policies also require a Windows 2008 server. Redirection should be configured on 2003 servers in a mixed domain anyway, because Windows 7 has additional options that can really confuse XP redirection. Edited June 30, 2011 by riffleman
bondbill2k2 Posted June 30, 2011 Author Posted June 30, 2011 (edited) RSAT for Windows 7, install that on a Windows 7 client (specifically, not on the server - you'd buy a Windows Server 2008 R2 licence instead). Then build the policies from there. Ideally, upgrade your servers or add a 2008 R2 DC - you'll be doing yourself a massive favour, and it doesn't have to cost much to do (a 64bit server + S2k8R2 licence can be had for a few hundred pounds). Staff members profiles will have to change - many aspects are not interchangeable between XP and 7 but it's admittedly easier with roaming - they can do both at once. We plan to go 2008 R2 early next year although im trying to get this brought forward as it will save alot of hassle, im also tempted to downgrade the new stations to XP for the time being.I think I need to use client side GPMC on 7 to redirect rather then just the 2003 GPMC so I can try and have cross network compatability as users will be going between XP and 7 systems on the same profiles. Edited June 30, 2011 by bondbill2k2
meastaugh1 Posted June 30, 2011 Posted June 30, 2011 I found this helpful: The Angry Technician’s Guide to Managing Windows 7, you Idiots « The Angry Technician
bio Posted July 1, 2011 Posted July 1, 2011 personally i would upgrade the forest & domain first. then migrate your clients. You have many extra options when running a windows 2008 r2 domain in combination with windows 7 clients instead of winxp with 2003 domain. bio..
bondbill2k2 Posted July 1, 2011 Author Posted July 1, 2011 Using GPM on the win7 client really shows some of the useful policys and new features of GP on 2008 and Its far better I can see already, going to try pull forward are schedule of 2008 curric and admin upgrades (we are currently on central active directorys with the LEA who wont support higher then 2003) Playing with the folder redirection now but ive had GPM on this client crash 3-4 times now! Very annoying.
MattyRVBC Posted July 1, 2011 Posted July 1, 2011 I had a similar issue when deploying Windows Visa onto a domain many years ago. The major change being that when using roaming profiles you don't just map the user my documents folder! you need to map all of the users home folders (Pictures, Videos, documents etc). I have RSAT tools running on Windows 7 on a 2003 domain and I have also tested this on a 2000 domain without any issues.
bondbill2k2 Posted July 1, 2011 Author Posted July 1, 2011 I had a similar issue when deploying Windows Visa onto a domain many years ago. The major change being that when using roaming profiles you don't just map the user my documents folder! you need to map all of the users home folders (Pictures, Videos, documents etc). . Just finished doing this for a test OU which ive made some users in, ill test them properly on monday, been busy day tracking down software lists from each department and starting new images on the XP machines
bondbill2k2 Posted July 5, 2011 Author Posted July 5, 2011 Well the folder redirection is working fine between xp and 7 but im having some issues with stupidly long load times. Event viewer for a user logon: "The Winlogon notification subscriber took 444seconds to handle the notification event (Logon)" "Windows License validated" The winlogon notification subscriber was unavaliable to handle a notification event" "The Winlogon notification subscriber is taking a long time to handle notification event (StartShell)" "The Winlogon notification subscriber took 599seconds to handle the notification event (StartShell)"
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now