Re: Script that will create a mapped drive for TS client

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 01/21/05


Date: Fri, 21 Jan 2005 15:43:21 -0800

OK, try this:

log on as a normal user, start a command window and type *exactly*
what you have defined in the Logon Script field in the user account
information, i.e. \\myserver\netlogon\logon.cmd

I suspect that you will see some kind of error message, like "path
not found" or "access denied" or whatever.
Feel free to post it here.

To troubleshoot command files, you can also put in the "pause"
statement (without the quotes) in the script. This will cause it to
halt and wait for keyboard input, which makes it possible to see
error messages generated by the script.

 --
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
 --- please respond in newsgroup, NOT by private email ---

"David Jensen" <DJNews1@xxAssociates.net> wrote on 21 jan 2005 in
microsoft.public.windows.terminal_services:

> Vera,
>
> What you outlined seems so simple and it sure seems that I did
> exactly what you said below. However, when logging a TS user
> in, it doesn't appear to even reference the logon.cmd file. I
> know the logon.cmd file is OK, since I tried it using the
> http://support.microsoft.com/?kbid=195461 link you gave me and
> it worked fine. I just can't get it to work when putting in the
> user profile.
>
> I put the the path \\myserver\netlogon\logon.cmd into the "Logon
> Script" field on the "profile" tab of the user's properties, and
> it was as if it was never there when I opened a TS session for
> that user. Certainly no drive was mapped. Was I supposed to put
> that string in quotes or something more than I did?
>
> It seems so simple and I just don't understand what I am doing
> wrong.
>
> Thanks for any further clarification that you can provide.
>
> David Jensen
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns95E4EC1AEDC03veranoesthemutforsse@207.46.248.16...
>> You can create logon scripts in a number of scripting
>> languages, but let's keep it simple: a command file.
>>
>> Assuming you don't run any logon script at the moment:
>>
>> 1. create a new textfile in notepad
>> 2. put in the line: net use X: \\my_server\my_share
>> (see comments below)
>> 3. save the textfile with a .bat or .cmd extension, let's say
>> logon.cmd
>> 4. put it in a location which is readable by all users. One
>> such place would be the shared NETLOGON folder on your DC.
>> 5. define the full path to logon.cmd in the Logon Script field
>> in the user account properties. Note that this will also map
>> the drive when the users logon to their normal workstation. If
>> you don't want that, check this:
>> 195461 - How to Set Up a Logon Script Only for Terminal Server
>> Users
>> http://support.microsoft.com/?kbid=195461
>>
>> About the command itself:
>>
>> X: use any unused drive letter you want for the shared folder
>> \\myserver is the name of the server where the shared folder is
>> located
>> \my_share is the name of the shared folder
>>
>> Example: net use P: \\ImageSrv\pictures
>> would make the folder Pictures on computer ImageSrv available
>> under the letter P:
>>
>> type "net use /?" to see all options for the net use command,
>> or check in Start - Help
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "David Jensen" <DJNews1@xxAssociates.net> wrote on 20 jan 2005
>> in microsoft.public.windows.terminal_services:
>>
>> > In the whitepaper from MS describing how to lock down TS, one
>> > of the recommendations is to "Remove Map Network Drive and
>> > Disconnect Network Drive". It goes on to say "If mapped
>> > drives are necessary, they can be mapped from a logon
>> > script".
>> >
>> > I have enabled this restriction and now I need to know how to
>> > create the script. I'm completely green here, but it is my
>> > assumptions that a simple script must be written that is
>> > stored in a file which is referenced in the "Logon Script"
>> > field on the "profile" tab of the users properties found in
>> > Active Directory Users and Computers. Can someone tell me
>> > how to do that (assuming that I'm on target)? If I am, then
>> > first of all, what should be the text of the script? Do I
>> > just put that into a text file in notepad? If so, what
>> > should the .xyz extension name be for the file? What is the
>> > common place to store the scripts on the server? If there is
>> > a problem with the script will I see an error or will it just
>> > not work?
>> >
>> > Is there anything else that needs to be done to make this
>> > work? Will the mapped network drive then be visible in my
>> > computer when that user logs on?
>> >
>> > Thanks for the education. It's clear that I need it.
>> >
>> > David Jensen
>> >
>> > Replace the xx in my email with MJ for my real email address.



Relevant Pages

  • net use script issue with terminal server and DFS
    ... with the standard version there's a problem with the logon script. ... starts but the desktop become blue and only a command window ... server there is no problem. ...
    (microsoft.public.windows.terminal_services)
  • Re: logon script from profile tab not working
    ... from the logon script field on the profile tab in AD. I've even written a ... simple one with MsgBox "logon script working!" ...
    (microsoft.public.windows.server.active_directory)
  • Re: logon script from profile tab not working
    ... from the logon script field on the profile tab in AD. I've even written a ... simple one with MsgBox "logon script working!" ...
    (microsoft.public.windows.server.active_directory)
  • logon script from profile tab not working
    ... I have a vbs logon script that works when you run it, ... from the logon script field on the profile tab in AD. I've even written a ... simple one with MsgBox "logon script working!" ...
    (microsoft.public.windows.server.active_directory)
  • RE: The share-name was not found. Be sure you typed it correctly
    ... You did put the logon script in the NETLOGON share on your DC and put just the name of the script in the logon script field right? ... Ian Bagnald ...
    (microsoft.public.win2000.networking)