Archive

Archive for the ‘Uncategorized’ Category

Quick Post: Windows Update Error 80244010

February 5, 2016 Leave a comment

When checking for Windows Updates it fails with an error code 80244010.

80244010

From what I can tell it’s an intermittent connectivity issue (or firewall block, etc.). I had to click Try again a few times but then it worked.

Error connecting to server conosle in vSphere client

October 27, 2013 Leave a comment

Description – When connecting to a server’s console you receive an error that says, “Unable to connect to the MKS: Failed to connect to server esxi01.laptoplab.net:902”

MKS Error

Cause – This is due to a DNS problem where the computer connecting to the console cannot resolve the name for the ESXi hosts. This is likely to happen in a lab environment. If this is happening in a production environment then you need to troubleshoot why you cannot resolve the names for your ESXi hosts. May be a sign of a bigger problem.

Solution/Workaround – Create HOSTS file entries for the ESXi hosts management IPs.

Categories: Uncategorized Tags: , , ,

Trainsignal Contest

September 19, 2012 Leave a comment

Trainsignal is having a contest to win a free trip to either Microsoft TechEd, Cisco Live, or VMworld. Follow the link to enter.

http://bit.ly/PQgeYx

Categories: Uncategorized

NLB Error

January 5, 2012 Leave a comment

I was checking some settings on my NLB cluster for my Terminal Services farm when I got the following error for one of the server.

Could not locate NLB on the specified computer. Error connecting to “server1.abc.com”

Looking through the Event Log I saw a bunch of random errors:

1104 – GroupPolicy – Windows was unable to read the Windows Management Instrumentation (WMI) filter information associated with the Group Policy object…

1090 – GroupPolicy – Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user.

2314 – Server Administator – The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible.

7034 – Service Control Manager Eventlog Provider – The DSM SA Data Manager service terminated unexpectedly.  It has done this 1 time(s).

The fix, run winmgmt /salvagerepository. If you get the error below, run the command again. You may need to find the service(s) that stopped & start it again (or reboot the server).

WMI repository salvage failed
Error code: 0x8007041B
Facility: Win32
Description: A stop control has been sent to a service that other running services are dependent on.

Categories: Uncategorized
%d bloggers like this: