• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 479
  • Last Modified:

Small Business Server 2003 issues. Want to revert to fresh install. Reformat or easier way?

Hello,

We recently had a consultant come in and "overhaul" our system... he ended up getting confused and doing all these backdoor type fixes and fixes for the fixes... needless to say he is not here anymore, but I would like to revert all the way back to a fresh install and start over.  What is the easiest way to do this.. and if there is no easy way... and I have to reformat the drive.  How would I do this with a SATA RAID 1 config?  I am definitely computer literate in the end user world, but am definitely new to servers.  Is it any different from reformatting an IDE standard configuration?

I have a feeling some will tell me to troubleshoot my issues and get more familiar with what I am doing.. as the same issues may come up again down the line... well here is a recap of what happened.  We wanted the server to be the center of everything.  So he consolidated it all... made our server a router by enabling DHCP and DNS (although he said it wouldnt work and had to use a third party program because for some reason our SBS wouldnt enable the services).  He then edited our "host" files on each client and gave us all static IPs. Did some more tweaks like making our server a proxy server.  

One of the big issues now is that the "Server Management" tool dissappeared... when you click on it.. the flashlight comes up and says cannot locate exe.  He tried to reinstall it with the SBS 2003 CD... but it didn't work.  

The first thing I plan on doing (and am doing it today) is to seperate the routing from the server and bring it back to hardware routing.  If this is not the smart way to do it, I hope someone can provide insight...

...sorry it sounds like there are many things that are not right... and I am not skilled enough yet to fix them.  If anyone can help out it will be much appreciated.
0
Pharcyde616
Asked:
Pharcyde616
  • 4
  • 4
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
What it sounds like is that your consultant knew NOTHING about SBS.  Which, unfortunately, is the case all too often.

The best thing to do WOULD be to flatten it out and start all over.  This includes your workstations as well (at least making sure that any changes such as host files were corrected - and removing the workstations from the domain).

Then, you should read the Getting Started Guide (http://sbsurl.com/start) and the other good resource for most everything SBS is http://sbsurl.com/techguide.

If you have two NICs, then you want to keep routing within your SBS.  The recommended config for that is here:  http://sbsurl.com/twonics

Overall, you should send your consultant a copy of this:  http://sbsurl.com/itpro and it's a good read for you too... even without any server background it shows why you should configure an SBS the default way.

Jeff
TechSoEasy
0
 
Pharcyde616Author Commented:
I know that you remove the users from the domain on the server end... but I was unaware that you had to do this on the client side also... how would you go about doing this?  Sorry for my ignorance.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You wouldn't remove the user on the client side, but the computer. The "client" itself.  Just unjoin your current domain and join a workgroup instead prior to taking down your old server.

Jeff
TechSoEasy

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
juanferminCommented:
Unfortunately, Reformatting a server can cause more problems than what it solves.  First thing I would do is check the Error logs to figure out what the problems are, and try to find solutions for them from there.  Other than that, you should really try to find someone in your area that knows SBS, make sure they bring references from reputable companies.
0
 
Pharcyde616Author Commented:
TechSoEasy - I found a response that you had posted to someone earlier.

1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients
5.  Reboot

1.  by THAT machine do you mean server?
2.  How do you unjoin the domain into a WORKGROUP.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
The complete text of those steps is actually:

The following needs to be done with the client machine:
1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients
5.  Ensure that the Network Settings are configured to automatically get an IP address. (DHCP enabled)
6.  Reboot

Then on the server, from the Server Management Console:
1.  Remove the client computers if it still shows in the Client Computer screen on the Server Management Console
2.  Add the client with it's NEW name using the Add Computer wizard

Then, go back to the client machine and join the domain by opening Internet Explorer and navigating to http://servername/connectcomputer

So, hopefully that answers your first question... no, not the server, the workstation.

You unjoin the domain into a workgroup by right clicking on MY COMPUTER > Properties > Computer Name > Change... and then change it from the domain to a Workgroup (workgroup name doesn't matter).

Jeff
TechSoEasy
0
 
Pharcyde616Author Commented:
I'm doing it this afternoon.  Lets hope this all goes well!
0
 
Pharcyde616Author Commented:
Thanks Jeff.  It took a night and a day, but server is up and running SMOOTH.  THANKS AGAIN!
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No problem... glad to hear that it worked out well though!

Jeff
TechSoEasy
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now