Hi all, I am using a testing Exchange Server 2007 with SP1, and W2K3 R2 x64 Standard. This Exchange have all roles, but have not the Edge Role, and only one server one AD (Standalone Mail Server) .... And I am testing the Exchange more than 1 month already ... I just discovered it is NEED very long time to shutdown the computer or reboot or restarting after patch the MS Patch each week or month..... Now, today after I install a patch, and then reboot ... it just stop at "Applying computer settings ..." I am waiting it already over 20 minutes ... How can I do now or check what is wrong on the system? Do it general on all of your Exchange? Thank you.

Hi, When you apply a update or install software to the machine, it will apply the related configuration to the system when it reboots. That could be normal. But Ill confirm whether any other applications running on this machine, whether it is heavy loaded. First, lets try to narrow down the root cause of this issue. 1. Please try to boot the computer to safe mode and check this issue. 2. Then we need to perform a clean boot to check whether any other application will start when it boot up. A Clean Boot will allow us to isolate any device drivers or programs that are loading at startup that may be causing a conflict with other device drivers or programs that are installed in your computer. 1) Run MSCONFIG.EXE. 2) In the Services tab, click "Hide All Microsoft Services" and click "Disable All". 3) In the Startup tab, click "Disable All". Click OK. (This will temporarily prevent third-party programs from running automatically during start-up.) 3. Please unplug the network cable on Exchange Server and reboot it to check the issue. If issue goes away, then please try to ping this machine from another computer to see whether it is a network issue. Besides, whether Exchange Server is also acted as a DC? When the machine startup, Exchange runs normally or slowly? Mostly, I suspect it is a Windows 2003 Server performance related issue. Please try to check the event log whether any related event has been generated there. (Note: Start-Run-Eventvwr) Also you can post this issue to Windows Server newsgroup to get better help. Discussions in General Discussion http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.server.general&cat=en_US_9741c575-ec92-42f8-85ba-00dfe1483cf5&lang=en&cr=US More information share with you: Domain Controller boots up slowly when pointing to itself as the only DNS server http://support.microsoft.com/kb/945765/en-us When you restart a computer that is running Windows Server 2003 or Windows 2000 Server, the computer stops responding, or the "Applying computer settings" screen appears for longer than you expect http://support.microsoft.com/kb/905716/en-us Hope it helps. Xiu

Hi Xiu, First, I am very thank you of your detail and kindly answer and tips for me. Now it work, the reason is like you said here .... "Domain Controller boots up slowly when pointing to itself as the only DNS server" I had install other DC for backup.... and the Exchange Server's DNS just only one IP, and only post to itself .... After I add the second DC's IP to the Exchange's Second DNS fill box, reboot, it go general, I spend half of day to troubleshooting this problems .... One question ... if the second DC dead, and the Exchange's DNS have two IP, both itself and the dead DC IP, will it happened again above problems?? Thank you again, and wish you have a nice day. Regards, Jimmy

Hi, The DNS Client service uses a server search list that is ordered by preference. This list includes all preferred and alternate DNS servers that are configured for each of the active network connections on the computer. WindowsServer2003 rearranges these lists based on the following criteria: 1. Preferred DNS servers are given first priority. 2. If no preferred DNS servers are available, then alternate DNS servers are used. 3. Unresponsive servers are removed temporarily from these lists. If the DNS Client service stops, the computer will not be able to resolve DNS names or locate Active Directory domain controllers and users may not be able to log on to the computer Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003 http://support.microsoft.com/default.aspx?scid=kb;en-us;825036 System Services-DNS Client http://www.microsoft.com/technet/security/guidance/serversecurity/tcg/tcgch07n.mspx Hope it helps. Xiu

Xiu, Thank you again of the other detail inform for me. Wish you have a nice day and all best. Best Regards, Jimmy Chan