IPMartin is an IT service provider. I find myself in the same situation. Any chance anyone can help me out? To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Thanks for your help :. Which of the following retains the information it's storing when the system power is turned off? Submit ». Instead, it will focus on installing SBS as an Exchange server that also features file and monitoring services.
Having installed previous versions of SBS and countless Active Directory and Exchange servers, the experts amongst us will be tempted to install components manually, the trademark of a real expert.
I would really recommend against it. Microsoft put a lot of effort in determining what most SBS installations require so that if you follow the wizards you will get a fully working server with little use for extra tweaking.
Also, SBS is restricted from a security perspective, so if you don''t follow the wizards to the end of the installation process, you will have to spend some time loosening these restrictions for some regular features to work.
The first step in installing SBS is setting up the operating system in the same way that Windows is installed. At his stage you should not proceed with the wizard.
Instead you should configure the server to support the rest of the installation. The following screenshot shows my recommendation for partitioning of a server. The rest is used for data such as databases and user files. Having configured the server partitions, now is a good time to configure the page file itself accessible by right clicking My Computer and choosing "Properties" or from the control panel.
If you install SBS servers with a single network card, like I do, you might get the following notice:. My recommendation is to leave all of the installation on the default drive C: and create folders for all of the data folders on the large data partition. My ServerB is now the main workforce of the network. Bringing it down will be a disaster for the company.
And I'm not willing to do it at all. I don't get why the server has to be standalone. I'm not exactly sure how you find the management consoles, but it might be "Server Tools" as the KB says. SBS has been around for a long time and I don't ever remember hearing of the console not getting installed with the initial server build - I was not aware that SBS could be installed without it, so I don't think it's something that's easily left out of the installation process.
If you didn't build Server B, there may be other issues you're not even aware of yet. Also, is it possible that the person who built Server B hacked it up to get two SBS boxes running in the same domain? If something was done to keep the second SBS in the domain from shutting down, that might be a case where, unless you're sure how to undo whatever was done, you really should reinstall in my opinion.
I installed the OS on ServerB from scratch. I might overlook something during the installation, but as I can recall there was nothing serious during the installation. I completed the OS installation without any hiccups. The server was functioning normally; the only thing missing is the console. If you spend some time to google, you will see lots of people who posted questions about how to reinstall the Server Management because they couldn't install the CAL licences on their servers, i.
I'm surprised there are also a lot of people having the same issues as mine. The SBS must have some critical weaknesses, and this one is one of those. I'm sure Microsoft won't care about SBS anymore. They want people getting rid of this OS to move to newer ones. I will have to reinstall the ServerB again. But the thing that makes me really upset is why this critical utility was treated as an optional component, and there is no way to add the component except for scrapping everything on the server and reinstall all over again.
Anyway thanks a lot for your time and your replies. I don't think anyone can propose better solutions to resolve this issue. There is only one way to resolve it; that is wipping out the server and reinstall everything from scratch again Do you have a "continue setup" icon on the administrator desktop?
If so, run it and follow through to the Component Selection screen. That'll let you install the Server Tools, or click the down arrow next to "Install" to get the other options not sure if it's Repair, Reinstall, or what but it should be obvious. Just a thought, because I think this runs automatically the first time, but it's worth a look if you've got the desktop icon. Merv, I'm not aware of this installation. Is this something you can download from internet?
After finishing the OS installation, I was prompted for installing updates. After the updates being installed, the OS was running with Service Pack 2. It needs to be removed from the domain and proper 'migration' procedure followed.
Well, it's too costly to go through the process to fix the problems. I think the best solution right now is to keep both servers running. I can handle other things without that console. The only thing that I really need is to install the CAL licenses onto the new server. I just don't want to spend so much effort in order to achieve this little goal.
0コメント