Microsoft Window 2003 Standard Server replacement queston

The new server will have different internal names for the clients than the old server (normal Windows way of naming). But if you set up the same userids in AD and have the same users folders, then the users should be able to log off (restart preferable) and log back in.

If their drives were persistent, you may have to make them non-persistent and log back in. Test one of the stations.

If it is the only server and there are no others, then it should think it is the only server.

.... Thinkpads_User

what do you mean the server crashed?  A crash should not merit a new server, at worst, it would warrant a re-install.  Unless you mean there was a hardware failure of something difficult to replace, like the motherboard.

I assume you have no backups or you would have restored the server.

WHY do you want to maintain the same server name and IP?  If your only previous server failed, then there is no problem re-using the same name and IP, but it's a different server.  Just like you can have two people with the same names and have one transfer their phone number to the other, they are still different people.  Windows domains and computers have a randomly generated unique ID (like a social security number) that will prevent you from just naming it the same and using the same IP and having things work.  Since you only had one server and (again, assuming) no backups, you cannot restore the domain information you had had.  So now you're stuck disconnecting and reconnecting all workstations to the new domain.  And yes, you have to setup the server as if you never had one - it's not going to know anything about your network automatically - domain/domain name/files/users/computers/etc.

Since this is not your area of expertise and you are not an IT Professional and this is a business (right), it would seem very unwise to do this yourself - I would suggest a major replacement like this should be done by a professional so you get it done right the first time.  Either that, or spend a few weeks reading books and doing test configurations - your first install should NOT be the one that you make THE install.
.

If I install this server as the primary server with the same name and IP as the old one, will I be able to connect all the clients as if the old one were still there after restoring the backups which has the share names, etc?

In a word.. NO you will not be able to do this. You can reinstall the older operating system and restore from backups and then upgrade to the newer operating system.

When you say the server crashed, what do you mean.. hard drive, power supply, motherboard?

Just sticking in a brand new unconfigured server that is running a different operating system and restoring data files will be a challenge.. It will be like starting from scratch except that you have some data files that can be restored.. you will have to setup shares/Active Directory etc, all over again.

The Server is several years old and the motherboard is bad, therefore I purchased a new Server with the current OS.  I do have backups.  Maybe I did not state the question I have clearly.  I know the new server has a different OS, 2008r2 vs 2003 standard.  I  was unsure whether I could restore the system state backups to the new server or just the data.  I think I have found that answer.

Thank you all for your help.

The server change is major, so you can restore the data (as I suggested near the top), but I don't think you can restore the system state because it is so different.

.... Thinkpads_User

I just going to put a little advice, if you have backups and a spear machine install the old Server version in the spear machine and restore your backups to have you AD back on track.

Then put your new server and try  a migration from 2003 to 2008, might be faster and a better solution than start from scratch.

thanks for the advice.  I appreciate it.

Actually, you may be able to use uTools UMove to preserver your Active Directory database (may require reinstalling a new system (virtual should be fine) running the old OS and then using UMove to effective import Active Directory.

On going issues:  I have installed the Server from scratch, moved and setup shares, created user and computer accounts, etc....  However the question now has become with the clients.  

Does anyone know if there is a way in both windows xp and windows 7 sp1, to use or copy the old profile?  The issues is when I put the new server in operation, I, of course, had to take each client pc out of the domain, put them in a workgroup, then join them to the new domain in order for network printers and such to work properly.

All the clients use Outlook 2007 for email and it is asking me to setup the email client as if the user pc was new.  I need to be able to copy the old profiles with settings to the new profile, if that is possible.  If not, the options I know of is to export/import pst files to new profile, then copy over the old profile to new one manually on each.

Did your Domain Name change?, Did you change your Exchange Server Name?

Did you get the users desktops back to normal or do they change.  Are you able to open the old OST files.

My Domain name is the same.  The exchange server is not on my Server therefore the ES name is the same also.  

the user desktop changes, once I join to the new domain as if they are a new user.  that was the question regarding how to get back to or copy the profile the user had on the previouse server domain.

I should be able to see and copy the ost file in windows explorer.  is that what you recommend?

Yes you will be able to see the ost but unable to make it work on your current profile.

I'm still surprise you have a new profile if your settings are the same????!!!!!

Anyways, if your only concern is your exchange settings, once you create the new profile, everything will be "dump" on this profile.  It may take long, depending on the user emails but you should be able to get every single email.  Regarding your archived files, if any, those will be pst files that you can get from the previous profiles.  If you need the path for those let me know.

Now, if you want all the user profile, Windows profile, the you can go to Start,All programs, Accesories, System Tools, Windows Easy Transfer, for Windows 7 and star, all programs, Accesories, System Tools, Files and Settings Transfer Wizard for WinXP, follow the prompts to create the "backup" or transfer files, then run it on the new profile and you should be ok.  This is in the case you can still access the old profiles.

Good Luck!

I am still working on the client issues....  

I have tryed the pc mover (suggested above).  it worked fine on the first xp client, however, it would not allow me to copy the profile but it did let me assign the new profile to the old one.  However, on the next client, windows 7, it would not allow me to assign or copy the profile.

I am also having issues with "some" of the windows 7 clients joining the domain.  I am getting the following:

An attempt to resolve the controller in the domain being joined has failed.  Please verify this client is configured to reach a DNS Server that can resolve DNS names in the target domain.

You must delete the computer account from the server, when you are going to join it to the domain, the system will create it properly by itself.

Then at every station run an elevated DOS prompt and type ipconfig /flushdns then ipconfig /registerdns.

Reboot and try to join the computer in the domain again.