start up script not running

[ptotham]

I have a RM CC4 network (which I am new to from a vanilla background) and I am testing deploying out printer via a script rather through the RM Console, I know the script works manually if run it while logged onto the computer, but when i put it in as a startup script under computer - policies -windows settings - Scripts-Startup and then do a gpupdate force and sync and then reboot it wont doesnt map any printers I have script stored on \\domainname\sysvol\domainname\ share but cant get it work, cant run gpresult /r to see what gpo the machine is getting cause I get the message back "INFO the user "domainname\username" does not have RSOP Data which i havent seen before...

 

can anyone shed any light on this problems please

 

Paul

[ptotham]

right bit of a update the my script is running I added a line to create a folder on C: for testing but it didnt map the printers.

[ptotham]

sorry this should have been posted under windows 7 forum not windows can a moderator or administrator please move this?

[ptotham]

i realised the script should be running at logon not startup so have now change it to run at logon which is does but the printers are still not being mapped???

[Foresthippy]

When you run the script manually, does it run and work without any interaction?

[bossman]

@ptotham

 

Why are you trying to do this using a script when there is a perfectly good tool in the RMMC for allocating printers?

 

Install the printer on your print server as a local printer, give it a static IP then when it is installed with the proper drivers share it and wait for it to come into the console then attach it to the computer or room OU and voila! job done. If you use printer credits then its a couple of minutes wait until you can apply credit details.

 

So easy and it works so well, its what the console has been designed to do

[ptotham]

@ptotham

 

Why are you trying to do this using a script when there is a perfectly good tool in the RMMC for allocating printers?

 

Install the printer on your print server as a local printer, give it a static IP then when it is installed with the proper drivers share it and wait for it to come into the console then attach it to the computer or room OU and voila! job done. If you use printer credits then its a couple of minutes wait until you can apply credit details.

 

So easy and it works so well, its what the console has been designed to do

 

at the moment we have to many printers and to many groups in the rm console we are scaling back and a script is a easier way than having to map printers the rm way. I have managed to resolve the issue now the RM Delivery Station is removing my printer mappings cause I haven't set any printers in my test group in the RM console