Quantcast
Channel: Windows 8.1 Installation, Setup, and Deployment forum
Viewing all articles
Browse latest Browse all 5362

Setup/migrate to VAMT 3.0

$
0
0

We currently run VAMT 2.0 for activating Windows 7/Office 2010 using our KMS key and need to upgrade to VAMT 3.0 for Windows 8/2012. I want to setup a new server with VAMT 3.0 alongside and migrate across but little bit unsure on few steps. In order for our current Windows 7/Office 2010 to continue activating via our new VAMT 3.0 server, is it simple changing the DNS entry for _VLMCS to new server or do I need to delete this and activate new server which should automatically take care of this. Or do I actually select all the licensed products in VAMT 3.0 and re-activate that way?

My plan so far is :

1) Install PowerShell 3.0
2) Download ADK http://www.microsoft.com/en-us/download/details.aspx?id=30652 which includes VAMT 3.0.
3) Select Volume Activation Management Tool and SQL Server 2012 Express
4) Start VAMT - enter .\ADK as Database server - create new database called 'VAMT3.0'.
5) Right click Products and select Discover products.
6) Select Products in the left pane. In middle, right-click the selection and selectUpdate license status and Current credential from the context menu.
7) Look at the license summary. This should tell you what VAMT automatically discovered.
8) Click View, - Preferences. Under Key Management Services host selection,make sure Find a KMS host automatically using DNS (default) is selected.
9) Right click Product Keys, Add Product Keys :
W7 Enterprise =***********
W7 Professional =***********
Office 2010 Standard = ***********
2008R2 = ***********
10) Uninstall the KMS key from VAMT 2.0 server by running : cscript c:\windows\system32\slmgr -upk
11) Install the default KMS key on VAMT 2.0 server : cscript c:\windows\system32\slmgr /ipk******************** (2008R2 – default key)
14) Delete the _VLMCS record from DNS (Forward Lookup Zone - _tcp).
15) Activate KMS on new VAMT 3.0 server : slmgr.vbs /ato
16) Check DNS record is pointing to new VAMT 3.0 server.
17) Perform test.
18) Check KMS count either in VAMT console or : slmgr.vbs /dli


Viewing all articles
Browse latest Browse all 5362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>