VMware
vSphere PowerCLI is a command-line and scripting tool built on Windows PowerShell, and provides more than 200 cmdlets for managing and automating vSphere.
Following on from Installing VMware ThinApp 4.6 - ThinApp Part 1 we will actually create a ThinApp.
The software of choice is Adobe Reader 9.1, a very common piece of software used in the enterprise.
It is also the perfect candidate for ThinApp application virtualisation due to the constant updates to the product. With ThinApp you would just need to re-recreate the package with the update and then replace the original ThinApp package with the new one (it sure beats trying to apply it to 1000's of computers).
1. Use vSphere Client to connect to your ESXi host (or vCenter server)
2. Browse a VMFS datastore (e.g. the local ESXi VMFS datastore if it has one)
3. Upload your VMware ESXi update/patch (.zip file) to the VMFS datastore
4. Put your host in maintenance mode (VMs will need to be powered off or vMotioned to other hosts if in a cluster)
Welcome to Part 6 of my vSphere 5.5 How To Series
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
One of the first things you will configure in vCenter Server is
-
Create a datacenter
-
Create a HA and DRS cluster
-
Add an ESX/ESXi host
We will also do all these tasks from within the vSphere Web Client because we shouldn't be using the old vSphere Client anymore :-( Even though I can do this 5 times quicker using the old client!
I recently noticed an error within the Horizon View events database I had not seen before. This error was in a new environment I was configuring and testing at the time.
The specific error was:
"Failed to perform space reclamation on machine VDI-WIN81-137 in Pool WIN81-POOL1"
The error was occurring ever hour and failing to reclaim disk space from the linked clone virtual desktops. If you have a blackout period configured for specific days and times then the space reclamation process will not run during these times.
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
Popular
- Reset 3COM Switch to Factory Defaults (Forgot Password)
- Disk Consolidation Needed - Unable to access file since it is locked
- SCCM 2012 - Software Center Unable to Download Software 0x87D00607
- VMware Visio Stencils - Diagram and Icon Library
- Moving BT Infinity DSL from Master Socket to Any Household Extension Socket
- WSUS Useful Client Commands WUAUCLT.exe
- Creating/Adding a Raw Device Mapping (RDM) to a Virtual Machine
Social Links
Disclaimer
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.