Upgrading to new servers: Few questions.

[Winchester]

We currently have 2 servers; one file and SQL; the other server is mainly just Exchange, with internet access (active directory syncs between the two). They both backup to a 100GB/200GB tape drive each night, using Veritas. Both are currently running Windows 2000 Server.

We just got a new Dell rack server (no OS), but am currently looking at getting another to replace the exchange server. I am wondering about getting the files to the new server. I have 2 days of down time allotted to move into our new cabinet and install this server. I have Windows 2003 Server License & CD to install as well. I am mostly worried about the SQL Server stuff. The general files etc wont be a problem IMO.

File Server: What is the BEST method of moving the files/databases to the new server? Should I install Windows Server 2003, then restore the files & data from the tape drive? Should I install Windows 2000 Server then restore the files, then upgrade to 2003 Server? Should I just do a restore from the backup tape drive? (since both servers backup to a single tape, will that be a problem?)

Exchange/Internet Server: Same as above.

I hope you see where I am going with this? I have until next thurs to have a plan. I have PowerQuest VolumeManager and have resources ($) to get other items as well.

 

[Rapidskies]

.

 

[mikecel79]

Need a little more information first.

We currently have 2 servers; one file and SQL; the other server is mainly just Exchange, with internet access (active directory syncs between the two). They both backup to a 100GB/200GB tape drive each night, using Veritas. Both are currently running Windows 2000 Server.

Do you mean both servers are domain controllers? When you say "internet access" do you mean it's also your proxy server? What version of SQL and SP are you running on this machine? What version and SP of Exchange are you running on this machine

For moving files I would just install Win2k3 and restore the files to that machine. Keep it simple. Then follow this procedure for move any shares to the new file server. That will take care of your files and permissions.

For moving SQL and Exchange can get complicated. Need to know what versions your running before you do it.

 

[Winchester]

I solved the SQL problem. The company who makes the program included MSDE on their latest software installation CD. So I am set there AFAIK. I am installing Windows Server 2003 right now, because I called and checked on this stuff with the company they said all I needed to do was backup my database then put in their CD and it and install their software which would then install the MSDE SQL engine, which is all that we need to run the program.

I am currently running BackOffice 2000, so ver 2000 on everything.

When I say "internet access" I mean port 80 is open so people can access their email from the outside.

I am pretty sure our exchange server is the domain controller, the DNS, DHCP, etc run off of it.

I just got off the phone with Dell OpenManage Support, he said since I am retiring the two current servers, that I will have problems moving the domain controller & active directory stuff. Can anyone expand a little in plain english. He pointed me to this link

 

[mikecel79]

Right off the start you've got serious security problem here. Putting a DC on the internet pretty much opens up yourself to attack. The chances of your machine being attacked are probably low but thats a risk that I am personally not willing to take for a business. Now that's said we can get into your problem.

solved the SQL problem. The company who makes the program included MSDE on their latest software installation CD. So I am set there AFAIK. I am installing Windows Server 2003 right now, because I called and checked on this stuff with the company they said all I needed to do was backup my database then put in their CD and it and install their software which would then install the MSDE SQL engine, which is all that we need to run the program

MSDE is not the same thing as SQL server. MSDE is meant to be a redistributable database system to ship with products. Were you using SQL before or was it MSDE? If it was MSDE then leave it the way it is now. If not I suggest you install SQL server and look into transferring database from one machine to the other, assuming of course the other machine is still around. Either way to run MSDE 2.0 or SQL 2000 on Win2k3 you must be at SP3a and have the security roll-up installed.

I am currently running BackOffice 2000, so ver 2000 on everything.

Exchange 2000 is not supported on Win2k3. You won't be able to install it at all. Exchange 2000 can be installed on a Win2k member server in a Win2k3 domain however. Do you plan on going to Exchange 2k3?

I am pretty sure our exchange server is the domain controller, the DNS, DHCP, etc run off of it
I just got off the phone with Dell OpenManage Support, he said since I am retiring the two current servers, that I will have problems moving the domain controller & active directory stuff. Can anyone expand a little in plain english. He pointed me to this link

You can't "move" AD to another set of servers. The best way would be to bring up a Win2k3 server. Run DCPROMO and promote it to a DC inside AD. This will prep the AD schema and bring it up to Win2k3 level. After that you can run DCPROMO on the other machines and demote them back to member servers. After that you can remove them from the domain. That's the safest way of doing it.

But you've got a problem here. Since your Exchange server is also your DC you can bring up the new Win2k3 server as a DC but you can't install Exchange on it. At least not your current version. You need to go to Exchange 2k3 for that. How many total servers do you have to work with and what runs on each one? Let's figure this out before we go any further.

