Application Virtualization - PROII
Application Virtualization - PROII
Application Virtualization - PROII
TM
Application Virtualization
Guide
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
No part of this documentation shall be reproduced, stored in a ret rieval system, or transmitted by any
means, electronic, mechanical, photocopying, rec ording, or otherwise, without the prior written
permission of AVEVA. No liability is assumed with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this documentation, A VEVA assumes no
responsibility for errors or omissions. The information in this documentation is subject to change without
notice and does not represent a commitment on the part of AVEVA. The soft ware described in this
documentation is furnished under a license agreement. This soft ware may be used or copied only in
accordance with the terms of such license agreement.
ArchestrA, Aquis, Avantis, DYNS IM, eDNA, EYESIM, InBatch, InduSoft, InStep, IntelaTrac, InTouch,
PIPEPHASE, PRiSM, PRO/II, PROV IS ION, ROMeo, SIM4ME, SimCentral, SimSci, Skelta,
SmartGlance, Spiral Software, Termis, WindowMaker, WindowViewer, and Wonderware are trademarks
of AVEVA and/or its subsidiaries. An extensive listing of AVEVA trademarks can be found at:
https://sw.aveva.com/legal. All other brands may be trademarks of their respective owners.
Publication date: 9/7/2018
Contact Information
AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 OHB. UK
https://sw.aveva.com/
For information on how to cont act sales, customer training, and technical support, see
https://sw.aveva.com/contact.
Contents
Introduction ............................................................................................................................................ 4
Recommended Best Practices for Sequencing (From Microsoft) ............................................................ 4
Items to document in a recipe include: ............................................................................................... 4
Recommended best practices: ............................................................................................................ 4
Sequencing PRO/II 9.4 ............................................................................................................................. 6
Recommendations .............................................................................................................................. 6
Steps: ................................................................................................................................................... 7
Introduction:
This document is designed as guide to help you quickly set up PRO/II® software deployment
using Microsoft® Application Virtualization (App-V). This guide provides details of the steps necessary
to sequence PRO/II software using the Microsoft Application Virtualization Sequencer.
The primary recommendation for all sequencing processes is for packaging engineers to familiarize
themselves with the installation and execution of the application prior to sequencing. Make sure to
read and become familiar with the installation instructions associated with the application so you
understand how the application runs, as well as the components of the application the user will
need.
Having step-by-step documentation on hand can help reduce unnecessary troubleshooting during
the sequencing process by ensuring no important steps are skipped. Always document the
sequencing process using a standard template, thereby creating a “recipe” that another packaging
engineer in the organization can utilize to recreate the same package.
User Account Control (UAC): Sequence with the same UAC setting that will be deployed
to user desktops. For example; if UAC is disabled on client workstations, UAC should also
be disabled on the sequencing workstation.
Extract self-extracting setup files to the %temp% directory of the sequencing machine
for optimal package size. Certain applications have EXE files that extract the installer to
the machine before the initial install. To avoid adding unnecessary files to the sequence,
it is a best practice to extract the installer onto the local machine prior to sequencing or
to extract the installer to an excluded location.
Selecting the optimal Primary Virtual Application Directory (PVAD): For best results, set
the Primary Virtual Application Directory to match the directory the application is installed
to for the following reasons:
o Application Compatibility: some virtual applications will not function correctly, or
even fail to launch, if the directories do not match.
o Performance: no file system redirection is needed resulting in improved runtime
performance.
o Locate the application installation directory:
Open the application installer, and note the installation path. (Ex. Notepad is
C:\Program Files\Notepad). Cancel the application installer. Launch the
sequencer and insert the installation path into the Primary Virtual Application
Directory.
Set the Primary Virtual Application Directory installation path (Ex. C:\Program
Files\AppName). When the application installer loads, change its default
installation path to match the Primary Virtual Application Directory
(C:\Program Files\AppName).
Disable “Auto Update” features. Some applications have the ability to check a web site
or a server for the latest application updates. This feature should be turned off, as
version control should be performed via sequencing new versions.
Disable “Install on First Use.” Some applications have the option to “Install on First
Use” for certain components. Do not sequence components with this option; choose
either “Run from My Computer” (install this component) or “Not Available” (do not
install this component). Application components that will not be used by any of the
targeted users should not be installed.
Configure and test the application after installation. Completing the installation of an
application often requires performing several manual steps that are not part of the
application installation process. These steps can involve configuring a connection to a
‘back-end’ database or copying updated files, etc. Do these configurations in the
“Configure Software” phase, after checking the “I am finished installing” box and clicking
“next” in the Sequencer. It is recommended to launch each application multiple times
until the program is in a static state in the Installation Phase. For example, the
sequencing engineer may need to run the application multiple times to get past all
registration and dialog box requests. Some applications perform different tasks on first
launch, second launch, and sometimes subsequent launches. Performing multiple
launches will ensure completion of any required post-installation tasks (e.g., accepting a
license agreement or setting file type associations).
Use the Description field in the Packages tab in the Package Editor to note any details
about the package that should be included. These notes will be valuable when revisiting
the sequence later or when upgrading.
If deploying via streaming, use the “Prepare for Streaming” section in the Wizard to
launch each executable in a suite of applications. This will ensure that each application
will have the required initial launch data on the App-V Client.
o Operations made during the “Prepare for Streaming” section will be included in the
primary feature block. When building the primary feature block, make sure to
execute the application’s most common operations so they are included in the initial
streaming of the application, creating an accurate primary feature block. If this is
not done, users might see delays as they start to use the application and will regard
it as being slow if many of the features they use are not in the primary feature block.
Additionally, in an environment where bandwidth is limited, it is important to have
an accurate primary feature block so users are not constantly making calls to the
server to download additional files in cache.
Define target operating systems in the Deployment tab only in situations where it is
required, such as applications sequenced specifically for Remote Desktop Services
(formerly Terminal Services) or when the sequenced package will only work on specific
operating systems or platform types (32-bit vs 64-bit).
Steps:
The section guides you through the step-by-step process of sequencing PRO/II 9.4 on a
Windows 7 32-bit computer.
Note:
15. Select Security Type, keep License server blank and Click Ok.
16. Complete Installation.
17. Install other application. Click Run to select Installer.
18. Install OLI Chemistry Wizard. Install is located at [PRO/II 9.4 setup
folder]\ThirdPartySoftware\OLI\OLI_Engine_in_PROII.9.2.5.exe .
19. Accept License Agreement and Click Next.