VIDM 3.3.x – Quick Tip – Lost your vApp Properties on your VIDM VMs?

Hellooo!

The other day I was upgrading VIDM (now called Workspace One Access) from 3.3.2 (SLES based) to VIDM 3.3.4 (Photon OS Based) and during the upgrade all my VIDM appliances lost their IP Configuration / Network Settings. I was performing this upgrade as part of the vRealize Automation 8.1 Upgrade to vRealize Automation 8.4.

It turns out that the Network Settings are not taken from the OS itself but from the vApp options configured in your vCenter for your VIDM appliances / VMs. The vCenter server crashed a while back and had to be rebuilt. Due to this the vApp Configuration was lost for each of the VIDM VMs and the Network Settings were lost during the VIDM upgrade.

In this blog post I’ll provide you with the default VIDM vApp Properties for your VIDM VMs in vCenter, make sure to set them before upgrading your VIDM Appliances! See the following KB for more information: https://kb.vmware.com/s/article/83587

General vApp Options

Let’s start with the General vApp options.
In vCenter go to your VIDM Virtual Machine, select Configure and click on Edit as shown below:

These general vApp properties can be set as shown below:

General ConfigurationValue
vApp StatusEnabled

IP AllocationValue
Authoring
IP protocolBoth
IP allocation schemeAll UNchecked
Deployment
IP protocolIPv4
IP allocationStatic – Manuel

OVF DetailsValue
OVF environment transportVMware Tools
Installation bootenable UNchecked

DetailsValue
NameIdentityManager
Product URL
VendorVMware,Inc.
Vendor URL

vApp Properties

The next thing to do is to set the vApp Properties on your VIDM Virtual Machines.

In vCenter go to your VIDM Virtual Machine, select Configure and scroll down to the Properties section. To add properties click add:

The VIDM vApp Properties can be set as follows (please set the ‘Value’ field to your Environment’s Value):

CategoryLabelKey class IDKey IDKey Instance IDDescriptionTypeChoice ListUser configurableDefault ValueValue
vmnamevmvmnameStringNoIdentityManager
ApplicationJoin the VMware Customer Experience Improvement Programceip.enabledSend anonymous customer experience data to VMware.BooleanYesTrueFalse
ApplicationTimezone settingvamitimezoneSets the selected timezone.String Choice“Pacific/Samoa”, “US/Hawaii”, “US/Alaska”, “US/Pacific”, “US/Mountain”, “US/Central”, “US/Eastern”, “America/Caracas”, “America/Argentina/Buenos_Aires”, “America/Recife”, “Etc/GMT-1”, “Etc/UTC”, “Europe/London”, “Europe/Paris”, “Africa/Cairo”, “Europe/Moscow”, “Asia/Baku”, “Asia/Karachi”, “Asia/Calcutta”, “Asia/Dacca”, “Asia/Bangkok”, “Asia/Hong_Kong”, “Asia/Tokyo”, “Australia/Sydney”, “Pacific/Noumea”, “Pacific/Fiji”YesEtc/UTCEurope/Paris
Networking PropertiesDNSvamiDNSIdentityManagerThe domain name servers for this VM (comma separated). Leave blank if DHCP is desired. All fields but hostname are required for static IP.StringYes10.10.2.9,10.10.5.9
Networking PropertiesDefault GatewayvamigatewayIdentityManagerThe default gateway address for this VM. Leave blank if DHCP is desired. All fields but hostname are required for static IP.StringYes10.10.2.1
Networking PropertiesDomain NamevamidomainIdentityManagerThe domain name of this VM. Leave blank if DHCP is desired.StringYesmikelab.local
Networking PropertiesDomain Search PathvamisearchpathIdentityManagerThe domain search path (comma or space separated domain names) for this VM. Leave blank if DHCP is desired.StringYesmikelab.local
Networking PropertiesHost Name (FQDN)vami.hostnameThe FQDN name for this VM. Leave blank for DHCP or reverse DNS to be used to lookup hostname.StringYesvidm-01.mikelab.local
Networking PropertiesIP Addressvamiip0IdentityManagerThe IP address for this interface. Leave blank if DHCP is desired. All fields but hostname are required for static IP.StringYes10.10.2.20
Networking PropertiesNetmaskvaminetmask0IdentityManagerThe netmask or prefix for this interface. Leave blank if DHCP is desired. All fields but hostname are required for static IP.StringYes255.255.255.0

Hope this post was of help for you.

Have a nice day!

One thought on “VIDM 3.3.x – Quick Tip – Lost your vApp Properties on your VIDM VMs?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s