As if 2016 weren’t bad enough…this year is going to be slightly longer than normal. New Year’s Eve will be one second longer in 2016 to adjust for the shifting rotation of the Earth.
A leap second is a one-second adjustment that is sometimes applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time, or UT1.
This leap second has the potential to cause chaos for IT systems that cannot deal with a 61-second minute. Websites such as Reddit, Yelp, LinkedIn have previously experienced outages for a period of time due to the leap second in 2012.
Most VMware products are unaffected by this time change that will occur this weekend However, some products are affected. Please see KB 2147498 for more information.
For those VMware products affected, the common work-around is to enabled Slew Mode for NTP. For more information see KB 2121016.
I’m excited to announce that I will be attending Tech Field Day 13 as a delegate. TFD13 will be held in Austin from 1-3 February 2017.
What is Tech Field Day? It is an event that brings together tech vendors and independent thought leaders to discuss products and share information and opinions.
I’m looking forward to hearing all the presentations from the different vendors and sharing what I learn. I can’t wait to share my experience from my first time as a delegate.
For more information about Tech Field Day, you can visit the site here. Or to find out how to become a delegate, you can go here.
Nothing is more fun than walking into a client site on a Monday morning and something that’s supposed to be easy (installing Horizon Agent in base image) doesn’t work.
I logged into the Windows 7 virtual desktop image and tried to install the Horizon Agent, however, I received a message stating: “The system must be rebooted before installation can continue.” Seemed simple enough, so I restarted the machine, and tried again. Same error. #facedesk
Did some digging and found an old KB (1029288). The KB doesn’t say that it is applicable to Horizon View 7.0.x but it solved the issue I was having.
First I tried to uninstall and re-install VMware Tools. No luck.
I went through the registry keys suggested by the aforementioned KB but there weren’t any associated strings associated with the registry keys.
At the very end of the list, two registry keys were listed:
There were values located in HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce, so I deleted all the values, rebooted the machine.
Voilà! I was finally able to get the Horizon Agent to install so I could proceed with my day. It appeared that there was a previously failed installation that was preventing the Horizon Agent from launching its own installer.
When provisioning Horizon 7 Instant Clones, you may have noticed some new folders that were created in the VM and Template view in the vSphere Web Client.
Each of these folders has a specific purpose for Instant Clones:
- cp-template-xxxx – Virtual machine that is a template used to create Instant Clones; this is created from the master image.
- cp-parent-xxxx – These virtual machines exist in a 1:1 relationship to the number of ESXi hosts in the cluster. I have a four node cluster, therefore I have 4 clone prep parent virtual machines. Each ESXi host has one of these powered on and in memory in order to provision the Instant Clone VMs.
- cp-replica-xxxx – This virtual machine is used to create the clone prep parent virtual machines. It will be also used as necessary to provision additional clone prep parent virtual machines.
- If the Instant Clones are updated with a new image, a virtual machine will be created here for staging purposes.