Group Policy Processing Oddity
Anyone seen this before: Machine: Windows 7 Pro, 64bit. Domain: Server 03. Machine and user on domain with gpo's applied. One policy is higher level with mapped network drives via a called vbs script...works fine. Lower level (department level) mapped network drives called by another vbs script...also works fine. Add the domain user to local machine administrator's group and mapped network drives no longer work. GP results show the policies and scripts being processed, but no drives are available. No errors in the log files. Remove the user from the local admin group and the drives re-appear at next login. Any ideas?
November 3rd, 2010 7:36pm

Had a similar issue last week http://technet.microsoft.com/en-us/library/cc766208(WS.10).aspx Was the answer!
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 8:15pm

Aidan, So, I am going to assume you mean the section (out of this enormous doc) regarding launchapp.wsf?
November 5th, 2010 12:03pm

Yes, sorry....was late at night when I spotted your post....clearly too late!
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 12:11pm

Will give it a try. All of our GPO scripts run from the policy location (to maintain a more secure policy processing envirinment), not a network share as they state here: 1. Copy the logon script and the launchapp.wsf script to a network share. Do you know if that matters? Additionally, do you know if this is resolved if the Win7 boxes are added to a server 08 domain, or will we need to use this launchapp.wsf there too? Thanks for your help.
November 5th, 2010 12:56pm

Setup the launchapp.wsf script but two critical things I notice... 1. At login, a pop up window prompts the user to run the task. User hits the "Ok" button, is prompted again that the task has run. 2. The more critical one, no mapped drives show up. Any other ideas?
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 6:32pm

Finally found the answer: http://support.microsoft.com/kb/937624/en-us?p=1 Once I enabled the registry key mentioned in the above link (apparently it "may" make the system less secure as Microsoft does not recommend it), IT WORKS! So, why has Microsoft created such a cluster%$*&#($ around the LSA tokens in Windows 7? Something as simple as mapping network drives for domain users who are also local machine administrators should be a scenario that Microsoft encountered in their strategic planning of building out Win7 !!
November 5th, 2010 7:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics