<< `Oh, @#$%. He's right.' | Home | Brian Gilstrap on Dependency Injection >>

Don'ts

  • Don't make your user mad.
  • Don't make your user lose work.
  • Don't make your user change email client.
  • Don't make your user change email protocol.
  • Don't make your user reconfigure ssh client.
  • Don't make your user's email stop working.
  • Don't make your user's any application stop working.
  • Don't make your user's email become slower than before.
  • Don't make your user's any application slower than before.
  • Don't make your user's shared folders stop working.
  • Don't make your user's printing stop working.
  • Don't make your user's email stop printing.
  • Don't make your user's mailing lists change the way they work.
  • Don't make your user's ssh session timeout change the way they work.
  • Don't make your user's daily routines stop working.
  • Don't make your user's occational use cases stop working.
  • Don't make your user's different login profiles overwrite each other.

Now go ahead and upgrade the network infrastructure.



Re: Don'ts

Sounds like somebody screwed up some OCI upgrades.

Re: Don'ts

Amen. At my current client "they" just upgraded the entire company to the latest Exchange server, forced all employees to upgrade to the latest version of Outlook, then refused to open POP or IMAP ports. Thus, we cannot use Thunderbird. Funny thing is, some developers use Linux and cannot run Outlook. All too often, the sysadmins have too much control and lose sight of the fact that they are here to serve us, their customer. Not the other way around.

Re: Don'ts

Don't change your user's login name to accomodate the limitation of your network administration tool! Don't continue the upgrade if the trial run goes badly.

Add a comment Send a TrackBack