One thing I failed to mention is a major factor in getting rid of the Bluecat 
devices.  The devices had a strong tendency to lockup and or stop accepting 
requests during periods of high usage.  Since the devices could not be pinged 
or gotten into by http/https or telnet, an emergency change request had to be 
done.  Once it went thru the 3 levels of change control, someone had to call 
the data center to have the devices powered off and back on.

Because of the many hundreds of zones and because they were standard zones (not 
AD Integrated) it took almost one month of effort to get off those devices.  
There was no command or utility to get multiple zone transfers so it was one 
zone at a time.  I also remember something about it wouldn’t transfer all the 
records in a zone because of the way the DNS records were handled internally 
and the records had to be manually edited.  Sorry, not the DNS records 
themselves, the zone files that were created by the Bluecats.  They were not a 
standard zone file and Windows couldn’t (wouldn’t) import them so the zone 
files had to be manually edited.  Cricket Liu would have been cursing those 
Bluecat zones.

Overall it was a major royal PITA and they were (are) glad to be off those 
devices.  The customer has had zero issues since moving to AD Integrated DNS 
zones and Windows DHCP.  And I think the Windows team is now making the network 
infrastructure team go through change control every time they need something 
done in DHCP or DNS (payback is hell you know).

Thanks


Webster

From: Webster [mailto:[email protected]]
Subject: RE: Slightly OT: RE: Migrate DHCP from 2003 to 2008 R2

The company I just helped move their DHCP and DNS stuff from the appliances did 
it because appliances are under the control of the network infrastructure team. 
 Any time a DNS record or DHCP reservation was needed, a change control form 
had to be submitted and go thru three layers of review processes and then wait 
for a scheduled monthly maintenance window.  When you are implementing Citrix 
PVS, that is a burdensome process.

Thanks


Webster

From: Guyer, Don [mailto:[email protected]]
Subject: RE: Slightly OT: RE: Migrate DHCP from 2003 to 2008 R2

Scalability/redundancy/features/centralization.


From: Don Kuhlman [mailto:[email protected]]
Subject: Re: Slightly OT: RE: Migrate DHCP from 2003 to 2008 R2

Hi Don. Just curious as to why the switch to appliance based DHCP from Windows ?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to