where IT meets experience
Today, my SCOM server noticed me something was wrong with my DNS servers. On both DNS servers I got the following error:
Alert: DNS 2003 Server External Addresses Resolution Alert
Source: %
Path: %
Alert description: DNS Server % cannot resolve external address .
Alert view link: %
If you have a KMS server running, newly installed servers will automatically activate. However, you can also manually activate your server by entering the command slmgr.vbs /ato
In my case, I recently installed a Windows 2008 SP2 server, but couldn’t get the machine activated. Everytime I ran the command slmgr.vbs /ato, the following error returned:
In Windows 7, the Remote Registry service is stopped by default. The startup type is Manual. This setting leads to the following error when you try to connect to the registry from another computer on the network:
As an system administrator, I know how difficult it can be to solve Windows Update errors. This is particularly the case with Windows Update, because Windows Update always returns generic errors. KB-articles will likely not help you, because these articles are written with theoretical knowledge, and are barely based on real-world scenarios.
On some of our HP DL360G6 servers, the following warning (event id 37) showed up in the event log of Windows 2008 R2
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 12/21/2009 5:04:12 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: <servername>
Description:
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 2139 seconds since the last report.”