"p byers" <email@example.com> wrote in message
> Having read the very enlightening thread, my mind got to wondering about
> what happens if the network is down - do the Logon Scripts cater for it
> satisfactorily ??
This depends somewhat on what you would consider satisfactory.
Domain-based logon scripts will only run for domain users logging on at
workstations having network connectivity to at least one domain controller.
They will not run for local user accounts, or for anybody if the network is
So, the basic answer would be that the logon scripts themselves, since they
would not run at all without network connectivity, would not cater for
That said, once a domain user is logged on with cached credentials he could
certainly run a "local copy" of the domain logon script manually if such a
file was maintained as per some of the suggestions in this thread. But the
"satisfactoriness" of the result would depend on what that script was
supposed to accomplish, and whether or not network connectivity was required
for it to succeed. If the network is down, then no drives will be mapped to
any server shares, and no network printers will be installed.
Our workstations map the "my documents" folder to a folder in the user's
home directory, which is on a server share. If they logon with cached
credentials, they can work locally, but if their profile has not yet run MS
office, they will have some problems. In some cases I have setup a batch
script that runs from the START - All Programs - Startup folder. If it finds
that the drive letter normally mapped to their home folder does not exist,
it will do something like this:
subst M: "%USERPROFILE%\mY dOCUMENT
> Pete (Northolt UK)
> "Justin R." wrote:
>> I'm currently working on revising my company's logon script. When a
>> user logs on, a remote batch file is executed that checks if the
>> client already has a file named "logonscript.vbs" on their PC. If
>> they do, it generates and compares the CRC checksum of the file to a
>> "logonscript.vbs" that exists on the domain controller. If the two
>> CRCs match, we know that the client has the latest version of the
>> script. However, if they do not, the latest version of the script is
>> copied from the domain controller to the client, and then executed by
>> the client workstation.
>> This seems like a lot of back-and-forth to me, and I'm having trouble
>> gauging whether it's the most efficient way of doing things. Part of
>> me wants to simplify things by simply running "logonscript.vbs" from
>> the domain controller without making a copy on the client's PC first.
>> This would eliminate the need to perform a CRC checksum comparison.
>> Is there a way for me to figure out how much bandwidth this would cost
>> on a per-logon basis? Any thoughts or suggestions? I'm pulling my
>> hair out over this (it doesn't really need much help, though, but
>> that's a separate issue entirely).
>> Thanks in advance.