Hello,

We have Visio 2013 & Project 2013 installed on Citrix XenApp and it is using MAK but I need it to use KMS.  We have a KMS server and the keys, where do I even start on converting those over as I haven't done this before?

Thanks

On your XenApp host (where Office/Visio/Project is installed), you can use ospp.vbs to change the installed product key from MAK to KMSclient key:
https://technet.microsoft.com/en-us/library/1825df76-7e23-459b-a6c1-224dd6eab81e#section1

The example shows changing KMSclient to MAK, but it is equally valid to change MAK to KMSclient.

Do I need to do anything on the KMS server?

If you have established a KMShost, with the relevant Office2013 KMShost configurations, and if that's already working in your environment for Office/Project/Visio KMSclients, you should have nothing else to do, if your RDS/XA host can communicate with your KMShost, you are ready.

If you have not established your KMShost for Office KMShost, then you need to do that.

By default, when you setup a KMShost, it will only service Windows KMS requests, so you need to add the Office KMShost "pack" and Office KMShost product key into that KMShost to extend the functionality.

Here is an article I wrote which may be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx

HA consultant did the Office 2013 MAK to KMS, Visio and Project were install as MAK later and now they want to charge to convert the 2 installs to use KMS.

Is it really that hard to do, they mentioned I have to reinstall Visio and Project?

HA consultant did the Office 2013 MAK to KMS, Visio and Project were install as MAK later and now they want to charge to convert the 2 installs to use KMS.

Is it really that hard to do, they mentioned I have to reinstall Visio and Project?

If your current product installation of Visio & Project is based on the Volume Licensing editions of Visio & Project (which is easily verified), conversion from MAK-to-KMS or KMS-to-MAK does not require re-installation.

Changing the current product key is all that is required.
For an RDS/XA scenario, assuming the example of a single RDS/XA host, Office is installed on that machine, as is Visio, as is Project. If Office is already converted to KMS, then you only have Visio x 1 and Project x 1, to convert.

This would require you to execute one command for each conversion (so two commands in total). The command simply changes the relevant product key for each product. Then perform activation, if required, although this is an automatic background task, in my experience. You need to have logged-in to the RDS/XA machine with Admin privileges to do this. You may need to kick off all users when you perform this task (to ensure that no Office/Visio/Project processes are in use). You may need to restart the RDS/XA machine, to complete this action, so be prepared to do that.

At worst, if something goes wrong with this simple task, you might need to uninstall/reinstall the Office/Visio/Project products. (although I've personally never encountered the need for that)

I've not personally installed/operated an RDS/XA scenario, but I do operate many thousands of desktop/laptop machines, and Windows Servers, and several KMShosts.

The GVLK product keys (which is what a KMSclient needs) are here:
https://technet.microsoft.com/en-us/library/dn385360(v=office.15).aspx

You can verify/display the current products and license types on the machine, by using cscript ospp.vbs /dstatusall

You can pipe that output into a textfile, for easier reading, and, as a record of "how it was before I changed it":
cscript ospp.vbs /dstatusall > c:\somefile.txt