Re: Logon Scripts for Dept. and Printers based on Groups and IP
- From: Corey Thomas <coreythomas@xxxxxxxxx>
- Date: Wed, 30 Apr 2008 06:13:17 -0700 (PDT)
For drive mapping, I have written a good sub you can use at h
ttp://vbscripter.blogspot.com/2008/03/better-drive-mapping.html
For handling group membership, we load all the groups into a
dictionary object. It cuts down on ADSI calls and uses less code than
select case statements. And the best part is that you can set the
compare mode to ignore case. :D If you want an example this code,
let me know.
-Corey
On Apr 29, 10:28 pm, "Al Dunbar" <AlanD...@xxxxxxxxxxxxxxxxxxx> wrote:
"Richard Mueller [MVP]" <rlmueller-nos...@xxxxxxxxxxxxxxxxxxxx> wrote in
messagenews:O9TWxhiqIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
"Pegasus (MVP)" <I....@xxxxxxxxxx> wrote in message
news:uH33ebhqIHA.2068@xxxxxxxxxxxxxxxxxxxxxxx
<mike...@xxxxxxxxx> wrote in message
news:abbad4b5-d0e8-46e4-88a5-9ea3b6679173@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a script that was put together by a several different scripts
and some reading I have done on scripting. Anyhow, I've attached a
script located below that will map department shares based on the
users active directory group membership and connected printer(s)
based on their IP address. The script works well until the IP address
part. If anyone can help, that would be great. Feel free to modify
it in any way that would make the script better!
Thanks..
=============
Splitting a string into its components is usually done with the
inbuilt "split" function:
arrOctets = Split(sIP, ".")
'Assuming IP's 172.23.1.0, 172.23.2.0, 172.23.3.0....
if arrOctets(2) = 1 Then Loc = "Floor7"
if arrOctets(2) = 2 Then Loc = "Floor9"
if arrOctets(2) = 3 Then Loc = "Floor10"
Some more comments on the script you posted.
1. I actually feel it is important for users to see error messages in a
logon script. If error messages are suppressed, no one is even aware that
anything went wrong. If someone notices that something isn't right
(missing drive mapping or printer), it could be days later and no one has
a clue where to look or how to troubleshoot. I want my users to see the
error messages and report them to me so I can fix them.
It's not often I get the chance to disagree with Richard!
I do not feel it is important for users to see error messages in a logon
script. In my experience, they usually do not notice them; but if they do,
they do not read them, understand them, write them down, or report them.
If the message is displayed momentarily, they will never see it. If
displayed in a popup they have to click away, they will just click. If this
is a recurring problem such as failing to map a drive they never use, they
will become conditioned to believe that all error messages are pointless.
In the event they have problems later, they just might tell me that "there
was some kind of error, but I don't remember what it said".
Our logon script logs its proceedings and error messages into a file in the
user's %temp% folder. When they report a problem that indicates a logon
script failure, that is the first place I look.
As an aside, logon scripts should be as simple as possible, and designed to
avoid errors. For example, ours has a MAP function that unmaps the drive
letter if already assigned. Having some drives pre-assigned is therefore not
an error.
/Al
.
- References:
- Logon Scripts for Dept. and Printers based on Groups and IP
- From: miketir
- Re: Logon Scripts for Dept. and Printers based on Groups and IP
- From: Pegasus \(MVP\)
- Re: Logon Scripts for Dept. and Printers based on Groups and IP
- From: Richard Mueller [MVP]
- Re: Logon Scripts for Dept. and Printers based on Groups and IP
- From: Al Dunbar
- Logon Scripts for Dept. and Printers based on Groups and IP
- Prev by Date: Re: burning DVD failure
- Next by Date: Re: Need a script to compare two files
- Previous by thread: Re: Logon Scripts for Dept. and Printers based on Groups and IP
- Next by thread: Re: Spam
- Index(es):
Relevant Pages
|
