RE: [ActiveDir] Server Reboot problem after SP4 installation

[Jim Patton]

Title: Message

When I re-applied SP4 I had the option to archive the files which would have overwritten the SP3 archive files. I elected not to overwrite the SP3 archive so that I would still have the rollback option available.   Compaq is going to replace the CPU this evening. I doubt seriously that it will resolve the problem, but it will eliminate the last piece of hardware that could possibly be contributing to this problem. If the problem remains the same, I’m going to roll back to SP3 on the one of the three servers that is currently affected. If rolling back to SP3 resolves the problem, then I’ll rollback to SP3 on the two remaining servers plus my 2nd domain controller.     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Weeks, Travis (COX-Atlanta) Sent: Thursday, September 18, 2003 4:59 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Server Reboot problem after SP4 installation   I had an issue with one of the 45 or so DC's I installed SP4 on.  It would reboot itself every few hours for no apparent reason.  Dropping it back to SP3 fixed the problem.   One thing to think about is that if he has already reapplied SP4 then he probably does not have the ability to uninstall SP4 and go back to SP3.  Doesnt the unintall folder get overwritten if you reapply the service pack? -----Original Message----- From: George Arezina [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 2:21 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Server Reboot problem after SP4 installation Jim, I could not agree with you more. Most techie support guys fall back on the same answer, “rebuild your server”. I would really like to see them rebuild a server if they did not have extra hardware to fall back on. I ran in the same trouble with Dell servers. We have Dell 1400, 2400, 2550, and 4400 servers. After my install of SP4 on 2550 series, problems became evident. I read back in July an article on SP4 http://www.winnetmag.com/Articles/Index.cfm?ArticleID=39644 It gave me a good warning what to expect once I installed SP4. Some of those problems appeared in my environment. I run a terminal server farm across 150 locations within Serbia. I installed SP4 on one server; my users reported all sorts of problems. I uninstalled SP4 and now run SP3 on all my servers until MS comes out with the next SP. My suggestion to you is uninstall SP4 and install only the security patches. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Patton Sent: Wednesday, September 17, 2003 20:25 PM To: [EMAIL PROTECTED]   I ran into a bit of a problem after upgrading six nearly identical servers to SP4. All six servers are Compaq DL380 G2’s running Windows 2000 Server and are nearly identical when it comes to the hardware configuration. Minor differences in the total RAM and total hard drive capacity that is installed.   The problem is that of the six servers, three will no longer shutdown or reboot properly. Both the shutdown and reboot process takes me to a black screen which then makes it necessary to manually power-off the server.   Using Compaq Insight manager and the latest version of SmartStart, I’ve made sure that all Compaq Drivers and Bios updates have been installed. No change in the problem.   I’ve reapplied SP4 – no change.   I re-installed the latest Compaq video drivers – no change.   I’ve applied all the latest Microsoft updates and hotfixes, which have not resolved the problem.   I’ve replaced the main system board, CPU and Smart 5i SCSI controller in one of the three affected servers – no change.   Compaq is suggesting that I re-build the servers to resolve this software problem. That’s a bit easier said than done considering that the servers in question are my first AD Domain Controller, my one and only Exchange Server, and a server used to provide services including VPN authentication.   My next course of action is to uninstall SP4 and rollback to SP3.   I was hoping that someone on this list might have already encountered this problem or may be able to offer some suggestions before I pay Microsoft to help me resolve this problem.   Thanks