Hi

I would of thought this would work best using the startup via Start Menu.

Stick a shortcut to your script in

C:\Documents and Settings\All Users\Start Menu\Programs\Startup

on each of your servers. The fact the command resides within the "all users" profile, will, as required run for all users.

Regards, David

Problem being that we need to control principally the administrator/support staff access and the services logons on the file servers. Thus a quick delete or the on console use of the left shift will bypass or erradicate the startup programs execution of such a script/batch file inserted into the startup folder.

The use of a "global" login script is transparent and forced. However local logins and services login does not seem to fall within such a login script configuration. I can add a script for each user but is 80 file servers its maintenance is a nightmare. Like wise the use of group profiles is not possible as some of the services/users do not execute a domain logon to access these servers for maintenance. To further complicate the issue some perform terminal server sessions to access the servers for maintenance or support.

Another problem has arisen to further complicate the issue. I cannot seem to force an interactive logon to run a script. Even if the user is supposed to execute a logon script. It seems that MS does not effect a full logon using interactive mode. Such as running a scheduled task with a user name.