Windows Screen Saver (password protect)

[GlobalCulture]

We use the screen saver to automatically lock our Windows Server SBS 2003. Unfortunately once locked the macro fails to complete i.e program loads but goes no further. If I turn off the screen saver, macro works perfectly. I dont wish to leave the server exposed logged on as administrator in the open office environment. Please advise.

[Marcus Tettmar]

If your macro needs to simulate a user or "see" windows then it cannot possibly work while Windows is locked. See:

http://www.mjtnet.com/msfaq17.htm

[GlobalCulture]

The post you gave me suggests Autologin was working for V8, then turned off for 2003 from V12.
We have Lite V13.
Are we able to back-grade in order to get this functionality?
Cheers
Peter

[Bob Hansen]

If I recall correctly, AutoLogin was dropped because of some unreliability with the Windows Services. Working one day, and failing the next time.

Just found this posting from Marcus, August 2006: http://www.mjtnet.com/forum/post22578.h ... 28b1f10925

And see his June 2008 very detailed notes here: http://www.mjtnet.com/forum/viewtopic.php?t=4796

So, if you do decide to use an older copy, be advised that it may not perform as you expect.

[Marcus Tettmar]

AutoLogon pre Vista/2008 was little more than a hack that exploited a security loophole. There really was no "proper" way of implementing it short of totally rewriting and replacing Windows' GINA dll (Graphical Identification and Authentication). Yep you had to completely replace it. And when your replacement went wrong? You locked everyone out. Scary stuff. We weren't prepare to go there, and quite likely clients would simply not allow such a big change to Windows anyway.

The workaround was a hack that essentially exploited a security loophole which allowed a system level service to interact with the logon console via the keyboard. Horrible and messy, but it worked. At least it worked with a vanilla out-of-the-box setup. But there were many instances where it just didn't work. Probably due to a combination of the multitude of possible security options companies can use. And more to the point when Vista came along Microsoft plugged this hole and we expected that an XP update would plug it there too (I don't know if that ever happened).

And when Vista came a long Microsoft introduced a proper API for a custom logon experience. A way to create an authentication method which DID NOT remove, replace or modify the standard one. So it was safe, properly documented and reliable. So we made the decision to make use of it, and due to the issues with the old system and the fact that it was not official we stopped providing it.

Yes, you can downgrade to v11 and make use of it but you will be on your own and we will NOT support it's Autologon method. You are free to try it and see if it works but if it doesn't, it just doesn't and we cannot help you with it. It is worth noting that even when we were providing it we had a statement on our site that it was not guaranteed to work for everyone.

So anyway, if you want a downgrade, email support with your license info and we'll set you up with the v11 download. Also if you need v13 functionality, you could install BOTH v11 and v13, use v11's autologon to run a v13 macro/compiled exe. But please remember - we cannot help you with v11's autologon and there are absolutely no guarantees that it will even work.