Today one more interesting issue..
Even though a user account have Domain Administrator Rights, was unable to logon to Console of the DC.
Encountered error “The local policy of this system does not permit you to logon interactively”. But was able to logon through terminal services
Verified GPOs, Local Security Policy…etc… but no clue found. To my interest, found that the user account was explicitly added to “Logon Locally” list under Security –> User Rights Management of the Domain Controller Policy.
Upon some more research & googling found a MS article, which helped me in resolving the issue.
After removing the User Account from “Domain Power Users Group”, was able to logon to DC console.
Here is the article link: http://support.microsoft.com/kb/841188
Today I worked on a interesting issue.
One of my client holds a SBS Server with all roles like DNS, AD & Exchange 2007.
Actual issue: WMI not connecting from Monitoring Server. Getting error “No more threads can be created in the system. (Exception from HRESULT: 0x800700A4)”
In order to resolve this issue, rebooted SBS Server which caused another problem.
The server got stuck during booting, on “Applying Computer Settings” and was never booted up completely. Connected to Computer Management console from another comupter and verified eventlogs and services. Identified that Exchange Services were not started. Hence computer stuck on Applying Computer Settings.
Tried booting the server in “Safe Mode with Networking”, but all efforts were gone in vain.
After researching alot (for more than 2 hours) found that IPV6 was disabled on this SBS 2008 box.
Apparently, that’s what an SBS Server does ,when you kill some of it’s most critical services. I quickly learned that disabling IPV6 on an SBS 2008 server is extremely dangerous.
Stopping IPV6 leads to multiple failing services, and will cause your server to hang during booting as a result
So, I had to re-enable IPV6. The fastest – and probably only – way was to boot the server into Safe Mode with networking services enabled. It’ll allow you to re-enable the protocol. Start the server again, and give it some time. Booting will take a few minutes longer than usual, but all your problems caused by
disabling IPV6 should be fixed now.
And reboot fixed DCOM/WMI Errors too..