Jump to content


Photo

PVS with KMS for Office, Visio and Access

Started by Julian Jakob , 19 March 2017 - 09:27 PM
2 replies to this topic

Best Answer Kelan Rowe , 27 March 2017 - 03:21 PM

Hi Julian,

 

Its not entirely clear when the error occurs, if only with visio installed and vdisk in standard, or if after installing and vdisk is still in private mode.

Installing visio with customer key:

Following link covers installing visio without different product key, creating custom MSP is probably easiest way to go.

https://blogs.technet.microsoft.com/odsupport/2010/12/03/volume-license-editions-of-visio-2010-install-premium-edition-by-default/

 

Installing office products within PVS, simplified steps:

Applicable for all windows and office combinations.

However, office 2010 and windows vista have inbuilt maximum rearms, so this method will utilise one of those rearms.

Office 2013 and above, and Windows 7 and above have unlimited rearms (rearm count increments to 1 from 0, on successful kms activation)

·         Shutdown targets and began process:

1.       Edit vdisk properties; uncheck KMS option, change access mode to “Private Image”

2.       Boot the vdisk in private mode, install and configure all the office products as required, ensure they work as expected, through reboots in private

3.       Finally reboot the vdisk in private mode, verify no office applications are running

ü  Rearm office

ü  Rearm windows

ü  Shutdown immediately

4.       Edit vdisk properties; check KMS option, change access mode to “Standard Image”, stream to multiple targets and verify working as expected.

Julian Jakob Members

Julian Jakob
  • 29 posts

Posted 19 March 2017 - 09:27 PM

Hey guys,

I always setup KMS with PVS for Windows and Office like this http://www.ingmarverheij.com/citrix-pvs-enabling-kms-licensing-on-a-vdisk/ and it always worked with old and current PVS Releases.

One environment Windows and Office Standard is activated via KMS for my Workers.

Now Visio and Access installed standalone afterwords. For these products there is the same KMS Host Key, but another KMS Client key. When trying to install the KMS Client Key for Visio or Access, always get a "Software Licensing Service reporter, that the product SKU is not found"

Installed Visio new, repaired it, installed it to another path, always this error. Deleted Office standard, installed Visio first and then Office standard, for Office OK, for Visio error again.

Any Ideas?

Thanks and regards
Julian

Julian Jakob Members

Julian Jakob
  • 29 posts

Posted 24 March 2017 - 08:01 AM

Nobody this problem? Nobody has to install Visio or Access afterwords a Office standard installation?



Kelan Rowe Citrix Employees

Kelan Rowe
  • 84 posts

Posted 27 March 2017 - 03:21 PM

Hi Julian,

 

Its not entirely clear when the error occurs, if only with visio installed and vdisk in standard, or if after installing and vdisk is still in private mode.

Installing visio with customer key:

Following link covers installing visio without different product key, creating custom MSP is probably easiest way to go.

https://blogs.technet.microsoft.com/odsupport/2010/12/03/volume-license-editions-of-visio-2010-install-premium-edition-by-default/

 

Installing office products within PVS, simplified steps:

Applicable for all windows and office combinations.

However, office 2010 and windows vista have inbuilt maximum rearms, so this method will utilise one of those rearms.

Office 2013 and above, and Windows 7 and above have unlimited rearms (rearm count increments to 1 from 0, on successful kms activation)

·         Shutdown targets and began process:

1.       Edit vdisk properties; uncheck KMS option, change access mode to “Private Image”

2.       Boot the vdisk in private mode, install and configure all the office products as required, ensure they work as expected, through reboots in private

3.       Finally reboot the vdisk in private mode, verify no office applications are running

ü  Rearm office

ü  Rearm windows

ü  Shutdown immediately

4.       Edit vdisk properties; check KMS option, change access mode to “Standard Image”, stream to multiple targets and verify working as expected.


Best Answer