Inherited Quirks

moss · 21 Jul 2011 at 22:25

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.

s0ck · 22 Jul 2011 at 12:34

AD domain name completely unrelated to the company and actually registered and owned by another company.

.local for the winnings

Doh!

PistolPete · 22 Jul 2011 at 12:43

A remote access platform that connects from a web based Sun Secure Global Desktop, to a Terminal Server to a Citrix Web portal to deliver apps to users.

Ev0 · 22 Jul 2011 at 12:43

Really poor SMS implementation at my previous place, but then again I was brought in to sort it out

A few things in the new job that are a little wtf but people seem to have their heads firmly in the sand for those...

moss · 22 Jul 2011 at 12:50

PistolPete said:
A remote access platform that connects from a web based Sun Secure Global Desktop, to a Terminal Server to a Citrix Web portal to deliver apps to users.

That sounds like an absolute nightmare!

Muffin` · 22 Jul 2011 at 12:54

The internal network and comms links. It's all on the cheap and it does 'work' but just seems so poorly thought out and rushed - I've had no end of issues with TMG 2010, although TMG 2010 does seem to DDos it's self daily :confused:

Just this morning people were complaining printing was slower than usual, logged onto the only F&P server, 1GB of RAM, with 997 in use, wooo, that'll be it.

Saundie · 22 Jul 2011 at 13:01

Our internal domain is called mainoffice.local, which is used by a number of our customers. This causes lots of problems when we VPN into their sites for remote support, as it means our workstations get confused and try to authenticate us against the remote domain. Fortunately we've been able to migrate a lot of our customers away from mainoffice.local to something more relevant to them, but I don't understand why we didn't call our domain something else in the first place. Apparently it's too late for us to change now.

moss · 22 Jul 2011 at 13:01

We have a partially externally managed printing contract, they have setup it up so that print jobs from remote sites come back across the (very slow) links to HQ then back to the remote site. As you can imagine printing anything other than text is a nightmare.

ruffneck · 22 Jul 2011 at 13:04

A busy website checkout relying on a webservice hosted internally to process orders.

PAz · 22 Jul 2011 at 13:10

Crappy SMB applications being used as Enterprise class systems that cannot handle the throughput.

PistolPete · 22 Jul 2011 at 18:41

moss said:
That sounds like an absolute nightmare!

Yeah - I forgot that that can sometimes be a VMware XP Virtual desktop in between the Terminal Server and Citrix, but thankfully it has the proper Citrix client and not useing the web portal.

moss · 22 Jul 2011 at 19:30

PistolPete said:
Yeah - I forgot that that can sometimes be a VMware XP Virtual desktop in between the Terminal Server and Citrix, but thankfully it has the proper Citrix client and not useing the web portal.

And I thought the Citrix setup we have at work was crappy! Ours has automatic failover, meaning that any server in the citrix farm fails, the rest automatically fail too!
Thankfully we are getting rid of it very soon.