Windows 7 Problems - Ideas needed

[BABVA]

Hi all,

 

I have managed to get WDS installing Windows 7 via a couple of key presses and am pleased for that. I have been scratching my head why things arent happening as they should be after the install. It turns out that 2 of 3 gpo's are running but the one created for the testing of modifying Windows 7 isnt running (gpresult /r). I have some questions if I may?

 

Ho

• How do i get the required policy to run? It should do folder redirection and changes to startmenu (gui stuff really)
  
• Is RSAT required to be installed to the Windows 7 client pc for GPO's to run?
  
• We have 1 2003 DC with schema and 2 2008 DC's - would this cause a problem? (The 2003 holds most FSMO)
  
• The only GPO templates I can find for Win7 are adml files which I can't import as a GPO. (have discovered that they live on the client pc)
  
• Do the ADML files need to be installed (RSAT for example) to the DC's? (The GPOs are processing from a 2008 DC & not the 2003)
  

 

Any help would be great, thanks.

[BABVA]

After a change of scenary & some thinking from a different angle I have solved most of my problems and have GPO's running and doing most of what I want. Not sure if I need answers to the questions any more but feel free to answer them if you think it would help for my understanding.

[SYNACK]

1. Forler redirection of documents and the like require the user to the be the owner of the folder that you are redirecting to, to force the policy to apply use gpupdate /force /boot and then use the RSoP snapin of MMC to see what has been applied, check the eventlog for any specific errors.

2. The RSAT tools are only needed to edit the policies not to allpy them.

3. No problem there, as long as the schema has been updated to 2008 if your 2008 boxes are DCs

4. The ADMX format is the new one for Vista and above, these need to be edited by a compatible editor like the RSAT one or the one under 2008.

5. The ADMX files do not need to be published on the server for them to work as the GPO settings are stored as a raw blob of registry data that does not rely on the templetes being present. You can put these files on the server centrally by creating a PolicyDefinitions folder somewhere in sysvol and adding them there but it is not required.