Upgrading member server to 2003 in 2000 environment

  • Thread starter Thread starter ra
  • Start date Start date
R

ra

I plan to update a member server to Windows 2003 so I can use IIS6
functionality. My environment is all W2K. What kind of issues can I
expect?

Thanks,

R
 
There's no problem at all adding a Windows Server 2003 box to a Windows 2000
domain.

I'm not sure if you're asking what issues you may have on that specific if
you upgrade. I would try to do a clean install if you can. You may have to
do some extra configuration with IIS6 (as it ships locked down), but I
suspect that's one of the reasons you want to use it.

The other issue is that once you have the new OS in your environment, you
have a new set of security patches to evaluate, test, and deploy.

Regards

Oli
 
Generally speaking, none whatsoever.

Pretty much the only thing that you would have to do - and this does not
apply as you are adding a member server and not a WIN2003 Domain
Controller - is extend the Schema by running adprep /forestprep ( on the DC
that holds the FSMO Role of Schema Master ) and adprep /domainprep ( on the
DC that holds the FSMO Role of PDC Emulator in *E*A*C*H Domain ). I might
go ahead and do this anyway so that you can take advantage of some of the
improvements.....

However, if you are running Exchange 2000 then please be aware of the
'mangled attributes' issue that is well documented ( including a pretty easy
fix ).

However, as with everything in this industry - test in a lab environment
first!

HTH,

Cary
 
Cary said:
Generally speaking, none whatsoever.

Pretty much the only thing that you would have to do - and this does not
apply as you are adding a member server and not a WIN2003 Domain
Controller - is extend the Schema by running adprep /forestprep ( on the DC
that holds the FSMO Role of Schema Master ) and adprep /domainprep ( on the
DC that holds the FSMO Role of PDC Emulator in *E*A*C*H Domain ). I might
go ahead and do this anyway so that you can take advantage of some of the
improvements.....

However, if you are running Exchange 2000 then please be aware of the
'mangled attributes' issue that is well documented ( including a pretty easy
fix ).

However, as with everything in this industry - test in a lab environment
first!

HTH,

Cary
Click to expand...

True, there would be no AD issues but if your current server is hosting
complex websites on IIS5 then you *may* encounter some problems when you
upgrade as the securtiy in IIS6 is a lot stronger.

..
 
ra,

Everyone's giving you great advice. Just remember to take care of your
current environment. As a general rule of thumb, you should never do an
in-place upgrade. Of course, this is not a technical limitation, but a
functional one. You need to keep any production environment stable and with
as little interruption or exposure to disaster.

If you cannot afford or acquire another server to install and migrate to,
you need to very carefully evaluate your desire to use the new features
versus the cost of complete loss.
 
Back
Top