Help needed on rebuilding SBS 2003 Server

[Lino]

Our 2003 SBS server at work is having a lot of issues. The box randomly freezes, Active Directory is in pieces etc. We were going to get a new server but management does not want to spend the money for the time being.

Our hard-drives are too small, I suspect the system is running out of disk-space and causing serious errors. I am planning to replace the hard-drives with at least 500GB drives. We use two sets of RAID-1.

What I first want to do is run Platform Confidence Tests on the machine, during one weekend. (However I don't know how to do this yet)

Then if the machine passes I want to reinstall the server from scratch. Which will also mean resetting up Active Directory, however if I do that how will it affect PC's already on the domain and the 2003 Standard server in JHB?

 

[The_Unbeliever]

Two choices :

1. Do a complete install, join the machine to the domain, use dcpromo to make iit a backup DC. Ensure that replication of objects is successful. Then demote the main DC, and promote the new PC to PDC. The FSMO rules should be transferred automatically.

2. Export the users with CSVNT, and reimport them on the new box. You'll also need to copy some security certificates, or you'll have to remove/rejoin the workstations from the new domain.

The first option is easy, but should some crud get transferred over, you're still stuck with a problem on the new DC.

Second one is a bit more difficult, but no crud will be transferred, you can edit out unneccessary objects in the CSV file before importing them on the new server.

And good luck with that - try to go with RAID6 if possible.

 

[Lino]

Libs can I PM you and ask you a couple more questions please?

 

[Conradl]

Server 2003 editions are cool, unlike 2008, in that they can be rebuilt on different hardware. The easiest option would be to ghost the disk, restore it to the new disks, and then repair the server. It would be a good idea to have a second DC though, using the option 1 above. Rebuilding AD from scratch is not a good idea, you would have to recreate all the users, and re-add all the clients to the new domain, which could take long.

BTW, in one above, make sure that you transfer all the FSMO roles before rebuilding the machine - best option would be to keep the old disk entirely intact in case you bugger something up....

 

[|tera|]

Our 2003 SBS server at work is having a lot of issues. The box randomly freezes, Active Directory is in pieces etc. We were going to get a new server but management does not want to spend the money for the time being.

Our hard-drives are too small, I suspect the system is running out of disk-space and causing serious errors. I am planning to replace the hard-drives with at least 500GB drives. We use two sets of RAID-1.

What I first want to do is run Platform Confidence Tests on the machine, during one weekend. (However I don't know how to do this yet)

Then if the machine passes I want to reinstall the server from scratch. Which will also mean resetting up Active Directory, however if I do that how will it affect PC's already on the domain and the 2003 Standard server in JHB?

Hey Lino.

I'd take a different route because it's my style

Why format/rebuild/transfer if it's not required?

Treat the Server as a Server, but apply the same steps and logic you would with a normal home based PC.

So the following needs to be done:
Malware Checks. Remove any nasties.
Check Startup Items: Use Autoruns from Sysinternals, nothing comes close. (delete rogue entries, services and pointless non existing driver references).

Update the Server Drivers. Not with Windows Update, but straight from Manufacturer. If it's an HP Server for example you can download one Package that Updates everything on the Server, sometimes even Firmware if it's needed. After that's done make sure to conduct a Windows Update preferably through IE to know what you need.Start with your Baby: AD. Active Directory can be a mess sometimes, but unfortunately it would be easier for you to start rebuilding and reorganizing it now than doing it after an import.

There is no easy way or shortcuts to take if you want it done correctly. Start at the Top and Work your way down. At work we sort by Company>Departments>Users etc. Our management is separate as they have a different ADM. So is the IT department. Make sure that Group Policies are correct, security roles/groups etc.

What is the Server used for? Start there and optimize further.

Hope it helps.
Cheers man.

Edit:

You also managed HDD space to be an issue?

Use this: http://www.diskspacefinder.com/ Download it from the Server. I managed to clear 75GB of space due to Temp Files on one of our Servers this week using this program. You think your space is being used by important data, so did I, but you'd be surprised

 

[Lino]

Thanks guys! I will be drawing up a proposal for the MD.

 

[HavocXphere]

I suspect the system is running out of disk-space and causing serious errors.

Surely that is something one can check not just suspect?

Running out of space shouldn't cause the server to freeze imo and def not randomly. Sounds more like something one would catch w/ memtest though I suppose this Platform Confidence Test is the same thing.

 

[The_Unbeliever]

Libs can I PM you and ask you a couple more questions please?

Yes, you can.

Was just a bit hectic today.

 

[Asha'man X]

Hey pal

You can export the existing users with CSVDE, it exports pretty much all of the user details, which can then edit before reimporting. However, passwords are not carried over so people will have to start from scratch again. All the workstations will have to be rejoined, as they won't have a trust with the new domain. If the server in Joburg is somehow joined to the domain then there will be problems if it isn't a dc, but if it isn't joined then it's no problem.

Random freezings could be a problem in Windows, but it could also be bad ram. One of our servers at school was doing this, eventually a Memtest pinned down the faulty stick of ram. Haven't had an issue since.

 

[Lino]

I plan to run the Intel Platform Confidence tests on the server tomorrow afternoon. I read it shouldn't take longer than 15 minutes.

 

[Lino]

I plan to run the Intel Platform Confidence tests on the server tomorrow afternoon. I read it shouldn't take longer than 15 minutes.

Did the tests and they passed without any issues at all. Still waiting for more quotes on replacement hard-drives before management will give the go ahead.

 

[Grep]

Two choices :

1. Do a complete install, join the machine to the domain, use dcpromo to make iit a backup DC. Ensure that replication of objects is successful. Then demote the main DC, and promote the new PC to PDC. The FSMO rules should be transferred automatically.

I know this works 100% on a server to server environment, but can the above be achieved on a SBS environment?

 

[Conradl]

I know this works 100% on a server to server environment, but can the above be achieved on a SBS environment?

You can only have a single SBS 2003 server in a domain, and that server must host all the FSMO roles, which is why I recommended GHOSTing the machine. The Backup DC can be Windows Server 2003 Standard edition machine though....