To be honest it sounds like you are in way over your head already. I suggest you do some reading on AD and Exchange migrations before you go ahead and just jump into this thing.

 

[Winchester]

Im not totally sure about the DC thing, it might be the other server, not sure. How can I tell for sure? I did not set all this crap up.

I have licensing for Exchange Server 2003, just dont have the media yet. I know 2000 is not compatible with Windows 2003 Server

Ive been reading a crap load on migrations. I will probably order another server this week to be the Exchange server. We will eventually move to 3-5 servers over the next 12 months, one for each function (SQL, Exchange, Spam, Internet, File/Print, etc)

 

[mikecel79]

If you can't tell which one is the DC yet you really need to learn more about AD before you continue. AD is a complex directory system. Microsoft makes it look very simple on the surface but it is indeed a complex system that if your not sure what your doing you can get into a LOT of trouble fast. Take some time and read up on AD at TechNet. It'll help you a lot more in the long run than just asking random questions here.

Here's how to find what your DCs are. Sounds like it's a very small company so I will make the assumption that there is only one AD site. Open up AD Sites and Services MMC console. It will be installed on all your DCs but can also be installed on your workstation with the Win2k Admin tools. Once that's open expand the Site folder and look for one called First Site Name or something like that (this of course assumes the person did not change the site name). Expand that and then expand the servers folder. That will list all your DCs.

Ive been reading a crap load on migrations. I will probably order another server this week to be the Exchange server. We will eventually move to 3-5 servers over the next 12 months, one for each function (SQL, Exchange, Spam, Internet, File/Print, etc)

Do youself a favor and make one of these a dedicated DC or combine the File/Print with the DC. Don't mix Exchange or SQL on a DC for performance reasons and to avoid problems like this in the future.

 

[Winchester]

Both servers are listed. A third server is listed, but it no longer exists. Licensing Computer is listed as our current file/print/sql server (fbclubbock.org is our domain).

I will make the one I am installing now (file/print) the DC, since it should be here for a couple of years. It will have SQL for now, until we get $ for new servers for that. I have to do it on this one because we are retiring the current ones.

PS: New server is a Dell PE2650 with 2 x XEON 3.06GHz, 1GB Ram, 4 x 146GB HDs. We have approx 75 users and about 100 computers.

 

[mikecel79]

Both servers are listed. A third server is listed, but it no longer exists. Licensing Computer is listed as our current file/print/sql server (fbclubbock.org is our domain).

The three servers listed are your DCs. This was what I was afraid of though. You now have an orphaned DC record in your domain. It will only be a matter of time before your DCs start complaining they can't replicate to this missing DC now. You'll need to use ADSI Edit to clear out the missing DC records. This Microsoft KB Article will show you how to do it.

I can't stress this last part enough. Do NOT follow this unless you KNOW what you are doing. You can do serious damage with ADSI Edit if you are not careful.

 

[Winchester]

I have been reading KB article after article and books etc all for some time now trying to gain as much knowledge as I can and will continue to until next Thursday when we actually make the move. It would be nice however to be able to do everything but the DC switch up until that time so that all I have to do next Thurs is the DCPROMO thing on the servers.

It possibly has been several years, well since Windows 2000 Server came out, that the third server has even been active. No less than a year for sure. AFAIK, the third server (NTSERVER) is actually now the exchange server, just with a different name (FBCSERVER), since both have exchange settings under them.

The Exchange Server is a Global Catalog Server.

I am planning on keeping the current servers running for a while just in case, I will however, move them (because we are going to a cabinet) and will have to change the name on them because of profiles and mapped drives etc. Will that be OK?

For now, I just want to concentrate on setting this up the right way. Everyone before me has done things half way, and as you can tell, leads to problems in the long run.

BTW: the AD Operations Master is the File/Print/SQL server Does that help any?

Mike, I appreciate your help.

 

[mikecel79]

AFAIK, the third server (NTSERVER) is actually now the exchange server, just with a different name (FBCSERVER), since both have exchange settings under them.

Ok does this mean it was reformatted and not removed from the domain? So I assume you have only 2 physical servers but there are 3 listed in AD correct?

The Exchange Server is a Global Catalog Server.

Good. This means it's also a Domain Controller.

I am planning on keeping the current servers running for a while just in case, I will however, move them (because we are going to a cabinet) and will have to change the name on them because of profiles and mapped drives etc. Will that be OK?

You can't change the name of a DC or an Exchange server. The name of the machine can't be changed without breaking AD or Exchange.