I am trying to execute the workflow to "Force Data Collection" via REST API.  No matter what I do, I am continuously getting Error 400.

I can run other API's in vCO, such as getting all workflows.

I assume the problem may be with the body field.  I've tried lots of different options, but cannot figure out the correct syntax to make this work.

Any suggestions would be appreciated.

Please see attached images.  Example A is a single port group, and example B is using two separate vSwitches. Are there any advantages to creating a separate vSwitch just for DMZ traffic over just placing DMZ traffic in a separate port group and using overrides to assign specific pNICs to each port group?

We can assume that proper redundancy will be present everywhere, and that the same ESXi host will serve both production and DMZ traffic.  Also assume that the DMZ traffic will be plugged into a physical firewall.  Each port group is a separate VLAN.  Again, if a single vSwitch would be used, we would dedicate specific pNICs to each port group appropriately via overrides so that the DMZ port group could not share the pNICs of the others.

I suppose I don't see any real difference in having a separate vSwitch vs doing port group overrides.  I don't believe one is any more secure than the other, but happy to learn otherwise!  Perhaps this is just preference and whatever is easier to manage?  I can imagine if I had 10 different DMZ VLANs that extra configuration would be required if the same vSwitch is used over just sticking those port groups on the switch and not worrying about where each pNIC was connected.  Any articles specific to security would be appreciated!

Thanks!

By Mark Benson, Senior Architect and Senior Staff Engineer, End-User-Computing CTO Office, VMware

• Introduction
• What are the requirements for deploying UAG appliances using this script?
• How do I run the script?
• Configuration Settings
• Standard SSL, TLS and Cipher Settings
• Managing SSL Server Certificate Files
• Network Setting for each NIC (UAG 3.3 and newer)

Introduction

In September 2015, I posted the article https://blogs.vmware.com/euc/2015/09/what-is-vmware-unified-access-gateway-secure-remote-access.html. Unified Access Gateway (UAG) is a VMware virtual appliance which is used with several VMware End-User Computing products for VMware Horizon, VMware Identity Manager and VMware AirWatch. In that article I mentioned the ability to perform a scripted deployment of a UAG virtual appliance to perform a repeatable deployment where all settings can be applied in a way that allows UAG to be production ready on first boot.

It is possible to deploy UAG in a vSphere environment using the VMware OVF Tool command. Whilst it is great to be able to specify all configuration settings in one go at deployment time, the downside of this is that the OVF Tool command line can become very long and complex. It is also easy to introduce errors on the command line as the command syntax for OVF Tool used in this way can be difficult to get right. Also, it is not possible to validate the settings with OVF Tool and it is therefore very easy to make configuration errors such as setting an admin REST API password that doesn't meet the required complexity rules.

Many Windows administrators managing a VMware End-User Computing product environment need an automated way to deploy UAG in a secure, reliable and repeatable way and to have complete control over the settings. For these reasons, we have developed a PowerShell script that can be used to deploy UAG and which overcomes the main difficulties of using OVF Tool directly on the command line. As this PowerShell script is delivered as a sample script, you can also adapt it as required for your specific needs although in most cases you won't need to modify it at all. The script calls the OVF Tool command but validates the settings and automatically constructs the correct command line syntax. The settings are taken from a simple .INI file. This script runs OVF Tool in a fully supported way for UAG deployment. Note that no password values or private key values are stored within the .INI configuration files.

The PowerShell script sets all configuration settings for OVF Tool at deployment time. This includes setting up the CA issued SSL Server certificate and all other possible settings. After UAG has been deployed by this script, there is no need to make configuration changes after deployment. UAG will be ready for production use on first boot. Using PowerShell and mastering configuration settings in a simple .ini file also simplifies the task or repeat deployments such as when upgrading UAG from one version to the next. You modify the .ova file reference in the .ini and re-run the PowerShell command. This automatically deletes the existing UAG appliance and replaces it with the upgraded image and automatically re-applies all of the initial settings from the .ini file.

What are the requirements for deploying UAG appliances using this script?

