Re: Strange mapping visibility issue with Vista x64 or x86... (login script issue)
- From: markm75 <markm75c@xxxxxxx>
- Date: Wed, 16 Jan 2008 10:38:19 -0800 (PST)
On Jan 16, 11:49 am, markm75 <markm...@xxxxxxx> wrote:
In vista.. if you goto start.. run.. notepad.. then do a file open.. i
can goto computer and see all the mapped drive letters for our 2003
domain (which are mapped at login via a script, this script is forced
to vista machines via running as limitted user technique via task
scheduler commands)..
If i open other 3rd party apps.. like installshield 12.. then try the
open command.. i only see drives which are mapped that are
persistent.. ie: these other mappings are mapped as not persistent at
login..
I'm not sure why this is the case...
I'm using this in a VBscript:
On Error Resume Next
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive "O:" , "\\server01\apps"
(if you put , true after one of these lines it is persistent).
The old way.. i had a .cmd file with this:
NET USE O: \\server01\apps /p:n
I'm 99% sure the old way worked fine, but i'm not sure why a vbs file
method would break the ability to see the mapped network drives for
3rd party apps?
Any thoughts?
Thanks
I should add that even if i change from a vbs to a cmd with net use
commands I still end up with the same thing...
.
- Follow-Ups:
- References:
- Prev by Date: Re: Problems to add PCs to domain
- Next by Date: Re: Problems to add PCs to domain
- Previous by thread: Strange mapping visibility issue with Vista x64 or x86... (login script issue)
- Next by thread: Re: Strange mapping visibility issue with Vista x64 or x86... (login script issue)
- Index(es):
Relevant Pages
|
Loading