RunVirtual Key may finally be the answer in App-V 5 SP3

RunVirtual enables App-V packages to run on locally installed applications e.g. add-ons

Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.

Syntax: <PackageId>_<VersionId>

Example: 4c909996-afc9-4352-b606-0b74542a09c1_be463724-Oct1-48f1-8604-c4bd7ca92fa

The application in the previous example would produce a registry export file (.reg file) like the following:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual] @="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe] @="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555

SP3 finally seems to have this all covered off.  Imagine there are 3 different addons for 3 different users.  One app can only have a relationship with one GUID string so a connection group is required.

According to the SP3 doc link below the users will only get the individual App-V packages in the connection group - the ones they are entitled to and not the ones they are not supposed to have.

FINALLY !

references
http://stealthpuppy.com/app-v-5-0-delivers-internet-explorer-plugin-nirvana/
SP2 related - it still wasn't *total* nirvana when this was written though.

https://technet.microsoft.com/en-us/library/dn858703.aspx

https://technet.microsoft.com/en-us/library/dn858700.aspx#BKMK_runvirtual_reg_key

http://www.tmurgent.com/TMBlog/?p=2211

http://virtualvibes.co.uk/everything-you-need-to-know-about-app-v-5-0-sp3/
http://virtualvibes.co.uk/connection-groups-2-0-in-app-v-5-0-sp3-more-manageable-more-flexible/
http://virtualvibes.co.uk/runvirtual-comes-to-the-user-in-appv-5-0-sp3/


Another reason why you need SP3.

Sequence an addon in SP2 - say a lovely ActiveX control with a shortcut to launch IE pointing to the relevent website.  Deploy, test and marvel at your wonderful package.

Now close your IE session and start a normal IE session which is just running normally.  NOW try your lovely package - ain't gonna work is it? cause it gives you a some kind of IE session spawned from the original.  Your ActiveX control is no where !  SP3 might sort that out for ya.

SCCM 2012 Configuration Manger Console may require the MDT

Could not load file or assembly file:///C:\Program Files (6)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft,BDD.CM12.Actions.dll’ or one of its dependencies. The system cannot find the file specified.

The above occurs because files named Microsoft.BDD* are not present. These are not installed by the SCCM Admin Console installation but by the Microsoft Deployment Toolkit (MDT). The files then have to be copied over to the required folder shown in the error message

KMS

Key Management Service (KMS) clients use DNS to locate a KMS server.  The DNS entry is a SRV type  with a name of _VLMCS

slmgr /dlv on the client to display the license information and which server has been selected for KMS.

this command queries the DNS for the KMS server addresses.
nslookup -type=SRV _vlmcs._tcp.<forward lookup zone>

Use cscript slmgr.vbs to get screen text output.  The default just pops up text windows which can be useless if there is a lot of text.

More information here https://technet.microsoft.com/en-us/library/ff793434.aspx

Some Microsoft products which are volume licensed use KMS servers to activate. Office 2016 is an example run the following to check the activation status.

change directory to C:\Program Files (x86)\Microsoft Office\Office16
run

cscript ospp.vbs /dstatus

Internet Explorer update fails with error code 9C59

This post refers applies to a failure of Internet Explorer (IE) to update from a previous version; in this case IE9 on Win7 SP1.

The automatic update repeatedly failed apply the update to IE10 and later IE11 and logged update failures in the the update history:
Installation status: Failed
Error details: Code 9C59

Significant time was spent attempting to assess how this error could be solved.  During troubleshooting the Windows Features window was discovered to be blank and it was surmised that this was the actual cause of the update failure, as IE 9 is considered a feature of Windows and is on this list of features.  Instead of attempting to solve the update failure attention turned to solving the blank Windows Features window as arguably this was even more serious than a failing update.

Initially blogs and guides recommended using system file checks as sfc /scannow and DISM commands described here http://www.thewindowsclub.com/windows-resource-protection-found-corrupt-files note DISM /Online /Cleanup-Image /RestoreHealth is not a valid command at least on Win 7 SP1.

While researching DISM the system update readiness tool (SURT) was discovered http://support.microsoft.com/kb/947821 It is a large download "Windows6.1-KB947821-v34-x64.msu"

This system update readiness tool solved the blank Windows Features.  After applying it the features were available in the display again.

Running the Windows Update to apply the IE11 update was then successful.

Remember to reboot after installing the SURT.

DISM = Deployment Image Servicing and Management

App-V 5 tech dives

Extension Points

http://blogs.technet.com/b/appv/archive/2013/01/03/microsoft-application-virtualization-5-0-integration.aspx

SCCM 2012 boundary groups

Several logs including this one http://www.trailingreboot.com/?p=60 suggest using one boundary group containing all ip subnet boundaries to do site assignment, then use additional boundary groups to define site servers (distribution points DPs) for ip subnets.

Microsoft Office Pro Plus 2010 SP2 partial install of excluded features

http://www.microsoft.com/en-us/download/details.aspx?id=39667


There is a bug in Microsoft Office 2010 SP2 released 22/7/2013 which results in the incomplete installation of some features even if they have been specifically excluded from the installation by the Office Customization Toolkit (OCT).

Without SP2, excluded features do not install.  However if the SP2 msp files (specifically officesuiteww-x-none.msp) are put into the Updates folder, then the problem occurs. An SP2 install to the original release installation also exhibits the effect.

It can be particularly problematic because the Access application feature installs file associations but not a complete application.  .accdb files appear to have associations but launching access results in the error

Can't find Language DLL msmain.dll

The publisher application feature MSPUB.EXE is also incorrectly installed when the feature is disabled in the OCT.  This results in this error

Publisher failed to start correctly last time.

The issue is discussed in the thread here:
http://answers.microsoft.com/en-us/office/forum/office_2010-office_install/office-2010-sp2-partially-installs-access-2010/9bb56acf-d48a-4244-b9ee-cda4e66fe58c



Workarounds:
The features can be installed then uninstalled in Programs and Features which properly removes them.