1. For UAG itself, a vSphere ESXi host and a vCenter Server is needed. Decide on the vSphere datastore to be used and the Network name to be used. If you are deploying a pre 3.3 version of UAG then a vSphere Network Protocol Profile (or IP Pool) must be associated with every referenced network name. This Network Protocol Profile specifies network settings such as IPv4 subnet mask, gateway etc. The deployment of pre 3.3 UAG appliances uses these values so make sure the values are correct. Note: In order to improve vSphere deployment flexibility, UAG 3.3 no longer uses NPPs or IP Pools. This means UAG can be deployed in environments where these are not set up. Instead, settings of IPv4 netmask, IPv6 prefix and defaultGateway (as required) must be specified in the .ini file instead. Refer to the network settings section below for details of the configuration of each UAG NIC for IPv4 and IPv6 combinations supported.
2. The PowerShell script runs on a machine running Windows 8.1 (or newer) or Windows Server 2008 R2 (or newer). This can be the vCenter Server itself if it is running on Windows, or can be a separate Windows machine.
3. The Windows machine running the script must also have the VMware OVF Tool command installed. Install OVF Tool 4.2.0 or newer. You can download it from here OVF Tool Software and Documentation.

How do I run the script?

• Download a version of UAG virtual appliance image from VMware onto your Windows machine. This is an OVA file. e.g. euc-unified-access-gateway-3.3.0.0-8539135_OVF10.ova. Refer to VMware Product Interoperability Matrixes to determine the latest version to download.
• Download the correct uagdeploy or apdeploy ZIP file attached below and extract the files into a folder on your Windows machine. Note that recent uagdeploy zip files are downloaded from VMware from the same location as the UAG images are downloaded. They are no longer attached to this page.
• On your Windows machine, open a PowerShell console and change directory to the location of your script.
• Create a .INI configuration file for your UAG virtual appliance. In this example, I am going deploy a new UAG appliance called UAG1. I have created a .INI file called uag1.ini which contains all the configuration settings for UAG1. You can use the sample .INI files contained within the uagdeploy ZIP file to create your .INI file and then modify the settings to the values you want.
• Make sure script execution is unrestricted for the current user. You can do this by running the command:
  set-executionpolicy -scope currentuser unrestricted
• You only need to run this once and only if it is currently restricted.
  If you get a warning about running this script, you can unblock that warning by running the command:
  unblock-file -path .\uagdeploy.ps1
  or
  unblock-file -path .\apdeploy.ps1
• Run the command .\uagdeploy.ps1 -iniFile uag1.ini as shown in the screenshot below. If you don't specify the -iniFile option, the script will default to ap.ini. You will be prompted to set a root password for the appliance and an optional password for the admin REST API. You will also be prompted for the vCenter password. Deployment takes around a minute depending on your host and storage performance. If you are prompted to add the fingerprint for the target machine, enter yes.

• When the script completes, the UAG appliance is ready to use. No further configuration steps are required.

.INI File Contents

The uagdeploy ZIPfile attached at the bottom of this post contains four example .INI files. uag1-basic.ini is a minimal .INI file which just contains the minimum settings needed. uag2-advanced.ini is a more complex configuration file showing additional settings available. uag3-securid.ini is an example of a configuration including RSA SecurID authentication. uag4-radius.ini is an example of a configuration including RADIUS authentication. You should start with just a basic .INI file to ensure that this deployment method works in your environment. You can then add more advanced settings in your .INI file and repeat the deployment. If you have already deployed the named UAG appliance, then running the script again will power off the appliance, delete it, and will redeploy it with the current .INI settings. This is a useful capability to use when either upgrading the appliance to a newer version, or just to change any of the settings.

Basic .INI File Example

##############################################

[General]

name=UAG1

source=C:\APs\euc-unified-access-gateway-3.1.0.0-6645767_OVF10.ova

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/host/esx1.myco.int

ds=Local Disk 1

netInternet=VM Network

netManagementNetwork=VM Network

netBackendNetwork=VM Network

honorCipherOrder=true

[Horizon]

proxyDestinationUrl=https://192.168.0.209

##############################################

The following table describes each configuration setting. These must be arranged in the .INI file under the appropriate Group Name shown in the first column and as shown in the sample .INI files.

Configuring UAG as a Web Reverse Proxy for VMware Identified Manager

UAG (or Access Point) 2.6 and newer can be used as a Web Reverse Proxy in front of VMware Identity Manager version 2.6 (and newer). Make sure you use a 2.6 (or newer) version of UAG or Access Point e.g.

