Application Deployment & Virtualization

There is some minor changes in Java 8u171 for SWV. Use the following cmd installscript: @echo off setlocal enableextensions @cd /d "%~dp0" REM The below command will look for and uninstall any previous Java 7 or 8 from the target machine REM wmic product where "name like 'Java 7%%' or name like 'Java 8%%'" call uninstall /nointeractive REM The first command will copy the Java configuration file to the target machine REM xcopy java.settings.cfg "C:\ProgramData\Oracle\Java\" /I /Q /R /Y > nul REM The following line will install the java software to the target computer REM Start /wait jre-8u171-windows-i586.exe INSTALLCFG=C:\ProgramData\Oracle\Java\java.settings.cfg /L C:\temp\jre-8u171.log Start /wait msiexec /i "%~dp0jre1.8.0_171.msi" NOSTARTMENU=1 JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 WEB_JAVA=1 WEB_ANALYTICS=0 WEB_JAVA_SECURITY_LEVEL=H DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /l*v c:\temp\java180_171.log /qr REM Delete javapath...

Backstory: From around Oracle Java 8u121 and up to current date some components in a virtualized Java would stop working if virtualized with AppV and SWV. Example: We have a couple of web app that is launched using JNLP, Applications stopped working from that update when fully virtualized. When started javaws.exe gets closed after around 10 seconds without any output, no errors, nothing. Old workaround: I found a way to “virtualize” some components like registry with an Hybrid package on SWV and AppV with some exe files scripted into base layer (local file system c:\). Even if this is working pretty good it’s not a proper virtual package and basefiles loaded into the browser could fail when you force removal by script. When possible we always want to make sure all files stay inside the virtual layer, that way we ensure compatibility and integrity of files and folders and we can forcefully close and remove virtual applications and be sure everything in the base Os is stil...

Backstory: If you ever come across a scenario with SWV/SWS where you want to make absolute 100% sure certain file types, registry keys or folders never get lost inside of your virtual layers during deactivate, reset or deletion of the virtual layers, there is three ways to make sure of that as far as I know if we count Data Layer.   Normally all file types associated with your program gets excluded when we repackage that program if they resides under the registry location: HKLM\SOFTWARE\CLASSES\.”file-type” Example of files that will be excluded from Sas Enterprise Guide package. But sometimes you can save files from inside a package in other formats and if you really want to make sure files always exist on the system after your packages get removed, then you have to make sure all file types from the save as dialog is also excluded. The easiest way to do that is with a new "virtual" package with ”Global excludes”, called GE in the rest of the article....

Backstory: I work at the IT department of a Norwegian Health Region, we are currently migrating around 13000 clients from Windows 7 x64 to Windows 10 x64 CB for Business using an automated ITMS workflow. On Windows 7 we have deployed around 400 virtual packages made with Symantec Workspace Virtualization, some are deployed with Symantec Streaming. But since SEV (Symantec Endpoint Virtualization) is EOL and extended support ends in july 2, 2018 we are repackaging everything we can into APP-V 5.x format. I could not find any information on others doing the same stuff so I had to create my own little tool doing all of the scripting as an automated process to make App-V work with ITMS. I want to share the fundamentals of my findings in this article giving back some of my own knowledge to the community showing that "Altiris" is the best tool even for App-V deployment, it's based on my original Symantec forum tread : What is the best method creating detection rul...