Startup Script create files on network

[BoomStick]

Hey all,

I was wondering if anyone knows what permissons need to be set on a network
share/folder to allow a startup script to create a file as it is executing.

For example, I like to create a text file for each machine on a folder on my
server that represents if something did or did not happen in the startup
script. I just want to be able to record those files during the startup
script. I know the script that creates the files works fine because I can
execute it while I'm logged on and it will create the file. I just does not
do it during the startup script.

Any suggestions you could give me would be most appreciated...

Jared

 

[Chriss3]

System I suppose Startup scripts running under System Account.

 

[Robert Cohen]

actually logon script always run on the permissions of the user logoning on.
It cannot do anything the user can't do on his/her own. So if the user
can't create the folder then the script wont. If the script needs to call a
file, that file needs to be shared for that user.

 

[Chriss3]

Robert Note we are talking about startup scripts here, not logon scripts.

 

[Robert Cohen]

sorry; my mistake; some days my tells my mind reads words other then are
actually written

 

[BoomStick]

Unless I did it wrong, that did not work. The reason I question it, is the
only account on the domain that was called "system" had some sort of weird
icon on it. But I added it to the NTFS permissions and I still don't get a
text file there.

Jared

 

[Chriss3]

The SYSTEM account should work. tell us the steps you take exactly to define
your startup script.

thanks.

 

[BoomStick]

I have a GPO in place that defines the startup script as
LGStartupRedirect.vbs.

That script just calls a script on my machine (startup.vbs). I don't have
change rights to the SYSVOL or NETLOGON directories, so I need to have this
script redirected so that I can make changes whenever I want.

The script that's on my machine DOES execute, because I have a wscript.echo
statement that does pop up before I get the login screen. The scrpt
performs all actions EXCEPT creating that text file on one of my file
servers.

I give SYSTEM change permissions on the folder.

One weird thing I noticed is that when I add "system" to the names for
rights and hit Check Name, it shows the picture of a user with a red arrow
going up. But when I look at the SYSTEM in the permissions window, the icon
looks like a group icon.

I'm also currious... Why is it that I can run setup.exe for office2003
through the login script and it can access my network resource for read, but
when I want to write to a network resource it does not do it.

I just added a file check statement into my script to see if it would be
able to read that particular directory. I said that if computername.txt
existed to pop up a message, and it did not pop up a message. I would seem
that the startup script does not have read or write access to that network
share for some reason.

Weird...

Jared

 

[Chriss3]

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
Permission for the particular share.

How ever I think the SYSTEM account always should have the right to create
files and folder to the local computer.

Share Permission is the problem here I think.

 

[BoomStick]

I figured it out!

Permissions weren't the problem at all. We are using a cluster for data
redundancy. This cluster has an alias assoiciated to it so that if we need
to bring a different server online as the primary, we can do so without
having to redirect everyones shortcuts and drive mappings.

Apparently startup scripts either don't like the alias, or are not going to
to dns to correctly determine the correct location that the alias is
pointing to.

I'm going to have to code my scripts with variables so that if the server
gets failed over to a different one, we can get the scrips back running with
just one modification.

Thanks for all your inputs.

Jared