source=euc-unified-access-gateway-3.1.0.0-6645767_OVF10.ova

For exact up to date information on UAG and Access Point compatibility, refer to the VMware Product Interoperability Matrixes.

For this setup, remove the entire [Horizon] section from the .ini file and replace it with a new [WebReverseProxy] section. Use the values shown in the sample uag10-vidm.ini file in uagdeploy ZIP file below. Set the proxyDestinationUrl to the URL of the Identity Manager server. If that service does not use a trusted CA signed SSL server certificate then you will also need to add the proxyDestinationUrlThumbprints value. Leave all other values in [WebReverseProxy] exactly as shown in the sample uag10-vidm.ini.

The setup requires "split DNS" to be setup where the URL hostname for an external user resolved to the address of UAG, and the same URL hostname for an internal user resolves to the address of the Identity Manager server.

Configuration Settings

Standard SSL, TLS and Cipher Settings

UAG is deployed with the following settings:

• SSL 2.0 disabled
• SSL 3.0 disabled
• TLS 1.0 disabled
• TLS 1.2 enabled
• TLS 1.2 enabled

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA

Managing SSL Server Certificate Files

Deploying a trusted certificate authority (CA) signed SSL server certificate on UAG gives users the assurance that they are connecting to a trusted environment. It also significantly reduces the security risk of a so called man-in-the-middle attack between the user and the service.

If you don't specify a certificate in the [SSLCert] section of the .ini file, UAG will generate a self-signed SSL server certificate. This will work, and can be useful for initial testing, but a self-signed certificate will not be trusted by Horizon  and other clients and therefore users will receive a warning when connecting via UAG.

For production environments, it is best to obtain an SSL server certificate from a trusted CA for use on each UAG appliance.

If you have the PEM format files for the SSL server certificate (including any intermediate CA certificates and root CA certificate) you can reference the files in the pemCerts and pemPrivKey values as described later in this section.

From UAG version 3.0, the deployment of the SSL server certificate became much simpler for customers who have their trusted CA certificate and private key in PKCS#12 (.p12 or .pfx) format. From UAG version 3.0, it is no longer necessary to convert the .p12 or .pfx file to PEM format using openssl commands as described below. Instead, you can now just reference the .p12 or .pfx file directly from within the .ini file. In the .INI file, add the following lines.

[SSLCert]

pfxCerts=mycaservercert.pfx

When the script is run, these certificates and private key will be automatically deployed to the new UAG appliance. The referenced pfxCerts file should contain the SSL server certificate with private key, and any intermediate certificates required. During deployment you enter the password associated with the .p12/.pfx file.

If there are multiple certificates with private key, then you can specify which one to use with the pfxCertAlias keyword.

If you have a certificate file with private key and certificate trust chain all in one PKCS#12 format file with either a .p12 or .pfx file extension, then with UAG 3.0 and newer you can use it use it directly without conversion as described above. For UAG and Access Point versions below 3.0 you must convert the PKCS#12 format file into the two PEM format files. PEM format is still supported for UAG 3.0 and newer and can still be needed if you have PEM format files. You can convert from PKCS#12 to the two PEM files with openssl (which you can download from Shining Light Productions - Win32 OpenSSL) by running the following example openssl commands which start with a PKCS#12 file called mycaservercert.pfx.

openssl pkcs12 -in mycaservercert.pfx -nokeys -out mycaservercert.pem

openssl pkcs12 -in mycaservercert.pfx -nodes -nocerts -out mycaservercertkey.pem

openssl rsa -in mycaservercertkey.pem -check -out mycaservercertkeyrsa.pem

Edit mycaservercert.pem and remove any unnecessary certificate entries. It should contain the one SSL server certificate followed by any necessary intermediate CA certificates and root CA certificate.

The pem file may contain text between the certificates such as "Bag Attributes". These lines are not necessary and can be removed. Make sure the .pem file does not contain any single-quote/apostrophe characters. These must be removed.

In the .INI file, add the following lines.

[SSLCert]

pemCerts=mycaservercert.pem

pemPrivKey=mycaservercertkeyrsa.pem

When the script is run, these certificates and private key will be automatically deployed to the new UAG appliance. The private key PEM file should be deleted from the Windows machine once UAG has been deployed.

