Re: Login script question

From: Richard Mueller [MVP] (rlmueller-NOSPAM_at_ameritech.NOSPAM.net)
Date: 02/26/04 

Date: Wed, 25 Feb 2004 21:08:37 -0600

Joe Banks wrote:

"Joe Banks" <JBanks@nospamfidelitynational.com> wrote in message
news:Xns949ABC1323F4Bjbanks.nospamfidelit@207.46.248.16...
> I was curious if there is a way that I can some how create a login script
> that will map drives acording to the local server?
>
> We are a bank that has what we call floaters. Theses are employees that
> may work in Branch A today and then Branch B the next day. I would like
to
> be able to create a login script that will map out the drives that this
> user needs according to the branch they are at today. All of the branches
> are the same as far as a directory structure is concerned.
>
> For example:
>
> Today at Branch A they login into a local computer and the login script
> maps the F: drive to \\Br-A\Data.
>
> The next day while at Branch B they login to a local computer and the
login
> script maps the F: drive to \\Br-B\Data.
>
>
> I posted this in another group and they suggested I post it here. I this
> is the wrong place, please re-direct me.
>
> I also have no experience in scripting, we are migrating from Novell to
MS,
> and I was curious if there are any good references for this?
>
Hi,

This newsgroup is appropriate for this question. First, I have some sample
VBScript logon scripts (and an FAQ) linked on this page:

http://www.rlmueller.net/freecode2.htm

Also, Clarence Washington has examples on his web site:

http://cwashington.netreach.net

I see a few options to handle your floaters (using a VBScript logon script).
First, if the computers are not mobile, you can check computer group
membership. You could have all computers at Branch A in one group, all those
at Branch B in another. If the clients are all W2k or above, you can get the
computer Distinguished Name from the ADSystemInfo object, bind to the
computer object, and check group membership. I do this in several of my
sample logon scripts to connect printers. Second, if each branch is a
different site, you can retrieve the site name from the ADSystemInfo object.
Or, if the offices are on different subnets, you could retrieve the IP
address. Actually, the computer group idea would allow greater flexibility.
You could have one group for each printer, for example. If you have laptops,
you might have to determine the site name. A snippet using ADSystemInfo:

Set objSysInfo = CreateObject("ADSystemInfo")
Wscript.Echo "Computer Distinguished Name: " & objSysInfo.ComputerName
Wscript.Echo "Site Name: " & objSysInfo.SiteName 

-- 
Richard
Microsoft MVP Scripting and ADSI
HilltopLab web site - http://www.rlmueller.net
--

Relevant Pages