Jump to content

Recommended Posts

Posted

We are jus moving all our switches to Radius for administration logins.

 

Got it working perfectly from an operation side, however, as we have 600 odd switches so adding these to the Radius server is going to be laborious. No problem I'd use a PowerShell script with a CSV to add the switches.

 

The Powershell script absolutely refuses to apply ether the Shared Secret or the Shared Secret template even though the password is correctly displayed in the output window :doh: .

 

I've tried adding the New-NPSRadiusClient with the shared secret hard coded, New-NPSRadiusClient applying the shared secret template and Set-NPSRadiusClient to change the shared secret after adding the client.

 

At this rate I thing I will be adding the clients disabled and then going through applying the template and enabling the clients manually.

 

Anyone got any solutions.

Posted

Now got a PowerShell script that adds the switches via a csv file. If I could only get it properly applying the shared secret.

 

One avenue I'm going to try is to set create a template with correct shared secret and then do a Set-NPRRadiusClient to change Name and IP. Last chance I suppose :-( .

Posted (edited)

In the end I found the following command, I jus now need to get this working importing from a CSV script

 

netsh nps add client name= [RADIUS CLIENT FRIENDLY NAME] address= [RADIUS CLIENT IP ADDRESS] state=Enable sharedsecret=[sHARED SECRET] napcompatible=No

Edited by Davit2005

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...