Vista and Login Scripts

[panda]

Hi,

Wonder if someone can help with the following

I have a GUI login script compiled as an exe which runs from a GPO on an OU. This part works fine.

The problem is that the login script when run under windows Vista does not appear. I can tell the script runs from the log files it creates, but the GUI side of the script does not appear.

If run from within Vista the script appears and functions as it should do so its not a problem with the script.

The GPO settings that I previously used on Windows XP machines that worked fine and loaded and displayed the script before loading the windows interface were as follows :-

Computer Config - Admin Templates - System - Scripts - Run Logon Scripts Synchronously

Computer Config - Admin Templates - System - Group Policy - Group Policy loopback procesing mode (replace)

Any suggestions would be great.

[thevistaman]

have you tried running telnet main?

[jdobiash]

I too, have had woes dealing with login scripts and Vista. I also run my scripts in sync and have the last thing it does is display a "Welcome Disclaimer" window where the user is required to click OK before it loads the desktop. Works great with XP, as you mentioned, but going to Vista they've changed the security model where the GPO runs outside of the normal user 'session' now, even when running user login scripts. So my result was, I could hear the "Welcome" screen appear (it beeps when it shows up), but it would sit there for about 20-30 seconds, then finally another 'Session' would come into view with the welcome screen. I wish I could find a way to speed this process up. My other login scripts work fine, but this one where it asks for user input seems to be the culprit.

My solution, so far, has been to modify the script so then when it runs on a Vista computer it puts the "Welcome Disclaimer" in the RunOnce registry key in HKLM so it runs after Explorer loads. I personally don't like it but it at least keeps it from holding up the computer for that extra time.

[reparg]

Hello Panda,

i have similar problem as you. I'm using Logon Box 2.3.0 from pcSupportNetworks with displays GUI with progress bar during executing scripts. This works with Windows 2000/XP but not with Vista.
Some kind of workaround is using Wscript.Echo in scripts but user have to press a key, which is annoying.
Unforunately Wscript.Popup is also not working.

Have you found any solution?

Regards,
Grega

[PreviousPoster]

I too have the same problem, please let me know if anyone fine a fix.

[Babscoole]

Don't know if it will help or not, but here's what I just went through for mine.

My logon script uses a small web page to display output on. Things such as letting the user know what drives and printers the script had just mapped for them, groups that the user belongs to, and the date of password expiration.

The first time that it tried to run, the web page went full screen, no data was written, and nothing was mapped (drives or printers). What was happening was that the script was hung at the very first query for external data, keeping the rest of the script from executing. Here's why..... The script and consequently web page were being pulled from SYSVOL on a domain controller, IE correctly determined that the page was coming from another machine within my subnet, so categorized it as an Intranet Site. With Vista, by default, Protected Mode is turned on for the Intranet Zone. This has the effect of sandboxing the page. There were two solutions that I found for this. The first was just to turn off protected mode for the Intranet Zone. I didn't care much for this solution as it breaks part of the Vista security model. What I wound up doing is adding my DC's (home of the SYSVOL) to the Trusted Zone through a GPO (the syntax is file://<Machine name&gt.

Now, my logon script UI was displaying correctly, drives were mapping, but the prints weren't being mapped correctly. They would show up in the printers control panel applet, but would not work and would give errors about the drivers. In diagnosing this issue, I found out that I couldn't install these network printers manually either, even as an admin with elevated rights. What I had to do to make this work is to configure the group policy settings for Point & Print Restrictions to tell Vista that my print server was OK to automatically install drivers from (Important: must be specified as FQDN, just the machine name won't work) and that it was ok to install with no user notification/interaction).

Now it all seems to be working ok. Hope some of this might be useful to those of you having problems.