As outlined by Ben’s article in Citrix blogs (see: https://www.citrix.com/blogs/2018/06/15/using-app-v-dynamic-deployment-user-configuration-files-with-xenapp-7-18/ )
a key new feature that has been added and long sought after was the ability to alter the dynamic configuration files that came with your app-v package. Delighted this piece is in now as a million and one use cases for it and just wish it was part of the LTSR release which would make it even better.
Essentially in tandem with the app-v sequencing feature for install capture in AppDNA (see: https://docs.citrix.com/en-us/dna/current-release/configure/install-capture/dna-execution-profiles/dna-execution-profile-appv-51.html) this helps speed up packaging times, also provides more flexibility in the testing cycle as most times will be looking to amend the deployment files rather than that binaries within the app-v package itself.
Doing some bulk analysis of apps recently and server experienced a crash. After coming back up and trying to do a re-analysis of the apps i got a “task locked” message trying to re-run.
Luckily didn’t need to chase up a DBA to release the lock from the SQL console option handily available from AppDNA console. To do click Administration | Tasks and in there will see the option to Release Locks click the offending task and release and your good to go.
Have a really beefy project land on my lap relating to application migrations and Windows 10 so looking to utilize AppDNA (version 7.11) to assist. With that in mind wanted to install the AppDNA Desktop Client on my machine in order to have quick and easy access but hit issues with the install.
Trying to install the Desktop Client and getting a cannot start Application message “Application cannot be started. Contact the application vendor”
If I click Details down in the error summary section it gives an error
Failed to load the runtime. (Exception from HResult: 0x80131700)
Had a google about and a lot of posts seem related to .Net Framework issues.
Noticed had .Net Framework 4.51 already installed on the system and was on the supported .Net Framework versions.
Noticed too that .Net 4.6 .1 (URL https://www.microsoft.com/en-ie/download/details.aspx?id=49982) was supported, downloaded and installed it and what you know worked a charm :).
Hope shaved a few mins off someones day mucking about looking for a fix.
If you happen to be lucky enough to be a Citrix Platinum level customer will be lucky enough to have AppDNA in your toolkit.
Nice video covering the piece’s. Interesting product as its uses extend far beyond the application virtualization space. For example if you have a separate Application Packaging team covering desktop-based apps will still have the same obvious benefits. Definitely one of Citrix’s best acquisitions.
Whilst working in AppDNA recently had to figure where to change the SCCM box we were connecting to as had been renamed. Slightly “tucked away” this setting so handy to remember.
- Logon to the AppDNA console
- Click Edit >> Settings >> ConfigMgr
- Enter relevant server details in fields and click Ok