Startup script uses the machine account not user, there for the machine may not have the sufficent rights to access that location. That's why it's a good idea to place the batch file(s) in the sysvol location.
I have created a GPO that installs PestPatrol from a .bat file located on a network share (Everyone has Read and Execute rights) and have it linked to a subOU within our Resource OU. I have another GPO that runs a PestPatrol scan from a .bat file located on the same share. I have placed a computer account in the subOU and it works just fine at my location. However, when I add a computer account that is located in another building within a separate subnet, I get an Event ID 1000 "The network location cannot be reached." Both computers are Windows XP and are members of the same domain. Any ideas why this might be happening?
Thanks in advance,
Susan
Startup script uses the machine account not user, there for the machine may not have the sufficent rights to access that location. That's why it's a good idea to place the batch file(s) in the sysvol location.
I don't think the Domain Admins will let us put our bat files in the sysvol folder. They just recently allowed us to create our own GPOs.... Hmmm, I'll have to keep working on that one.
Thanks for the quick response.
You could create a new global group, then add all your computer accounts to it. Then add that new security group to that folder. That should ensure the machines have sufficent access.