Migrating to windows 2003

[helpdesk2005]

Hello everyone i am looking to migrate my domain controller to windows 2003 from nt but wondering if the following will be able to interact with it. I am running windoes 98 clients, exchange 5.5 and sql server 7. Any help or guidelines of what to do and possible steps is much appreciated. I realize the chances of 98 working and interacting with 2003 is slim but i have gotten 98 to talk to 2003 but no policy pulling yet...maybe that's where the issue is. Thank you for your help.

 

[aftertaf]

windows 98 and other non NT 5 OS can't pull policy like 2000/XP GPO... but they can be domain members.


NT4 can use policies, but not GPO, via the netlogon share (i think)

I think exch 5.5 & sql7 will work, though you'd be better asking someone else, or googling to see.

For your client OSs, if possible, try to upgrade to minimum w2000

Aftertaf
________
Regain control of your PC, at

http://www.debian.org

If you break your hard drive, it'll be DPlank's fault

 

[helpdesk2005]

so if i want to do any kind of upgrade it looks like i'll need to go 2k with the client os huh?

 

[aftertaf]

not an absolute necessity...
unless you want to use GPO.

Win 98 clients can use AD, they need the AD client installing to exploit things like better authentification, site awareness, password resets...

but you would have a nicer, more fun and less hassle park if all in 2k

Aftertaf
________
Regain control of your PC, at

http://www.debian.org

If you break your hard drive, it'll be DPlank's fault

 

[Electro121]

Hey HelpDesk,

In terms of upgrading the products - Exchange 5.5 will be compliant as well as SQL 7 but a few things will be needed. Exchange 5.5 you will need to use the AD connector, SQL7 will need the latest service pack. Your Win98 clients can also work with the environment natively depending on your needs.

I think the bigger question is to try and understand your setup and end goals by upgrading. What is it that you are trying to achieve by upgrading to Windows 2003?

If you are wanting to take full advantage of 2003 it would be best to update your clients to Windows 2000 or XP. As well, Exchange 2000 / 2003 has some huge advantages with being AD integrated, stability, etc.

So - let us know your plans so we can better answer your question.

Thanks!

Darryl Brambilla
IT Manager

 

[Stevehewitt]

Electro121 said it really. There is very little point in upgrading from NT4 with those clients and apps. Most of the functionality in Windows 2003 with AD, Group Policies etc, will not fully function (if at all) so I would look at possibly upgrading more than just your servers - no huge benifit unless the rest of your infrastructure catches up!

Cheers,



Steve.

"They have the internet on computers now!" - Homer Simpson

 

[markdmac]

I have to disagree that there is little point in upgrading. For one, there is no longer support for NT4, so hotfixes and security flaws are whatever they are. In the event of a critical system failure it is nice to know you have the ability to contact Microsoft directly if you are willing to spend the money for the incident. Security and stability on Windows 2003 is far better than any other server OS Microsoft has ever released.

Exchange 5.5 is soon to be in the same boat as NT. Support for it is going away within the next 2 months and that should be enough of a reason to upgrade considering how mission critical email is to most organizations. Furthermore the AD Connector is a pain. Once you get it running you won't have to touch it, but this is the single most frustrating piece for many of my customers if they try to do an upgrade themselves.

Regarding the Windows 98, you will want to install the DSCLIENT on those machines. Again I would point out the lack of support but in this case also the inherent security issues that come with 98. We are talking about a system with NO security. If it is connected to the Internet then you are just asking to have your domain become riddled with spyware and possibly viruses depending on the software solutions you have chosen. Seven years for an OS is long enough to milk the value of the OS. It is time to replace those machines.

My suggestion to you would be to upgrade the domain to Windows 2003. Then install a new Exchange 2003 server into the 5.5 site and use the move mailbox wizard to move mailboxes to the new server. Then retire the old server. Note that there is not a direct upgrade path from 5.5 to 2003 Exchange. If you need to re-use that hardware you would have 2 options.
1. Perform an interim upgrade to 2000 and then install 2003
2. ExMerge out your mailboxes, wipe the system clean and start from scratch with Windows 2003 and Exchange 2003. Then import the PST files using ExMerge.

