When this Notes administrator had to rename his servers he never intended to hide them from his users. But that's exactly what happened. Find out how our hero became an unintentional master of server disguise.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Last year, another company acquired our company. That meant that I had to rename our servers, organizational units, domains, etc. Since our company is involved with many acquisitions, I thought it would be best to give our servers logical but generic names. So I named one of our servers "LNSERVER1" and the other "LNSERVER2" (i.e., Lotus Notes Server 1 and 2). It made perfect sense to me.
The weekend of the big change came along and everything went off without a hitch. I sent the users instructions on how to update their connection documents. On Monday morning, I started getting calls from users saying that they couldn't access the servers. I asked them if they updated their connections and they said yes. I had one user explain what he put in the server name field and he stated that he typed "inserver1". Little did I know that a lower-case "L" looks exactly like an upper-case "I". At that point, it was too late to back out so I sent out corrected instructions in all caps.
To this day, I still have to fight with the users because they can't find "LNSERVER1" or "LNSERVER2." They only see "inserver1" or "inserver2".
Do you have your own blooper? Send it in and claim your fame.
Every story in our bloopers series comes to us directly from a SearchDomino.com administrator, developer or consultant. For obvious reasons, some contributors -- including this tale's author -- choose to remain anonymous.