Sequencing VLC Media Player using App-V 5.1

1)  Launch the Microsoft Application Virtualization Sequencer from Start-> All Programs

2)  Select the create package (default) option.

3) Select the "Standard application" type in the type of application to be sequenced.

4)  Select "Perform a custom installation" in the select installer screen and click next.

5) Provide the virtual application name as VLC Media Player and click next.

6) Install the VLC Media player application now.

Uncheck Desktop shortcut option.

Uncheck Run Vlc Media Player option and click finish.

7) Once Installation is completed, Select "I am finished Installing" and click next.

                                   

8) In the configure Phase, launch the required shortcuts and perform custom changes if needed and remove unwanted shortcuts.

Here we have removed all unwanted shortcuts other than the main VLC Media Player shortcut. Launched it and unchecked the check for updates and allow network access.Launched it again to make sure everything is captured in feature block 1.

Click Next.

11) Select stop now to create virtual package and click next.

12) Save the package.

Standalone Powershell Testing in the client side:

Execution Policy should be bypassed first.Then enter the below command in PS to publish the VLC Media Player App-V package.

Add-AppvClientPackage "path to .appv file" | Publish-AppvClientPackage -Global | Mount-AppvClientPackage

Shortcut Location:

Shortcut launch:

                                    

                                 

App-V 5.0/App-V 5.1 Applications not launching when selected "RunAs" option

Question: We have an environment where user has separate login account and for testing purpose there is an administrator account to which we as an administrator login to the published applications for troubleshooting. With App-V 5.0, we are unable to launch by shift+Right clicking on the shortcut and selecting "RunAs" option to troubleshoot. This worked exactly as desired in App-V 4.6 The Applications are published through SCCM 2012 for the users. We are not seeing any error when launching the App-V 5.0 shortcuts using "RunAs". When normally double clicking on the shortcut, it launches fine. What might be the reason?


Reason: The reason is, the App-V 5.0/5.1 application has been published for the user through SCCM 2012. When published for a particular user collection, the application will work only for that users. It won't work for other users. This is the reason why "Run as different user" failed to launch the application.


Solution: If you want your Admin account to launch the shortcut, then it should also be added to the  user collection in the SCCM 2012 console or you may want to publish the application globally to the machine so that all the users and the admin account can launch the shortcut properly.


I have added the user/admin account  to the collection and updated the statistics in SCCM 2012, even then I am not able to use "Run as different user". What might be the cause?


If the deployment is made available to the user, then the application needs to be installed first to all the users in the collection then only "Run as different user" will work for that user account.
For example: user A and user B are in the user collection and the application has been deployed to the user group through SCCM 2012. User A logs in and installs the application as it has been made as available. Launches the shortcut and it works fine. Now tries to launch the shortcut using " RunAs" option and entering User B credentials. It fails to load because the application has not been installed to the User B. After installing the application to the User B and tried to launch the shortcut in User A with User B credentials the application launches fine. This is because the application has been installed for User B. This method is not required if the deployment is made as required in SCCM 2012.


NOTE: When published to the users, the "Run as Administrator" option will work properly as desired. Only the "Run as different user" will fail to launch the shortcut correctly.

Internet Explorer getting crashed after upgrading App-V 5.0 SP2 or SP3 to App-V 5.1

After upgrading from App-V 5.0 Sp2 or App-V SP3 to App-V 5.1 , Internet explorer starts crashing for no reason.

The Application event log shows two possible errors:

1.Faulting module : EMET.DLL
2.Faulting module : NTDLL.DLL

This is a known bug with App-V 5.1. Some possible workaround is to either revert back to 5.0 or follow the below steps.

Solution:

Remove the following lines in the registry and IE 10 / IE 11 will stop crashing.

HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / AppV / Client /Virtualization

ProcessesUSingVirtualComponents

Data:

%ProgramFiles%\Internet Explorer\iexplorer.exe

%ProgramFiles(x86)%\Internet Explorer\iexplorer.exe

You can also try removing the App-V 5.0 earlier versions manually and then install App-V 5.1 instead of upgrading to avoid this issue.

Though the above said step is just a workaround, it is not a recommended way to bypass this issue. We need to wait for Microsoft to come up with possible fix or service pack soon.

Technet post - https://social.technet.microsoft.com/Forums/en-US/f1bdd607-dd05-450c-90b7-8fcd8b8bccc1/internet-explorer-1011-hangs?forum=mdopappv&prof=required

Management console generates “Could not load file or assembly Newtonsoft.Json” error - App-V 5.1 Support Tip

After upgrading the App-V 5.0 Service Pack 1 Database and Management Server, the following error is generated when loading the App-V management console:


Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


To know more about resolving this issue click on the below official Microsoft TechNet link:


http://blogs.technet.com/b/appv/archive/2015/10/22/app-v-5-1-support-tip-management-console-generates-could-not-load-file-or-assembly-newtonsoft-json-error.aspx