Windows 2K3 Logon Script - Map Network Drive... VBScript and NET USE


Recommended Posts

Hi,

Long time reader... but infrequent poster - be kind!

Short Version

I want to create a log on script that maps \\Server\Users\%USERNAME%\%USERNAME%'s Documents\ to Z: and then have Windows Explorer pop up showing the new folder.

Long Version

Side Note

***I want to clear up now - when i set up the Roaming Profiles, i used the %USERNAME% variable (to move the profile folder to C:\Users Shared Folder\%USERNAME%\%USERNAME%'s Profile\) - but now with Windows XP and special folders, once in the user account, the %USERNAME%'s Documents folder doesnt show as Fred's Documents (for example), but "My Documents". So, i dont know in these scripts if i need to specify \%USERNAME%'s Documents or \My Documents***

I have a sever and a couple of workstations setup with Roaming User Profiles and "My Documents" all stored on the server. The file structure on the server is:

C:\Users Shared Folder\%USERNAME%\%USERNAME%'s Documents\

\%USERNAME%'s Profile\

So im trying to say the Profile and Documents are in the same folder (%USERNAME%) on the server, so all the information for each user (their documents and profile data) are stored in a folder on the server, called their username.

The server is Windows 2K3 SBS, workstations are XP Pro.

Ive been using this site for guidance.

What i want is to run a script at logon that will connect the "%USERNAME%'s Documents" folder (on the server) to a drive (say Z:) (on the user's workstation) and then open that Z drive in Explorer on the user's pc.

But using the link above i can only get to "\%USERNAME%\" (the folder above what i want). I want it to map straight to the "%USERNAME%'s Documents" folder, so the Profile folder isnt shown, as now the profile folder is shown by mapping to \%USERNAME%, (so they cant muck about with it).

What's the code? Im using the template below, but I have no idea of VBScript.

  Code said:
' MNDUserNameBonus.vbs

' VBScript to map a network drive to the UserName. And open Explorer

' Author Guy Thomas http://computerperformance.co.uk/

' Version 2.2 - September 2005

' -----------------------------------------------------------------'

Option Explicit

Dim objNetwork, objShell

Dim strDriveLetter, strRemotePath, strUserName

strDriveLetter = "X:"

strRemotePath = "\\grand\home\"

' Purpose of the script to create a network object. (objNetwork)

' Then to apply the MapNetworkDrive method. Result K: drive

Set objNetwork = WScript.CreateObject("WScript.Network")

' Here is where we extract the UserName

strUserName = objNetwork.UserName

objNetwork.MapNetworkDrive strDriveLetter, strRemotePath & strUserName

' Bonus code to open Explorer at the mapped drive letter

Call ShowExplorer

WScript.Quit

Sub ShowExplorer()

Set objShell = CreateObject("WScript.Shell")

objShell.run ("Explorer" & " " & strDriveLetter & "\" )

End Sub

' End of Example of MapNetworkDrive logon script.

I can use NET USE, and that works to map the drive with the %USERNAME% variable, but it dont know how to get it to open the folder afterwards. Also i dont know the differences of using NET USE (ie .cmd) compared to objNetwork.MapNetworkDrive (ie .vbs). Is there a way to combine the both commands? Or is there a way to complete both objectives using one of them? Whats the differnce between cmd and vbs files for logon scripts? Which are better?

Alot of questions i know, any help is appreciated.

Cheers

Edited by Major_Disaster
  kingofthecarts said:
So you want to map their "My Documents" to their My Documents on the Server? If I'm Correct.

No. Sorry if i wasnt clear.

I want to map the user's My Documents folder (which is stored on the server), to a drive (say Z:) on the workstations... so it appears in My Computer (My Documents on \\server\users for example).

Thanks for the quick reply.

  Major_Disaster said:
No. Sorry if i wasnt clear.

I want to map the user's My Documents folder (which is stored on the server), to a drive (say Z:) on the workstations... so it appears in My Computer (My Documents on \\server\users for example).

Thanks for the quick reply.

Can you make the users folder on the server their logon name example "jsmith"

Then share "jsmith" and remove "Everyone" and add only "jsmith" with full permissions

Then in their logon script. Just use

net use z: \\servername\%username% /persistant:yes /yes

Ahh Edit:... I see you want to open it afterwards, why not just add a shortcut to Z: in the startup folder...

Thanks for the reply - the quality, and quantity, of the help here is quite remarkable!

Well, tbh ive already managed to get a NET USE in much the way you have described to do the actual mapping - and it works. But this is only a small network, and im trying to learn new things and be a bit flashy... hence i was wanted to making the folder open in explorer once it has been mapped. For that i found:

  code said:
' MNDUserNameBonus.vbs

' VBScript to map a network drive to the UserName. And open Explorer

' Author Guy Thomas http://computerperformance.co.uk/

' Version 2.2 - September 2005

' -----------------------------------------------------------------'

Option Explicit

Dim objNetwork, objShell

Dim strDriveLetter, strRemotePath, strUserName

strDriveLetter = "X:"

strRemotePath = "\\grand\home\"

' Purpose of the script to create a network object. (objNetwork)

' Then to apply the MapNetworkDrive method. Result K: drive

Set objNetwork = WScript.CreateObject("WScript.Network")

' Here is where we extract the UserName

strUserName = objNetwork.UserName

objNetwork.MapNetworkDrive strDriveLetter, strRemotePath & strUserName

' Bonus code to open Explorer at the mapped drive letter

Call ShowExplorer

WScript.Quit

Sub ShowExplorer()

Set objShell = CreateObject("WScript.Shell")

objShell.run ("Explorer" & " " & strDriveLetter & "\" )

End Sub

' End of Example of MapNetworkDrive logon script.

But though that does show the folder after being mapped, it doesnt work with %USERNAME%.

I spose i could have one NET USE (.cmd file) and then just the Sub ShowExplorer() bit of the .vbs file? But thats kinda messy and i was wondering it there was a neater solution.

I realise im being fussy, but i just want to learn...

Thanks again

EDIT: Just saw your post. Yeah that would work. But what would be the code to add a shortcut to the startup folder?

  kingofthecarts said:
Or in the batch script you could add "explorer z:" Then it would open it.

Perfect. Thanks a bunch. Just what i wanted, and in only 2 lines of code!

A few questions though to satisfy my curiosity... weve managed to get this running with 2 lines of code, whereas the .vbs seemed to take 15 - how come the difference? Is one method "better" than the other?

Now to the desktop! Im wanting to put a few icons / links on the destop via logon script. I can make a folder on the server of links and then just use a logon script to copy them to the user's desktop folder easily enough (i hope) but how would i go about adding their "My Documents" folder to the desktop?

Something like this work?

Thanks for the continued help.

Much appreciated.

EDIT: Just saw your edit! I simply added

explorer Z:

to the logon script and it worked... what is the effect of "ECHO OFF"? (Be gentle - i see it all the time on the net, but only being a teenager i dont know anything before XP... so all these DOS commands are foreign to me... if indeed that is DOS related!)

"My documents" is the z: drive? right? Make a shortcut where the batch script is to the z: drive, then copy the shortcut over to the desktop?

Example:

xcopy "My Documents.lnk" "c:\documents and settings\%username%\desktop" ** Single User Desktop **
OR
xcopy "My Documents.lnk" "c:\documents and settings\all users\" **Put on ALL users Desktops **

Another way would be to redirect the "My Documents" folder path. Then show the "My documents" folder on the desktop.

ECHO OFF = Just Hides Stuff - Such as the command lines. But with a short script there is really no time to see anything :p

  kingofthecarts said:
"My documents" is the z: drive? right? Make a shortcut where the batch script is to the z: drive, then copy the shortcut over to the desktop?

Example:

xcopy "My Documents.lnk" "c:\documents and settings\%username%\desktop" ** Single User Desktop **
OR
xcopy "My Documents.lnk" "c:\documents and settings\all users\" **Put on ALL users Desktops **

Another way would be to redirect the "My Documents" folder path. Then show the "My documents" folder on the desktop.

ECHO OFF = Just Hides Stuff - Such as the command lines. But with a short script there is really no time to see anything :p

Thanks for carrying on putting up with me and all my questions! Its just that i find this interesting (odd eh?!)

Anyways, that worked well thanks - ive kinda modified it, as shown below:

xcopy "\\Server\Users\Desktop Shortcuts\My Documents.lnk" "%USERPROFILE%\Desktop"
xcopy "\\Server\Users\Desktop Shortcuts\My Computer.lnk" "%USERPROFILE%\Desktop"
xcopy "\\Server\Users\Desktop Shortcuts\Shared Documents.lnk" "%USERPROFILE%\Desktop"

But! When run a second time the a message comes up asking whether i want to overwrite (as the files are allready there). How do i stop this? Is this an "always answer yes" or "silent" or do i add that "ECHO OFF"?

Thanks again

  kingofthecarts said:
sorry got busy, kool, glad to help out :). I do this type of stuff alot :). , lol, forgot about %userprofile%.

Hope that helped ya :)

Yeh thanks a lot, you really helped. I dont do this stuff... at all. That was my first go at logon scripts, so not bad me thinks.

BTW, if anyone is interested, i found this. 3 Lines of VBScript allowing you to rename network drives.

So now i have 3 scripts that run:

1. Map To My Computer

(NET USE)

2. Rename Mapped Drives

mDrive = "N:\" etc

3. Desktop Shortcuts

XCOPY

Pretty cool!

  Joel said:
Why not do this in a GPO? You've chosen possibly the most complicated way to do this.

http://www.computerperformance.co.uk/w2k3/...er_redirect.htm

Eh? Ive allready set up roaming profiles and moved all the user data to the server.

I wanted (and have) now made it so whenever someone logs on they get a customised Desktop and My Computer.

/confused

My Documents redirection has nothing to do with roaming profiles. You've created a script to map the path when it's already a part of the GPO options. Why not use the tools provided for you instead of a script? Home folders are right there in each user's profile tab in AD.

Im glad i helped with that VBScript.

I think i now see what Joel meant about it being much easier to map the My Documents folder using Home Folders. Ive just fiddled with it now... so it basically just does NET USE DRIVELETTER: \\server\\my documents in a nice GUI way right? So just an easier way of putting the My Documents folder as a mapped drive in My Computer (on the client) without you having to make any scripts, right?

Ahh, looking at that link Joel posted i know see what he was talking about.

Ahh that looks rather clever... my next question was gona be how can i point all the start menu folders to the same location?!

Right, let me have a tinker with that and ill be back to report later.

Thanks again guys.

well, if you redirect "My documents" in GPO it should redirect the "my documents" to it's set location. (example: x:\%username%\my documents\") Or something along those lines.

Also (the reason I do Batch Scripts is because I have to do like 3 or 4 shares) GPO and AD settings I find are good for single share instances (IMO).

  kingofthecarts said:
Also (the reason I do Batch Scripts is because I have to do like 3 or 4 shares) GPO and AD settings I find are good for single share instances (IMO).

There's nothing wrong with batch scripts for shares, but redirecting system folders is best done in AD.

I have folder redirection set up for My Documents I then have the following in a Logon script.

Dim WSHShell

Set WSHShell = CreateObject("WScript.Shell")

myDrive = WSHShell.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Personal")

Set objNetwork = CreateObject("WScript.Network")

objNetwork.MapNetworkDrive "U:" , myDrive

This reads where the My Documents for the current user is redirected to from the registry and then maps U Drive to the My Documents folder of the user. This ensures that if you change the location of folder redirection in GPO the map follows.

Hope it helps.

  G Man said:
I have folder redirection set up for My Documents I then have the following in a Logon script.

Dim WSHShell

Set WSHShell = CreateObject("WScript.Shell")

myDrive = WSHShell.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Personal")

Set objNetwork = CreateObject("WScript.Network")

objNetwork.MapNetworkDrive "U:" , myDrive

This reads where the My Documents for the current user is redirected to from the registry and then maps U Drive to the My Documents folder of the user. This ensures that if you change the location of folder redirection in GPO the map follows.

Hope it helps.

Why use this over the settings in a GPO? :unsure:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Not Netflix's fault and they had to switch to content creation. Content owners jacked up prices, won't allow them renew, and didn't give them the option to license new content.
    • As sphbecker said you obviously missed the hidden /s at the end of my comment.
    • Everything I have ever read about Windows 11's telemetry collection over Windows 10 is that it's minor. Why would Microsoft be leaving data on the table with Windows 10? That doesn't even pass the smell test. LOL Windows 11 can be less performant in certain cases (and faster in others) but that has always been blamed on extra security features in WIn11. Windows 11 when I used it always ran fine for me. I would say If you were really concerned about either you wont be running Windows to begin with or limited to a secondary machine.
    • There was a brief time when they allowed Netflix (ad free) to pretty much license everything affordable, and piracy actually went down. When they saw how much Netflix was making, number of users, etc, they stopped allowing renewing of content and withholding it to make their own streaming services.
    • Wine 10.9 released bringing EGL support for all graphic drivers and several bug fixes by David Uzondu Wine 10.9 is out now, bringing EGL library support for all graphics drivers. For anyone trying to get Windows software running smoothly on Linux or macOS, this unification of EGL access promises more consistent graphical behavior and potentially better performance for applications that lean on it. EGL is a crucial bridge, letting things like OpenGL ES (often used in mobile apps, some desktop applications, and even games) talk to your system's window manager. Having it standardized across all drivers under Wine means fewer instances where an app might render beautifully on one setup but turn into a pixelated mess or refuse to launch on another. Gamers, and especially those dabbling with newer Windows titles, will appreciate that the bundled vkd3d, Wine's secret sauce for translating Direct3D 12 calls to Vulkan, has been upgraded to version 1.16. Every update to vkd3d generally means improved compatibility with the latest and greatest Direct3D 12 titles and ongoing fixes for stubborn ones. Considering vkd3d is a core component for projects like Steam's Proton, which enables a massive library of Windows games on Linux and the Steam Deck, this update is certainly welcome news. Key improvements vkd3d 1.16 brings include: DXIL shaders are now supported in the default configuration, raising the maximum supported shader model to 6.0. Graphics pipeline state objects can be created from shaders with embedded root signatures. Implementation of the SetEventOnMultipleFenceCompletion() method of the ID3D12Device1 interface. Experimental support for compiling DXIL shaders is now a fully supported and enabled-by-default feature in libvkd3d-shader. libvkd3d-shader has initial support for geometry shaders and various new intrinsic functions. The vkd3d demos now work on both Microsoft Windows and Apple macOS builds. Moving on, support for compiler-based exception handling with Clang also makes an appearance; this is a technical enhancement that can lead to greater stability for applications built using that specific compiler when they are run through Wine, reducing unexpected crashes for a subset of programs. Furthermore, Wine 10.9 introduces initial groundwork for generating Windows Runtime metadata in WIDL, its Interface Definition Language tool. As always with development releases, there is a solid list of bug fixes, 34 of them in this particular version. Some notable ones include resolving fullscreen issues with the classic 3D Pinball - Space Cadet, fixing display artifacts in Empire Earth, sorting out text display problems in the EA app launcher, and addressing crashes or visual glitches in games like Dyson Sphere Program and platforms like Geekbench 6. If you're interested in trying out this release, follow the installation instructions for your platform: Ubuntu/Debian, Fedora, or macOS. Installation guides for other platforms, including Slackware, are also available. The release notes for version 10.9 are available here.
  • Recent Achievements

    • First Post
      ClarkB earned a badge
      First Post
    • Week One Done
      Epaminombas earned a badge
      Week One Done
    • Week One Done
      Prestige Podiatry Care earned a badge
      Week One Done
    • Week One Done
      rollconults earned a badge
      Week One Done
    • Week One Done
      lilred1938 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      143
    2. 2
      Xenon
      130
    3. 3
      ATLien_0
      124
    4. 4
      +Edouard
      102
    5. 5
      snowy owl
      97
  • Tell a friend

    Love Neowin? Tell a friend!