“Warning: Syslog is not configured. Please check the Syslog options….” message after upgrading to VMware ESXi 4.1 Update 2

After upgrading an ESXi 4.1 host to Update 2 the following warning message was displayed on the summary tab  in the vSphere client:

Warning: Syslog not configured. Please check Syslog options under Configuration.Software.Advanced Settings in vSphere client.

This happens to be a fix rather than a bug =) The following issue is resolved in the Update 2 package as you can read in the Release Notes:

The vSphere client does not display an alert message if Syslog is not configured
If the configuration information is not found while loading the syslog.conf file, an alert message related to configuration issues is not displayed in the Summary tab of the vSphere client.

This issue is resolved in this release. You can now see the following message in the Summary tab of the vSphere Client if Syslog is not configured:

Warning: Syslog not configured. Please check Syslog options under Configuration.Software.Advanced Settings in vSphere client.

The warning was correct because there was nothing configured for this setting.

So I checked the other hosts, which I upgraded earlier for their value of this setting. The totally logical value of [] /scratch/log/messages came to light. I didn’t look any further and put in the same value on the host that had the error.

No more worries 😉


VMware vCenter Server Active Directory Web Services LDAP error on instance ADAM_VMwareVCMSDS

While browsing the vCheck 5 report (Thank you Alan), I noticed the following error:

Active Directory Web Services encountered an error while reading the settings for the specified Active Directory Lightweight Directory Services instance. Active Directory Web Services will retry this operation periodically. In the mean time, this instance will be ignored. Instance name: ADAM_VMwareVCMSDS

Luckily this error is documented e.g. here and here.

Replace the ‘Port SLL’ REG_SZ key under HKLM\SYSTEM\CurrentControlSet\Services\ADAM_VMwareVCMSDS\Parameters

for a REG_DWORD key with the name ‘Port SSL’ and decimal value 636 (or simlpy create the key)

UPDATE: Thank you David Ho, for the correction =]

Now restart the VMwareVCMSDS service and the error should be gone.

Please note: This is a fix for vCenter Server 4.1 and 5.0 on Windows Server 2008 R2. Running vCenter Server 4.0 on Windows Server 2008 R2 is not supported until Update 3. I got this error after a fresh install of vCenter 5.

Migrating Terminal Server Licenses from Windows Server 2003 to Windows Server 2008 R2 using the Remote Desktop Licensing Manager

Here’s a step-by step guide to migrate your Terminal Server licenses from a Windows Server 2003 server to a Windows Server 2008 R2 server.

Why 2008 R2? Because it has a kind of transfer wizard that isn’t present in 2008. If you want to transfer your licenses to 2003 or 2008 server, you’ll have to get on the phone with Microsoft. In both situations you’ll need the authorization and/or license codes, so keep them at hand. If you can’t find them anymore, you can ask Microsoft to send you a license report for your company. You’ll also need a connection to the Internet so the wizard can contact the Microsoft Clearinghouse server to register your transfer.

Start the Remote Desktop Licensing Manager

Add your servers to the overview screen to the left by right clicking on All servers and choosing Connect

You’ll end up with something like this:

Right click your new server and choose Manage Licenses

The Manage licenses Wizard will start. Click Next on the welcome screen

The wizard will try to contact the Microsoft Clearinghouse server

Now choose your action. I’ll choose the first option because this a a migration and not a disaster recovery

Put in the source license server’s DNS name

I had to put in the IP address because our source license server had a name with an underscore and the wizard did not like that

Agree to discontinue using the source license server

Choose you license program

I chose Open License which required me to input the Authorization number and License number

Choose your product version, license type and the quantity

The licenses will be migrated

You’re done

If you receive the error “The Microsoft Clearhouse server could not be contacted. Ensure that you have Internet connectivity …..”, you can try to first open a browser windows to http://microsoft.com and (repeatedly) try the last step (press Back and Next) of the migration again right after the Microsoft website appears. This resolved this weird problem in my case.

%d bloggers like this: