Server Management and CEICW Not Available
Hi Everyone,
I just purchased an HP DL360 G5 SBS and, using HP SmartStart, installed Small Business Server 2003 R2. Everything seemed to go very well. I installed SP2, Exchange, Setup Windows Update and installed all critical updates and exchange hotfixes.
However, I'm trying to perform some configurations and I'm noticing some of SBS' components appear to be missing. Specifcally, I want to run CEICW. I was informed this wizard allows you to easily configure exchange to control an internet domain name as well as the local domain. However, I can't find the CEICW. In fact, after researching, I was told to run CEICW from the server management console. I also DO NOT have this console or even a folder under "Program Files" called "Microsoft Small Business Server 2003".
Another server I just received, a Dell poweredge SC1950, came with SBS 2003 pre-installed. And it has all these features!
I've tried installing all the service packs, resource kits, etc, but can't seem to get these items installed???
Thanks,
Rick
I just purchased an HP DL360 G5 SBS and, using HP SmartStart, installed Small Business Server 2003 R2. Everything seemed to go very well. I installed SP2, Exchange, Setup Windows Update and installed all critical updates and exchange hotfixes.
However, I'm trying to perform some configurations and I'm noticing some of SBS' components appear to be missing. Specifcally, I want to run CEICW. I was informed this wizard allows you to easily configure exchange to control an internet domain name as well as the local domain. However, I can't find the CEICW. In fact, after researching, I was told to run CEICW from the server management console. I also DO NOT have this console or even a folder under "Program Files" called "Microsoft Small Business Server 2003".
Another server I just received, a Dell poweredge SC1950, came with SBS 2003 pre-installed. And it has all these features!
I've tried installing all the service packs, resource kits, etc, but can't seem to get these items installed???
Thanks,
Rick
You mentioned you had 2 SBS servers, they cannot be on the same domain. Only one SBS per domain.
ASKER
Hi ... There is no continue install icon an there was no break or unexpected event that occurred during the install process (that I remember). I'm not sure if I may have cancelled any portion of the install process -- I don't remember denying the installation of anything...
Also, yes, these servers are unrelated and don't exist on the same domain. I was just referencing the second server to illustgrate the difference (no server management console present on the HP box).
Also, yes, these servers are unrelated and don't exist on the same domain. I was just referencing the second server to illustgrate the difference (no server management console present on the HP box).
Hello RangerRick1,
you can get the icon back on the desktop when you go to add/remove programs on the sbs server and choose to change the settings.
It will check for the installed components again and it will display the icon again, please read this:
http://sbs.editme.com/servercomp
Regards,
suppsaws
you can get the icon back on the desktop when you go to add/remove programs on the sbs server and choose to change the settings.
It will check for the installed components again and it will display the icon again, please read this:
http://sbs.editme.com/servercomp
Regards,
suppsaws
ASKER
There is no "Windows Small Business Server 2003" or "Windows Small Business Server 2003 R2" in the add/remove programs list. (so I can't follow the instructions in that link...)
Since this server isn't in service yet, I'm considering wiping it and reinstalling from scratch to see if this happens again... Unless anyone else has any ideas???
Since this server isn't in service yet, I'm considering wiping it and reinstalling from scratch to see if this happens again... Unless anyone else has any ideas???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It says "Windows Small Business Server" on the logon banner and when viewing MY COMPUTER properties... It does not say "Windows 2003 Standard" anywhere.
I certainly like your suggestion of a upgrade to retai drivers. I'll try that...
--Rick
I certainly like your suggestion of a upgrade to retai drivers. I'll try that...
--Rick
It would say Small Business Server because you used the SBS discs, however SBS is based on Server Standard so if you don't do the Small Business portion of the setup you just have Server Standard.
ASKER
Got ya.
So if I run the SBS installer of the SBS discs, it should try an SBS upgrade, right? [ie: the theory is it was smartstart that did the wrong installation??? - I know I tried to meticulously take my time to select the proper O/S during the smartstart process ... but I guess something may have gone wrong...]
--Rick
So if I run the SBS installer of the SBS discs, it should try an SBS upgrade, right? [ie: the theory is it was smartstart that did the wrong installation??? - I know I tried to meticulously take my time to select the proper O/S during the smartstart process ... but I guess something may have gone wrong...]
--Rick
You could try to fix things, but it will be much easier to just reinstall the whole thing.
You will keep the drivers because you always need to start with the smartstart cd.
You will keep the drivers because you always need to start with the smartstart cd.
Rick,
Yes just do an upgrade using the SBS discs. It will be less effort than wiping and re-installing and will keep smartstart out of the loop this time.
Yes just do an upgrade using the SBS discs. It will be less effort than wiping and re-installing and will keep smartstart out of the loop this time.
It's not that much work reinstalling an sbs from scrach.
When sbs didn't install correctly and you want to fix things by 'upgrading' things could still be messed up.
It's better to start from a perfectly installed SBS, but that is just my opinion ...
When sbs didn't install correctly and you want to fix things by 'upgrading' things could still be messed up.
It's better to start from a perfectly installed SBS, but that is just my opinion ...
I agree that if the core windows portion has problems then the upgrade will not help.
However, I think that it is more likely that the core Windows Server is okay and the SmartStart just messed up the the SBS portion. What makes us think that will not happen again?
I would upgrade and see what happens.
Another option that would take SmartStart out of the equation would be to make sure you have the harddisk controller drivers on a diskette, or slipstream them onto the installation media, then install SBS the normal, non-HP, way. That way you can be sure there is nothing else influencing the installation.
However, I think that it is more likely that the core Windows Server is okay and the SmartStart just messed up the the SBS portion. What makes us think that will not happen again?
I would upgrade and see what happens.
Another option that would take SmartStart out of the equation would be to make sure you have the harddisk controller drivers on a diskette, or slipstream them onto the installation media, then install SBS the normal, non-HP, way. That way you can be sure there is nothing else influencing the installation.
ASKER
You're right the SmartStart process installed just the Server 2003 components, not the SBS components. And what's worse--it must have been my mistake. I decided to try a full reinstall for several reasons (no upgrade problems and the server really did not having on it to loose yet). After carefully following the procedure and making absolutely sure I selected the correct O/S - The reinstall was successful and everything that was missing was present.
Oh well, problem solved and the new server is up and running smoothly. I had a little trouble with exchange getting RPC over HTTPs working (but that's another story)... But I hung in there and got it working too...
Thanks Guys!
Oh well, problem solved and the new server is up and running smoothly. I had a little trouble with exchange getting RPC over HTTPs working (but that's another story)... But I hung in there and got it working too...
Thanks Guys!
Otherwise put the install disks back in and re-do the sbs component portion.