sharing experiences…
On a newly installed Windows 2008 server (HP DL360G6), I found the following error in my event log:
Log Name: System
Source: Service Control Manager
Date: 30-7-2010 8:52:42
Event ID: 7026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: servername
Description:
The following boot-start or system-start driver(s) failed to load:
cdrom
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.