Slow Shut Down

  • Thread starter Thread starter Tom
  • Start date Start date
Hi Tom,

There are lots of causes for slow shutdown, for example

1) Multiple types of policies can be applied to Windows 2000 users and
computers
2) If LM Announce messages are being generated.
3) This happens with Exchange 2003 (and sometimes even with Exchange 2000
for that matter), because Active Directory services shuts down before
Exchange services shut down.

The best thing to find out which cause the slow shutdown is configure
Windows so that you receive verbose startup, shutdown, logon, and logoff
status messages. In scenarios where you are troubleshooting slow startup,
shutdown, logon, or logoff behavior, you may find it helpful to enable
verbose logging.

To enable verbose logging, use one of the methods that are described in
this section.

Use Group Policy
===============
You can use Group Policy to switch between normal and verbose status
messages. If you are in a domain environment and you want to enable verbose
logging on a group of computers, follow these steps:
1. Start the Active Directory Users and Computers snap-in.
2. Right-click the container for the domain or the organizational unit to
which you want to apply the policy settings, and then click Properties.
3. Click the Group Policy tab.
4. Click New, and then type a descriptive name for the new Group Policy
object (GPO) that is created.
5. Click the new GPO and click Edit.
6. Browse to Computer Configuration\Administrative Templates\System.
If you are using a standalone computer or if you want to enable verbose
logging on only one computer, follow these steps:
1. Click Start, and then click Run.
2. Type gpedit.msc, and then click OK.
3. Browse to Computer Configuration\Administrative Templates\System.
back to the top
Use Registry Editor

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

You can use Registry Editor to switch between normal and verbose status
messages. To use Registry Editor to enable verbose logging, follow these
steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. On the Edit menu, point to New, and then click DWORD Value.
4. Double-click the new key that is created, type verbosestatus in the
Value Name box, and then type 1 in the Data value box.
NOTE: If the following key is present, and if the value is set to 1, status
messages are not displayed:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
\DisableStatusMessages

Tom, also for more information have a look at the article
http://support.microsoft.com/default.aspx?scid=kb;EN-US;316243

Thanks,

(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 
In
Tom said:
What causes slow shut downs in Win 2000. It hangs on
saving system information.

start
run
type
gpedit.msc

navigate to

Computer Configuration
Administrative Templates
System
Logon

Maximum retries to unload and update user profile ...

set enabled and to say 5 ... default if not configured is 60!!

also see

http://support.microsoft.com/default.aspx?scid=kb;en-us;837115&Product=win2000

in particular

"User Profile Hive Cleanup Service"

http://www.microsoft.com/downloads/...6D-8912-4E18-B570-42470E2F3582&displaylang=en
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top