I'm interested if anyone has come across a similar scenario to what we have at the organisation I am currently working for. The organisation has signed up for an E3 subscription to Office 365, however would like to continue to using their volume licenses
of Visio and Project 2013 (at least until new versions are released at which point they'll likely move to the same subscription model).
Using the Office Deployment Tool, I've created App-V 5.0 SP2 packages for
a. "O365ProPlusRetail"
b. "ProjectProVolume" and "VisioProVolume"
Both App-V packages ignore any exclusion rules in the configuration.xml file I've defined. This is expected and I can control which applications are published using Config Mgr 2012 R2. Both packages deploy and run as I would expect.
The issue I specifically have is that if I publish both App-V packages (using different package ID's) to the same PC with modified DeploymentConfig.xml files:
a. "O365ProPlusRetail" package only enables Word, Outlook and Excel (subscription licensing)
b. "ProjectProVolume/VisioProVolume" package only enables Visio and Project (volume licensed)
it appears as though the Word, Excel and Outlook from (b) are utilised instead of from (a) even though they are specifically disabled. This means that Word, Excel and Outlook activate to our local KMS server, rather than using the user credentials as we would prefer.
To confirm I can see that package (a) is already running when I run the following command: Get-AppvClientPackage | select Name, InUse, InUseByCurrentUser
Name InUse InUseByCurrentUser
---- ----- ------------------
Microsoft Office 15 ProjectProRetail_O365ProPl... True True
Microsoft Office 15 VisioProVolume_ProPlusVolu... False False
If I then open Word (which should only be enabled in the first package), I see that the second package is now in use
Name InUse InUseByCurrentUser
---- ----- ------------------
Microsoft Office 15 ProjectProRetail_O365ProPl... True True
Microsoft Office 15 VisioProVolume_ProPlusVolu... True True
I've also confirmed that all the applications (besides Visio and Project) are disabled in the second package:
Name EnabledGlobally
---- ---------------
Database Compare 2013 False
Spreadsheet Compare 2013 False
Excel 2013 False
OneDrive for Business 2013 False
InfoPath Filler 2013 False
Lync 2013 False
Access 2013 False
Telemetry Log for Office 2013 False
Telemetry Dashboard for Office 2013 False
Office 2013 Upload Center False
Publisher 2013 False
Lync Recording Manager False
Microsoft Outlook Mobile Service False
OneNote 2013 False
Send to OneNote 2013 False
Organization Chart Add-in for Microsoft Office programs False
Outlook 2013 False
PowerPoint 2013 False
Microsoft Office 2013 False
Office 2013 Language Preferences False
SharePoint Designer 2013 False
Visio 2013 True
Project 2013 True
Word 2013 False
Office XML Handler False
Internet Explorer False
Notepad False
Perhaps what I am trying to do is unsupported but I can't find anything explicity calling this out - and surely other organisations will have a similar scenario to us. Is there any best practice recommendations from Microsoft in this regard?
Cheers, Tim
Using the Office Deployment Tool, I've created App-V 5.0 SP2 packages for
a. "O365ProPlusRetail"
b. "ProjectProVolume" and "VisioProVolume"
Both App-V packages ignore any exclusion rules in the configuration.xml file I've defined. This is expected and I can control which applications are published using Config Mgr 2012 R2. Both packages deploy and run as I would expect.
The issue I specifically have is that if I publish both App-V packages (using different package ID's) to the same PC with modified DeploymentConfig.xml files:
a. "O365ProPlusRetail" package only enables Word, Outlook and Excel (subscription licensing)
b. "ProjectProVolume/VisioProVolume" package only enables Visio and Project (volume licensed)
it appears as though the Word, Excel and Outlook from (b) are utilised instead of from (a) even though they are specifically disabled. This means that Word, Excel and Outlook activate to our local KMS server, rather than using the user credentials as we would prefer.
To confirm I can see that package (a) is already running when I run the following command: Get-AppvClientPackage | select Name, InUse, InUseByCurrentUser
Name InUse InUseByCurrentUser
---- ----- ------------------
Microsoft Office 15 ProjectProRetail_O365ProPl... True True
Microsoft Office 15 VisioProVolume_ProPlusVolu... False False
If I then open Word (which should only be enabled in the first package), I see that the second package is now in use
Name InUse InUseByCurrentUser
---- ----- ------------------
Microsoft Office 15 ProjectProRetail_O365ProPl... True True
Microsoft Office 15 VisioProVolume_ProPlusVolu... True True
I've also confirmed that all the applications (besides Visio and Project) are disabled in the second package:
Name EnabledGlobally
---- ---------------
Database Compare 2013 False
Spreadsheet Compare 2013 False
Excel 2013 False
OneDrive for Business 2013 False
InfoPath Filler 2013 False
Lync 2013 False
Access 2013 False
Telemetry Log for Office 2013 False
Telemetry Dashboard for Office 2013 False
Office 2013 Upload Center False
Publisher 2013 False
Lync Recording Manager False
Microsoft Outlook Mobile Service False
OneNote 2013 False
Send to OneNote 2013 False
Organization Chart Add-in for Microsoft Office programs False
Outlook 2013 False
PowerPoint 2013 False
Microsoft Office 2013 False
Office 2013 Language Preferences False
SharePoint Designer 2013 False
Visio 2013 True
Project 2013 True
Word 2013 False
Office XML Handler False
Internet Explorer False
Notepad False
Perhaps what I am trying to do is unsupported but I can't find anything explicity calling this out - and surely other organisations will have a similar scenario to us. Is there any best practice recommendations from Microsoft in this regard?
Cheers, Tim