In a perfect world this might not be needed but I’ve seldom see that in reality. So I understand the reasons behind their request. Even if such software is in place more likely than not it doesn’t cover all devices (printers, copiers, scanners, load balancers, …) You’re lucky if they know and have a list of all devices that need their DNS entries changed, sometimes you don’t even have that. Often a management solution for settings the IP configurations on hardware devices is not in place even when does tools exists (i.e. There are devices that do not accept FQDNs, can’t be DCHP clients. But al lots of devices that need a DNS Server are a pain to deal with. Servers that have static IP addresses without using DHCP reservations can be dealt with via scripting. Normally DHCP takes care of the DNS servers for clients. They wanted to preserve the server names and IP addresses for these servers. That would have made it very easy as not only are they already running on the latest Windows version but they had some extra requirements. įor several reasons not all domain controllers or core infrastructure servers should be virtualized so this was not just a matter or doing a P2V migration and be done with it. These are in fact the servers that where upgraded to Windows 2008 R2 some 16 months ago right after Windows 2008 R2 went RTM. At one place I provide Infrastructure consulting & services the supportable life of some servers running Active Directory, DNS, WINS and DHCP has come and gone (+5 years old DELL PE1850) so I was asked to renew them.
0 Comments
Leave a Reply. |