Skip to main content

Microsoft Network Policy Server Synchronization Script

This powershell script is written for automating to export configuration from master NPS and then import it on a secondary NPS in order to keep a secondary NPS ready with latest configuration. Script must run on secondary node. The account that runs the script must be the member of both of the master and secondary servers local administrators group.

$nps_master = "master_nps_server" #Master Network Policy Server's HostName or IP Address
$nps_conf_dir = "C:\Tmp\NpsConf\" #XML configuration file store directory.
$nps_conf_path = "C:\Tmp\NpsConf\NpsConf-$nps_master.xml" #XML configuration file path.
$nps_conf_share_path = "\\$nps_master\Tmp\NpsConf\NpsConf-$nps_master.xml" #Master Network Policy Server's share path.
if (!(get-eventlog -logname "Application" -source "Nps-Config-Sync")) {new-eventlog -logname "Application" -source "Nps-Config-Sync"}
trap {write-eventlog -logname "Application" -eventID 0001 -source "Nps-Config-Sync" -EntryType "Error" -Message "NPS Synchronization Script Error: $_. The Script is $($MyInvocation.MyCommand.Definition)"; exit}
invoke-command -ComputerName $nps_master -ArgumentList $nps_conf_path -scriptBlock {param ($nps_conf_path) Export-NpsConfiguration -Path $nps_conf_path}
copy-item -path $nps_conf_share_path -destination $nps_conf_dir
get-item $nps_conf_path
Import-NpsConfiguration -Path $nps_conf_path
remove-item -path $nps_conf_share_path
remove-item -path $nps_conf_path
$success_message = "Network Policy Server Configuration is successfully synchronized from $nps_master. The Script is $($MyInvocation.MyCommand.Definition)"
write-eventlog -logname "Application" -eventID 0002 -source "Nps-Config-Sync" -EntryType "Information" -Message $success_message


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) Slave1 Node: (Centos 7.2) Slave2 Node: (Centos 7.2) Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/ Each Node: /etc/