Logon script issue
Ok this has had me scratching my head now.
Recently two scripts have stopped working correctly. They have worked fine previously and to the best of my knowledge nothing pertinent to scripts has been altered GPO wise recently.
The script is running but it seems to be missing out certain parts. In particular the creation of folders. If I manually create the first folder then the drive will map at logon (so script is running)
However the Files folder is then NOT created.
net use T: "\\fps03\CA$\Current\%username%" /persistent:NO
net use H: /delete /y
net use V: /delete /y
net use Y: /delete /y
net use Z: /delete /y
c:\robocopy.exe \\Fps03\CAfiles$\ t:\files /e
If the user runs this batch file from the desktop it runs fine, creation, mapping and copying.
Is this on a machine?
Has this machine got a gig port?
Is the script running before the network is operational on the machine?
Does system and the correct group have the permissions to create this folder?
Normally when I create a user folders are created and permissions set at that time.
Is there anything in the event log?
Is there anything in the rsop.msc?
What happens when you login as a user and run the script in cmd?
@apeo as stated (right at the end of my post) It runs fine.
This was all set up and working just fine until recently. Possibly a WU that has broken something.
Machine -yes, I assume you mean a client PC.
All our machines have 1Gig ports however most just run at 100Mb, including the one I'm testing on beside me.
Permissions were set a while back and the User I can confirm does have permission to create a folder.
Nothing in Event log bar a few errors as it's trying to redirect some folders to the T drive.
Well my group policy results wizard shows the script has been applied and nothing untoward.
Ok so I tested a staff account and the script runs fine. It's not a permission issue but at this stage I'm thinking it's mandatory profile related.
<edit> It is mandatory profile related</edit>
Sorry, didn't read that bit because I thought it was part of you signature :D. Assume your users are on Windows 7, here we've had some funny problems with bat scripts so we generally use vbscripts and/or powershell. Funny thing is sometimes we use vbscripts to launch the shell.