Jan 02
When installing ChangeAuditor form Quest (a next, next finish installation) I received an error when I tried to logon with the client but I did not get any error during or after the installation. I got the following error:
Info","Could not connect to net.tcp://<FQDN>.local:49309/Service. The connection attempt lasted for a time span of 00:00:02.0779654. TCP error code 10061: No connection could be made because the target machine actively refused it <IPadress>:49309. "

Continue reading »
Feb 21
When installing the Microsoft System Center Operations Manager (SCOM) 2007 R2 database on a Microsoft SQL Server 2008 R2 the installation failes because a prerequisite is not met:

This is caused by an outdated installer which doesn’t recoginize SQL 2008R2. Altough installing on SQL 2005 / 2008 will prevent this message there is an alternative.
Continue reading »
Oct 06
When I configured a new template in VMware Labmanager I got a blue screen of dead with a stop code 0x0000005D. I knew that de ISO I was using was fine because i used it with in vCenter a few times.
The solution is easy I just forgot to choose the right virtual hardware profile. The default of VMware Labmanager is Windows 2003 and I had the Windows 2008 R2 CD mounted.
You can choose the right hardware profile at the properties tab and than select the appropriated Guest OS.
Jun 04
When creating a virtual machine from a template in VMware Vsphere, most of you will make use of the “Guest Customization Wizard” to create a new SID for Windows Virtual Machines and other sort of things in which you want your new virtual machine to differ from the template.
Normally this is no problem, but when you want the newest of the newest like Microsoft Windows Server 2008 R2 64-bit, VMware doesn’t support guest customization, not even when you have updated your ESX and Virtual Center to the latest software-level. You get the following message:
Continue reading »
Feb 11
When installing vCenter on Windows 2008 R2 and you’re planning to connect to a Windows 2008 SQL server you must use a 32 bit ODBC DNS. This is old news for the most of us. But When your planning to use the Windows 2008 (R2) as the platform for vCenter you must first install the Microsoft SQL Server 2008 Native Client on the server or else there is no Native client visibly in het selection menu form ODBC.This dynamic-link library is not default present on your system en must be installed separately.
So download the Microsoft SQL Server 2008 Native Client for W2008 or W2008R2. Watch out read the page carefully because there are a lot of download links on them. You must have the Microsoft SQL Server 2008 Native Client. install this on the system you plan to use for vCenter. Go to %systemdrive%SysWOW64odbcad32.exe and make you’re 32 bit DNS in the System DNS tab. For more information see ICT Freak