Synopsis: This tutorial will cover a basic "upgrade" path to go from Server 2008 R2 to Server 2012 R2. This tutorial assumes you have a single Network Policy Server and you are wishing to reuse the same machine name, IP, and settings. In environments needing high availability, you will need to complete each of the steps below, adding/removing each server being upgraded from your network load balancer.
In a standalone instance, you will experience some downtime as you will have to retire the old machine and setup a new one.
Tutorial
- Login to your Server 2008 R2 NPS server
- Open up a command prompt with Administrative Privileges
- Execute the following command
- netsh nps export filename="c:\users\YOURUSERNAME\Desktop\NPS.xml" exportPSK=YES
- netsh nps export filename="c:\users\YOURUSERNAME\Desktop\NPS.xml" exportPSK=YES
- Copy the NPS.xml file to your local machine
- Disjoin the NPS server from the domain
- Retire the machine
- Recreate a new Server 2012 R2 machine with the same name and IP address
- Join the Server 2012 R2 machine to the domain
- Open up Server Manager and select Add Roles and Features
- Click Next > on the Before You Begin screen
- Click Next > on the Installation Type screen
- Click Next > on the Server Selection screen
- Check Network Policy and Access Services (click Add Features when the screen pops up)
- Click Next > on the Features screen
- Click Next > on the Network Policy and Access Services screen
- Check Network Policy Server and click Next >
- Click Install
- Click Close once the installation has successfully completed
- Copy over your XML file from the old NPS server to your new Server 2012 R2 NPS server.
- Open up an administrative powershell prompt
- Execute the following command
- Import-NpsConfiguration -Path c:\users\YOURUSERNAME\Desktop\NPS.xml
- Import-NpsConfiguration -Path c:\users\YOURUSERNAME\Desktop\NPS.xml
- Head over to Server Manager and select Tools -> Network Policy Server
- Verify the rules imported (I selected RADIUS Clients and Servers -> RADIUS Clients to see if it imported my WLAN controller)
- Connect your machine to your wireless network! 🙂
I'm running NPS on Windows Server 2008 R2 and going to move it to 2012 R2 server. The given export command didnt work from commandline, but starting netsh and entering nps and then giving command "export c:\nps_export.xml exportPSK=Yes" worked as expected.
the "filename=" is not part of command and adding that to command will result "The filename, directory name, or volume label syntax is incorrect." error.
the right syntax didn't work, I tried to run it "netsh nps export "c:\NPS_export.xml" exportPSK=yes" command gave same error.
Also starting netsh and then giving command “nps export C:\NPS_export.xml” exportPSK=Yes” works fine. Somhow the “netsh nps export C:\NPS_export.xml” exportPSK=Yes” just generates error “The filename, directory name, or volume label syntax is incorrect.”
Hi Jari,
It sounds like the file path you have specified is incorrect. The filename specifier is part of the command. You can read more about the command here: http://technet.microsoft.com/en-us/library/cc732059(v=ws.10).aspx
Hope this helps,
Jack