Logon scripts for vista

As a tempory fix i've copied the. I'm guessing there's some new security setting in vista that is preventing these scripts from running. Strange thing is that the logoff script seems to work fine. Anybody else come across or know how to remedy this issue?! Joined Nov 3, Messages My experience with GPO drive mapping login scripts was similar.

Scripts delivered by GPO run with elevated permissions if they are available. The drives were mapped correctly, but only accessible from applications I later started elevated. This is not a problem for regular users, only admins, since users have no-where to elevate to no admin privellages. Let me know if this is your problem and get some more details for you. Both the machines are being used by "regular" users although they are administrators on their local machines.

I've read the microsoft documentation on User Account Control settings but this seems to suggest that normal users should be fine and administrators should see the bat file run but then no drives will be displaye in explorer. This wasn't the case when i logged on to either machine! Thanks Tom. A local administrator would still have the dual credentials situation, so potentially could have GPO scripts running elevated purely a guess I'm afraid.

I suggest you run a simple application, say Word or command prompt, elevated and see if they can see the drive mappings you are expecting. Start command prompt normally and elevated and in each type 'net use' to see a list of network drives. If they differ, then you're probably experiencing the same problems I have.

Seem's your right! When running command prompt as an elevated user i can see the mapped drives. How did you solve this problem!? The fix I found runs the drive mapping script as a 'run now' scheduled task, using the current users' credentials. This on its own doesn't entirely solve the problem because if you start an application elevated, you then also don't get to see the drives- the complete reverse of the original problem.

With this in mind I did a hybrid- if the user is an administrator, run the script normally elevated and as a run now task not elevated. If not an administrator, run the script as normal. Only do any of this if it is Vista. Also bear in mind all other login scripted tasks are also presently running elevated.

He has written more than a thousand articles and has authored or been series editor for over 50 books for Microsoft Press and other publishers. He currently runs an IT content development business in Winnipeg, Canada. Your email address will not be published. But needs to be done on EACH workstation. Not fun for an IT person in a larger company.

Obviously include domain before username if you are on a domain. Dear Troll Did you actually have anything constructive to contribute or are you only capable of insulting others when you have no idea what you are reading. I have acutally learned a great deal from the posts of those that have actually taken the time to read and consider the problem.

I'm even understanding the "why" of things better thanks to the link by? The Security policy change described would be difficult to deploy company-wide unless the change could be made through Group Policy on the domain. I'm looking into that now. Back to the "failed miserably" comment. Yes, it was an extreme comment considering I've only had a Vista machine on site for a couple of months. I am a big supporter of MS and everything they have done for not just the computer industry, but for the World in general.

I just find it very difficult to believe that after 5 years of developement, MS would have this UAC set up the way it is. Seems incredibly difficult to impliment the OS with the default settings. If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.

Keep in mind though that this solution cannot do anything to merge mappings between two different user accounts. So it cannot help enterprises that make an administrator use a standard user account for routine tasks and then a separate administrative account for admin tasks. I will be looking for solutions to this in future articles. Posted by Gordon Martin at AM. Hi Aaron, Actually, the disadvantages tend to outweigh the benefits.

But without giving too much away, you might want to check out this list of apps that need additional rights in order to function: www. BTW, here's a fun example of how using Power Users can be a disadvantage. Any ways to work around THAT?? Short of ditching UAC. Very cool overview. I'm surprised this isn't closer to the top of the Google results, because this is the only place that really summarizes all the options. Anyway, I just wanted to make a quick comment - it is possible to eliminate both problems with launchapp.

Sleep" statement at the bottom of launchapp. The scheduled task doesn't wait for the desktop session to start. It's just that normally launchapp. And of course you'll also need to enable "Run logon scripts synchronously. There are more elegant solutions too, but that's the general idea.

Thanks for the update. People used to be able to find this as quite a high search result, but the article has naturally slid down since it is now almost 2 years old. Post a Comment.

Vista Vitals.