Re: Things to watch out for during 9.0->9.1 upgrade?

oegf_at_ejnfep.com
Date: 08/20/04


Date: Fri, 20 Aug 2004 10:39:26 GMT


|It depends on the size of the organisation... If you have a small company
|that doesn't rely heavily on its IT, then yes, upgrading and fixing the
|problems as they occur might be acceptable - not recommended, but
|acceptable.

The thing is that Linux and other FOSS has made IT affordable for SMEs.
When the upgrade involves say a machine with a Postfix server and an
IMAP server, asking for a period of parallel testing imposes more
disruption than the change itself.

|For a large company, where loosing the DNS or DHCP server for even an hour
|could result in millions of pounds in lost revenue, the IT Manager would
|have to be crazy (and shortly thereafter looking for a new job) to attempt
|to upgrade any server or workstation without having fully tested the new
|software first.

That would be the kind of organisation that would go for SLES anyway.
And YOU would probably be a bit risky too.

The main thing to do is not to blindly apply the same principles
everywhere, but choose the appropriate strategy for the situation. I
have sympathy for both ends of the spectrum. I know programmers who will
not write anything but standard Bourne shell constructs for portability
reasons. Then there are sites that simply dictate that all machines
shall have bash installed and keep them so.

-- 


Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)