Hi Timbo,
Mapped drives created from an elevated access token will not be visible from
processes running in limited user token. If you use Group Policy to create
mapped drives, it uses the elevated access token. As a result, your user
account (runs with the limited user token by default) won't see the mapped
drives. For more details and a workaround see:
Group Policy Scripts can fail due to User Account Control:
http://technet2.microsoft.com/Window....mspx?mfr=true
The script launchapp.wsf helps you create mapped drives under limited user
token via Group Policy.
SEE ALSO
http://www.winhelponline.com/blog/ma...ompt-in-vista/
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog:
http://www.winhelponline.com/blog
Windows® Troubleshooting:
http://www.winhelponline.com
"Timboi" <> wrote in message
news:E81F7C9B-2AC4-4686-999F-...
> Hi,
>
> I'm new to Vista (used to XP) and playing around a bit. I've logged on to
> a
> Server 2003 AD domain and the mapped drives that are usually connected via
> script aren't visible in 'Computer'. My first thought was perhaps some
> sort
> of incompatibility between Server 2003 group policy (or script) and Vista
> Business but when I was creating my recovery disks, I selected create ISO
> and
> when browsing for a location, the usual mapped network drives were
> available.
> So it appears that the recovery software can see my mapped drives (and
> therefore the OS must be able to see them) but I can't see them in the OS
> under 'Computer'. Is there something I need to turn on or off?
>
> Cheers,
>
> Timbo