If you find that the deployment of UAG works when you don't specify the PEM files (i.e. for UAG to use a self-signed SSL server certificate) but fails when you supply your own certificate as described above, then follow these steps. It could be caused by a missing intermediate or root certificate in your specified PEM file.

• Log into the console of UAG as user root and enter the root password you chose when you ran the uagdeploy.ps1 script.
• Using an editor such as vi, look at the log file /opt/vmware/gateway/logs/admin.log
• If you see entries saying "Unable to build the certification path" and "No issuer certificate for certificate in certification path found" it means that you having missing intermediate or root certificate entries in the PEM or .p12/.pfx file specified for.

• To correct this, you must make sure that any required intermediate certificates and/or root certificate are present in the PEM file and then re-run the uagdeploy.ps1 script.

Network Setting for each NIC (UAG 3.3 and newer)

The table above shows the 11 IPv4 and IPv6 combination modes supported in UAG 3.3 and newer for each NIC with examples for the first NIC (eth0). The same settings can be applied to the second (eth1) and third (eth2) NICs as required.

NIC0 - eth0 - ipMode0, ip0, netmask0, vcip0, v6Prefix0.

NIC1 - eth1 - ipMode1, ip1, netmask1, vcip1, v6Prefix1.

NIC2 - eth2 - ipMode2, ip2, netmask2, vcip2, v6Prefix2.

Troubleshooting Deployment Problems

1. I get a security warning about running scripts downloaded from the Internet

Verify that the PowerShell script is the script you intend to run, and then from the PowerShell console, run the command:

unblock-file .\uagdeploy.ps1

2. I get an error saying "ovftool command not found".

Make sure you have installed the OVF Tool software on your Windows machine and that it is installed in the location expected by the script. OVF Tool Download.

3. I get an error saying "Invalid Network in property netmask0" or "Cannot initialize property 'netmask0'. Network 'VM Network' has no associated network protocol profile"

The message may state netmask0, netmask1 or netmask2, Check that a value has been set in the .INI file for each of the three networks (netInternet, netManagementNetwork and netBackendNetwork),Also check that a vSphere Network Protocol Profile has been associated with every referenced network name. This specifies network settings such as IPv4 subnet mask, gateway etc. so make sure the associated Network Protocol Profile has correct values for each of the settings.

4. I get a warning message about the operating system identifier being not supported (id: 85)

The full message is: The specified operating system identifier 'SUSE Linux Enterprise Server 12.0 64bit' (id:85) is not supported on the selected host. It will be mapped to the following OS identifier: 'Other Linux (64-bit)'.

This can be ignored. It is mapped to a supported operating system automatically.

5. How do I configure UAG for RSA SecurID authentication?

Add the following two lines to the [Horizon] section of your .ini file:

authMethods=securid-auth

matchWindowsUserName=true

Add a new section at the bottom of your .ini file containing:

[SecurIDAuth]

serverConfigFile=C:\temp\sdconf.rec

externalHostName=192.168.0.90

internalHostName=192.168.0.90

The IP addresses should both be set to the IP address of UAG. The sdconf.rec file is obtained from RSA Authentication Manager (RSA-AM) which should be fully configured according to RSA documentation.

Make sure you are using UAG 2.5 or newer and that the RSA-AM server is accessible on the network from UAG.

If there is a firewall between UAG and your RSA Authentication Manager server, make sure it isn't blocking the communication. This is normally UDP 5500 from UAG to RSA-AM and the reply traffic.

Rerun uagdeploy PowerShell command to redeploy your UAG configured for RSA SecurID. Refer to VMware UAG RSA SecurID Authentication Setup Video for a full step-by-step description of this setup. Also Refer to the RSA Ready Certification Document for VMware UAG.

Note that when RSA SecurID is configured in the .INI file, then after deployment when UAG first starts up, it performs a check against RSA-AM. If RSA-AM is not available, or if DNS cannot resolve the hostname of RSA-AM referenced in the sdconf.rec file, or if a firewall is blocking the UDP port for this communication, this startup will fail. When this initial handshake fails, the RSA SecurID component on UAG remains disabled. You can open up the sdconf.rec file with a text editor and although it is a binary file, you can see the RSA-AM hostname(s). If you suspect a communication failure, you can log in to the console of UAG as root and run nslookup with that hostname to verify that it can be resolved. Once you have resolved any environment issues, just rerun the PowerShell command to redeploy UAG.

