I just want to be clear here for all packaging efforts; You 99.9% of the time package on a clean VM, what is a clean VM? Packaging Best Practice Capturing VM: The Windows OS version you will deplo...
See more...
I just want to be clear here for all packaging efforts; You 99.9% of the time package on a clean VM, what is a clean VM? Packaging Best Practice Capturing VM: The Windows OS version you will deploy to production VDI pool. Apply all Windows Updated that will be applied in production. Turn off Windows Auto Update or defer updates as long as you can. Turn on Notifications to let you know there are updates. Install the Packaging VMware solutions. (list below do not all have to be installed) App Volumes Agent ThinApp shortcut to ThinApp capturing source on file share. DEM Application Profiler. Make any Desktop User Config as you need, like File Explorer... Shutdown and take a Base Capture snapshot. This will be your snap that you will revert too, to start a new packaging effort. AppVolumes Packaging: Revert VM to Base Capture snapshot. Power on VM. In AVM console, attach new package to the Capturing VM. Complete your application install and configuration. Complete the AppVolumes packaging process. Revert the VM to the Base Capture snapshot. If you were notified about OS updates; Power On VM from BC snapshot. Apply updates Shutdown VM and make new BC snapshot. FYI, If you have an application install that needs other applications to be installed prior to the app you are working with, then you need to install those applications and create another snapshot that refers to the apps being installed, like Office, Chrome, Adobe, and/or Edge... P.S. You DO NOT want to have a packaging VM to have your production Image configuration. To hard to maintain and you need to test and package on a clean VM first. This process is the best way to have the cleanest and know what is in your packages. This will also keep your packages from capture bloat.