I have a vbscript logon file assigned in group policy. It works as expected
under Windows XP, but none of my Vista machines semems to run the file, as
none of the mapped server shares shows up. I cant find anything related in
the event log.

Please advice as how to debug this problem.



Regards;
/jb

You need to use a Vista Group Policy...
See
http://technet2.microsoft.com/Window....mspx?mfr=true
for more information...
---
Jeffrey Randow
jeffreycentex@xxxxxx
Windows Networking MVP 2001-2006
http://www.networkblog.net

On Tue, 13 Nov 2007 23:07:59 +0100, "Jonny Bergdahl"
<jonny.bergdahl@xxxxxx> wrote:

>I have a vbscript logon file assigned in group policy. It works as expected
>under Windows XP, but none of my Vista machines semems to run the file, as
>none of the mapped server shares shows up. I cant find anything related in
>the event log.
>
>Please advice as how to debug this problem.
>
>Regards;
>/jb

> You need to use a Vista Group Policy...

> See
> http://technet2.microsoft.com/Window....mspx?mfr=true
> for more information...

I didn't find anything in that document that says I need to migrate my existing Group Policy settings to support logon scripts för Vista. However, I did find the following that applies to my setup:

----
UAC may prevent Group Policy logon scripts from appearing to work properly. For example, a domain environment contains a Group Policy object that includes a logon script to map network drives. A nonadministrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the nonadministrative user starts Windows Explorer. The user sees their mapped drives. Under the same environment, an administrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the administrative user starts Windows Explorer. The user does not see their mapped drives.
When the administrative user logs on, Windows processes the logon scripts using the elevated token. The script actually works and maps the drive. However, Windows blocks the view of the mapped network drives because the desktop uses the limited token while the drives were mapped using the elevated token.
-----

In short - the script is run, my network drives are actually mapped, but UAC prohibits Windows from showing them in Explorer. It also outlines a workaround using launchapp.wcf to run the script under the limited token.

Regards;
/jb

I've only had admx files work in my environment...

---
Jeffrey Randow
jeffreycentex@xxxxxx
Windows Networking MVP 2001-2006
http://www.networkblog.net


On Wed, 14 Nov 2007 22:17:47 +0100, "Jonny Bergdahl"
<jonny.bergdahl@xxxxxx> wrote:

>> You need to use a Vista Group Policy...
>> See
>> http://technet2.microsoft.com/Window....mspx?mfr=true
>> for more information...

>
>I didn't find anything in that document that says I need to migrate my existing Group Policy settings to support logon scripts för Vista. However, I did find the following that applies to my setup:
>
>----
>UAC may prevent Group Policy logon scripts from appearing to work properly. For example, a domain environment contains a Group Policy object that includes a logon script to map network drives. A nonadministrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the nonadministrative user starts Windows Explorer. The user sees their mapped drives. Under the same environment, an administrative user logs on to the domain from a Windows Vista computer. After Windows Vista loads the desktop, the administrative user starts Windows Explorer. The user does not see their mapped drives.
>When the administrative user logs on, Windows processes the logon scripts using the elevated token. The script actually works and maps the drive. However, Windows blocks the view of the mapped network drives because the desktop uses the limited token while the drives were mapped using the elevated token.
>-----
>
>In short - the script is run, my network drives are actually mapped, but UAC prohibits Windows from showing them in Explorer. It also outlines a workaround using launchapp.wcf to run the script under the limited token.
>
>Regards;
>/jb
>
>
>

Here is a real simple fix for Vista and Windows 7. Just add this registry item. Copy and past the lines below into a text file and name it networkdrivefix.reg or whatever you want. Then double click the file to add it to your registry. You can keep the UAC running too.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001