Hi Using Windows 2008 R2 64bit and trying to get the task schedule to start up the cmd.exe but it's not working, I can see it running but no cmd windows will show on the desktop, I have changed the trigger /run if not logon, run as admin settings etc. and it's showing running but it's just not popping up the dos windows, path is in Windows\system32\cmd.exe. I am trying to run another .exe program since it's not working I thought I will try the cmd.exe dos windows.
I have also tried the same thing on a windows 7 machine with the same result, why is it not popping up? any ideas? If I can get it to pop up I know it's working and I can use it to start another .exe file.
Thanks
You have to use "Run only when user is logged on" for a task to run interactively. Also make sure the Hidden checkbox is not checked on the General tab. Tony
But it should work with the option run if user is logon or not.
If I manually run it, it shows it's running but nothing pops up.
Windows 7 and Windows Server 2008 both do not support services or programs running in session 0 to interact with the user. This is because of session 0 isolation. Because the task scheduler service (like most services) runs in session 0, it will not interact with the logged on user. Even if it is set to use the user's credentials, it will not interact with the desktop session. Older services can get around this limitation if the Interactive Services Detection Service is enabled (it is disabled by default). This may work for what you need to do, but services running from the command prompt or non-GUI services will not trigger the detection, so your mileage may vary depending on what you are ultimately trying to accomplish. You can check out all of the details about the Windows Service Hardening that occurred in Windows server 2008 and Windows Vista here.
Let me know if you have any questions.
-----
IT Desktop & Network Consultant - MOS Master Certified, MCP, MCSA, MCITP - Windows 7, CCNA Certificate Pending, A+, Network +::geek::
It's just a WOL.exe program than needs to be running and it has a schedule in it to start the machines, if I manually run it, it will pops up and if I leave it on until all the schedule are done the machines will turn on then I can close it. Before I had it running on our Windows 2003 server and it pop up and closed after say 60mins. Now for some reason it won't pop up since we upgraded the main server to 2008, I still have the 2003 server on the network but I have not raise the functionality yet. So I tried to moved the task schedule to the Windows 2008 server but it does says it's running but nothing pops up. I have tried to enabled the interactive service detection but still nothing pops up. What can I do?
Thanks
Kiwi_hk, Does the program need any input from you or does it just sit there and send out the magic packets at a certain time?
Does the program close automatically once all of the computers have been turned on or do you manually have to close the program window?
My suggestion if it does not require input but needs access to the network is to run it as a scheduled program like normal using the Network Services account. This will allow it access to network resources. It still will not pop up any window as it sounds like it may be a DOS or command prompt based program only, but as long as it requires no input, this is fine. The only downside is that you will not be able to monitor the normal program window that you would see if you were to run it from within a regular user account.
The other option is to look into a newer version of the program that is compatible with Window 7/Vista/2008 and that has a full GUI or a built in scheduler.
-----
IT Desktop & Network Consultant - MOS Master Certified, MCP, MCSA, MCITP - Windows 7, CCNA Certificate Pending, A+, Network +::geek::
Basically the program don't need any input and it usually close itself after the task schedule ends, I can set it to 1 hour, but the problem is the program don't start up the machines even the task says it's running and no windows pops up, if I just manually open the wol.exe program it will start the machines so I think wol is not running at all with the task schedule.
They key here is to make sure that the task runs using the Network Service account on the server, not using the Administrator or System account. It will not have the proper access to the network unless it runs under the correct account. -----
IT Desktop & Network Consultant - MOS Master Certified, MCP, MCSA, MCITP - Windows 7, CCNA Certificate Pending, A+, Network +::geek::
so how do I do this? I have tried running the task with local administrator of the DC and can only use "run only when user is logged on" since the other options are greyed out but it works with the wol popping up.
I have tried running the task with domain administrator and I can choose run whether user is logged on or not and nothing pops up.
I have tried running the task with network service account selected which it didn't work since the options are greyed out but run weather users is logged on or not is selected.
Quote -- "I have tried running the task with network service account selected which it didn't work since the options are greyed out but run weather users is logged on or not is selected." I don't understand what you mean here? What options were greyed out? It should list the options that are shown in this picture. The settings you see in that screenshot are what should be used.
Let me know if you have more questions or if you still are unable to get it to work.
-----
IT Desktop & Network Consultant - MOS Master Certified, MCP, MCSA, MCITP - Windows 7, CCNA Certificate Pending, A+, Network +::geek::
When I choose Network Service the options for both "run only when user is logged on" and "Run whether user is logged on or not" are grayed out. My one don't have the NT authority/network service, just network service when I choose the account. We are using 64bit Windows 2008 R2 server.
