If this is the case for you, right-click the drive you want to format and click Initialize Disk. This will prompt a new window asking you to select a partition style for your disk. If you’re going to be using the drive with a version of Windows prior to Windows Vista, you’re going to want to go with MBR.
![]() -->
Applies To: Windows Server 2016
You can export the entire NPS configuration — including RADIUS clients and servers, network policy, connection request policy, registry, and logging configuration — from one NPS for import on another NPS.
![]()
Use one of the following tools to export the NPS configuration:
Important
Do not use this procedure if the source NPS database has a higher version number than the version number of the destination NPS database. You can view the version number of the NPS database from the display of the netsh nps show config command.
Because NPS configurations are not encrypted in the exported XML file, sending it over a network might pose a security risk, so take precautions when moving the XML file from the source server to the destination servers. For example, add the file to an encrypted, password protected archive file before moving the file. In addition, store the file in a secure location to prevent malicious users from accessing it.
Note
If SQL Server logging is configured on the source NPS, SQL Server logging settings are not exported to the XML file. After you import the file on another NPS, you must manually configure SQL Server logging.
Export and Import the NPS configuration by using Windows PowerShell
For Windows Server 2012 and later operating system versions, you can export the NPS configuration using Windows PowerShell.
The command syntax for exporting the NPS configuration is as follows.
The following table lists parameters for the Export-NpsConfiguration cmdlet in Windows PowerShell. Parameters in bold are required.
Administrative credentials
To complete this procedure, you must be a member of the Administrators group.
Export Example
In the following example, the NPS configuration is exported to an XML file located on the local drive. To run this command, run Windows PowerShell as Administrator on the source NPS, type the following command, and press Enter.
Export-NpsConfiguration –Path c:config.xml
For more information, see Export-NpsConfiguration.
After you have exported the NPS configuration, copy the XML file to the destination server.
The command syntax for importing the NPS configuration on the destination server is as follows.
Import Example
The following command imports settings from the file named C:Npsconfig.xml to NPS. To run this command, run Windows PowerShell as Administrator on the destination NPS, type the following command, and press Enter.
For more information, see Import-NpsConfiguration.
Export and Import the NPS configuration by using Netsh![]()
You can use Network Shell (Netsh) to export the NPS configuration by using the netsh nps export command.
When the netsh nps import command is run, NPS is automatically refreshed with the updated configuration settings. You do not need to stop NPS on the destination computer to run the netsh nps import command, however if the NPS console or NPS MMC snap-in is open during the configuration import, changes to the server configuration are not visible until you refresh the view.
Note
When you use the netsh nps export command, you are required to provide the command parameter exportPSK with the value YES. This parameter and value explicitly state that you understand that you are exporting the NPS configuration, and that the exported XML file contains unencrypted shared secrets for RADIUS clients and members of remote RADIUS server groups.
Administrative credentials
To complete this procedure, you must be a member of the Administrators group.
To copy an NPS configuration to another NPS using Netsh commands
This stores configuration settings (including registry settings) in an XML file. The path can be relative or absolute, or it can be a Universal Naming Convention (UNC) path. After you press Enter, a message appears indicating whether the export to file was successful.
For more information about netsh, see Network Shell (Netsh).
![]() Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |