application

Recently I came across the App-V technical document stating that "The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated." https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v5/creating-and-managing-app-v-51-virtualized-applications https://github.com/Microsoft/windows-itpro-docs/blob/master/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md So I ran a quick test to confirm on the same.I used App-V 5.1 sequencer and App-V 5.1.86 client for testing. During monitoring phase, I created a New folder in desktop for convenience.I then created 3 new files with different extensions (CO_123, CO_456.txt, CO_897.dll) and then proceeded stopping the monitoring phase. I was expecting that sequencer will throw an error or fail as mentioned in the Microsoft technical document. To my surprise sequencer completed without any issues. I ...

When trying to install App-V 5.1 and earlier version of sequencer in windows 10 version 1607, it fails with the below error. Solution: You would need to download the latest SDK for windows 10 version 1607 which has sequencer along with it. Using this sequencer you can proceed virtualizing apps. https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit

Lat week I was asked by one of my friend to troubleshoot an issue which he was facing earlier. Question: When Installing App-V 5.1 sequencer, it fails to install with the below error.   Solution: When Installing the sequencer, it places log files in %temp% location. We can analyze the possible reason by looking into it. When opened the appv_sequencer_xxxxx_0_CoreX64 log file (which is the actual MSI install log), and Ctrl+F search and giving Return value 3 we see that there is a pending restart needed before installing the sequencer. The sequencer msi has a Launch condition to check for any pending restart. We restarted the machine and again tried to install the App-V 5.1 sequencer setup. this time it got installed successfully.

Recently I came across a question in TechNet about App-V 5.0 Sequencer getting crashed when saving a package and its possible reasons. In this blog I am listing out the possible reasons for sequencer crash and its solutions provided from other App-V techies. First and foremost it's always  a good start to check in the event log when ever there is an issue. Check the screenshot as where to look for sequencer log entries. Always enable show analytic and debug logs from view menu. 1. rels files: The App-V 5.0 sequencer fails to sequence if there is any .rels files present in the package. You can identify a relationship part by the presence of a file with a ".rels" file extension in a folder named "_rels". To know more check the link from Microsoft. https://support.microsoft.com/en-us/kb/2843030 2. Invalid manifest detected: Missing or invalid ProgId entries might also cause sequencer to crash with Invalid manifest detected error log. Check the link from Dan Gough. ...

Question :   Consider application entries are going to both C:\ Drive and E:\ Drive .. In this case whether we can go ahead with sequencing this application?  as these both locations entries will be reflecting in VFS. Answer : App-V 5.0 won't support multiple drive entries. Below you can find an example. start the sequencing steps using App-V sequencer 5.0 SP3. 1. Select create a new virtual package. 2. Select create package. 3. Select standard package. 4. Select custom installation. 5. Enter the virtual package name as test. Click next. In the monitoring phase, Go to c:\programfiles (x86) , create a folder named test1 and add a file. eg: 1.jpg. Go to E:\ drive, create a folder named Test2 and place a text file test2.txt . 6. Click "I am finished monitoring"                                       7.Select continue to modify the package option and click next. 8. In the package ed...

Ques: I have sequenced an application and have succesfully tested it. Now I need to change the shortcut name as there is already another package with the same shortcut name in the same start menu location that exists on the client machine.When I opened the .appv file for editing using the App-V sequencer, I am not able to see the Shortcuts and FTA tab visible in the package editor. How can I edit the shortcut name now. Do I need to re-sequence again? Ans: No need to re-sequence the application again.Open the .appv file using Microsoft Virtualization Sequencer 5.0 SP3 and select the Update Application in Existing Package option instead of Edit package.In the select Installer phase, select perform a custom installation option.Do not install anything, Just select I am finished Installing and proceed by clicking next-next.Select modify package using package editor. Now you will be prompted with Shortcut and FTA tab where you can edit the shortcut name.    Another easy way is to ...