Windows/Office activation troubleshooting guide

Update 2-Oct-2015 :-

• Update the server name to vaserver2 to accommodate the Windows 10/ Office 2016 activation.

Please note below on the troubleshooting process for Windows/Office. It has been proven works with RMA Standard Operating Systems

• Windows 7, 8, 8.1, 10 Enterprise edition
• Office 2010, 2013, 2016 Standard edition

Steps :-

• To activate Windows
• Open elevated command prompt (run as local administrator) and execute command cscript slmgr.vbs /dli to determine the current activation status.

• Check the result
• Description should say "VOLUME_KMSCLIENT channel". If not, then execute command cscript slmgr.vbs /ipk <KMS-Client-Key>. You can find the KMS Client Key at http://go.rmagroup.net/it2b1 (it has to match your Operating System version/ edition).
• License Status should NOT say "Licensed". If it is so, then you do not need to continue the troubleshooting steps as it has already been activated.
• KMS machine name from DNS and KMS machine IP address should say "vaserver2.hq.rmasia.net:1688" and "10.66.2.63" respectively. If it shows only IP address means you are having a DNS problem. If both shows nothing, then you need to manually point the KMS server by executing command cscript slmgr.vbs /skms vaserver2.hq.rmasia.net or cscript slmgr.vbs /skms 10.66.2.63 (make sure you can ping the KMS server).
• After that, execute the command cscript slmgr.vbs /ato to activate Windows. If nothing goes wrong, it should return

• To activate Office
• Open elevated command prompt (run as local administrator), find ospp.vbs and navigate to that directory.

• Execute command cscript ospp.vbs /dstatus to determine the current activation status.

• Check the result
• License Description should say "VOLUME_KMSCLIENT channel". If not, then execute command cscript ospp.vbs /inpkey:<KMS-Client-Key>. You can find the KMS Client Key at http://go.rmagroup.net/v7vdv (Office 2010) and http://go.rmagroup.net/18wez (Office 2013) (it has to match your Operating System version/ edition).
• License Status should NOT say "---Licensed---". If it is so, then you do not need to continue the troubleshooting steps as it has already been activated.
• DNS auto-discovery should say "vaserver2.hq.rmasia.net:1688" but not always (it may work without). You can manually point the KMS server by executing command cscript ospp.vbs /sethst:vaserver2.hq.rmasia.net or cscript ospp.vbs /sethst:10.66.2.63 (make sure you can ping the KMS server).
• After that, execute the command cscript ospp.vbs /act to activate Office. If nothing goes wrong, it should return

If you struggle or needs ITM support, please submit an ITM support ticket at our ITM Helpdesk.