Jump to content

Strange mapping visibility issue with Vista x64 or x86... (loginscript issue)

Guest markm75

By Guest markm75
in Windows 2003 Server

 Share

Recommended Posts

Guest markm75

Guest markm75

Posted
Posted

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

  • Replies 4
  • Created
  • Last Reply

Popular Days

Popular Days

Guest markm75

Guest markm75

Posted
Posted

Re: Strange mapping visibility issue with Vista x64 or x86... (loginscript issue)

 

On Jan 16, 11:49 am, markm75 <markm...@msn.com> 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...

Guest markm75

Guest markm75

Posted
Posted

Re: Strange mapping visibility issue with Vista x64 or x86... (loginscript issue)

 

On Jan 16, 1:38 pm, markm75 <markm...@msn.com> wrote:

> On Jan 16, 11:49 am, markm75 <markm...@msn.com> 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...- Hide quoted text -

>

> - Show quoted text -

 

Actually.. ive found the solution.. partially.. it appears the

EnableLinkedConnections registry setting needs changed..

 

http://support.microsoft.com/kb/937624

 

Would anyone know how i can implement this in a GPO (admx)?

 

Thanks

Guest markm75

Guest markm75

Posted
Posted

Re: Strange mapping visibility issue with Vista x64 or x86... (loginscript issue)

 

On Jan 16, 2:50 pm, markm75 <markm...@msn.com> wrote:

> On Jan 16, 1:38 pm, markm75 <markm...@msn.com> wrote:

>

>

>

>

>

> > On Jan 16, 11:49 am, markm75 <markm...@msn.com> 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...- Hide quoted text -

>

> > - Show quoted text -

>

> Actually.. ive found the solution.. partially.. it appears the

> EnableLinkedConnections  registry setting needs changed..

>

> http://support.microsoft.com/kb/937624

>

> Would anyone know how i can implement this in a GPO (admx)?

>

> Thanks- Hide quoted text -

>

> - Show quoted text -

 

Nevermind..

 

I also found a nice tool for creating and converting admx files from

this page (near the middle):

http://www.microsoft.com/technet/technetmag/issues/2007/02/Templates/

Guest markm75

Guest markm75

Posted
Posted

Re: Strange mapping visibility issue with Vista x64 or x86... (loginscript issue)

 

On Jan 16, 3:33 pm, markm75 <markm...@msn.com> wrote:

> On Jan 16, 2:50 pm, markm75 <markm...@msn.com> wrote:

>

>

>

>

>

> > On Jan 16, 1:38 pm, markm75 <markm...@msn.com> wrote:

>

> > > On Jan 16, 11:49 am, markm75 <markm...@msn.com> 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...- Hide quoted text -

>

> > > - Show quoted text -

>

> > Actually.. ive found the solution.. partially.. it appears the

> > EnableLinkedConnections  registry setting needs changed..

>

> >http://support.microsoft.com/kb/937624

>

> > Would anyone know how i can implement this in a GPO (admx)?

>

> > Thanks- Hide quoted text -

>

> > - Show quoted text -

>

> Nevermind..

>

> I also found a nice tool for creating and converting admx files from

> this page (near the middle):http://www.microsoft.com/technet/technetmag/issues/2007/02/Templates/- Hide quoted text -

>

> - Show quoted text -

 

I've run into this issue now.. i've made sure the admx file is local

and in sysvol (though only locally having it seems to make it visible

in the editor)..

 

But when i reboot.. my new policy i created and linked to the our

workstations OU.. says it wasnt applied.. empty.. yet if i look at the

settings in the manager i see this custom setting showing up..

 

Any ideas on this one?

 Share
Go to topic listing
×
×
  • Create New...