|
Posted by Roger Abell [MVP] on December 19, 2006, 1:12 am
Please log in for more thread options
Hi B,
Some of your post I could not follow too well.
You say this is happening, rather failing to happen,
when started by login script.
In general there are only three or so things that
can go wrong.
1) does the account (that logged in) have permission
to the remote file (share and ntfs levels)
Note: for login access is as the user, so grants to
Domain Computers group is not needed
2) does the account have permissions to write a new
or modified copy to where it attempts to copy file
3) is networking working so that remote share is
available for the copy
I would not have the shared file/folder/share set as
you have described - with Everyone Full, as that is
asking for problems. Authenticated Users (which
effectively includes Domain Computers although as
said this is not needed) should be enough when set
to Read if all that is happening is a copy.
>I use log on script that copy one file from cluster share to local
>computer.
>
> These is first time that I stumbled with access deny error. At other
> customers a did not hat that kind of error.
>
> Permissions on share is Domain computer , and Authenticated user and
> Everyone Full control. Same is on security permissions, and I check on
> file that Domain computer has full control included file that it copy
>
> A did not change anything on AD, when I implemented solution. But at these
> customer, they have high security environment, and they probably change
> something on cluster. I thing that, because domain admin, does not have
> permission to manage cluster, so thay probably change something. I can
> differently implement script, but, I would like to make it work as
> computer log on screen.
>
> Script work, if I run it as administrator, I did not cachet it if it run
> as regular users, because it copy files on Windows\system32 directory, and
> user does not have permissions to write there.
>
>
>
> On computer I set up domain computer to have full control under windows
> directory, but no help. Problem is on file share on cluster.
>
>
|