|This will be a “note to self” kind of post. But I guest if you work with IBM or vendor based Windows Server media like IBM’s ROC/OEM you will run in to this. When you get the Windows Server 2012 R2 Datacenter ROC media from IBM, and try to install it in a VM on a IBM VMware vSphere host, you will get to a point where the installer stops and says :|
|IBM has been so kind to include a system check, to see if the media is used on a non IBM server. This is okay, but in my case the host is a IBM System x! The checker is not designed to run on a VM so you have to do one of two things. 1) you could go out and find a retail Windows Server 2012 R2 DC OEM media that has no hardware vendor checker. 2) you can edit the .vmx file of the VM to add the SMBIOS.reflectHost and set it to true like this : SMBIOS.reflectHost = “true”. This updates the virtual machine BIOS with the IBM Original Equipment Manufacture (OEM) information required to use IBM-provided Operating System (OS) installation media. IBM addressed this with there Windows 2008/R2 ROC media, but it is still true with Windows Server 2012 R2.|
|Please leave a comment below if you have similar experiences with other vendors or any comment to this post. Thank!|
|Okay, so I got this error in the event log (ID 5003) on a Exchange Server 2010, after a update and a reboot of the server. The Information store service could not start up|
Event ID 5003: Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
|The time was okay on the server and the DC (PDC) was okay. Then I checked the VMware tools to see if the “Time Sync” Feature of the vmware tools was disabled, and it was. I noticed after a second reboot that the time was off by 10 minutes, and then jumped back to the correct time!?. Then I looked at the VMware vSphere host in the “Time Configuration” the time was of by… you guest it.. 10 minutes! The host was set to sync with an external time server (pool.ntp.org). But the time was off anyway. So I decided to reboot the host, to see if the time was off by 10 minutes after a reboot and it was! Then I did another reboot and jumped in the UEFI (BIOS) of the server and there it was… time in the BIOS was 10 minutes behind. I corrected it and booted the host and now the time on the host and the VM was okay even after a reboot.|
|I hope that you can use this information, I know where I will look next time there is a time sync issue in a VM. Please leave a comment below if found the useful. Thanks!|
Today I had to install a Brocade FC HBA on a IBM System x server, at a customer site. It turns out that VMware did not include the HBA driver in the vSphere 5 update 1 install media. So I had to find the driver my self. Here is a quick guide how to install the Brocade offline bundle (and for that matter other offline bundles as well. First I downloaded the Brocade Offline bundle from the support site. Then I uploaded the .zip file to the /tmp folder on the VMware vSphere ESXi 5 host using WinSCP, remember to turn on SSH for this. Next I logged in to the ESXi host using putty. From the command line I typed esxcli software vib install -d /tmp/brocade_offline_bundle.zip this starts the installation. After it’s done I rebooted the host and after the boot I could see the HBA from my vSphere 5 client. All done. Hope this will help you.
In this post I will go thru how to update VMware vCenter Server Appliance (VCSA) to version 5.0 Update 1A. First of all make sure that you have a snapshot or backup of you’re vCenter. Next log in to the webinterface https://vCenterServerIP:5480. Go to the Update tab and click the “Check Updates” Accept the EULA 🙂 and click OK to install the update Now wait… the installation can take up to 120 minutes. After the installation has completed you will need to reboot the VCSA. From the System->information tab click reboot Now you’re VCSA is updated and you are good to go. Pleas have a look at the VMware vCenter Server 5.0 Update 1a Release Notes for known issues and more
VMware har med vSphere ESXi 5 lavet en ny måde at håndtere vCPU’er på. Man vælger nu “Number of virtual sockets” og “Number of cores per socket”, jeg kunne i starten ikke se hvorfor man ville gøre dette og beslutte mig for at undersøge det nærmere. Efter lidt googleing frem og tilbage kom jeg frem til at det selvfølgelig er pgt. licensering pr. CPU socket! Fx. hvis man benytter Microsoft SQL kan man vælge en pr. bruger eller en pr. fysisk sokkel. En pr. socket er markant dyrere end en pr. brugere, der er dog et break-even som man skal tage forbehold for. Problemet her med pre-vSphere 5 versioner er at man ikke kan vælge sockets men kun “vCPU counts”. Det kan man nu i vSphere 5. Hvis man fx har en CPU med 8 cores og giver den all 8 til en VM, så vil man skulle betale 8 x socket licenser hvis det var med vSphere 4.x “vCPU counts” men med vSphere 5 kan vælge at sige 1 virtual socket og 8 cores per socket. Herved betaler man kun for en CPU licens. Så vil du spare på dine licens penge er det vær at konfigurer din vSocket’s og cores korrekt.
Efter installationen af vCenter på den embeddet SQL 2005 express er det nødvendigt af sætte databasen til simpel recovery mode, man kan også vælge at tage backup af databasen med et backup software og her vælge at tage transactions log backup. I mindre miljøer er det dog ikke nødvendigt med en fuld SQL server og express er en ok valg. Der vil komme en fejl i event loggen der hedder noget i sil med nedenstående og Eventid’et er 9002. : The transaction log for database ‘VIM_VCDB’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases For at løse problemet kan man downloaded og installere Microsoft SQL Server Management Studio Express og sætte databasen til simpel mode fra bulk-log. Det kan også være en god ide at shrike de filer der er skrevet. højre-click VIM_VCDB vælge Tasks –> Shrink –> Files. Herefter kan vCenter server servicen startes igen.
- PowerShell modul for Azure Blueprint
- Powershell CmdLet not found in Azure Automation Runbook
- Windows 10 Fall Creators Update comes with SSH build-in – Is putty dead?
- ATP safe links has been extended to iOS and Android mobile devices
- Update management, inventory, and change tracking in Azure Automation
- Active Directory (1)
- Azure (7)
- Backup (7)
- Design (2)
- Exchange (2)
- Exchange Online (1)
- Homelab (1)
- Hyper-V (1)
- Microsoft (8)
- Misc (1)
- Office 365 (2)
- SSH (1)
- Trainsignal (1)
- Upgrade (2)
- vCenter (10)
- VCP (1)
- VCSA (2)
- Veeam (6)
- VMware (45)
- Windows 10 (3)
- Windows Nano Server (1)
- Windows Server (4)
- Windows server 2012 (1)
- Windows server 2012 R2 (1)
- Windows Server 2016 (1)