VMware
Welcome to Part 3 of our vSphere 5.5 installation.
If you missed any of the previous parts of the series or want go back here is the jump list:
- vSphere 5.5 - Part 1 - ESXi Server 5.5 (inc U1) Install
- vSphere 5.5 - Part 2 - vCenter Single Sign On (SSO) Install
- vSphere 5.5 - Part 3 - vCenter Inventory Service Install
- vSphere 5.5 - Part 4 - vCenter Server Install
- vSphere 5.5 - Part 5 - vSphere Web Client Install
- vSphere 5.5 - Part 6 Creating a Datacenter, HA/DRS Cluster and Adding a Host
So what does the vCenter Inventory Service actually do?
vCenter Inventory Service reduces direct client requests to the vCenter server with query caching, reducing the load on core vCenter Server processes.
The main use case of the vCenter Inventory Service is to manage the vSphere Web Client inventory objects and property queries that the client requests when users navigate the vSphere environment.
The vSphere Web Client requests only information viewed on the screen, so navigation is more efficient.
In vCenter Server 5.0, vCenter Inventory Service was a separate process. With the updated vCenter Server, it is now a separate independent component and can be offloaded to a separate server or closer to the vSphere Web Client.
This reduces traffic and improves response times.
I thought I would share this one with you all showing the reliability and stability of VMware ESX 4.0 ...
If you new to vSphere 5.1 or 5.5, you might be asking what is the Single Sign On thing?!
"vCenter Single Sign On (SSO) is a component of the VMware Cloud Suite. SSO deals with identity management for administrators and applications that interact with the vSphere platform.
SSO is based on identity management technology built by RSA and specifically tailored for VMware Cloud Infrastructure deployment."
In english what this means is that previously when you logged into vCenter via vSphere Client you authenticated directly with Active Directory.
However now when vSphere Client connects to vCenter, it's authenticating via vCenter SSO. Which in turn has your Active Directory as an authentication method.
As the VMware product portfolio expands what VMware are trying to do is use SSO for authenticating all their products.
To provision and present a Windows 8.1 (or Windows 8/7) virtual desktop via VMware View, there are a couple of VMware components that need to be installed on the master image and a number of steps performed.
In this part I will guide you through the steps to build a Windows 8.1 master image which will used to provision a desktop pool with View Composer linked clones.
Summary of Steps:
-
Create Virtual Machine
-
Install Operating System
-
Configure Operating System
-
Install VMware Tools
-
Install View Agent
-
Shutdown VM
-
Snapshot VM
Share this blog post on social media:
Tweet
Latest Blog Posts
- vSphere 7 U1 - Part 3 - Creating a Datacenter, HA/DRS Cluster and Adding a Host
- vSphere 7 U1 - Part 2 - Deploying vCenter 7.0 U1 VCSA
- vSphere 7 U1 - Part 1 - Installing ESXi 7.0 U1
- Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM
- View Administrator Blank Error Dialog/Window After Upgrade