infoblox_nios:ms_managment
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_nios:ms_managment [2023/04/17 13:47] – bstafford | infoblox_nios:ms_managment [2024/10/23 10:17] (current) – [DHCP] bstafford | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Normally, use the GMC to manage the Microsoft Management members. | Normally, use the GMC to manage the Microsoft Management members. | ||
| + | |||
| + | When you delete a MS server in NIOS, all zones synced from that MS server are removed from the Grid. | ||
| Never use GM to do MS AD ID Sync. | Never use GM to do MS AD ID Sync. | ||
| Line 30: | Line 32: | ||
| ===== DHCP ===== | ===== DHCP ===== | ||
| The Infoblox Management Member must be able to talk to the DHCP hot spare server in addition to the main DHCP server in order to be able to deactivate scopes and re-active scopes. | The Infoblox Management Member must be able to talk to the DHCP hot spare server in addition to the main DHCP server in order to be able to deactivate scopes and re-active scopes. | ||
| + | |||
| + | ===== DHCP Migration ===== | ||
| + | The process below works for DHCP Networks/ | ||
| + | - Unassign the DHCP Range (from Windows Servers) | ||
| + | - Delete Microsoft Servers from DHCP Network | ||
| + | - Add Infoblox DHCP servers to DHCP Network | ||
| + | - Assign DHCP Range to Infoblox Failover Association | ||
| + | |||
| ===== Management ===== | ===== Management ===== | ||
infoblox_nios/ms_managment.1681739266.txt.gz · Last modified: by bstafford