Re: Common tasks of script developer
- From: "billy" <wcasse@xxxxxxxxx>
- Date: 15 Sep 2005 11:33:45 -0700
the scripter's job is to make the complex simple.
first and formost there are the logon script(s). when you log onto a
domain computer, you want your drives mapped, your printers mapped,
audit run, etc. - all of this without the user hitting a key.
in my environment, management set a policy that "desktop support"
personel were supposed to check a dozen things and fix them if
nessessary. they sent out a 10 page document on what to check and how
to fix. not supprisingly, most of these things were not getting done. i
came up with a script that could do all of the checks and apply all the
fixes. this became the logon script for desktop support.
there is AD migrations (as someone already mentioned), and AD changes.
if your domain is large, it is inconcevable to make mass changes (like
changing the home drive letter for a list of 1000 users) by hand.
scripts handle this kind of job very well.
in my environment, user account creation is fairly complex. accounts
created by hand take about 10 minutes or so and have an error in them
about 25% of the time. accounts created by script are always correct
and are created in less than 1 minute.
.
- Prev by Date: weekday
- Next by Date: Re: Script Host Error Problem
- Previous by thread: Re: Common tasks of script developer
- Next by thread: Script Host Error Problem
- Index(es):
Relevant Pages
|