Scripted netwrok drives not appearing

  • Thread starter Thread starter Timboi
  • Start date Start date
T

Timboi

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
 
Mick,

Thanks for the reply. What am I looking for in there? Network discovery is on.
The strange thing is I can definitely access network locations by mapping a
drive (or putting a UNC path in 'Run' box). It's just odd that the recovery
application knows there are mapped drives but Windows Explorer just isn't
showing them (and the fact I can map a drive using a drive letter that the
Recovery app says is in use is eve stranger).

Cheers,

Timbo
 
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/Windo...878e-48db-a3c1-4be6ac7cf7631033.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/mapped-drives-are-not-seen-from-elevated-command-prompt-in-vista/

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog: http://www.winhelponline.com/blog
Windows® Troubleshooting: http://www.winhelponline.com
 
Ramesh,

Cool - it's seems the UAC is the culprit. Turning it off allows the mapped
drives to appear (I've just started learning about Vista so this might be
basic stuff to many).
I'm obviously going to have to get more info about the UAC. I know the jist
of what it's for but is it really that essential to have turned on? I know
with *nix systems it's advisable to never login as root and to elevate
privileges only when required but I've always logged in as an administrator
on Windows machines and never found a problem with this way of doing things.

Cheers,

Timbo

Ramesh said:
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/Windo...878e-48db-a3c1-4be6ac7cf7631033.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/mapped-drives-are-not-seen-from-elevated-command-prompt-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 said:
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
Click to expand...
Click to expand...
 
You're welcome Timbo.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog: http://www.winhelponline.com/blog
Windows® Troubleshooting: http://www.winhelponline.com


Timboi said:
Ramesh,

Cool - it's seems the UAC is the culprit. Turning it off allows the mapped
drives to appear (I've just started learning about Vista so this might be
basic stuff to many).
I'm obviously going to have to get more info about the UAC. I know the
jist
of what it's for but is it really that essential to have turned on? I know
with *nix systems it's advisable to never login as root and to elevate
privileges only when required but I've always logged in as an
administrator
on Windows machines and never found a problem with this way of doing
things.

Cheers,

Timbo

Ramesh said:
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/Windo...878e-48db-a3c1-4be6ac7cf7631033.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/mapped-drives-are-not-seen-from-elevated-command-prompt-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 said:
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
Click to expand...
Click to expand...
Click to expand...
 
Hallo,
i´ve the same Problem on Clientsystem XP Prof.;scripted drive mapping via
GPO.Server 2003 AD domain. sometimes (not permanent) when different users
login some (not all) of the networkdrives (mapped via script using GPO)
aren't visible in "computer"; but if the user in cmd prompt run a "net use"
all Driveletter are seen.

can be this the same problem; same solution ???

Thanks

Wolfgang
 
Back
Top