If you need to redeploy UAG with the PowerShell command when it was previously configured for RSA SecurID, then you must first "clear node secret" on RSA-AM so that trust can be re-established.

6. How do I configure UAG for RADIUS authentication?

Add the following two lines to the [Horizon] section of your .ini file:

authMethods=radius-auth

matchWindowsUserName=true

Add a new section at the bottom of your .ini file containing:

[RADIUSAuth]

hostName=192.168.0.100

authType=PAP

authPort=1812

radiusDisplayHint=XXX Token

For more information on these and other settings, refer to the sample uag4-radius.ini file in the latest uagdeploy ZIP file below. Also refer to the [RADIUSAuth] descriptions in the table above.

Make sure you are using UAG 2.5 or newer and that the RADIUS server is accessible on the network from UAG.

If there is a firewall between UAG and your RADIUS server, make sure it isn't blocking the communication. This is normally UDP 1812 from UAG to to the RADIUS server and the reply traffic.

Rerun uagdeploy PowerShell command to redeploy your UAG configured for RADIUS.

Note that when RADIUS is configured in the .INI file, then after deployment when UAG first starts up, it performs a check against the configured RADIUS server. If the server is not available or if a firewall is blocking communication, this startup will fail.

7. How do I configure UAG for Client Device certificate authentication?

Add the following line to the [Horizon] section of your .ini file:

authMethods=certificate-auth && sp-auth

Add a new section at the bottom of your .ini file containing:

[CertificateAuth]

pemCerts=C:\Users\Administrator\Documents\SSL\CA Certs\north-ca-256.cer

The .cer file is the public certificate authority (CA) certificate that was used to issue required client device certificates.

A client device certificate must be installed in the user or computer certificate store on the system where the Windows Horizon Client is installed. This proves the identity of the client computer. Unless the client supplies a valid certificate issued by this CA, then UAG will reject the connection with an error as shown below.

Client devices that do supply a valid certificate will get the normal user authentication prompt.

This feature is typically used to ensure that only Windows domain joined client computers can connect to desktops and applications via UAG. The client device certificates can be managed automatically as part of a Windows client machine enrolment policy.

For the Cryptographic Service Provider (CSP) specified in the certificate issuing template, use the "Microsoft Enhanced RSA and AES Cryptographic Provider". This supports SHA256 certificates and TLS 1.2. SHA1 is generally now considered too weak for authentication purposes so you should use SHA256.

For Windows to be able to use the certificate for client authentication purposes, the user on the client computer must have read access to the certificate private key. It is not necessary or desirable to make the private key exportable. The Key Usage of the certificate must include "Digital Signature" and "Key Encipherment (a0)".

8. I get an error saying "Locator does not refer to an object"

This means that the target= value (used by vSphere OVF Tool) is not correct for your vCenter environment. Refer to the table above for examples of the target format used to refer to a vCenter host or cluster. If you are not sure of the names to use, you can start with the top level object, e.g. by specifying:

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/

This will then show a list of possible names to use at the next level. You can then expand it, one level at a time based on this list.

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/host

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/host/Cluster1/

or

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/host/esxhost1

or

target=vi://administrator@vsphere.local:PASSWORD@192.168.0.21/Datacenter1/host/my folder/esxhost1

Note that folder names, host names and cluster names used in the target value are case sensitive.

9. I get an error saying "Transfer failed and Error: failed to send http data"

This will happen if your target entry references an ESXi hostname that cannot be resolved by your local computer.

This will also happen if you are using a version of vSphere OVF Tool that is not compatible with the version of vSphere and vCenter you are using. I have seen this error after upgrading vSphere to version 6.5 where I was using an older 4.1.0 version of OVF Tool which is not compatible. In this case, the solution was to upgrade to OVF Tool version 4.2.0 or newer - see OVF Tool Software and Documentation.

For any questions on UAG, post a message on the discussion section of the Horizon community forum.

What program do you use to open this file?

I'm running Fusion 11.5.1 on a 2018 15" MBP w/ i9 2.9GHz and 32GB ram.
Since upgrading from Mojave to Catalina 10.15.0 and now Catalina 10.15.1...
If I've got a VM running and I close the lid, putting the machine to sleep.... when I later awake the machine (by opening the lid), the keyboard and trackpad are dead.  The touchbar and touchid work and I can unlock using my fingerprint.  But, a few seconds after coming out of sleep, the keyboard & touchpad a non-responsive and I see a message window saying;

"Bluetooth Mouse or Trackpad Setup

There isn't a wireless mouse or trackpad connected.

Looking for a wireless mouse or trackpad. If one is found it will be connected to your computer. Check you cables if you expect to use a USB mouse. If you don't want to set up a mouser or trackpad, press Command-Q to Quit.

If you are attempting to use a wireless mouse or trackpad and it isn't found, make sure it is turned on and "discoverable." If you are using an Apple wireless mouse or trackpad, turn on your mouse or trackpad. If you are trying to use a non-Apple wireless mouse or trackpad, see the documentation tat came with the mouse or trackpad"

At that point I can not use the trackpad to move the mouse pointer, nor type anything on the keyboard.  Infact the keyboard backlight is even dead at that point.

At first, I could not do anything but power down (by holding the power button for over 10 seconds) and power backup.
I've subsequently found that if I close the lid for a minute and then re-open the lid again, the keybaord and trackpad will usually coma back to life.

Again, this only seems to happen when putting the machine to sleep whilst a VM (either Win10 or Linux) is actively running and then trying to awake the machine from sleep.

Anyone else noticing this behavior?

HI,

I have network background and have experience with cisco vxlan+evpn solution. Now as business required, I began to touch NSX.

I have to admit NSX makes things easier comparing with the complex Evpn solution.

While there are something confurses me and I hope someone can help to clearify:

  —————————————————————

  |               |                 |                     |                  |

vtep1      vtep2           vtep3            vtep4        controller

  |              |                 |                     |          

VM1        VM2           VM3               VM4

above is the simplified topology. when VMs are online, Vteps will send all relevent details(mac,ip,vtep segment id) to controller, so controller will form a large VIB tables for vxlan data plane.

1. Will controller sync these VIB tables(mac table and arp table) with all VTEP1-4?

2.if yes what is the mechniasm? since VMs behind VTEPs cannot be online and offline, when it happens VIBs in controller will change.So how will controller update VIB in time，periodic update or triggered update?

3.if NO. when VM1 behind VTEP1 wants to speak to VM2 VTEP2. VTEP1 needs to  ask controller where is VM2 and controller reply it is behind VTEP2. if this is done everytime among VTEPS, controller will have unnecessary burdens.

EVPN provides the controll plane making every VTEPs has a synced mac table and arp table, I just do not understand how NSX deai with it.

Regards

Michael

We are setting up our windows 10 pool linked clone pool - using a master image  Win10 1809 - I have optimized the image with all of the standard tools- I have managed to Nuke to ... My login times and my times to "unlock" sessions are horrible compare to Win 7 32 VM's

Averaging about 40-55 seconds when using either imprivata or HTML.

The issues seems to be with windows session persistence - I can watch (via) console as the Vm "Spins up" everytime i lock and unlock a session.

I do have the pool settings
"Refresh OS disk on Logoff" set to "Never"
"Automatic logoff after disconnect" "after 240 min"

using PCOIP

Etc...

all the standard stuff checked..

Does anyone have any advice on how to Improve the long on and lock unlock time for windows 10

what we got

Win 10 1809 4 Gig 4 CPU 2 Sockets per core 4 Gig RAM 40 Gig HD- View Agent  7.9 Golden Image
Vmware Horizon  7.9 Build 13956742
ESXI: VMware ESXi, 6.5.0, 8294253
VmTools 10.2.1

Hi,

I got the following error when I tried to call retreiveInternalContent().

I used smartConnect to get the serverinstance.

Could someone share some comments? Thank you!

Traceback (most recent call last):

  File "perfNamespace.py", line 696, in main

    guestOperationDict.get(args.guestoperation.lower(), unknownOperation)(leftovers, args)

  File "perfNamespace.py", line 189, in listNamespaces

    svcInstIntCont = svcInst.RetrieveInternalContent()

AttributeError: 'vim.ServiceInstance' object has no attribute 'RetrieveInternalContent'

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055ed2fdb3820] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

VMware vCenter Server Appliance 6.7.0.10000

NSX manager 6.4.0

I can not find the top gun Thursday session to review the recorded sessions

Hello,

I have a simply question,

i have searched in the documentation for this case but not result

It's possible to have 2 instance of vra/vro (7.3) connected on  the same vCenter (6.0u3)

There is no incompatibility ?

Thanks

Hello!

I have about a dozen VMs in Vcenter.  They are all ThinProvisioned and about 200 GB in size.  I wonder if it's possible to shrink some of these VMs a bit so that they'll take less time to backup to a cloud DR service.  There is generally about 120 GB free on these VMs and it would be great to just shrink the total size down to say, 150 GB.  I wonder what issues I might encounter or if it's generally safe to do this.   Thanks!

-Joe Lambert  

Hi, 

I have a business group, where I have added an AD group. The BG is entitled to deploy machines. 

If the AD group is added in the Support Role, the deployment is fine. 

But if the AD group is added as either Shared Access Role or User Role, it is not working. 

It is possible for the user / group to initiated the deployment request, but it fails when it hits vRO via an Event. 

All properties from my custom form is simply not transfered to the vRO workflow. 

What am I missing here - do I need to set specific rights on my workflow, event, or other?

Or is a deployment only expected to work when started with Support Role?

vRA 7.6. 

Best regards, Kjeld 

We are in the design phase for vSAN cluster. If I am going to use Active/Active uplinks NIC teaming which is connected to 2 different physical switches. Do I need a VPC link between those physical switches ?

Kindly see the below images

I need some help validating this Network config for a stretched cluster.

Ill summarize whats on the attached, not so good, diagram.

- cluster is running 6.7u1

- Each data site has Nexus vpc Pairs as cores.

- L2 between data site. the vsan vlan has an EIGRP advertised SVI which is part of an HSRP group with 4 members (1 SVI per nexus, so 2 per site) (this is one of the key things i want to validate) 

- Each host has static route which uses the vsan SVI (10.10.1.0      255.255.255.0        10.10.0.0   vmk2       MANUAL) (want to make sure this is recommended or if i should use something else)

- das.usedefaultisolationaddress = false

- HA advance setting is configured with the following das.isolationaddress(1-4): IPs 10.10.0.2(Site A),  10.10.0.4(SiteB), 10.10.0.3(SiteA),  10.10.0.5(SiteB) in that order (want to validate this too)

- As you can see vsan witness traffic always flows through the primary site (sub optimal routing, not big deal unless HSRP fail-over time is too high and could cause vsan issues after a site failure while 10.10.0.1 becomes available again.

Questions:

1- Should i advertise (route) the vsan SVIs.

2- Can i use a different route for witness traffic to avoid traversing the ISL

3- Is the HA advanced settings (Isolation addresses) configured properly.

What would you recommend to improve this design. Dont be shy with the details .

I understand this is very networking "heavy" but that is what we have to deal with by using Ethernet based distributed storage systems which HCI is. As we always hear.. network reliability is key to HCI.

Thanks in advance folks!!

Looking forward to your responses.

Hallo All,

Looks like I'm missing something.

Hope it should be okay to ask here.

I'm reading vSAN 6.7 Deep Dive.

In stretch cluster we use "Read Locality" to keep restrict reading within the Site-A but does it mean the in case Primary site fails, then no replica will be available there to recover.

So in other words, If I put Site Disaster Tolerance = Dual Site Mirroring and also select "Read Locality" how will it function? Or I'm missing something.

Thanks,

Preetam

Hi all,

I wonder if there is such an instrument in VMware structure which can manage several vCenter Update Managers, on any level (vCloud Director, any of vRealize, etc)?

Have anyone ever met something with this functionality?

My organization is looking to track usage for a specific purchased app within Airwatch to see if our locations are actually using said app and how often.  I've been looking through every google search for Airwatch API stuff and have yet to see anyone looking to do something similar.  Any help would be greatly appreciated.

Have started studying VMware Horizon. Right now Im just a regular student wondering if there is any cloud
provider where I can build all the server resources required for a Lab, for a decent money?

I belive I need to set  up these components:

vCenter

ESXi

Connection

DC

File/ Sql

Composer

Security

(Only want to publish only 2 desktops/ VDI and 2 applications, for 2 users)

Really appreciate your answer