isthewebsitedown » Windows 2003

SBS new install checklist

admin — Fri, 30 Apr 2010 16:07:52 +0000

I was going to make one, but this guys is much better: http://blog.mpecsinc.ca/2009/05/sbs-2008-setup-checklist-v111.html

I am working on a checklist for a migration from standard server or sbs 2003/2000. Look for it soon.

Download HKCRScan.exe tool for troubleshooting MS Article ID 823159

admin — Tue, 01 Dec 2009 19:05:24 +0000

Users were getting a “HTTP/1.1 503 Service Unavailable” on both https:///Exchange , https:///Public and on https:///microsoft-server-activesync, they get a login prompt and then a “HTTP 501/HTTP 505″

The below tool should be run from the command prompt. It should identify and remove registry keys over the 259 character limit. It will kick back any errors. If you have null keys (keys that are faulty but unremovable), you can use RootKitRevealer from sysinternals and get rid of them. I understand that regdelnull can do something similar, but in this case, it was a corrupt key, not a key with null characters.

In my case, the affected key was relating to the driver for the Intel storage controller (VEN_8086&DEV_24D3&SUBSYS_458015D9&REV_02). Not cool. I could not delete or rename the key and could not set/view permissions on it. Ran RootKitRevealer, which caused a stop error/reboot (crap) but successfully removed the key. IN OTHER WORDS, DO NOT DO THIS IF YOU DO NOT HAVE A TESTED BACKUP.

“To help troubleshoot this issue, run the HKCRScan tool (HKCRScan.exe). The HKCRScan tool enumerates the HKEY_CLASSES_ROOT registry hive to locate subkeys that contain more than 259 characters. Additionally, HKCRScan helps determine if there is an invalid discretionary access control list by returning error code 0×5. This error code means “Access denied” when it enumerates a registry key. The HKCRScan tool is an internal tool developed by Microsoft.”

Download: HKCRScan

Weird Problem of the Day: Windows 2008 R2 and Windows 2003 DC’s Not Replicating

admin — Thu, 12 Nov 2009 17:42:58 +0000

OK, one of our techs was onsite upgrading a basic single server DC/File Server/App Server. He joined the server to the domain, promoted it and ensured that the files in the sysvol share were replicating. Everything looked fine. He transferred the FSMO roles, again without error. When he ran the dcpromo on the old server to demote it, he got an errors saying that

“The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers”

Weird. So I had him do all the normal steps, moving FSMO back and forth, waiting 15 minutes, restarting netlogon and FRS services. Nothing helped. FRS was running, stuff was replicating, but apparently something was still missing.

Running “repadmin /showreps” yielded a few errors:

“Last attempt @ 2009-11-12 18:45:37 failed, result 1256 (0x4e8): The remote system is not available. For information about network troubleshooting, see Windows Help.”

Bottom line, R2 and 2003 servers sometimes have security problems replicating between them. There is a hotfix, probably the worst-titled one in history, to fix it.

“Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: “No authority could be contacted for authentication” when you use Remote Desktop Connection”

Crap huh? No way you would find that if you were searching for a problem with AD replication. There is a tiny note in there that one of the problems you might experience is replication-related. So we requested and ran the hotfix, rebooted and magically dcpromo worked as the maker intended it to. I hope that this makes it into a service pack or critical update at some point soon, because we have a lot of Windows 2003 servers that are eventually going to need to be replaced.