Micheal_A's Posts

Making any application changes to the files or registry will not be kept after logging off. You must make the changes in the package. If you need to make config changes for different scenarios, you ... See more...
Making any application changes to the files or registry will not be kept after logging off. You must make the changes in the package. If you need to make config changes for different scenarios, you have to create separate packages or use DEM for profile management.
Yes, you need to upgrate the current package and give it a build version to have it increment to a package update and not an application version update. Example:  AppVol Application Name: OpenSrc N... See more...
Yes, you need to upgrate the current package and give it a build version to have it increment to a package update and not an application version update. Example:  AppVol Application Name: OpenSrc NotePad++ - First AppVol Package Name: OpenSrc_NotePad++_8.5.12_v1.0 - Goto this package in AppVolMgr and select the upgrate button to make changes to the data in this package. - Upgrate AppVol Package Name: OpenSrc_NotePad++_8.5.12_v1.1 - Mount to your packaging VM and make all the changes you need to the application files. Complete the packaging as you did with the first package, and you now have an updated version of the package to deploy. Here is the link from our documentation. https://docs.vmware.com/en/VMware-App-Volumes/4/com.vmware.appvolumes.admin.doc/GUID-5BFB9B44-791D-4A7A-A21D-D51E6A9ECC41.html      
Review this link: https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/td-p/2886368 You will need to remove all shortcuts from your AppVol package and create DEM shortcuts,... See more...
Review this link: https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/td-p/2886368 You will need to remove all shortcuts from your AppVol package and create DEM shortcuts, by following this link below. Note: I remove the shortcuts and place them in a folder (DEM Shortcuts) in the DEM_Config share, under ...\@WorkSpace\DEM_Shortcuts\. This way I can grab all the information I need to create the DEM Shortcuts. https://docs.vmware.com/en/VMware-App-Volumes/2303/app-volumes-admin-guide/GUID-8A646618-43F1-4FC4-8466-52E48E8EE825.html  
You should be using this tool to create your Gold Image. This will disable all that is not needed for a VDI environment. You will also be able to custom configure and tweak. https://techzone.vmware.... See more...
You should be using this tool to create your Gold Image. This will disable all that is not needed for a VDI environment. You will also be able to custom configure and tweak. https://techzone.vmware.com/resource/windows-os-optimization-tool-vmware-horizon-guide
You need to to mark the AoD shortcuts to not be created in the AVM UI during the package creation for AoD packages. Follow the steps in the link @Mickeybyte replied with to create your shortcuts in... See more...
You need to to mark the AoD shortcuts to not be created in the AVM UI during the package creation for AoD packages. Follow the steps in the link @Mickeybyte replied with to create your shortcuts in DEM.  
Your problem is the agent is not connecting to the AVM server. Focus on the that. FYI, Only install VM Tools and AVM agent. No Horizon agent. You show access the capturing VM from vCenter, since y... See more...
Your problem is the agent is not connecting to the AVM server. Focus on the that. FYI, Only install VM Tools and AVM agent. No Horizon agent. You show access the capturing VM from vCenter, since you managing the VM form vCenter.    
Where does the VMs show Powered Off? I'm assuming in AVM UI and when you are selecting a computer for capturing. Did you create a capture VM and only install the AVM agent? Then create a base s... See more...
Where does the VMs show Powered Off? I'm assuming in AVM UI and when you are selecting a computer for capturing. Did you create a capture VM and only install the AVM agent? Then create a base snapshot of the VM for reverts after packaging applications? If you can give us a little more detail and maybe some screenshots to your issues, we can help you solve this a little faster.  
@julatoski  Thank you for keeping on point. The first solution I mentioned was for the first lease of AoD. When I had clients trying to use it with DEM and we did not have the advanced options at t... See more...
@julatoski  Thank you for keeping on point. The first solution I mentioned was for the first lease of AoD. When I had clients trying to use it with DEM and we did not have the advanced options at the time and having a conversation with you on this topic awhile back. If you guys don't have a video of AoD steps, let me know and I will put something together. Thanks again,
@curtistcreps  The DEM shortcuts target paths should change to the executable path after the initial launch. No mater were it is created. The latest release has Apps on Demand: Command-line Deliver... See more...
@curtistcreps  The DEM shortcuts target paths should change to the executable path after the initial launch. No mater were it is created. The latest release has Apps on Demand: Command-line Delivery available. Review these links and let us know if that helps your scenario. Command-line Delivery of Applications in App Volumes (vmware.com) Also, in AVM you can set the Application Assignment (Optional) "To not deliver the package at user login or computer startup, select Do not deliver for these assignments at startup or login." Assign an Application to an Entity (vmware.com) 
You did not login after the reboot of the packaging VM to complete the AVM provisioning. Read the AVM prompts closely, it is easy to miss.   
I fixed the post to state STOP not Disable. You do not disable the service, just stop the AppVolumes service. REM AppVol Stop Service NET START | FIND "App Volumes Service" >nul IF errorlevel 0 N... See more...
I fixed the post to state STOP not Disable. You do not disable the service, just stop the AppVolumes service. REM AppVol Stop Service NET START | FIND "App Volumes Service" >nul IF errorlevel 0 NET STOP "App Volumes Service" REM Delete AppVol SvService.log file del /F /S /Q "%PROGRAMFILES(x86)%\CloudVolumes\Agent\Logs\svservice.log" del /F /S /Q "%PROGRAMFILES%\CloudVolumes\Agent\Logs\svservice.log" You need to have the service stopped and the logs cleared before you create Instant-Clones from the Gold Image. You want each IC VM to have a fresh start for that VM.  
AppVolumes does not monitor the installer of an application. It monitors the changes of the system, C: drive and Registry. Start a nd package in the AVM and mount the package to your capturing VM. T... See more...
AppVolumes does not monitor the installer of an application. It monitors the changes of the system, C: drive and Registry. Start a nd package in the AVM and mount the package to your capturing VM. Then copy all necessary files, registry, and shortcuts to the required locations for the application to launch successfully. Launch the applications to make sure it is working as expected.  Complete the AVM packaging and test mount on you capturing VM or a test pool to verify the application was package successfully.      
Follow this documents steps for LDAP configuration. Read through this page: Connecting Securely to Active Directory (vmware.com) Then follow these steps to make AD a secure connection: Configure ... See more...
Follow this documents steps for LDAP configuration. Read through this page: Connecting Securely to Active Directory (vmware.com) Then follow these steps to make AD a secure connection: Configure CA Certificates in App Volumes Manager (vmware.com) Also try putting your domain alias before your login name, (Corp\Username)    
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.  
Do you have Adobe and Edge installed on your packaging VM? You should only have Windows OS with updates and any middleware installed as your base capture VM. This way you will only capture what you ... See more...
Do you have Adobe and Edge installed on your packaging VM? You should only have Windows OS with updates and any middleware installed as your base capture VM. This way you will only capture what you need for that application. If your application needs Office/Edge/Adobe to be present during install, then install and take a snapshot before you capture the application.    
You need to update your packaging VM before you capture your application. Most likely these are prerequisites that are need for this version of the application. You have three options to decide how... See more...
You need to update your packaging VM before you capture your application. Most likely these are prerequisites that are need for this version of the application. You have three options to decide how you want to package this application. Package the application and all prerequisites and deploy as a full package. Install all prerequisites before running the capture of the application and take a pre-packaging snapshot. Most likely you will need to update you Gold Image with these prerequisites for this application to function properly. Update both your packaging and Gold Image VMs, then package your application. You have to decide which solution works for you, take in account for other applications and will they work with these new updated prerequisites. If not, you may need to look at ThinApp for isolating this application and its prerequisites to function properly with your other applications that are mounted or installed to your Gold Image.  
You will need to place a SR with GSS. Make sure you state the resolution here after working out the issue.    
You need to update your AppVol agent on the provisioning VM. You have an agent version that does not support OnD.  
Look in your image you set us. There is a field for the Template and version used.
What version is your templates? It looks like they are 4.0.1 and needs to be 4.4.4 or greater. Make your templates and agents are up to the latest version of AVM. Looks like the provisioning VM age... See more...
What version is your templates? It looks like they are 4.0.1 and needs to be 4.4.4 or greater. Make your templates and agents are up to the latest version of AVM. Looks like the provisioning VM agent is at 4.5.0.77