- On this an “OS only” workstation, and only used for theapplication capture and building process.
- Install all critical Windows Updates to the device (rebootingand checking until 0 critical updates are to be applied).
- Log in as the local administrator. (Enable local Administrator if disabled)
- Disable start up apps & processes and services by running “msconfig”, these might contact network resources or (re)start processes after reboot:
(Commands like msconfig, gpedit, can be run in a DOS prompt (command prompt) by typing in search “cmd”)
Windows Firewall (all properties)
Windows Defender AntiVirus (if applicable) – gpedit.msc
Comp Config > Admin Temp > Win Components > Windows Defender AntiVirus > Turn off Windows Defender=Enabled
OneDrive (if applicable) – gpedit.msc
Comp Config > Admin Temp > Win Components > OneDrive > Prevent the usage of OneDrive for file storage = Enabled
Comp Config > Admin Temp > Win Components > OneDrive > Prevent the usage of OneDrive for the file storage on Windows 8.1 = Enabled
Notifications (if applicable) – Settings > System > Notifications &Actions > Notifications Section = Disable
Skype (if applicable) – Open Skype > Tools > Options > uncheck option to start Skpewhen windows starts > Save
Open Task Manager (taskmgr) and review started services and processes (be careful there are some dependencies).
PATH may have unnecessary locations, verify if all are needed.
Remove unnecessary files (these change between OS types);
Empty Recycle Bin from desktop
- Control Panel > Programs > Uninstall any unnecessary programs OR any programs that may be installed that you want to capture.
- Xbox, Games, etc.
- Install the ZAV Utility
- License the ZAV Utility
- Shut down the workstation.
- Copy VM (or image) this workstation to save as a template.
- (If working with a VM workstation, Save as “ZAVReady”. Include comments of OS version, OS bit type, etc.)
- Start up the workstation.
- Log in as local Administrator.
- Copy installation files (or load the installation media) ontoworkstation, that is not to be captured in the package.
- Connect to any network services that the application needs innormal use (drive mappings, login to a particular system,etc).
- Launch the ZENworks Application Virtualization Utility. (run as administrator and usethe latest ZAV version available)
- License the installed ZAV utility (otherwise the captured appwill be “trial” time bombed)
Up to this point the workstation should have all the necessaryresources to run the application about to be installed.
Yet the device is as plain an OS as possible.
Note: If the ZAV Package deltas and builds can be saved locally orto a network location.
If the builds are to be saved to a network location or repository,connect to the repository at this point so it is available when youbuild the application package. (Or you can move the filesafter the capture.)
Process of Capturing the Application
- ZAV Utility | select “Capture Before”, once complete move tothe next step.
- Add any files wanted to be contained in the “Capture” (Filesand Registry can be added after the Capture, modifying the packagebefore the Build)
- Install the application
- Open the application (this is important to have settings savedto Capture)
- Any installation prompts – answer them to Capture thosesettings.
Example: Microsoft Office applications prompts oninitial install the Updates-Automatic, Notify, or None. Keepin mind, if Automatic or Notify is selected, each time the appopens it will attempt to go to the vendor to get thoseupdates.
- License the installed application (if required)
- Add/Remove/Modify registry changes, shortcuts, files, etc.
- Close the application
- Open the application again making sure all application promptsdo not appear (if another prompt appears answer it and close/openthe application again)
- Empty Trash
Capturing the Application
If there is nothing else to add the the package
ZAV Utility | select “Capture and Diff”
Select a the location for the deltas (snapshot) to be saved (thiscan be on the local device or a network repository if connectedpreviously).
Add/Remove/Modify registry changes, shortcuts, files, etc. (ifadded earlier then already captured)
Example: MS Office creates shortcuts, these can beremoved from the delta file system Start Menu or desktop.
VBWarning registry settings that MSAccess uses, can beadded/imported into the delta Registry
ZAV Utility | Multiple (button)
Add all possible triggers to the package (use all .exe’s in theapplication), by doing this a rebuild won’t be necessary whenanother .exe is needed from the package.
Note: If this is not done and an internal .exe needs to beexecuted, the package will have to be modified with the trigger,rebuilt and redistributed.
Runtimes – If common runtimes are needed in the ZAVapplication – a selection of Runtimes can be selected above underRuntimes (tab). (Java, Dot NET, etc.) This can be in lieu ofinstalling the Runtime in the application while creating thebuild. Refer to documentation for use.
MSI Installer – To create an .msi installer for the virtualapplication choose “Setup” and under “Project Details”, Browse tothe output file location and check “Automatically generate MSIafter successful application build” this will put a .msiversion of the application in the specified Output file locationalong with the .exe.
.msi version will put the application in Add/Remove Programs touninstall.
ZAV Utility | Output File – select the location and name the zavapplication package.
Triggers – Auto Start
Remember a 32-bit OS can not run an app built on 64-bit OS.
Building the Virtualized Application
Selecting Build, will build the package and compile into an .exe(and .msi if specified)
After the “Build” copy the .exe (or .msi) to your location forlaunch and test it on the production environment.
This can be deployed through ZENworks Configuration Management system as aBundle.
Save the ZAV Configuration
Save the Image (or snapshot the VM) as<ApplicationName>-ZAV
Modifications to Captured package – go to Output Filelocation, open the “snapshot.xappl”, modify, rebuild and redeployto test on production device.
Be sure to test, if fails on a regular environment device, run iton the “ZAVReady” image saved above.
Note: Testing on ZAVReady VM (or image) requires manually addingthe network resources required by the application.
Put “ZAV” in the name of the .exe so the application is easilyidentifiable.
Put the ZAV file in their own directory for applicationseparation.
Example: for runtime version of MSAccess 2010
C:Program Files (x86)ZAVMicrosoftMSAccess2010RT-ZAV.exe
Note: If running a 32-bit ZAV application on a 64-bit OS environment, put theZAV file in C:Program Files (x86) file structure so it can findall the 32-bit host .dll’s required to run. Also, 64-bit ZAV Applications cannot run in a 32-bit environment.