Finally I would recommend the replacement of the Windows 98 machines to Windows XP. I would not recommend going to Windows 2000 as its supported life will soon be going away too. You may not be aware, but for hotfixes Microsoft will soon no longer be supporting Windows XP. They will require a minimum of Windows XP SP1 as a prerequisite for all critical updates.

I hope you find this post helpful.

Regards,

Mark

 

[Electro121]

I completely agree with markdmac on his comments regarding upgrading. There is defintaley merit to performing the upgrades.

The challenge that HelpDesk might be facing though is a management team that is questioning the need to spend a lot of money on software / possibly hardware. Unfortunately management does not always see the immediate problem (viruses, spyware, security / product end life). Past experience has shown management to be reactive instead of proactive in the IT area.

I would recommend upgrading either way but depending on your options (financial to do it right) you may have to pick and choose your battles here.

Thanks!

Darryl

 

[markdmac]

Budgeting is always a problem, but as stated 7 years is a bit much. Any company that relies on computers needs to invest in the infrastructure.

Sounds like helpdesk2005 already has the go ahead for Windows 2003. That should be a good catalyst for Exchange 2003 since that is the only version of Exchange that can run on windows 2003.

I hope you find this post helpful.

Regards,

Mark

 

[asktheman]

exchange 2000 will runn on w2k3

 

[markdmac]

That is incorrect. Exchange 2000 will not run on Windows 2003.

I hope you find this post helpful.

Regards,

Mark

 

[helpdesk2005]

thanks for the responses guys and the extra but very appreciated explanation markdmac.

