Hi Ziggi, > Did you mean to run the scheduled task as a differnt user (for instance not > as Administrator) ? > > By default there are two users under Win2000: Administrator and SYSTEM. > Will setting the scheduled task under SYSTEM will stop this stupid DOS box > from poping-up - how do you think ? > > Or it's a must to define a separate "dummy" user with necessary privilidges > to run such scripts withou DOS box ?
Some organisations make a (security) practice out of removing the default accounts from all systems. Sometimes a server is left logged in, to either an admin or an 'operator' account all the time. Sometimes consoles may not be left logged-in whilst unattended... The problem arises (as best I can make out) when the script is being run under the same username as the currently logged-in user. That's the only relationship that really matters! Accordingly I set up a script-operator group (as per the printer-operators group), set up a dummy user and made it a member of script-operators, banned local and remote log-ins, and then set up privileges/access to required resources, eg db. Then using an admin account, transferred the necessary 'bits', and set up the scheduled task to run on the server - using the script-operator account/pswd. Such a rigmarole, but at least the console ops are not complaining any more (and how come they only ever seemed to use the console at the same time after the hour that the script was set to run? I reckon there was another 'solution' - change the scheduled time/cycle...) Regards, =dn -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
