Today I was looking for the Top 10 blog posts of year 2009 at the VMpros blog. The ten posts with the most hits, retweets and pingbacks I posted down here:

VMware: Howto setup vCenter Server 2.5 on Linux connecting to Oracle XE 10g Release 2 – Part I

VMware: Howto setup vCenter Server 2.5 on Linux connecting to Oracle XE 10g Release 2 – Part II

VMware: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 1

VMware: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 2

VMware: Get a vSphere Client working on a Windows 7 machine

VMware: Reload the vmx from Service Console

VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server (1010828)

VMware: Terminal server performance tuning on VMware ESX

VMware: Host Upgrade Utility 4.0, ESX 3.01 to ESX 4.0.0

Microsoft: How to Migrate Printers from Windows 2003 to Windows 2008

To use Microsoft Windows Cluster Service in VMware ESX you need to config you’r VM’s with independent persistent disks.

VM configuration:

I deployed two Windows 2003 SP2 Enterprise 32-Bit VM’s with both 12 GB of OS disks and two NIC’s. I called these: VMPROS-CL01 and VMPROS-CL02.

VMPROS-CL01 with ip: 172.16.254.78 and for MSCS nic ip: 1.0.0.1

VMPROS-CL01 with ip: 172.16.254.89 and for MSCS nic ip: 1.0.0.3

Registered this VM’s in domain VMpros.nl

  Read more…

For more info why see: http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx

Since alot people use it for windows xp we decided to publish NewSID via our site.

You can download NewSID here

I just installed a Windows 2008 behind a proxyserver  and i saw that it couldn’t update.

To solve this issue you can do the following:

• Run the Command Promp as Administrator
• Type netsh
• Type winhttp
• Type import proxy source=ie

Now Windows Update will ask you for a username and password before it wants to check for an update.

By re-installing Client Access Role (CAS) on my Windows 2003 R2 Enterprise 64 bit and Exchange 2007 Enterprise machine I get:

“The Microsoft Internet Information Service is in 32-bit mode and this is a 64-bit computer. The mode must be changed before Setup can continue”

Read more…

After reinstalling CAS yesterday (Client Access Role) in Exchange 2007 I get every minute a SSL Certification prompt for accept of install the certificate in Outlook 2007:

Read more…

Today I updated Exchange 2007 SP1 with rollup 6 to (Windows 2008 Standard SP1 64 Bit) rollup 7, 8 en 9. After each installation I rebooted the server en checked if de Database was mounted. After installation of Microsoft Exchange Rollup 9 and restart server I can’t connect my mail database. I receive this error:

Error:

Exchange is unable to mount the database that you specified. Specified database DOMAIN\First Storage Group\Public_Folders; Error code:MapiExceptionCallFailed: Unable to mount database. (hr=0×80004005,ec=-1023)

Read more…

Some customers had some problems with bad Exchange performance when McAfee GroupShield 7.0 Patch 1 is installed. McAfee released a new hotfix called: Hotfix 491164

Information about the hotfix:

Environment

McAfee GroupShield 7.0 + Patch 1 for Microsoft Exchange
Microsoft Windows 2003
Microsoft Windows 2008
Microsoft Exchange 2003
Microsoft Exchange 2007

Problem

After starting the McAfee GroupShield 7.0 service, delays may be experienced with email processing. If the GroupShield service is stopped, mail delivery and processing returns to normal levels.

Cause

One of the processes used by GroupShield, (the Postgres process), takes an extended time to complete its I/O (input/output) operations. As a result, the GroupShield reporting threads have an extended waiting time which increases the RPC Averaged latency and results in a delay while processing email messages.

Solution

This issue is resolved in Hotfix 491164 for McAfee GroupShield 7.0 + Patch 1.

Hotfix package name: GSE7HF491164.ZIP

For more information: https://kc.mcafee.com/corporate/index?page=content&id=KB66095

Little note: Hotfixes are created to address specific issues and are not posted publicly, but are available by contacting McAfee Technical Support. I installed the hotfix and it’s resolved my problem.

When you install Exchange 2007 it’s standard configured that it doesn’t allow extern mail.

Mostly you get the error “530 5.7.1 Client was not authenticated”

You can resolve this by giving the AnonymousUsers group receive rights.

You can do this via the exchange 2007 shell.

First get the receive connector name:

Get-ReceiveConnector

Then use the following command:

Set-ReceiveConnector -Identity “MAILSERVER\Default mailserver” -PermissionGroups “AnonymousUsers”