With a great thank you to Denis Gundarev for putting this guide together. I herby present to world how to provision Office in an Appstack.

General Information

This recipe provides step-by-step instructions on how to provision and manage App Volumes AppStacks with Microsoft Office 365. This guide does not cover all aspects of App Volumes deployment and configuration; it only covers aspects specific to Office 365 deployment in App Volumes environment.

These instructions are provided "as is" and do not fully cover licensing scenarios. Readers should consult with Microsoft licensing or support specialists regarding Office 365 plans and advanced configuration.

Important: Office365 is currently available in two versions: Office 2013 and Office 2016. App Volumes 2.10 has been tested only with Office 2013. Office 2016 version of Office 365 may work; however, that version is not currently on the compatibility list.

Process for Provision Office 365 AppStack

The following table provides a high-level description of the provisioning process:

Requirements

App Volumes                                                                                               

App Volumes 2.10 is the first version of App Volumes that is compatible with Office 365. If you have been using a previous version of App Volumes, make sure that all components, including the Manager, agents and templates are updated.

Office 365 Subscription

Shared Computer Activation is required when App Volumes delivers Office 365. This functionality is only available with Office 365 subscription plans that include Office 365 ProPlus. Currently only the following Office 365 plans support Shared Computer Activation:

• Office 365 ProPlus
• Office 365 Enterprise E3
• Office 365 Enterprise E4
• Office 365 Government E3
• Office 365 Government E4
• Office 365 Nonprofit E3
• Office 365 Nonprofit E4

Internet Connectivity

Office 365 ProPlus contacts with the Office Licensing Service on the Internet to obtain or renew a licensing token whenever the user is logging in and launching Office. Therefore, reliable connectivity is required between all target computer s and the Internet.

You also need the Internet to download or update the Office 365 Installation source.

Compute and Storage Resources

To prepare the Installation source, you need a computer that is connected to the Internet and that runs one of the following operating systems:

• Windows 7
• Windows 8 or 8.1
• Windows Server 2008 R2
• Windows Server 2012 or 2012 R2

Important: We recommend running preparation on a computer that doesn’t have AppStacks or Writables attached. Since no components are not installed into the system, this could be your workstation.

During preparation, about 1.5GB are downloaded from the internet, each additional language pack adds 175-250 Mb.

We recommend storing installation source package on theremote file server.

User accounts

Office 365 require each user to have a user account to sign in to Office 365.  Users must also be assigned an Office 365 license from the Microsoft Office 365 Portal.

It is possible to configure theenvironment to allow a Single Sign-On (SSO), so that users don’t need to type their Office 365 credentials every time they log in. Such a configuration is out of the scope of this guide; please consult with your Microsoft representative.

Understanding Installation Methods

• Office 365 subscriptions use Click-to-Run technology to install Office applications on a computer. This differs from Windows Installer technology (MSI) technology that is used to install the volume license editions of Office, such as Microsoft Office Professional Plus and Microsoft Office Standard.
• You cannot have Office products that use two different installation technologies on the same computer. This also applies to standalone applications.

This mean that following scenarios are not supported:

• Having AppStack with standalone Office 365 applications like Visio, Project, Skype for Business, or OneDrive for Business attached to a computer with an MSI-based installation of Office 2013 on the base operating system image.
• Assigning AppStacks that use different installation methods to the same computer.

Please also note that Microsoft does not support mixing any of the install methods with Office delivered using Microsoft App-V.

• You cannot mix 32-bit and 64-bit Office AppStacks.

Planning the AppStack

Click-to-Run:  Microsoft does not support two separate Click-To-Run packages on the same computer. For example, you cannot have Office 365 ProPlus AppStack, and Office Visio AppStack assigned to the same computer.

To resolve this issue, we recommend deploying all Office applications as a single Click-To-Run package to a single AppStack.

However, if your licensing does not permit the use of additional Office applications for all users, you should create separate AppStacks with all required combinations and assign them to appropriate domain groups.

Example: Suppose all users need to have a base Office 365 package, while some users need Visio, others need Project, and others need to have all applications.  In this case, you create 4 AppStacks as defined below:

