Category: vmware

Installing ESXi 5.0 on a HP Proliant DL380p Gen8 – and failing?

If you land here at this post my guess is, that you are confused, cause what used to business as usual ended up with an error saying no network available. Well a fix could be here. My guess is that you have installed using the ESXi ISO provided by vmware, this is the first fail, you have to use the image provided by HP or build your own. (at least at the time of thisLearn More

How-to: Upgrade Windows Server 2008 R2 from Standard to Enterprise without a media.

Phase 1: Dism /online /Set-Edition:ServerEnterprise /ProductKey:489J6-VHDMP-X63PK-3K798-CPX3Y (This is the default KMS Key 3 days activation for Windows Server 2008 R2, provided by Microsoft, hopefully im allowed to publish this key here, anyways this license provides 3 days of access to register your own key.) You have to use this KMS key in order to make the upgrade work, after the upgrade your Windows will have 3 days to activate, Activating using GUI, will disable aLearn More

SSH Access to ESXi 5

If you like me need the oppotunity to use SSH once and a while, in your ESX envoirment, then you might wanna take a look at this post. First let it be saif that, when you ENABLE SSH access, your host shows a yellow exclamation inside your vCenter, don’t worry, thats normal and it clears, once you disable SSH access again (which of coarse you do) Well to ENABLE, follow the steps below: Enabling ESXiLearn More

Removing “ghost nic”

***UPDATE 14.03.2018*** During Microsoft patch Tuesday (14-03-2018), MS released a patch that tampered with the NIC within vmware. This is seen througout the World and has frustrated many admins. The fix is however very simple just follow the instructions i provided several years ago, regarding, what i call ghost NIC. This could happen during P2V migrations and during vmxnet3 updates. The problem seems related to Windows Server 2008 R2 but maybe not limited to thatLearn More

Wrong Scsi adapter Windows 2003

When you have converted a Windows Server 2003 to a virtual VM you may experience the following Message from esxi.xxx.local: The guest operating system is Windows Server 2003 and one or more virtual SCSI devices are installed in the virtual machine. Windows Server 2003 does not support the BusLogic SCSI adapter that VMware ESX currently uses for virtual SCSI devices. Install the VMware driver in the virtual machine. Download the driver from “http://vmware.com/info?id=43“. Click OKLearn More

Converting with vCenter Converter Boot CD

Yesterday when i tried to convert a physical domain controller i received an error after around 2% completion, the error wrote “ERROR: unable to open file %s” i had checked vmware tools and remove system recovery points so no options left to tweak, i quikly found out that this error was related to DNS, so i checked my DNS settings and found a miss typing. I corrected that and voila.

© 2021: Noervig's notes | Easy Theme by: D5 Creation | Powered by: WordPress