About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
One of the lesser known features of VMware ThinApp is that you can supply a Virtual Computer name.
This is documented as follows in the package.ini reference guide:
The VirtualComputerName parameter determines whether to rename the computer name, to avoid naming conflicts between the capture process and the deployment process.
There are various scenario’s where this parameter is convenient, some examples:
In the first example the solution is simply to fixate the computername. You might also want to fixate the volume serial number. See License check fails on Citrix XenApp for an example.
The second example is especially problematic in VDI Environments (user could have a different machine each day) or SBC (load balancing over a farm of servers).
For a natively installed application we can use the Terminal Server Application Compatibility mechanism to return a username instead of a computername.
With ThinApp we can simply set the VirtualComputerName to an environment variable, so we can solve the problem like this:
.NET .NET FrameWork Active Directory Altiris Apple Automation Manager Citrix Dell Delphi Excel Exchange Exchange2003 Exchange2010 Hack HP iOS Java LinkedIn Linux Lync MSI Office Office 2010 Passat Password PowerPoint PowerShell RES RNS510 SasLibEx SCOM Security Terminal Server ThinApp TSAdminEx VBS VCDS Visual Basic Visual Studio VMWare Volkswagen VW Windows PE Wordpress XenApp