Can I assume DHCP scopes imported from a Windows Host are now static objects and hold no relationship to the scope on the Windows side?
1. Imported scope, now lives in Discovered Subnets
2. Network engineer changes the name of the scope on the Windows side
3. New scope name has not been imported, old scope name still exists in Discovered Subnets
I guess we are expecting a fully automated IPAM synch in the product. Well, the network team is.
Can anyone comment on this?
I just want to give them an idea of how they still need to manage scopes manually in IPAM.
The fact that it did not import the NEW renamed scope is also a question - is there a reason why? I'm not saying that's a bad thing, but I'm trying to understand if there is a GUID or meta data associated with the scope.
The IPAM documentation doesn't mention how scopes are synchronized (or not) unless I didn't see it.