Not sure if this is the best part of the forum for this thread but it seems the most appropriate as its only likely to apply to people with reasonably large networks/domains.
What inherited quirks/bad designs/implementations do you have to put up with at work?
The one which annoys me most at work is our internal network uses a public IP addressing scheme, from a random Uni in America. I'd love to change it but most of our network is mission critical (999 control room/links to stations) so it would take a crazy amount of planning/downtime.
Although it doesn't cause any real problems, recently a consultant said it might cause some issues when we implement Microsoft Forefront later this year.
Also our internal domain name is the same as our external URL, which was fine until a few weeks ago when we moved our website to external hosts. A small tweak sorted that problem out though.
What inherited quirks/bad designs/implementations do you have to put up with at work?
The one which annoys me most at work is our internal network uses a public IP addressing scheme, from a random Uni in America. I'd love to change it but most of our network is mission critical (999 control room/links to stations) so it would take a crazy amount of planning/downtime.
Although it doesn't cause any real problems, recently a consultant said it might cause some issues when we implement Microsoft Forefront later this year.
Also our internal domain name is the same as our external URL, which was fine until a few weeks ago when we moved our website to external hosts. A small tweak sorted that problem out though.