• AppStack with Office 365
• AppStack with Office 365 + Visio
• AppStack with Office 365 + Project
• AppStack with Office 365 + Visio +Project

32- vs. 64-bit versions:  Office 365 ProPlus is available in a 32-bit and a 64-bit version.  Select the version when preparing the installation source.

Language:  You may also select which language packs should be included into the AppStack.

For more details on versions and language packs, see the “Customizing the Configuration File” section below.

Preparing Office 365 Installation Source

Unlike MSI- based installations, Office 365 Click-to-Run is not available at Microsoft Volume Licensing and can be only downloaded by Office Deployment Tool (ODT).

You can download the Office Deployment Tool from the Microsoft website. The download includes a sample configuration file, Configuration.xml. The Office Deployment Tool performs the tasks that are specified by using the optional properties in the Configuration.xml file.

Important:

There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:

• Office Deployment Tool (Office 2013 version)
• Office Deployment Tool (Office 2016 version)

The Office Deployment Tool is a downloadable self-extracting executable file that contains the following:

• Office Deployment Tool .exe file
• Product updates behavior

• A sample Configuration.xml file

Customizing the Configuration File

A custom .xml configuration file for Click-to-Run is used to specify download and installation instructions such as the following:

· Product and languages to install

· Installation source path

· Level of user interfaces to display

· Logging options

The .xml file may be edited using Notepad or any other text editor. We recommend saving the configuration to a separate file for each AppStack you are planning to create. While you may name the file anything you like, we recommend that you give it an informative, descriptive name.

Example configuration.xml:

<?xml version="1.0" encoding="UTF-8"?>

<Configuration>

  <AddSourcePath="\\FileServer\Office15\WS32"

       OfficeClientEdition="32">

    <ProductID="O365ProPlusRetail">

      <LanguageID="en-us"/>

      <LanguageID="ja-jp"/>

      <ExcludeAppID="Groove"/>

      <ExcludeAppID="Lync"/>

    </Product>

    <ProductID="ProjectProRetail">

      <LanguageID="en-us"/>

    </Product>

    <ProductID="VisioProRetail">

      <LanguageID="en-us"/>

    </Product>

  </Add>

  <UpdatesEnabled="FALSE"/>

  <DisplayLevel="None"AcceptEULA="TRUE"/>

  <LoggingLevel="Standard"Path="%temp%"/>

  <PropertyName="AUTOACTIVATE"Value="1"/>

  <PropertyName="SharedComputerLicensing"

            Value="1"/>

</Configuration>

In the example below following parameters are important:

ExcludeAppID="Groove"

ExcludeAppID="Lync"

LanguageID="en-us"

LanguageID="ja-jp"

UpdatesEnabled="FALSE"

DisplayLevel="None"

AcceptEULA="TRUE"

<LoggingLevel="Standard"Path="%temp%"/>

PropertyName="AUTOACTIVATE"Value="1"

PropertyName="SharedComputerLicensing"

            Value="1"

This document provides the only minimum required information on how to configure the .xml file to use in the App Volumes environment. For additional details, refer to Microsoft documentation:  Reference for Click-to-Run Configuration.xml file.

Downloading Office 365 ProPlus

To download the installation source, run setup.exe from ODT, specify the “/download” parameter and provide a path to the custom .xml file.

Example:

\\FileServer\Office15\setup.exe /download \\FileServer\Office15\Download.xml

The source path should now be populated with an Office folder containing the Office 365 ProPlus installation source.

Provision the AppStack

1. Using App Volumes Manager, create a new AppStack. Make sure that it is created using 2.10 template or higher.
2. Start AppStack provisioning by assigning the new AppStack to the Provisioning VM.
3. Log in to the provisioning VM as administrator.
4. Open the elevated command prompt.
5. From the elevated command prompt, run setup.exe from ODT.  Specify the “/configure” parameter and provide a path to the custom .xml file to install Office 365: 

Example:

\\FileServer\Office15\setup.exe /configure \\FileServer\Office15\Download.xml

1. Wait until the command finishes.  Please note that a progress window will not be displayed. The process can take several minutes to complete. 
2. Verify that Office 365 is installed by checking shortcuts in the Start menu. Do not run any of the Office applications after installation. If you need to configure any settings, consider using of Group Policy templates.
3. (Optional) Modify the shortcut layout.  Make sure that you do this ina common Start menu available for all users.
4. Finish the provisioning by clicking on the “OK” button.
5. The provisioning VM restarts.
6. Login to the provisioning VM to complete the process.

Third-party Applications and Office Add-Ons

Most third-party applications and add-ons are dynamically discovered by Office in cases when they are delivered by AppStacks separately from the Office 365 AppStack. However, in some scenarios, add-ons may need additional configuration or require Office to be present during the provisioning. If a third-party add-on is not interconnecting with Office 365, follow the steps below to troubleshoot the issue:

1. Verify with the application/add-on vendor that the version (32-bit or 64-bit) that you use is supported by the application/add-on and that Click-To-Run deployment is supported.
2. Verify that the application works as expected when both Office 365 and application are installed on the base operating system image when no AppStacks or writables are attached.

Updating the AppStack

Click-to-Run deployments of Office 365 differ from traditional MSI-based deployment in the method of upgrading/patching the installation. Updates are not distributed with Windows Update and must be installed using ODT.

There are two methods of upgrading:

1. a) New AppStack (Recommended)
2. Run setup.exe from ODT with/download parameter to refresh the installation source. You can use the existing .xml file without modification.
3. Create and provision a new AppStack using the instructions above.

1. b) Updating AppStack
2. Run setup.exe from ODT with /download parameter to refresh the installation source. You can use the existing .xml file without modification
3. Using App Volumes Manager, select a command to update an existing AppStack.
4. Start AppStack provisioning by assigning the new AppStack to the Provisioning VM.
5. Log in to the provisioning VM as administrator.
6. Open elevated command prompt.
7. From the elevated command prompt, run the Setup.exe from ODT, specify the /configure parameter and provide path to the custom .xml file to install Office 365.

Example:

\\FileServer\Office15\setup.exe /configure \\FileServer\Office15\Download.xml

1. Wait until the command finishes.  Please note that a progress window will not be displayed. The process can take several minutes to complete
2. Verify that Office 365 is installed by checking shortcuts in the Start menu. Do not run any of the Office applications after installation. If you need to configure any settings, consider the use of Group Policy templates.
3. (Optional) Modify the shortcut layout.  Make sure that you are doing this in a common Start menu available for all users.
4. Finish the provisioning by clicking on the “OK” button.
5. The provisioning VM will restart.
6. Login to the provisioning VM to complete the process.

References:

