julatoski's Posts

Hi @Lieven. There is a known issue when a folder is redirected using Microsoft group policies or DEM, the relative path from user profile directory is not valid.  There is a hot fix build available ... See more...
Hi @Lieven. There is a known issue when a folder is redirected using Microsoft group policies or DEM, the relative path from user profile directory is not valid.  There is a hot fix build available from VMware Global Services for this issue.  It is also planned for the next release. Are you using folder redirection? 
Please refer to this updated link: https://docs.vmware.com/en/VMware-ThinApp/2203/rn/vmware-thinapp-2203-release-notes/index.html Our team is looking into a fix for this. Thanks for tour patience.
I agree.  Unfortunately in an effort to help, @Micheal_A posted something originally that isn't supported by the product.  @curtistcreps the "app launch" command is not officially documented and is ... See more...
I agree.  Unfortunately in an effort to help, @Micheal_A posted something originally that isn't supported by the product.  @curtistcreps the "app launch" command is not officially documented and is only intended to be used internally by the product.  It plays a partial role of delivery with additional functionality which removes the icon so it can be replaced the program's icon.  It does not expected to be called more than once.  For your special use case, you will want to skip the next couple paragraphs and read about the official command-line solution that shipped with version 2203.    Apps on Demand in App Volumes 4, version  2111 and later does not require use of the aforementioned command-line feature. Creating custom shortcuts are not required to enable desktop / start menu shortcuts that deliver apps on demand.  The best way to ensure you first have the icons is to verify the shortcut icons appear while a package is set to "Classic" mode.  Additionally ensure the app has been captured or updated using agent 4.5 or later. This is because the shortcuts are automatically detected by App Volumes while finalizing the package and the additional information is added to the .json (both outside and inside the package) with the shortcut, icon and exe information.  Shortcuts that reside in the user's profile are not saved to a package during app capture as these are excluded in the capture policy and the location changes from user to user. When the package is updated with 4.5 or later and delivery is set to "On Demand" those same icons should automatically act as on-demand triggers to delver and launch the app.  So in short... You should be able to package on 4.5 or later and set delivery to "On Demand".  The regular shortcut icons added by app's installer (in areas outside the user's profile) should automatically be ready to deliver the app on demand. --- Now, on to what Michael was discussing.  If you want to create your own Apps On Demand entry points on the system (not the ones in the package) then you can use App Volumes 4, version 2203 to execute a command in the guest via shortcut or File Type Association.  This is a more advanced feature and it is not for the faint of heart.  Here is the command: svservice app run When the following command runs, the App Volumes agent gets the application package delivered to the end user and the application or file is launched:   <svservice.exe path> app run {application_guid} <exe_path> <arguments> application_guid - GUID of the application package that gets delivered. Application GUID is present in the App Volumes Manager admin UI, Applications page. exe_path - location of the application executable which must be run arguments - there can be multiple arguments and this parameter is optional. For example: for file type association, file path must be provided as an argument. This is detailed in the App Volumes 4, version 2203 Administration Guide.  This is an advanced function and not required for Apps on Demand.  As Michael indicates, DEM has tools to help manage shortcuts and FTAs.   Here is an example showing the command being used in a registry entry for a File Type Association: As you can see the what would normally be just: "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE" "%1" has been wrapped with: svservice.exe app run {app_guid} where app_guid is listed on the application page.   This would "lazy load" the app.  If the app is already present it should just run.  This is where @curtistcreps ran into issues using the undocumented launch command that should not be used.  This same method for FTAs would also apply to a shortcut (or anywhere the exe is used).  What is normally just the exe_path should be prefixed with the svservice.exe to lazy load and run the app.  I know that is a lengthy explanation but there were multiple things going on it this thread.   @Lieven -- a video is not a bad idea.  Will propose one back to the team or see if there is one already created that I can share. Hope this helps.
For those that replied about a session, I'm looking into arranging a session and will get back to you.   @electricd7 - Regarding the issue of not being able to update an existing package which shou... See more...
For those that replied about a session, I'm looking into arranging a session and will get back to you.   @electricd7 - Regarding the issue of not being able to update an existing package which should work for you, can you please submit a support request so our support team can work through it with you?   Thanks.
Thank you for your patience. 2.19 is there to address updates without updating the App Volumes manager. To stay current on functional and security updates we ask all customers use the App Volumes 4 m... See more...
Thank you for your patience. 2.19 is there to address updates without updating the App Volumes manager. To stay current on functional and security updates we ask all customers use the App Volumes 4 manager server.   Our team is in the final steps of building the command-line migration tools for 2.x Writables. Just a little longer as we work out the last bits before release.
Hi @Lieven -- Realize this response is a little late as I just saw it for the first time.  Happy to have a session with you for Apps On Demand if you can message me.  If others also have interest, pl... See more...
Hi @Lieven -- Realize this response is a little late as I just saw it for the first time.  Happy to have a session with you for Apps On Demand if you can message me.  If others also have interest, please let me know and we can do a larger session.
You may also be able to run the same commands from the OnPostEnableApp.bat file within the package as well.   https://docs.vmware.com/en/VMware-App-Volumes/2103/app-volumes-admin-guide/GUID-DA2C9E23... See more...
You may also be able to run the same commands from the OnPostEnableApp.bat file within the package as well.   https://docs.vmware.com/en/VMware-App-Volumes/2103/app-volumes-admin-guide/GUID-DA2C9E23-7C51-4A6F-9895-EB31EB6B5217.html  
Additionally a quick link to App Volumes category is here: https://wsone.ideas.aha.io/?category=6800444093779262733  
There is a binary available from Global Support called "RunAsUser.exe" that can be used to execute code as the user from the .bat System context.  I would ask that you also file a request so that we ... See more...
There is a binary available from Global Support called "RunAsUser.exe" that can be used to execute code as the user from the .bat System context.  I would ask that you also file a request so that we can track it and update you if we bring it to the GA product ISO: https://wsone.ideas.aha.io/?category=6800444093779262733 Thank you.    
Programs data (as in "Windows Installed Programs") are stored in the App Volumes Manager and available through the UI under each Package and a full list across all Packages is available on the Progra... See more...
Programs data (as in "Windows Installed Programs") are stored in the App Volumes Manager and available through the UI under each Package and a full list across all Packages is available on the Programs tab.
Thank you for your feedback.  We have refreshed the App Volumes 4, version 2103 documentation with updated guidance around snapvol.cfg and other policy and batch file information. https://docs.vmwar... See more...
Thank you for your feedback.  We have refreshed the App Volumes 4, version 2103 documentation with updated guidance around snapvol.cfg and other policy and batch file information. https://docs.vmware.com/en/VMware-App-Volumes/2103/app-volumes-admin-guide/GUID-D47D7FEA-7553-4DD4-9E69-052525B0C665.html Thanks for your patience and understanding as we work to improve the documentation.
App Volumes will add PVSCSI controllers automatically; however, it does not change the existing VM controller.   "VMware Paravirtual SCSI controllers are high performance storage controllers that ca... See more...
App Volumes will add PVSCSI controllers automatically; however, it does not change the existing VM controller.   "VMware Paravirtual SCSI controllers are high performance storage controllers that can result in greater throughput and lower CPU use. These controllers are best suited for high performance storage environments." https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-7A595885-3EA5-4F18-A6E7-5952BFC341CC.html   Additionally we recommend pre-adding controllers to the VM before cloning as this reduces the number of reconfigs required at user login.  The App Volumes team uses pre-added Paravirtual SCSI controllers when testing App Volumes 4.
Hi @run2 I'm glad you were able to find a solution to the problem.  We identified an issue in the ISO creation process for App Volumes Tools.  We have remedied the issue and updated the 2103.1 (4.4.... See more...
Hi @run2 I'm glad you were able to find a solution to the problem.  We identified an issue in the ISO creation process for App Volumes Tools.  We have remedied the issue and updated the 2103.1 (4.4.1) binary.  It is now available for download as VMware_App_Volumes_v4.4.1.4_12052021.ISO. Thank you for helping to identify this issue.
This is automatically done via the installer.  You can only install either the Agent or Tools on a machine.  Make sure they are not both installed.   If you are still having issues, I recommend yo... See more...
This is automatically done via the installer.  You can only install either the Agent or Tools on a machine.  Make sure they are not both installed.   If you are still having issues, I recommend you reach out to our Global Support Services team to assist you.
I have not.  You might want to verify svdriver is running.  Also ensure you are installing on a new machine, not one running App Volumes Agent.
We are looking into guidance for migrating Writable Volumes.  At this time we recommend customers upgrade their Manager to App Volumes 4 and continue using 2.18 agents until we are able to address th... See more...
We are looking into guidance for migrating Writable Volumes.  At this time we recommend customers upgrade their Manager to App Volumes 4 and continue using 2.18 agents until we are able to address the Writable Volumes migration challenges. Thank you for your understanding.
The hard limit of VMDK disks is based on the limitation of vSphere SCSI controllers which is 60 disks. This number is derived from 4 wide bus controllers with 15 available SCSI IDs for hard drive... See more...
The hard limit of VMDK disks is based on the limitation of vSphere SCSI controllers which is 60 disks. This number is derived from 4 wide bus controllers with 15 available SCSI IDs for hard drives.  If you reserve one disk for an operating system, that technically leaves 59 disks available for app packages and a writable volume. Historically for 2.x we tested 5 AppStacks and 1 Writable Volume per login and similarly for App Volumes 4 we test App Volumes at 25 applications and 1 Writable Volume per login, which is probably the guidance our support specialist has quoted you. Hope this helps.
Hi Natestack​, I agree with Ray_handels​ that there should be no file space concerns with a 20GB disk for a 500MB application because the disks should be thin provisioned and should only use t... See more...
Hi Natestack​, I agree with Ray_handels​ that there should be no file space concerns with a 20GB disk for a 500MB application because the disks should be thin provisioned and should only use the space required by the application.  However, you shouldn't be seeing drive letters if you are properly configuring the templates. I recommend filing a service request with our Global Support Services team so they can help you with the drive letter issue. Thank you.
I apologize for needing to reply in English as my Spanish is less than ideal and could lead to further confusion.  I'm attaching a screenshot where you can see multiple applications assigned to "... See more...
I apologize for needing to reply in English as my Spanish is less than ideal and could lead to further confusion.  I'm attaching a screenshot where you can see multiple applications assigned to "Domain Users" which is effectively everyone.  Additionally you could create your own group for Everyone if you see a need, such as "All Employees." You will have to assign "Domain Users" from one application first.  Once that is done, you can use Directory -> Groups to add your other applications such as Chrome, a PDF reader, etc. As VirtualSpence​ indicated earlier, you may also just capture the apps together in one package and assign to Domain Users, if you want to manage it as one "application" in App Volumes. Hope this helps further clarify how you can assign multiple applications to everyone (or Domain Users).
Glad you are exploring the possibilities with App Volumes assignments.  Applications in your inventory should represent the application (irrespective of version) that you want to the deliver to y... See more...
Glad you are exploring the possibilities with App Volumes assignments.  Applications in your inventory should represent the application (irrespective of version) that you want to the deliver to your users.  The assignment is how you will associate users to their apps.  The "current" marker gives you more control and flexibility to mark a particular package as current and abstract that assignment.  For example, in an application called Adobe Reader you might have two versions each in its own package and marker Adobe Reader DC as "current" with the marker. Next if your intent is to deliver Adobe Reader to everyone, then you can assign the "current" package (Adobe Reader DC in the example) to "Domain Users."  Furthermore, you can browse to the Directory tab, find "Domain Users" under groups, and assign multiple applications at a time. Finally, if you would like to the "current" package and perhaps give a couple users an old retired version, then you can make specific package assignments for those users and groups as needed.  In our example case, if Joe has an assignment to a specific package like Adobe Reader XI, it will deliver that package instead of the Adobe Reader DC which is assigned to everyone via the current marker. Hope this helps explain in a little more detail about our assignment model and how it can help you manage day-2 assignment.