Re: Xcopy not working in startup script

On Oct 3, 6:11 pm, "Richard Mueller [MVP]" <rlmueller-
nos...@xxxxxxxxxxxxxxxxxxxx> wrote:
Slingshotz wrote:
This is driving me nuts and I have not been able to find any answers
on any user group. This is a basic batch file script that I am
deploying through group policy in the startup script to copy
templates
from the server to the local machine. I'm deploying it during the
startup so that every computer gets it, regardless of who logs in.

=========================
if NOT exist "C:\Templates" md "C:\Templates"
pushd "\\servername\Templates\"
xcopy *.dot C:\Templates /Y /D
popd
=========================

The script works perfectly when run by itself, but during the startup
script when a computer starts up it keeps saying that *.dot is not
found.

=========================
File not found - *.dot
0 File(s) copied
=========================

When I replace the xcopy with a regular copy command, it works during
startup but I need to only copy the files when there are newer
templates on the server and thus have to use xcopy.

I have confirmed that the computer has permisisons to copy from the
server share (it obviously works as the copy command works). I have
also tried it without the pushd commands to no avail, i.e.

=========================
if NOT exist "C:\Templates" md "C:\Templates"
xcopy \\servername\Templates\*.dot C:\Templates /Y /D
=========================

The error message is the same, it says file not found. And I have
confirmed that xcopy is working on the target machine. Like I said,
it works fine on it's own, but when deployed through group policy it
won't copy the files (but it makes the folder ok).

Any suggestions would be greatly appreciated as I've burnt many hours
trying to figure out this silly little problem.

I am not familiar with pushd and I cannot explain why copy would work when
xcopy does not. However, 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".

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab -http://www.rlmueller.net
--- Hide quoted text -

- Show quoted text -

That was one of the first things I did was to add the Domain Computers
group to the share to be able to read. I even tried granting Everyone
to have read rights to the folder just to make sure it wasn't a
permissions issue. All pushd does is map a temporarily drive letter
for the UNC path and set that drive letter as the current working
drive. I found that suggestion when trawling around on the groups as
I thought it might have been a UNC issue with the dos window.

I forgot to mention that the script I am trying to run it on is a new
XP Pro computer (on the domain) with a 2003 domain controller, so it's
not a really strange setup.

.

Relevant Pages

  • Re: Startup Script create files on network
    ... You have to seen the difference between Share Permissions and NTFS Security, ... My advice here is to give the SYSTEM account Full Control at the Share ... > That script just calls a script on my machine. ... > that the startup script does not have read or write access to that network ...
    (microsoft.public.win2000.group_policy)
  • Re: Active Directory Computer Attributes
    ... I had grant permissions to Domain Computers to write all properties for all ... If I use a startup script to update the comments attribute, ... the computer object should have rights ...
    (microsoft.public.scripting.vbscript)
  • Re: Deny _WRITE_ access to a file
    ... > trying to talk about was a STARTUP script (if I'm not mistaken, ... > script runs as BUILTIN\SYSTEM). ... If it is possible to script a permissions change such that the ... folder remains read/write for everyone except for the restricted group who ...
    (microsoft.public.windows.server.security)
  • Re: Deny _WRITE_ access to a file
    ... > trying to talk about was a STARTUP script (if I'm not mistaken, ... > script runs as BUILTIN\SYSTEM). ... If it is possible to script a permissions change such that the ... folder remains read/write for everyone except for the restricted group who ...
    (microsoft.public.security)
  • Re: Deny _WRITE_ access to a file
    ... > trying to talk about was a STARTUP script (if I'm not mistaken, ... > script runs as BUILTIN\SYSTEM). ... If it is possible to script a permissions change such that the ... folder remains read/write for everyone except for the restricted group who ...
    (microsoft.public.win2000.security)