Startup script trouble with group policy

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Was going to post this in the Networking forum but it is 2KServer related.

Here’s the problem, I have a vbs script that I'm wishing to use on a group of PCs through Group policies. I've applied a Start-up script to the GPO that contains the computer accounts but when they boot I get an error stating that the file could not be found or something like that ( I cant quite remember as it was at work). But the script is in the correct place as I can navigate to the sysvol domain.com\policies\GUID folder through the network and double click it. I've also tried placing the vbs file into a share and using the UNC but get the same results.

Do I need to include any parameters for the script? All the script is doing is adding a network printer to the group of PC's. This has been doing my head in this afternoon so any help and ideas would be great.

SimonV

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Is the script accessing resources on another machine ? If so, do the machines have the correct permissions to access those resources ?

 

@ Phil, Yeah it is, but the permissions are correct as I can run the script after loging on the the PC and it works fine???

@Andrew, the script is in the sysvol\domain.com\policies\GUID etc etc folder and I checked that it had replicated between the DC's.

I'll try again today when I get to work. Cheers.

Si

 

When you log on and run the script it is using the logged on users credentials, on startup it has to use the computer account. If the computer account doesn't have permissions to the resources then it isn't going to be able to run. I had similar problems recently when I wrote a script to drag an update from a server when the PC's rebooted.

 

I'm sure I've added the permisions for the computer account but I'm not at work yet so cant check. I'll post later when I get infront of the PC. You never know Phil you might be onto something, it was a long day yesterday I could have added the wrong computer account!! :roll:


Si

 

The exact error I'm getting is:

[code:1:050e2c256f]Script:
\\itsuite\sysvol\itsuite\policies\{623a642c-db6c-4345-91ae-2b26631f7aac}\machine\scripts\startup\printer.vbs
Line: 4
Char: 1
Error: The system could not find the file specified

Code: 80070002
Source: (null)[/code:1:050e2c256f]

itsuite being the domain. The script is connecting the client to a shared printer on another client. Does this need to be run after the startup event, say in a login event?

does the computer account need to be in a certain group to execute the script?

HELP ME!!!!!!!

 

Si, can you post your script?

 

Here goes Phil:

[code:1:019cc178e0]Set WshNetwork = CreateObject("WScript.Network")
PrinterPath = "\\itdept\canons20"
PrinterDriver = "Test Printer"
WshNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
WshNetwork.SetDefaultPrinter "\\itdept\canons20"[/code:1:019cc178e0]

 

Have you tried taking it out of the startup script and putting it in the logins cript?

 

No it might be me thats a bit of a thicko here, explain in simple Andrew

Not yet, I tried using a batch file that called the vbs file but got the same error. I'll give it a go later as I've got called to somthing else now.

Cheers, Si

 

Now I get you, yes its a W2K domain and the users will be using different PC's throughout the building more than one user will use the same PC in this group of PC's. That would mean that I would have to install the printer everytime a new user logs on.

I'm totaly confused now as I've got so many jobs to do and the other tech here is as much use as a chocolate teapot.

My head hurts today, boy do I need a drink.

 

Manually installing the drivers on each PC defeats on of the godsends of having a windows 2000 network, i.e. having drivers download from the print server with no intervention from the admin required.

All you need to do is install the print driver on one server / PC then share it. Your script will work, I have exactly the same configured in Group Policy for 20- 30 print queues on one server. If you set the script up in a login script, add the PC's you want to get this printer into a group and set the security for the GPO to execute for the security group you just created.

The next time a user logs on to that PC the printer will be connected and be the default. The way we have them set up is based on the user not PC. But I guess yours will be for classroom PC's so you'll get a lot of people sat at the same PC's.

 

K, Andrew your spot on, Phils a big boy he won't take it the wrong way.

On a serious note I tried to do this but it didnt work. I set up the shared printer then loaded the drivers onto another PC as local admin. Logged out then back in with a domain account but the printer wasnt there. (could this be that I'd already logged into this PC previously so the printer didnt get carried into the profile?)

What am I doing wrong here. Boy have I had a hard day. My head is totally confused on this, I cant remember when I've done this before how I did it. Well as its the weekend I wont get to do this till monday anyway.