Cannot edit logon script propertie (wrong path c:\windows\.. instead of sysvol path)
- When I want to modify a logon script (GPMC.MSC), the show files option show a wrong path. Instead of Policies\{22..), it shows C:\Windows32\System32\GroupPolicy.
The Logon script runs correctly for users, and on other domain controllers, I can change the GPO. The GPO is synchronized correctly. My only concern is that I can't modify all logon scripts GPO on 2 domain controllers.
Answers
Hi,
I understand that when trying to modify a logon script, the Show Files option shows a wrong path: C:\WINDOWS\System32\GroupPolicy.
Normally, for a domain GPO, the correct path for Show Files should be: \\server\SysVol\domain\Policies\{GUID}\User\Scripts\Logon. For a local group policy, the path is: C:\WINDOWS\System32\GroupPolicy\User\Scripts\Logon
So, please first make sure the group policy you edit is a domain GPO.
If you are editing a domain group policy, I am afraid that this group policy object is corrupted and the Group Policy Template location recorded in the Group Policy Container is wrong.
Let’s follow the steps below to check the gPCFileSysPath attribute for the GPO.
a) On the problematic DC, run "adsiedit.msc" to open the ADSI Edit MMC.
b) Locate the GPO in
Domain--->DC--->CN=System--->CN=Policies--->CN=<GUID>--->Right click--->Properties.
c) Check whether the gPCFileSysPath is properly pointed to the \\server\SYSVOL\domain\Policies\<GUID>\ instead of C:\WINDOWS\System32\GroupPolicy\.
Please note that if the gPCFileSysPath for a GPO is pointed to an incorrect location, the whole GPO is corrupt and will not be processed.
If it is not \\server\SYSVOL\domain\Policies\<GUID>\, please recreate it to check the problem continues.
If the issue persists or you are not clear about it, please collect the following information so that we can perform further research on this issue:
1. Does this issue exist for all group policies or just some specific ones?
2. Please create a new domain group policy and configure a logon script. Is the file path correct for the newly created group policy?
3. Please collect MPS report for further research:
1) Download proper MPS Report tool from the website below.
Microsoft Product Support Reports
2) Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", "Server Components", click Next.
3)After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.
Regards,
Bruce
- Marked As Answer byBruce-LiuModeratorMonday, November 23, 2009 6:43 AM
All Replies
- I think C:\Windows32\System32\GroupPolicy is the location where the script was stored originally. You can edit the gpo and change the path.
Isaac Oben MCITP:EA, MCSE - Thanks for your reply, but this path was never used. I have hundred GPO for login scripts and for all, it shows me C:\Windows32\System32\GroupPolicy. But again only on 2 domain controllers. On the other, every thing is fine.
Hi,
I understand that when trying to modify a logon script, the Show Files option shows a wrong path: C:\WINDOWS\System32\GroupPolicy.
Normally, for a domain GPO, the correct path for Show Files should be: \\server\SysVol\domain\Policies\{GUID}\User\Scripts\Logon. For a local group policy, the path is: C:\WINDOWS\System32\GroupPolicy\User\Scripts\Logon
So, please first make sure the group policy you edit is a domain GPO.
If you are editing a domain group policy, I am afraid that this group policy object is corrupted and the Group Policy Template location recorded in the Group Policy Container is wrong.
Let’s follow the steps below to check the gPCFileSysPath attribute for the GPO.
a) On the problematic DC, run "adsiedit.msc" to open the ADSI Edit MMC.
b) Locate the GPO in
Domain--->DC--->CN=System--->CN=Policies--->CN=<GUID>--->Right click--->Properties.
c) Check whether the gPCFileSysPath is properly pointed to the \\server\SYSVOL\domain\Policies\<GUID>\ instead of C:\WINDOWS\System32\GroupPolicy\.
Please note that if the gPCFileSysPath for a GPO is pointed to an incorrect location, the whole GPO is corrupt and will not be processed.
If it is not \\server\SYSVOL\domain\Policies\<GUID>\, please recreate it to check the problem continues.
If the issue persists or you are not clear about it, please collect the following information so that we can perform further research on this issue:
1. Does this issue exist for all group policies or just some specific ones?
2. Please create a new domain group policy and configure a logon script. Is the file path correct for the newly created group policy?
3. Please collect MPS report for further research:
1) Download proper MPS Report tool from the website below.
Microsoft Product Support Reports
2) Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", "Server Components", click Next.
3)After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.
Regards,
Bruce
- Marked As Answer byBruce-LiuModeratorMonday, November 23, 2009 6:43 AM
