Quote:
Originally Posted by Harv
it is common for scripts to work when you run them but not as a Startup script. When a Startup script runs there is no user. Startup scripts run with System privileges on the local computer, but with the permissions of the computer object elsewhere in the domain. The most likely cause is that the computer object (computer domain account) lacks permissions in the share. If all computers need permissions, you can grant the permissions to the domain group "Domain Computers".
Also it may be worth adding the actual filename to the end of the copy command as scripts like completeness.
One other thing is where are you deploying it in the gpo - user config or machine config and have you got the gpo running both types of script ( you can be selective so check whats selected ).
|
its under the Machine GPO
i currently have all the computers in a nice tidy GPO but all these stupid new requests are going to do my head in if i cant start pushing files out
i have managed to do a registry key via the machine GPO which seems to work fine
i will put the full address on the end of that sapdoc.ini file and see what happens
also the 'domain computer' permission is that located in the GPO for access or somewhere else
attached is the overview of the GPO