General discussion

Locked

NT Workstation Security Issue..Need Help

By mshossain ·
My project, windows AT Scheduler will run a job at a specified time while the NT Workstation is "locked" by local user or admin.

Purpose:
1. Windows AT scheduler will run the first program on time.
2. First program then start the second program and put ID and Password at the login box of second.

The problem I am facing with the "Locked" condition:
3. The first is not able to put the Id and Password at the login box of the second.
4. As a result second does not get started.

Exception:
5.But If the Workstaion is "unlocked" everything works just fine.

Question:
1.Why is it doing like that?
2.Is it because of security issue with NT Server 4.0?
3.Can any one give me any suggestion?

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NT Workstation Security Issue..Need Help

by maxwell edison In reply to NT Workstation Security I ...

The article found at this link may be some help to you.

http://www.ntsecurity.net/Articles/Index.cfm?ArticleID=21947

(REMOVE SPACES from the pasted URL)

Maxwell

Collapse -

NT Workstation Security Issue..Need Help

by mshossain In reply to NT Workstation Security I ...

The article did not give me any info that I needed.

Collapse -

NT Workstation Security Issue..Need Help

by mshossain In reply to NT Workstation Security I ...

The article did not give me any info that I needed.

Collapse -

NT Workstation Security Issue..Need Help

by Ken Wolf In reply to NT Workstation Security I ...

You might change the Start Up properties for the Task Scheduler service. Select Log On As "This Account" and choose an account that is a member of the administrator's group. You would want to check the User Rights of the account also to make sure their account can "act as part of the operating system"

Good luck,
Ken

Collapse -

NT Workstation Security Issue..Need Help

by mshossain In reply to NT Workstation Security I ...

Thanks for the answer. I finally figured it out why it was not working. Please see the notes below:

The task scheduler can not perform any "SendKeys" event on NT while the workstation is unlocked condition. The sendkeys feature of Windows Scheduler requires interaction with the desktop. When logged out no desktop is available therefore any tasks requiring keypresses to be sent must be run while the computer is logged in. If no one is logged in, Windows Scheduler Service will still run the application but the application will not receive any keypresses.

The reason Windows Scheduler can not send keypresses when computer is locked, sending keypresses facility need to interact with the desktop in order to function correctly. When NT/2000is locked or logged off it prevents any application becoming the 'foreground' application, which is required if the application is to receive keypresses.

Sendkeys only available, If you have selected "Send Keypresses/Run Task" in Action. Enter any keypresses you would like to be automatically sent to the Window. Note: Normally the keypresses are sent to the window, then the task is run. If you select 'Perform Action if Window Does NOT Exist' the reverse is true - the task is run first and then the keypresses are sent. If you have 'Run Task' set to 'none' then the keypresses will be sent to the window you are watching for. In order to send keypresses to the window it needs to be the 'foreground' window. Windows Scheduler will bring the window to the foreground in order to send keypresses, very occasionally the current foreground window may not relinquish the keyboard focus which will prevent the sendkeys from working.
-Mohammad S Hossain

Collapse -

NT Workstation Security Issue..Need Help

by mshossain In reply to NT Workstation Security I ...

Thanks for the answer. I finally figured it out why it was not working. Please see the notes below:

The task scheduler can not perform any "SendKeys" event on NT while the workstation is in locked condition. The sendkeys feature of Windows Scheduler requires interaction with the desktop. When logged out no desktop is available therefore any tasks requiring keypresses to be sent must be run while the computer is logged in. If no one is logged in, Windows Scheduler Service will still run the application but the application will not receive any keypresses.

The reason Windows Scheduler can not send keypresses when computer is locked, sending keypresses facility need to interact with the desktop in order to function correctly. When NT/2000 is locked or logged off it prevents any application becoming the 'foreground' application, which is required if the application is to receive keypresses.

Sendkeys only available, If you have selected "Send Keypresses/Run Task" in Action. Enter any keypresses you would like to be automatically sent to the Window. Note: Normally the keypresses are sent to the window, then the task is run. If you select 'Perform Action if Window Does NOT Exist' the reverse is true - the task is run first and then the keypresses are sent. If you have 'Run Task' set to 'none' then the keypresses will be sent to the window you are watching for. In order to send keypresses to the window it needs to be the 'foreground' window. Windows Scheduler will bring the window to the foreground in order to send keypresses, very occasionally the current foreground window may not relinquish the keyboard focus which will prevent the sendkeys from working.
-Mohammad S Hossain

Collapse -

NT Workstation Security Issue..Need Help

by mshossain In reply to NT Workstation Security I ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums