Hello,

I bought a new server HP DL380 Gen9, and installed ESXi5.5 U3 HPE.

Then I met a very strange matter.

I used vclient 5.5 U3 connect to ESXi host and found many tasks. These tasks will happen every minute.

I added this ESXi host in VCenter 6.5, then every some time(it looks like one minute), this host will disconnect from vcenter and display not responding about 2 seconds.

Whatever I change vcenter to 5.5 U3 or move this host into the same LAN with VCenter, this strange problem persists.

Could any one help me? Thanks.

Task Log in vclient:

Configure Storage I/O Control on datastore

Completed

vpxuser

2017/12/20 9:50:02

2017/12/20 9:50:02

2017/12/20 9:50:02

Update vSphere Distributed Switch list

Completed

vpxuser

2017/12/20 9:50:02

2017/12/20 9:50:02

2017/12/20 9:50:02

Select virtual NIC

135.251.69.111

Completed

vpxuser

2017/12/20 9:50:02

2017/12/20 9:50:02

2017/12/20 9:50:02

Flush firmware configuration

Completed

vpxuser

2017/12/20 9:50:01

2017/12/20 9:50:01

2017/12/20 9:50:02

Update management server IP

135.251.69.111

Completed

vpxuser

2017/12/20 9:50:01

2017/12/20 9:50:01

2017/12/20 9:50:01

Update global message

Completed

vpxuser

2017/12/20 9:50:01

2017/12/20 9:50:01

2017/12/20 9:50:01

Event Log  in vcenter:

Best Regards,

Xici

Have an app that needs to redirect to APPDATA\LocalLow\Application and i created the config file and still no app info in that folder .  Now what am i doing wrong?  Any help is appreciated.  thanks.

Hi

I can not use my vshere client with opera

EXsi 6.0 3073146

se client vcenter suse entreprise 11 French version

When I try to use it

503 Service Unavailable Failed to connect to endpoint

can you please help me ?

thank in advance

Xavier

We have two sites, each with a two-host cluster of VMWare ESXi 5.5.  We use Veeam for backup and replication.  The replication job by Veeam is giving me trouble.  Veeam suggests I contact VMWare.  Since I am currently unable to open a support request with VMWare, I will post here.

The replication job by Veeam frequently fails with "invalid snapshot configuration".  I know the workaround of deleting the replica in Veeam, but that is temporarily helpful.  The error will just appear again against another VM in the replication job.  Deleting a 1TB replica and hoping the replication with complete on the next run is getting old and is frustrating.

Anyway, VMWare records "An error occurred while reverting to a snapshot: A required file was not found." at the same time as Veeam does.  VMWare also records "Failed to revert the execution state of the virtual machine to snapshot Veeam Replica Working Snapshot, with ID 48254".

I can not find the VM's log file, though logging is enabled. Where is the VM's log file?

What do I search for in the log files to reveal a clue or the cause of this snapshot issue?

Hello,

I'm trying to figure out if we have a configuration problem or the hardware is just slow.

host: hp dl360p g8 with 2 nic 1gig in own vswitch (for iscsi according to documentation, mtu 8900)

1 switch tp-link (I know).. tl-sg5428. iscsi has it's own vlan, flow-control on spaning tree off jumbo frames on

msa 2040 // 20 10k sas 12gb/s disk in 2 volumes both in raid 5 /// 4 1gig nics in same tplink switch

When veeam deletes the replica's snapshot (it's the vcenter that tells the host to delete the snapshot), it takes 1 hour to complete.

I get read and write speeds in the avg of 25MB/s to 30MB/s (in both cases).

I have set the mpio to round robin.

I have already done a lot of tweaking and testing and I haven't done much progress.

Please help

Marco.

Good afternoon, tell me please setup in the Sun I use vmvare esxi 6 version. Turned in the Center. Created in the datacenter created a cluster.In the cluster I added the necessary hosts, I have a physical.car ESXI sumiry writes " "

I'm trying to configure a stretched cluster...

and many more mistakes in the cluster

tell me how to properly configure vSAN

All of a sudden I am receiving an unable to authenticate when trying to use the VSphere Web Client when logging into a VCenter server running VCenter server 6. I can however authenticate and log in with the same credentials when I use the normal VSphere Client but I need to access feature that are only available in the web client. The VCSA is a virtual machine on an ESXi host running ESXi 5.5. Im pretty new to VMware and Im not sure where to even start troubleshooting. Any help is greatly appreciated

Hi all, we have a Horizon 7.1 environment consisting of the following:

4 x Unified Access Gateways

6 x Connection Servers

1 x Composer Server

1 x MS SQL Server

We are looking at enabling the Horizon Pod feature as part of a possible expansion. Our question is, can multiple Pods all use the same vCenter?

Thanks in advance

I‘m new to setting up ESXi in a long time, and am setting v6.5u1 up on my Mac Mini.

I installed  a 1tb USB drive, and the install seems to have gone fine, without any issues. After booting up, though, I don’t have any datastores created.

Looking at the Web UI, I see three partitions.

1: EFI System - 249 MB

2: Basic Data - 2.5 GB

3: Basic Data - 928.13 GB

However, the partition diagram shows the 928.13 GB partition as free space.

The link to create a new data store is greyed out, and the table is empty under the data stored tab.

I have searched for quite awhile, without any real success finding anything that helps me out.

Hopefully, someone here has gone through this install, and might be able to help guide me on narrowing down a fix.

TIA

VMWare Essentials plus licensing question: We have 3 servers, one of them is old and we bought a replacement. When I try to add the new server to vCenter it won't let me because we have our limit of 3 already. So it's asking me to remove one of my 3 servers before I can add the new one.  If I remove the old server from vCenter what will happen to the VMs running on it? They are production VMs.  The vm's running on it are using local storage, there is no shared storage.

Hi,

I have created a VM within Workstation 14 Pro and then exported it to an OVF or OVA file. If I then try and import it as a new machine I get the error that it 'did not pass OVF specification conformance or virtual hardware compliance checks', but little else in the way of telling me exactly what failed.

Exporting the VM from VMX to OVF/A via ovftool and then importing results in the same error.

If I tell Workstation to ignore the error, the VM is imported with a Hardware Compatibility of ESXi 6.5. If then export and re-import this VM then I do not get any errors.

The original VM had a hardware compatibility setting of Workstation 14.x and I cannot find any way to downgrade it. Perhaps this is not possible?

Have I run in to a bug, or is there something else I should be doing?

Buenas tardes.

Tengo una máquina virtual con CentOS 7 a la cual le quiero agregar una controladora de audio, lo que pasa, es que, al  darle a editar la configuración, no me aparece para elegirla:

¿Como podría hacer para agregar una controladora de audio?

Muchas gracias.

Un saludo.

Is there a way to specify SSHsession timeout in Orchestrator's Run SSH command workflow? We seem to be getting hung up once in awhile, and it tends to happen during the destination VM boot up. Session gets opened but is not completed and get's stuck in established state indefinitely.

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

Introduction

Updated December 2017 for version 3.2

From version 2.9 the appliance is is now called Unified Access Gateway (UAG) instead of the old name of Access Point. It's the same, just a different name.

In September 2015, I posted A Technical Introduction to Access Point for Secure Remote Access article. Unified Access Gateway (UAG), formerly known as Access Point, is a VMware virtual appliance which is used with VMware Horizon (View) and Horizon Air (DaaS). In that article I mentioned the ability to perform a scripted deployment of an Access Point virtual appliance using VMware OVF Tool in order to perform a repeatable deployment where all settings can be applied in a way that allows UAG to be production ready on first boot. This procedure is described in the document Deploying and Configuring Access Point.

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 Horizon environment need a much simpler 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 sample PowerShell script that can be used to deploy Access Point 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 Access Point according the procedure in the document Deploying and Configuring Access Point . 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.

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

1. For Access Point itself, a vSphere ESX host with a vCenter Server is needed. Decide on the vSphere datastore to be used and the Network name to be used. A vSphere Network Protocol Profile 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 Access Point uses these values so make sure the values are correct.
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-access-point-2.9.0.0-5178136_OVF10.ova. Refer to VMware Product Interoperability Matrixes to determine the version to download.
• Download the correct uagdeploy or apdeploy ZIP file attached below and extract the files into a folder on your Windows machine.
• 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 Access Point 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.

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.

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 && sp-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 && sp-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.

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

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.

I am one of the admins that maintain our Mac lab images across campus. About 90% of these systems are Mac only. The other 10% are going to be running both macOS (Sierra) and Windows 10 (Fall Creators edition). We have JAMF which we are using but not to its full extent.

In the past, these machines were using boot camp for dual boot purposes. However, Fall creators update has made it near impossible to push out Win10 in boot camp without pulling hair out. We have decided to move to Fusion 10 Pro with a Shared VM. I currently have the following set up:

1. Using the Mass Deployment package to set volume license, suppress installation questions and store VMdisks in the "Shared Folder".
2. Bare bones win 10 image for quicker deployment to test systems.
3. VM settings (such as network card, start up vm, etc) set up.

These items are all going out great and the experience is the same from one computer to the next. The issue is that all users have access to everything in Fusion. Any user could alter the vmx or choose to pick a net network connection.

Enter Encrypt and Restrict
It does most of what we want and, at the very least, what we need. The only problem is it requires you to encrypt which requires a password. We can't have our users prompted for a password at each launch. We could train them to store the password in the keychain but... the keychain is re created at each login. Our default profile "wipes away" the current login keychain to avoid the dreaded keychain window that no user can ever figure out how to fix.

Does this group have any suggestions for restricting the VM but balancing that with usability?

Hello,

I read the virtual disk type doc Virtual Disk Types .

It says this "Sparse disks employ the copy-on-write (COW) mechanism, in which virtual disk contains no data in places, until copied there by a write. This optimization saves storage space."

If I write some thing to disk for multiple times, so according to "copied there (to the disk) by a write", the disk will maintain several copies of previous disk data.

The storage will have duplicated old data, so why it says "This optimization saves storage space." ?

anyone can tell me why? thanks in advance.

FYI, the HTML Client that comes with SDK 6.5 or 6.5u1 has problem with the latest Java JDK on Windows 10 and MacOS High Sierra.

The client home page doesn't come up and the browser console shows errors such as:

Uncaught SyntaxError: Unexpected token )

clarity-angular1.min.js:38 Uncaught SyntaxError: missing ) after argument list

and

(anonymous) @ init.js:6

folder-ui.min.js:1 Uncaught ReferenceError: angular is not defined

The work-around for Windows 10 is to use Java SDK 1.8.0_144

We haven't found any work-around yet for MacOS High Sierra.  Let us know if you have one!

Can someone tell me where VMWare is at in regards to cloning Windows 10 1709?  I have not be able to clone a windows 10 build 1709 with OS Customization from vCenter. After vCenter creates a copy of the VM, Sysprep never kicks in.  My 1703 build clone just fine.  I've seen some discussions on the subject in the Horizon forums, but I'm not using Horizon.  The bigger problem is, if I try to patch my windows 10 they will update to 1709 and I can't prevent it.  Once updated I can't clone them any longer.

everything is working nicely. i want update the base image with an update to the OS and some of the apps I installed.

whats the best way to do this?

thanks

jayesh

Have a problem.... We have a pool created from Parent VM with some standard applications like firefox, office, java and app volume agent installed on it.

We see that when a user with writable volume connects to this pool, writable volume is letting the user to uninstall the application that comes along with image. After they uninstall, they can never use those application even they connect to a different VM on the pool, the VM is supposed to have the all standard apps on it. Uninstall apps never show up on Add or remove programs.

Is there way to block users to uninstall the apps that comes along with image?.