![]() Run the Connection server installer, and a few clicks later, I was looking at the login prompt to the Horizon Admin Console. ![]() The install of the Horizon Connection Server in my lab was pretty easy. This is a good thing – and why it is a good idea to get in the lab often. Some of the smallest things (ahem configuring network stack) took me a bit and forced me to learn something new. I have to admit it was a bit “different” not have any of the familiar GUI interfaces. I have always been pretty comfortable at command line and wanted to try out Windows Server Core. ![]() I decided to try Windows 2016 Server Core for my connection server. Do I run 2012 now, and upgrade it later or jump to a newer version now? Lab Headaches can turn into knowledge Horizon 2006 does not support Windows Server 2012 so I had to make an early choice. I had been using Windows Server 2012 in my lab as those were the latest licenses I was able to get from my Microsoft Technet subscription before they ended that program. I decided to install Horizon 7.12, setup a few desktop pools and learn about Instant Clones with an eye to upgrading to Horizon 8 (aka Horizon 2006 as it prefers to be known) in the near future. It has been a while since I have done much with Horizon so I thought setting it up in my lab would help me get up to speed. Recently I started working with a new customer who is migrating to VMware Horizon View.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |