Follow

How do I install DIA Chrome using ProfileUnity FlexApp Packaging Console

Product: ProfileUnity

Product Version: 5.6

Expires on: 365 days from publish date

Updated: Oct 21, 2013

 

Problem:

When I download and package Google Chrome in the ProfileUnity FlexApp Packaging Console, Chrome does not play back in the ProfileUnity packager.   

 

Symptoms:

Chrome does not package correctly. 

 

Problem:

When I try to FlexApp Google Chrome the packager fails to package properly.

 

Possible Resolution:

This issue has been traced to the version of Chrome being installed.  The proper version of Chrome needs to be the enterprise version:

“GoogleChromeStandaloneEnterprise.msi” found at this link: https://www.google.com/#q=chrome+download

 

Preparation for this:

  • Must have Admin rights.
  • Pre-downloaded software you wish to FlexApp and package either onto the Packaging Console Machine or onto a network share.
  • Access to the ProfileUnity FlexApp Packaging Console
  • Access to the Netlogon folder
  • Access to a Non-Persistent ProfileUnity client that will be running the software 

 

Step 1. Download the GoogleChromeStandaloneEnterprise.msi version of Chrome in the MSI format.

chrome_instlall_006.png

 

Step 2.  Create a package using FlexApp 

Logon to the ProfileUnity Packaging Console to create a package.

FlexApp_captures01.png

 

Step 3.

Fill in the information necessary so that the packager is able to locate and create the package based on the installer of that program, (in this case Chrome…..   .Msi)

FlexApp_captures02.png

 

  • Package name = Name of software you want to package
  • Installer Location first line = Location to MSIexex.exe (from packaging machine, machine your on now).
  • Installer location second line = location where the package installer location exist
  • VHD Location = Location on your network the will spin up as a VHD containing the installed version of the software you packaged.
  • This information will be read by the client at logon and infused into the registry making the software look like it is native to the local machine
  • VHD size = The size designated to hold the VHD and the installed software.  This is where the software will be read from at logon.
  • VHD compression = Leave checked
  • VHD Type = Use the default to Dynamically expanding as this allows the VHD to grow as needed up to the size indicated.

 

 

Once the "create a package window" is set, choose “Create” and the packager will begin Packaging Chrome as seen here.

Step 4

FlexApp_captures07.png

 

Once the packager creates the Chrome Package choose “SAVE” to add this package to your inventory of valid DIA Apps for ProfileUnity users.

 

Validate on the client that Chrome and its symbolic links are attached to the package. See below we can see both have occurred.

FlexApp_captures08.png

 

If no shortcut available to access Google Chrome in VDI pool appears on the Desktop, create this separately since Chrome does not.


Step 5 - Create a shortcut.

Open the ProfileUnity Management Console and choose the Shortcut icon.

Edit the desktop shortcut using the ProfileUnity Management Console “shortcuts” for this procedure.

 

 FlexApp_captures092.png

  • * Filter — Set to "No Filter - Apply this to all"
  • * Type Set to "Shell Shortcut"
  • * Action set to " Create"
  • * Check Box Overwrite existing Shortcut set to checked
  • * Shortcut Name Set to "Google Chrome"
  • * Shortcut Location "User Desktop"
  • * Pinned Item Location set to "Start Menu"
  • * Target Set to "C:\Program Files (x86)\Google\Chrome\Application\Chrome.exe"
  • * Start In (leave blank)

 

Once created  update the configuration ini and save it off to the netlogon folder for ProfileUnity.

 

See Also:

How to create custom icon file and use with ProfileUnity's Shell Shortcut Creation module

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.