Title. We're trying to put better process around when we stand up a new internal IP range. The list seems endless and complex. Need to add it to any number of systems for scanning, AD Sites and Services, internal routing, DNS, DHCP, PAC file entries. Does it have a public gateway? Register it with X, Y, Z public providers as being part of our network.
This is just scratching the surface. We tend to always forget SOMETHING when provisioning a new network and is often found months after the network is in use and either tickets are re-routed eternally or users just deal with a bad experience for a while.
We'd like to work toward getting it right the first time. I think we can gather most/all of the THINGS that need to be done, but how do we put this data to use and make it effective to consume?
- Wiki/KB documentation listing everything?
- ServiceNow/ITIL workflow?
- Something else?
How are other enterprises approaching "new network onboarding"?
No comments:
Post a Comment