H
Harrison Midkiff
Hello:
Last week my primary corporate file server crashed. It took me most of the
afternoon to get the server back online. During this time just about every
computer in the organization came to a crawl! The reason for this was all
users have mapped home folders and drives on this server. Many people tried
to reboot there computers but the logon took 10 minutes or more. The
lockups and slow logins were so bad some departments decided to close. Very
bad.... I know loosing this server would have tremendous effects, but I
would not have thought the workstations would have been effected as much as
they were.
Does anyone have any idea how to avoid something like this from happening
again? I am curious if there is a setting in AD I can make to help with
this?
Harrison Midkiff
Last week my primary corporate file server crashed. It took me most of the
afternoon to get the server back online. During this time just about every
computer in the organization came to a crawl! The reason for this was all
users have mapped home folders and drives on this server. Many people tried
to reboot there computers but the logon took 10 minutes or more. The
lockups and slow logins were so bad some departments decided to close. Very
bad.... I know loosing this server would have tremendous effects, but I
would not have thought the workstations would have been effected as much as
they were.
Does anyone have any idea how to avoid something like this from happening
again? I am curious if there is a setting in AD I can make to help with
this?
Harrison Midkiff