so ill tell you what i have here..i have an nt dc, 2 nt bdc (if i want to replace my dc with w2k3 i am looking to just replace one of those 2 bdc's). How can i test that the w2k3 will be good to go as a bdc? i guess i should just call it a new domain and start pointing pc's to it as i migrate is that the way to go?

my company depends on roaming profiles and group policies will 98 work with these? this is the make/break point, everything is run through scrips, profiles and policies if i can't those to go then i'm screwed. We currently use static for the stations..yep..good ol static but will go dhcp with the new setup.

do i need to touch my sql 7 servers if i migrate to w2k3 or will that be ok - i know sql 2005 is out..but i don't want to do a lifetime's worth of upgrades at once if i don't have to.

and as for exchange - right now i heard there is no way to back up mails on 5.5 to a tape drive or watever method and that freaks me - is this true and markdmac you're saying exchange 2000 won't work with w2k3? can i upgrade 5.5 to 2003 straight?

this is a huge huge huge ass project for me and could kill the organization if not done properly so i am taking everything that i can get and evaluate before i move ahead.

 

[aftertaf]

mark:
" I would not recommend going to Windows 2000 as its supported life will soon be going away too"


Really? speculation or known fact?

helpdesk:
-.i have an nt dc, 2 nt bdc (if i want to replace my dc with w2k3 i am looking to just replace one of those 2 bdc's).

Nope!
You replace your PDC, as active directory domains dont have the notion of PDC/BDC. They are all readwriteable masters!

-my company depends on roaming profiles and group policies will 98 work with these?

GPO : Nope. 2k or XP
profiles... not 100% sure, but would say Nope too!


-do i need to touch my sql 7 servers if i migrate to w2k3
Yep! ;-)
2003 dont support SQL7

-exchange 2000 won't work with w2k3?
true, the schema (seeing as it integrates with A.D.) isn't compatible between the two.

-this is a huge huge huge ass project for me

And needs planning correctly!

I'd go for a totally new domain and migration bit by bit.

Here we have an NT4 domain being migrated to 2003, Exch 5.5
and we're giving it 9 months to make sure it all works!

bear in mind, exch 5.5 on a NT4/2000 server can be a member of a 2003 domain... I'd leave the mail server till the very last!

as for the sql databases. what OS are they running on?

Each bit is a big project... get it right, in the right order, and you'll be up for a medal ;-)

Aftertaf
________
I reserve the right to be wrong, be confused, be suffering because it is monday, or because it is nearly the weekend.

 

[helpdesk2005]

thanks aftertaf - so if i migrate to w2k3 pdc it looks like my 98 clients (500 of them) will be screwed since i depend on group policies and roaming profiles. As for the exchange i guess that this will be the last bit for sure my sql 7 is running on NT. Thanks.

 

[markdmac]

I agree with Afteraf's comments. Regarding 2000 life cycle, Microsoft has an N-1 policy. Current version minus one. R2 is scheduled for release soon. [red]Mainstream support for Windows 2000 Server and Professional ends June 30, 2005.[/red]

http://www.microsoft.com/windows2000/server/evaluation/availability/default.asp

The following URL ends with LifWin, you will need to cut/paste.

http://support.microsoft.com/default.aspx?scid=fh;

[ln];LifeWin


I was in a class for Microsoft Partners 2 weeks ago and was told that for patching, Microsoft is going to discontinue support for Windows XP. Before everyone freaks out on me keep reading. All hotfixes going forward will require a minimum of Windows XP SP1.

Helpdesk2005, you have two options available to you. You can do a greenfield deployment and slowly migrate resources to that new Domain. Or you could upgrade the existing domain.

Based on the information you have provided I would recommend going with the upgrade. It is important that you understand that the ONLY way you can upgrade is to do the PDC first. Just pick a server that is either the current PDC or one of your BDCs that you want to upgrade. If you choose a BDC then you must first promote it to PDC and can then upgrade it.

To answer your question about Exchange, no you can not upgrade from 5.5 to 2003. You would need to perform an interim step of upgrading to 2000 first. I would not go that route as it is a lot of extra work. The easier method (that provides better fallback in case anything goes wrong) is to get your domain running on AD first with the ADC (active directory connector) working on your 5.5 server. Then add a new Exchange server running 2003 in the same site as your existing 5.5 server. The Exchange 2003 install actually has a menu choice for doing this as it is a very common situation. Once your two Exchange servers are running together, you can use the Move Mailbox wizard to move your users over to the 2003. You can then direct all incoming mail to the 2003 server and gracefully remove the 5.5 server using MSKB 822450. Mail will continue to flow at all times during this method, though users will need to be out of their mailboxes while you move them.

Another option for you is to use ExMerge to export all mailboxes and then start the server from scratch as a Windows 2003/Exchange 2003 Server and import the PST files using Exmerge. Mail will of course not flow while the server is down for the re-imaging.

Your 98 Clients will have very limited ADDED functionality. Your existing profiles and scripts can run, just the way they do now using the Netlogon share, but they will not get settings from AD GPOs. You will want to install the DSCLIENT program on each of the 98 boxes (requires 98 SE).

500 98 desktops is certainly a lot to have to worry about. Your organization needs to start replacing those machines. Consider that there is no inherent security in Windows 98. I can boot a machine and hit Esc to bypass the logon. And there have not been security updates for it for years! You might want to take a look at RIS to get XP to push down to those machines so you don't have to visit all 500 your self. RIS is free and included in your Windows 2003 Server. Another great option that I really like is Symantec Ghost. It has a multicast feature that severely cuts down on the burden on the network when pushing down an install. Not free but worth the extra investment as it will cut down on your time greatly.




I hope you find this post helpful.

Regards,

Mark

 

[asktheman]

i have exchange 2000 running on a windows2003 domain all dcs running w2k3

 

[markdmac]

Yes, you can certainly have Exchange 2000 in a 2003 domain. You can also have Exchange 2003 in a Windows 2000 domain.

Exchange 2003 can exist on either 2000 or 2003 servers.

Exchange 2000 can not be installed on Windows 2003.

I hope you find this post helpful.

Regards,

Mark

 

[asktheman]

You will received a message saying that exchange 2000 is not meant for w2k3 etc.. but if you continue it will install fine and work correctly.. I have don't this... It is MS way of getting people to sign up to Exchange 2003. and so they should, and the features are alot better and with OMA and Active SYNC, it is a must for todays Gadget happy MD's...

But exchange 2000 will install on w2k3..

 

[benzgc]

Here is a link on how to that might help with your questions.

http://www.microsoft.com/downloads/...a0-76f0-4e25-8de0-19544062a6e6&DisplayLang=en

BENZ