Re: Mapping a drive

From: Jim Pattison (jpattisonrem_at_ovesherbtel.net)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 18:16:14 -0500

Robert,
Thanks, making my script a cmd file solved the problem.
Also, thanks for the idea on the printers. I'll give that a whirl also.

Jim

"Robert R Kircher, Jr." <rrkircher@hotmail.com> wrote in message
news:pK6dncY-7fzFscbcRVn-iw@giganews.com...
> Jim,
>
> This really should be all that problematic. You need to create a script
> or cmd file and add it to your GPOs User Config > Windows Setting >
> Scripts.
>
> I personal use the old fashioned NET USE command in a CMD file
> Example
> net use <driveletter> \\servername\sharename.
>
> Because Win2K Pro and XP make persistent connections I sometimes add a net
> use <driveletter> /D which disconnects any currant connection for that
> drive letter, before I make the connection just to ensure that the
> connection is made to the right share. This can also be helpful if you
> share location changes or the drive mapping changes.
>
> I also connect to printers in CMD scripts using the following command
> rundll32 printui.dll,PrintUIEntry /in /y /n \\server\printer
>
> This will make the network connection, install the printer if it doesn't
> exist on the client and make it the default printer.
>
> You can see all the options if you run rundll32 printui.dll,PrintUIEntry
> /?.
>
> One thing to note is the location the GPO is places. Make sure you place
> common connection high up in the OU higherarchy and user spicific
> connections on lower lever OUs.
>
> HTH
> --
>
> Rob
>
>
> "Jim Pattison" <jpattisonrem@ovesherbtel.net> wrote in message
> news:e68TWaipEHA.648@tk2msftngp13.phx.gbl...
>> Kevin,
>> Thanks. After a couple of tests I see that getting scripts to run
>> proeprly on a Windows server is as hard for me as it was on Netware 5
>> servers. Looks like I need to do a bit more reading.
>>
>> Jim
>>
>> "Kevin Sullivan" <ksullivan@autoprof.com> wrote in message
>> news:OHqrA4cpEHA.3724@TK2MSFTNGP10.phx.gbl...
>>> Traditionally mapping a drive is done with a logon script. Net Use
>>> \\<serv..>\<share>.... plug it into a batch file and associate it with a
>>> user profile and there you go. Enter Group Policy and now there
>>> Microsoft
>>> provides a Client Side Extension to process some additional event
>>> triggered
>>> scripts. We now have Startup and shutdown scripts under the computer
>>> configuration and logon and logoff scripts under the user configuration.
>>> So
>>> mapping a drive can now be handled via a script but handled int he
>>> single
>>> configuration management environment of Group Policy. Easy. we even now
>>> have
>>> more scripting capabilties so we can use VBScript or JScript (or others)
>>> and
>>> use the WScript.Network object and MapNetworkDrive method... easy
>>> right...
>>>
>>> The idea of doing configuration through Group Policy is absolutely the
>>> correct expectation of the platform. Unfortunately out of the 11
>>> extensions
>>> Microsoft provided to us that piece of functionality is not there.
>>> Scripts
>>> are still 'event' driven. The user must logon in order for it to take
>>> affect. This is one scenario that comes up often and drove us to create
>>> Drive Mappings as one of the extensions we provide to Group Policy.
>>>
>>> If you wnat more information you can contact me offline.
>>>
>>> Kevin
>>> kevin@autoprof.com
>>> "Jim Pattison" <jpattisonrem@ovesherbtel.net> wrote in message
>>> news:uTjbYncpEHA.3300@TK2MSFTNGP12.phx.gbl...
>>>> Hi all,
>>>> Is there a way to use a group policy object to map a network drive? OR
>>>> is
>>>> that best done with a profile?
>>>> Thanks,
>>>> Jim
>>>>
>>>>
>>>
>>>
>>
>>
>
>