Prog DOESNT RUN from NETWORK on startup

Using a win2k3 server and winxp pro clients.

We recently had a change in our network, but before that there were no problems like this.

I have an entry in the registry under Run- \\server\path\prog.exe (one of the startup directories)

If I type that path and try to run it, it works fine. I'm thinking it's a connection issue.

The PC isn't getting a network connection fast enough, but it still tries to run the program before that, and of course, it fails.

Is there any easy way to delay the startup of my remote program? I already realize that I could make a program that waits for a connection and then looks for that path, but I really dont prefer to do it that way.

In the policies, there is a policy for Wait For Network or something similar, enable that for the computers and restart them. I can't exactly remember where it's located but I'll have a look for you tomorrow. That should get you going again.

You could try something like this :

Code:

---

:loop
@if exist "\\server\shared\prog.exe" goto found
@goto loop

:found
@start "\\server\shared\prog.exe"
@exit

---

And perhaps also a counter to check the number of iterations its gone through already...

thanks guys.



You think it's something like this:
To turn off Fast Logon Optimization, you can use the following policy setting:

Computer Configuration \ Administrative Templates \ System \ Logon \
Always wait for the network at computer startup and logon


http://msdn.microsoft.com/library/de...timization.asp
?

It sounds right, but who knows :D And I personally can't test it right now. 'Have to wait until my work opens.

Yeah, that's the one i was referring to.