Inconsistent parameters PolicyStore PersistentStore and Dhcp Enabled

7 thoughts to “Inconsistent parameters PolicyStore PersistentStore and Dhcp Enabled”

1. I found a solution to this problem.
   it’s not really clean.

   before performing the new-ipaddress

   Set-ItemProperty -Path (“HKLM: \ SYSTEM \ CurrentControlSet \ services \ Tcpip \ Parameters \ Interfaces \ {0}” -f $ netadapter.DeviceID) -Name EnableDHCP -Value 0

   after that the system no longer considers the PersistentStore DHCP as enable

   the new problem is that you will need to reset the value to 1 if you want to back to dhcp before Set-NetIPInterface -Dhcp Enabled.

   Reply

2. gci -Path “HKLM:\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\” | Set-ItemProperty -Name EnableDhcp -Value 0

   Reply

3. I found that although an “Inconsistent parameters…” error is thrown, the IP Address, Subnet Mask and Default Gateway addresses were set successfully. Therefore I programmed around the error, considering it a success.

   Reply

   1. Please ignore this post, I was mistaken. I found my issue and have posted it below.

      Reply

4. I eventually found out the reason I was getting “Inconsistent parameters…” error when using New-NetIPAddress to try and set IP addresses on a 2012 R2 Team.
   I had mistakenly thought that the network connections, Ethernet, Ethernet 2 etc would consistently map to the same physical NIC every time I built my server, but they don’t. Hence I had teamed two NICs that were in different VLans and were effectively reporting that they were disconnected, hence the “Inconsistent parameters…” error.
   You can use Get-NetAdapterHardwareInfo to consistently map physical NICs.
   Hope this helps someone.

   Reply

5. I was getting the error with the NIC connected and found this stopped the error.

   Set-NetIPInterface -InterfaceAlias $nicAlias -DHCP Disabled

   Reply

6. Your script is running too fast, and a (start-sleep 5) just before you go into the mode to assign the IP’s

   Reply