Office 2013 Deployment Tool for Click-to-Run (https://www.microsoft.com/en-us/download/details.aspx?id=36778)

Overview of shared computer activation for Office 365 ProPlus (https://technet.microsoft.com/en-us/library/dn782860.aspx)

Office installed using Click-to-Run and Window Installer on same computer isn't supported (https://support.office.com/en-us/article/Office-installed-using-Click-to-Run-and-Window-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd)

Determine the deployment method to use for Office 365 ProPlus (https://technet.microsoft.com/en-us/library/gg998766.aspx)

Overview of Click-to-Run customization (https://technet.microsoft.com/en-us/library/jj219428.aspx)

Reference for Click-to-Run configuration.xml file (https://technet.microsoft.com/en-us/library/jj219426.aspx)

Update Office 2013 or Office 365 (https://support.microsoft.com/en-us/gp/office-2013-365-update)

Product IDs that are supported by the Office Deployment Tool for Click-to-Run (https://support.microsoft.com/en-us/kb/2842297)

Download Click-to-Run for Office 365 products by using the Office Deployment Tool (https://technet.microsoft.com/en-us/library/jj219424.aspx)

Group Policy Administrative Template files (ADMX, ADML) and Office Customization Tool (OCT) files for Office 2013 (https://technet.microsoft.com/en-us/library/cc178992.aspx)

Hello Everyone,

I am looking for an eSATA card that I can use with a Dell Server I have.   I have run out of disk space - and I have an external hardware RAID 5 array that I want to plug into the machine and use as an additional datastore in esxi 5.1. 

I have an eBox R5 from DatOptic - a very nice device - that I used to use with this server (a Dell T410 for those who might know it) when it ran Windows.  When I switched to esxi to run my VMs - the card was not supported - so I stopped using the external raid array.  Now I need the additional storage again. 

So - what I would like to find is a simple eSATA card that I can plug into the machine and access that storage.  It connects to the Server via an eSATA cable - and I think the eSATA interface will allow me to treat it like just another drive on the computer - and thus as a new DataStore in esxi.

Any product recommendations would be very much appreciated!!! 

eSATA card that will work with esxi 5.1

G. Bradley MacDonald

brad_AT_timeacct_DOT_com

I'm hoping someone can help me while I wait on vmware support, this has got me scratching my head as to why.

I'm in the process of moving from AMD to Intel Hosts, as part of that process I'm also configuring a distributed vSwitch. Each host in the cluster has 2 10gb NICs and 2 fiber channel HBAs. This is an HP Blade environment with Flex Connect.

When applying a host profile to a host it says the host is not in compliance, but when I check it should be.

This is a shot of the non-compliance:

Here is a shot of the dvSwitch as it relates to an affected host.

This exact same config works in my DR site perfectly. Same hardware even.

Thanks in advance guys!

I downloaded 3 official cloud ready images QCOW2 format:

- cirros -> i can ping instance | i can ssh with cirros:cubswin:) | i can ssh with keypair

- ubuntu trusty -> i can ping instance | i cannot ssh!!! | i cannot ssh with keypair

- centos7 / rhel7 -> i cannot ping instance | i cannot ssh | i cannot ssh with keypair

is a VIO problem?

PS with windows or with my own linux images i have no problems

I resolved this, will leave here for reference, and explain at bottom

Here's my setup:

iMac w/ El Capitain, UPS Worldship Admin

LAN-connected, WiFi off

Windows 10 in Fusion 7, VMware Tools Installed

UPS Worldship 10.0.22

Windows Firewall is OFF, both Public/Private

Running ESET EndPoint on Windows side, and ESET CyberSecurity on Mac side

iMac w/ El Capitain, UPS Worldship Remote

1 USB Zebra 2844 Printer connected to WINDOWS side in Fusion 7 via USB

This printer is Shared with all via Windows Printer Prefs

Printer is set as default in UPS WS settings

LAN-connected, WiFi off

Windows 10 in Fusion 7, VMware Tools Installed

UPS Worldship 10.0.22

Windows Firewall is OFF, both Public/Private

Running ESET EndPoint on Windows side, and ESET CyberSecurity on Mac side

===========================

Problem:

I can print labels from UPS WS Remote PC, but not from UPS WS Admin VM-PC

From Remote I can connect via Network to Admin VM-PC, no problemo.

I cannot find the shared printer to add it to the Admin printer list.

I cannot connect from Admin to Remote via ethernet Network.

My Windows setups are similar or same on each VM-PC, but I only get one-way networking.

Have now very temporarily disengaged ESET to no avail.

I have brought the Admin iMac/PC and placed next to Remote, connected to same switch.

=============================

Background:

I had the USB printer connected to the MAC side of the Remote Fusion PC, which was shared from MAC side and was available to Windows side....most of the time. It usually worked OK.

Eventually something would go wrong with this functionality, every few days, usually on my days off, and I would need to perform restarts on PC then MAC sides on each iMac to get the printer back on the Admin machine; this became unmanageable, so I tore that setup apart today and am stuck trying to go the more "simplistic" Windows-only route(should be).

I have moved our company entirely to Macs finally, and UPS is the last App for which we need Windows, then it will be Sayonara Windows. Until that happy day, I need to resolve this network/windows/Fusion issue.

======================

Side Question:

How do I look up the IP address or network device name of Printer on Remote VM-PC so I can try a Manual Add Printer process? I have no idea what the path would look like going through two layers of dirty Windows and two layers of Mac.

HELP please!

I'm running out of chicken-blood and holy water

Thanks!

=======================

Resolution;

I was apparently trying to connect over network to wrong PC address "WIN-XJFGHSD464JRYGJRIDfFHD" when I should have been trying "WIN-JFUDSYEHBfwef&#$JD"

Silly me.....I guess it was totally my fault.
Dear Microsoft, please allow possibility for use of friendly names for those of us who don't have 69 workstations to manage, and allow us to edit your assigned and unruly device names.

Looking for documentation and examples of using REST API using curl command especially with searchindex to findbyip and findbydnsname.

Thank you

I have VMware Workstation 12 Pro.  I've been using it for weeks without a problem.  Suddenly the mouse will stop working in VM.  This happens while the guest is booted and running.  I click to another window and click back, and the mouse will not work in the guest.  This happens in all guests regardless of operating system.  The only way to resolve this is to reboot the host.  Then I can use the guests again for about 15-20 minutes before the problem happens again.

As an admin I can assign a writable volume of X size. How does the end user know if they are in danger of running out of writable volume space? For example. If I create a writable volume of 15GB for a user and they copy a 30GB file to their desktop what happens?

Hi,

Can anyone help me with the correct condition under subscriptions with vRa-7 to enable a vRo workflow to run when VM reconfigure action is triggered?

Regards,

Venkat.

Hi Everyone,

My question is regarding application configuration and licensing in relation to App Volumes. We're in the process of building a new Win 7 64bit SOE and to that we're adding app stacks. So far I've done a bit of testing with Office 2013, Adobe Acrobat, Lync 2013, Firefox and IE just to name a few. When testing all these as a user I'm finding much configuration is lost. I'm prompted for registration keys and other configuration changes are lost.

How are others maintaining the user settings they want? What is best practice here? I have 20+ applications that have various configuration problems that come up once the app stack is applied, although these were configured when the app stack was created.

I'm a fairly inexperienced desktop support tech and only just begun looking at the app volumes solution. Any thoughts or direction on this would be great.

I'm running VMware Workstation 12 on Windows 10.  Guest is Windows 7.  Bridged networking doesn't work.  The guest gets a 169.x.x.x address.  I've uninstalled and reinstalled twice.  I'm running this on a laptop so I selected the wireless network adapter in the virtual network settings for bridged network.  Still doesn't work.  Only NAT works.

Hello all,

With all the labs you guys got going with VCSA 6. What version are you using because once installed I am not getting any Management tabs once logged in.

Everything including and ESXi servers and VCSA DNS records are good. I'm even able to SSH in. BTW the only browser that works is Firefox. It seems like incompatibility.

Both of my labs are doing this.

Thanks in advance.

Danie

Hi,

Just wondering if anyone has knowledge of or has users connecting via remote access through an SSL VPN (clientless) using PCoIP?  I know SSL VPN  using a full tunnel with a client will allow you to connect using PCoIP, but what about a clientless SSL VPN solution ? Juniper only allows you to connect to the virtual desktop via RDP.  I believe Cisco ASA is the same way.

Is this just not possible, or am I not looking at the right vendors?

Thanks,

Mike

I've been trying to suspend a running vm with vmrun suspend 'path to vmx' but it isn't getting suspended at all. In fact nothing happens at all.

Does anyone have any ideas on how to troubleshoot this? I used to do this in earlier versions of Workstation for a backup job and it worked well.

I'm using Workstation 11

Hi All ,

I have a problem to add to network driver to esxi my system Spec below and version driver that you added

System , Lenovo ThinkCentre E93  With Intel I217V/LM Network interface card

and version that you added

The ESXi 5.5 driver package includes version 1.1.1 of the Intel i40e driver

The ESXi 5.5 driver package includes version 5.2.7 of the Intel igb driver.

VMware ESXi 5.5 Driver CD for Stratus hardened Intel Oplin 10GigE Network Driver

The ESXi 5.5 driver package includes version 3.21.4 of the Intel ixgbe driver

VMware ESXi 5.5 Driver CD for Stratus hardened Intel Zoar/Kawela 1GigE Network Driver driver

i use ESXi-Customizer-v2.7.2 to add above VIB driver files and working fine after all above get at the same message  no network adapter

Please help me and clarify about Intel I217V/LM  which family belongs or give me driver

Hello,

at the moment i'm using a pre defined workflow in the orchestrator to create a virtual machine. My problem is, that I only can choose between thin or thick lazy zero provisioning. In my usecase, I need a eager zeroed disc.

I tried to do this with a change of the configuration but I failed at all. I think I need a new Action that changes the configuration of the virtual machine and uses VcVirtualDiskType. Maybe someone can help me out?

Thanks a lot,

regards

Is there any impact n manually deleting some old snapshots that were created by the Back-up software?

Hi All,

vSAN QUESTION

Setting up vsan homelab (all flash)

3 x Dell Optiplex 9010 SFF Boxes

• 3 x Vsphere 6.x hosts
• 2 x 512GB SSD (AHCI)
• 32GB RAM per host
• 1 x 32GB USB or SSD for esx install
• 2 x gig nics per host

I can also replace the 2nd 512GB ssd with 1TB HDD if required.

Basically - I want to setup a all-flash vsan but don't have the budget for now to add a HBA.

Will be grateful for your assistance and insight.

Kind Regards

I am trying to do a clean install of vRA 7.0 with the Wizard and selcting the simple install with external DB. DB is created during installation.

The Installation fail after a while running the database part with an error message:

Command Result

Message:

Error configuring vRealize Automation Server. For more information, refer to vCAC-Config.log after collecting the IaaS logs.

Description:

Output:

Downloading installer...

Execution time:00:02.625

Download succeeded.

Installing vCAC Server Custom Setup files on the disk

Executing:"C:\Users\<Username>\AppData\Local\Temp\VMware\vCAC\\vCAC-Server-Setup.exe" /s /w /V"/qn ADDLOCAL=Database INSTALLDIR=\"C:\Program Files (x86)\VMware\vCAC\\Server\" /Lvoicewarmup! \"C:\Program Files (x86)\VMware\vCAC\InstallLogs\Server-Setup.log""

vCAC Server Custom Setup Installation Succeeded, ExitCode:0

Execution time:00:17.231

Configuring vCAC IaaS core components:

- Database

Executing:"C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\\vCAC-Config.exe" /S "/P:C:\Users\<username>\AppData\Local\Temp\VMware\vCAC\\ConfigToolProperties.vCAC-Server-Database-ConfigTool.xml" "/L:C:\Program Files (x86)\VMware\vCAC\InstallLogs\vCAC-Config.log"

vCAC-Server-Custom-Database-ConfigTool Installation Failed, ExitCode:5500

Error configuring vRealize Automation Server. For more information, refer to vCAC-Config.log after collecting the IaaS logs.

Execution time:00:09.129

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

vCAC-Config.log:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2016-01-11 12 01 38 222  :================= Logging started at 2016-01-11 12 01 38 206  ==================

2016-01-11 12 01 38 222  :Product version: 7.0.0.5833.

Info : 2016-01-11 12 01 38 269  :Initialized configuration property for feature Database. Node read DATABASE_INSTANCE.

Initialized configuration property for feature Database. Node read DATABASE_NAME.

Initialized configuration property for feature Database. Node read DATA_PROTECTED.

Initialized configuration property for feature Database. Node read DATABASE_DATA_PATH.

Initialized configuration property for feature Database. Node read DATABASE_LOG_PATH.

Initialized configuration property for feature Database. Node read WINDOWS_AUTHEN_DATABASE_INSTALL_FLAG.

Initialized configuration property for feature Database. Node read DATABASE_INSTALL_SQL_USER.

Initialized configuration property for feature Database. Node read DATABASE_INSTALL_SQL_USER_PASSWORD.

Initialized configuration property for feature Database. Node read PRECREATED_DATABASE_FLAG.

Initialized configuration property for feature Database. Node read CREATE_MSSQL_AZMAN_STORE_FLAG.

Initialized configuration property for feature Database. Node read DATABASE_USE_ENCRYPTION.

Info : 2016-01-11 12 01 38 379  :Executing C:\Windows\Microsoft.NET\Framework\v4.0.30319\MsBuild.exe "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" /t:BuildDB /p:UsePreCreatedDatabase="False" /p:DBServer="<SQL Servername>";DBName="<DB name>" /p:DBUser=""  /p:DBPassword=******

Info : 2016-01-11 12 01 38 677  :Microsoft (R) Build Engine version 4.0.30319.34209

Info : 2016-01-11 12 01 38 677  :[Microsoft .NET Framework, version 4.0.30319.34209]

Info : 2016-01-11 12 01 38 677  :Copyright (C) Microsoft Corporation. All rights reserved.

Info : 2016-01-11 12 01 39 147  :Build started 11.01.2016 12:01:39.

Info : 2016-01-11 12 01 39 633  roject "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" on node 1 (BuildDB target(s)).

Info : 2016-01-11 12 01 39 633  :BuildDB:

Info : 2016-01-11 12 01 39 633  :  ##BuildDB Creating and populating database

Info : 2016-01-11 12 01 39 648  :  sqlcmd -S <SQL Servername>  -i CreateDatabase.sql -v DBName="<DB name>" DBDir="\." LogDir="\." -b

Info : 2016-01-11 12 01 45 025  :  Creating Database '<DB Name>'.

Info : 2016-01-11 12 01 45 025  :  Using default SQL database data and log directory

Info : 2016-01-11 12 01 45 025  :  Setting database compatibility level to SQL 2008.

Info : 2016-01-11 12 01 45 025  :  Disabling full text search.

Info : 2016-01-11 12 01 45 025  :  Setting database settings.

Info : 2016-01-11 12 01 45 119  :  Executed CreateDatabase.sql.

Info : 2016-01-11 12 01 45 151  :  sqlcmd -S <SQL Servername>  -d "<DB Name>" -i VMPSOpsUser.sql -v ServiceUser="<Username>" UseWindowsAuthentication="True"

Info : 2016-01-11 12 01 45 480  :  Executed VMPSOpsUser.sql.

Info : 2016-01-11 12 01 45 825  :Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (1) is building "C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (2) on node 1 (RunLiquibase target(s)).

Info : 2016-01-11 12 01 45 825  :RunLiquibase:

Info : 2016-01-11 12 01 45 825  :  "\bin\java.exe"  -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks

Info : 2016-01-11 12 01 45 840  :  The system cannot find the path specified.

Info : 2016-01-11 12 01 45 840  :C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe"  -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.

Info : 2016-01-11 12 01 45 856  :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (RunLiquibase target(s)) -- FAILED.

Info : 2016-01-11 12 01 45 887  :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (BuildDB target(s)) -- FAILED.

Info : 2016-01-11 12 01 45 887  :Build FAILED.

Info : 2016-01-11 12 01 45 887  :"C:\Program Files (x86)\VMware\vCAC\Server\Database\DeployVMPS.xml" (BuildDB target) (1) ->

Info : 2016-01-11 12 01 45 887  :"C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml" (RunLiquibase target) (2) ->

Info : 2016-01-11 12 01 45 887  :(RunLiquibase target) ->

Info : 2016-01-11 12 01 45 887  :  C:\Program Files (x86)\VMware\vCAC\Server\Database\Liquibase.xml(28,5): error MSB3073: The command ""\bin\java.exe"  -Djsse.enableCBCProtection=false -Djava.library.path="C:\Program Files (x86)\VMware\vCAC\Server\Database" -cp "liquibase.jar;jtds-1.3.1.jar" liquibase.integration.commandline.Main --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sqlserver://<SQL Servername>/"<DB Name>";ssl=request releaseLocks" exited with code 3.

Info : 2016-01-11 12 01 45 981  :    0 Warning(s)

Info : 2016-01-11 12 01 45 981  :    1 Error(s)

Info : 2016-01-11 12 01 45 981  :Time Elapsed 00:00:06.74

When can we expect the VMware Horizon Client for Windows 10 Mobile....waiting for the ultimate end-user-experience > VMware Horizon with Lumia 950XL and Continuum