network script in startup folder fails to run

[SilloSyben]

Hi,

I recently inherited a Windows 2000 automated install that is having trouble running a VB script (link to a script on a network share) from the startup group when the machine reboots. The script uses case statements to install some apps and hotfixes in a particular order, shifts case and reboots. When the machine comes back up, it auto logs in and runs the script again until it runs out of software to install (5 cases).

The problem occurs when the machine reboots and auto logs in, it attempts to run the link in the startup group and I get an error stating something to the effect, the \\FULL_PATH_TO_SCRIPT is not available. Seconds later, I can click start/programs/startup/SCRIPT_NAME and it runs fine. When it reboots and runs the next case, I get the same error.

I've been thinking it was the script running before the machine could grab a DHCP IP address so I put a 10 second sleep using "run" in the registry. That didnt help because while the machine was sleeping, it tried to kick off the link.

I'm looking for one of several things. Has anyone else encountered this behavior With Win2K/SP4 and been able to attribute it to a post SP4 hotfix? If it's a known Windows problem, I'd prefer not to change the scripting flow already in place and fix Windows. If not, can someone recommend a good way to approach this elusive problem? I'm not opposed to using RunOnceEx to access the script over the network. I do have a sneaking suspicion that running a link to a network resource vs. calling the script from a batch file on the local disk is the problem.

Any tips would be greatly appreciated.

[ravashaak]

Hmm. Ya know...I once had a somewhat similar issue and it wound up being the permissions on the network share. My script ran under SYSTEM context since it was defined as a startup script through a GPO. However, since the share didn't have proper permissions for that computer (in my case, the "domain computers" group), the resource was unavailable and the script would bomb. My user account had proper permissions and could invoke the script manually and it would run successfully.

I'm not sure if the above applies to your situation. I guess it would depend on how your script is invoked at startup

- Ravashaak