OS – WINDOWS 2003 SERVER STANDARD WITH SP2
Recently I did an authoratative restore of my active directory. Now I am facing a weird problem. I cannot open and edit any login scripts (under Group Policy) that I could previously do. The login scripts are all saved in the default path of SYSVOL. Interestingly, I can create and save any file extension excepting vbs. Moreover, I can open and edit vbs scripts stored in any other locations excepting SYSVOL.
I tried one simple experiment before doing authorative restore. I downgraded my server to a simple standalone server by removing AD. Then I made a clean install of AD with DNS. Now, I tried to save a a file with vbs extension in the SYSVOL folder. The same problem as above persisted.
Here, I may point out one thing. I had made a complete update of my system using windows update prior to AD restore. (The server was a DC then). Now, I am not sure, if the problem regarding SYSVOL and VBSCRIPT is since the windows update or since the authoratative restore.
One more thing – After the windows update, filesvr.msc (sessions) is not working properly. I am using filemgmt.msc instead.
Editing VBSCRIPTS in SYSVOL and filemgmt.msc works flawlessly in an additional DC in the same domain using the same username. This DC has a real time replicated copy of the SYSTEM STATE.
Any help is appreciated.
