Sign in to follow this  
Followers 0
Guest olivier

WinWaitActive doesn't work on restrictive account

5 posts in this topic

Hi,

I have written a script using WinWaitActive which works under an admin account but not under a very restrictive user account.

Moreoften, the timeout value works fine under this restrictive account but not the part which looks at the window title.

I have not yet try to unconfigure each GPO item.

Does anybody have an idea ?

For information, my OS is W2K SP3.

Share this post


Link to post
Share on other sites



Hi,

I have written a script using WinWaitActive which works under an admin account but not under a very restrictive user account.

Moreoften, the timeout value works fine under this restrictive account but not the part which looks at the window title.

I have not yet try to unconfigure each GPO item.

Does anybody have an idea ?

For information, my OS is W2K SP3.

Not one I've heard before :) I can't think of what policy would restrict it either, WinWait only uses a simple and often used API call. How about running AU3SPY on the restrictive account to see what it "sees" (AU3Spy uses pretty much the same code as Autoit)

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

Very restrictive account? Restrictive enough to prevent that account run the window you are waiting for?

I can't think of anything else, I have not come accross this issue before and I am running many scripts with winwaitactive for plain user accounts.

Edited by nobby

CheersNobby

Share this post


Link to post
Share on other sites

Thanks for your replies.

You're right : the GPOs do not affect the script.

I have tried to launch AU3SPY and it works.

Then I have put my script.exe file in the Start menu and now it works.

The problem was that I started the script through the network with psexec (from the pstools of systernals); but I don't know why.

Thank you again. :)

Share this post


Link to post
Share on other sites

Thanks for your replies.

You're right : the GPOs do not affect the script.

I have tried to launch AU3SPY and it works.

Then I have put my script.exe file in the Start menu and now it works.

The problem was that I started the script through the network with psexec (from the pstools of systernals); but I don't know why.

Thank you again. :)

Ah, you might have to give whatever account the process is running "interact with desktop" rights if you want to do send/clicky things. The default system accounts don't have the right.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0