2

We will be setting up a tertiary RADIUS server at a remote site. Up until now, changes to the RADIUS database has been done manually, since it was only 2 servers. With a third one coming online I wanted to see if there is some way to sync the changes between RADIUS servers using Windows Server 2008 R2.

3 Answers 3

5

Why not use an active directory back end? If you do this, you will only have to update the appropriate groups once instead of on all servers? This is very easy to configure in NPS.

3
  • Seconded- what RADIUS software are you using, @Josh? That will help shape an effective answer, don't you think?
    – mfinni
    Sep 28, 2010 at 19:56
  • Using Server 2008 RADIUS... Nov 13, 2010 at 2:41
  • Is this solution only for group memberships etc? For example I've added a new type of device with different policies -- I need to add the new clients and policies to the other NPS servers. How do I do this with AD, or am I stuck with the export/import cycle below? Dec 12, 2014 at 17:59
4

I just came across your question. I have been working with nps in windows 2008/2008r23 alot recently. If you haven't found a good solution for this problem I might have one.

Decide on which of your servers is going to be your master. Make your chances on this server. Using powershell you can export the configuration for nps including shared secrets to a config file. It will not include sql database accounting setup. You can save it on a shared location between your servers. Then on the slave server (your servers that you want to apply your changes to) you can run the powershell import. You can script the export and import on your servers.

Export Config from powershell prompt on master server

netsh nps export filename = "C:\config.xml" exportPSK = YES

Import Config from powershell prompt on slave server

netsh nps import filename = "C:\config.xml"

You can script this and also substitute any shared storage you have between the servers. With powershell you can copy the file over to your remote servers with

copy-item C:\Config.xml \server\share\Config.xml

Potentially you could take these pieces and with a little more powershell and have a script that you run whenever you make a change that will push out the change to all of your nps servers.

2

When I was looking for a solution for this problem, I found this article by Microsoft:

Manage Multiple NPS Servers by Using the NPS MMC Snap-in

If anybody has the same issue, I hope this link will help.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .