Jul 19 2014

Deployment Visio 2013 and Project 2013 as AppV 5.0 package created with Click to Run

image_pdfimage_print

Office 2013 – and its components – can only be made available as an App-V 5.0 package with Click to Run. The required steps – including streaming to the client with the App-V 5.0 Management Console – are described in this article.

Step 1: Download Office Deployment Tool for Click to Run

  1. Download Office Deployment Tool for Click-to-Run.
  2. Run the downloaded ‘officedeploymenttool.exe’. It will extract the setup.exe together with an example xml file.

Step 2: make the download.xml file

  1. This file contains all the settings which applications should be downloaded. More information can be found at Reference for Click-to-Run configuration.xml file.

    In this example the content is:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    
    <Configuration>
     
     <Add SourcePath="\\demo-dc\OfficeClickToRun\" OfficeClientEdition="32">
        <Product ID="ProjectStdRetail">
          <Language ID="en-us" />
          <Language ID="cs-cz" />
          <Language ID="nl-nl" />
        </Product>
        <Product ID="VisioStdRetail">
          <Language ID="en-us" />
          <Language ID="cs-cz" />
          <Language ID="nl-nl" />
        </Product>
      </Add>
    </Configuration>

    [warning]Of course the share should be present.[/warning]
    In this example Visio and Project will be downloaded in English, Czech and Dutch.

  2. Create a batch file with the following content:
    1
    2
    
    "%~dp0setup.exe" /download "%~dp0download.xml"
    pause
  3. Run the script to download the files:
    Run 'download.cmd' as admin.

    Run ‘download.cmd’ as admin.

  4. After a while all the files are downloaded:
    All files have been downloaded.

    All files have been downloaded.

Step 3: make the package.xml files

For both Visio and Project a package xml file will be made. That is needed as Visio and Project have a different package id. That package id is defined in the property PACKAGEGUID in the packager.xml file.

  1. The file for Visio:
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    
    <Configuration>
     <Add SourcePath="\\demo-dc\OfficeClickToRun\" OfficeClientEdition="32">
        <Product ID="VisioStdRetail">
          <Language ID="en-us" />
          <Language ID="cs-cz" />
          <Language ID="nl-nl" />
        </Product>
      </Add>
     
      <Updates Enabled="TRUE" />
      <Display Level="None" AcceptEULA="TRUE" />
      <Logging Level="Standard" Path="\\demo-dc\OfficeClickToRun\Logging" />
      <Property Name="AUTOACTIVATE" Value="1" />
      <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
      <Property Name="PACKAGEGUID" Value="7f4665b1-fd4c-429c-ad58-0ada42ab9002" />
    </Configuration>
  2. The file for Project:
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    
    <Configuration>
     <Add SourcePath="\\demo-dc\OfficeClickToRun\" OfficeClientEdition="32">
        <Product ID="ProjectStdRetail">
          <Language ID="en-us" />
          <Language ID="cs-cz" />
          <Language ID="nl-nl" />
        </Product>
      </Add>
     
      <Updates Enabled="TRUE" />
      <Display Level="None" AcceptEULA="TRUE" />
      <Logging Level="Standard" Path="\\demo-dc\OfficeClickToRun\Logging" />
      <Property Name="AUTOACTIVATE" Value="1" />
      <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
      <Property Name="PACKAGEGUID" Value="83ff5d32-d55c-42b9-b667-310a9df623f7" />
    </Configuration>
  3. The package guids can be created with this powershell command:
    Powershell command: [guid]::newguid()

    Powershell command: [guid]::newguid()

  4. Create the packager.cmd to create the packages for both Visio and Project:
    1
    2
    3
    
    "%~dp0setup.exe" /packager "%~dp0packager_visio.xml" %~dp0AppV50Packages
    "%~dp0setup.exe" /packager "%~dp0packager_project.xml" %~dp0AppV50Packages
    pause
  5. Run the script to create the packages:
    07 Run packager cmd as administrator7
  6. You can view the progress:
    View progress.

    View progress.

  7. Ready:
    10 Finished
  8. If you open ‘ProjectStdRetail_cs-cz_en-us_nl-nl_x86_DeploymentConfig.xml’ there are references to the Czech language:
    11 The deployment config contains references to cz

Step 4: Modify the packages in the sequencer

If needed you can modify the packages in the sequencer. At least App-V 5.0 SP2 sequencer is needed.

In this scenario the packages are modified to change the names.

  1. Open the project .appv file with the sequencer:
    Open the project appv file with the sequencer.

    Open the project appv file with the sequencer.


    Edit package.

    Edit package.

  2. Edit:
    14 Edit
  3. The final result. [important]Please be aware that the first language that is mentioned, is ‘cs-cz’ for Czech. That is why all the shortcuts have a Czech description. I do not know if this is by design or that is a bug…
    You should expect that en-en should be default, as that language is set as the first language in the ‘packager_project.xml’ file.
    15 The results cz as mentioned first[/important]
  4. Modify both the package name and description:
    16 Modify package name and description
  5. And save the package:
    17 Save the package
    18 Check the file name
    19 Wait

Step 5: Import Visio and Project

  1. Import Project 2013 in AppV 5.0 using the Application Virtualization Console
  2. Edit the AD access:
    20 Edit AD access
  3. Unselect the applications you do not need:
    24 Unselect all the applications you do not need
  4. Publish the application
  5. And do the same for Visio (not documented)

Step 6: Test on the client

  1. Log in on a client.
  2. After a short while both Visio and Project are visible in the Start Menu:
    25 After a while the applications are available on the client
  3. Start Word:
    25 After a while the applications are available on the client
  4. You have the option to insert both a Project and Visio object in Word:
    27 Option to insert Project document
    28 Option to insert Visio drawing
  5. And work with it:
    29 Visio

Step 7: Remove Project and Visio

  • Remove the group from the application in the Application Virtualization Console.
  • It might take a longer time if the application is in use:
    30 Visio is still in use
    You see that in the event viewer.

    You see that in the event viewer.


    But Visio is removed after reboot.

    But Visio is removed after reboot.

  • If you start Word, the options for inserting a Project or Visio object are not available anymore:
    33 Options to insert Project and Visio objects are gone
  • Permanent link to this article: https://www.vroom.cc/wordpress/deployment-visio-2013-and-project-2013-with-click-to-run/