To be SBS2003…or not to be…that is the question!

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 To be SBS2003…or not to be…that is the question!

This topic contains 7 replies, has 4 voices, and was last updated by Avatar universal 5 years, 10 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • Avatar
    LSainsbury
    Member
    #162677

    Hi,

    We’ve just taken on a new client with an SBS2003 server – well at least that’s what it claims to be in system properties and winver reports the same.

    However, there’s no sign of the SBS Console, no SBS programs group, no Small Business Server folder in c:Program files, the registry hive HKLMSoftwareMSSmall Bus Server contains very little and no SBS components in Add / Remove Programs.

    What gives? Anybody seen that scenario before? A migration will be fun for that one… :razz:

    Avatar
    cruachan
    Participant
    #330639

    Re: To be SBS2003…or not to be…that is the question!

    Sadly I have. Only time I’ve seen it the scenario was someone slipstreamed windows sps and RAID drivers into the SBS install media, which breaks SBS thinking that it is SBS. AD works though so you can migrate to full product OK, not much of an issue now that SBS is no more anyway.

    Avatar
    universal
    Member
    #388518

    Re: To be SBS2003…or not to be…that is the question!

    LSainsbury;278642 wrote:
    Hi,

    We’ve just taken on a new client with an SBS2003 server – well at least that’s what it claims to be in system properties and winver reports the same.

    However, there’s no sign of the SBS Console, no SBS programs group, no Small Business Server folder in c:Program files, the registry hive HKLMSoftwareMSSmall Bus Server contains very little and no SBS components in Add / Remove Programs.

    What gives? Anybody seen that scenario before? A migration will be fun for that one… :razz:

    I’ve seen that lots of times.

    There’s probably nothing wrong with the setup at all. With SBS 2003, the basic installer installs the OS only. When you reboot, the SBS wizard guides you through the installation of all the other components, like AD and Exchange, but you can also just cancel the Wizard, and it will leave a shortcut on the desktop should you ever want to run it again.

    But you can choose to install everything manually instead. There are a number of advantages to that approach, not the least of which is the ability to partition the disk any way you like.

    And here comes the really great part: Should you at a later date decide to install the SBS management tools, they’ll still work! OK, so the User Management tools still insists all user objects be created in an OU called “SBS Users” under “My Business”, but you can always move them afterwards.

    SBS 2003 is just Windows 2003 + Exchange + Sharepoint with a peculiar licensing scheme. You MUST make the server a DC, otherwise it’ll shut down after an hour (or was it two?), but otherwise you’re free to install whatever components you like in whatever manner you prefer.

    TL;DR: This setup isn’t likely to cause any trouble if you want to migrate to a more recent platform. In fact, you can treat it as any other single-server Windows 2003 AD environment.

    Avatar
    LSainsbury
    Member
    #308866

    Re: To be SBS2003…or not to be…that is the question!

    Thanks for the replies.

    Yes there is a “Continue Setup” exe on the desktop – Exchange is partly installed – I don’t know how that could happen if the install didn’t continue.

    There are no AD groups relating to SBS like My Business etc….

    Avatar
    universal
    Member
    #388520

    Re: To be SBS2003…or not to be…that is the question!

    LSainsbury;278658 wrote:
    Yes there is a “Continue Setup” exe on the desktop – Exchange is partly installed – I don’t know how that could happen if the install didn’t continue.

    Whoever installed it must have decided to run setup.exe manually from the Exchange CD instead. Which works just fine.

    LSainsbury;278658 wrote:
    There are no AD groups relating to SBS like My Business etc….

    Because the SBS Management Tools aren’t installed.

    You don’t need to have a “MyBusiness” OU just because you have Small Business Server. You can create any AD objects you like using the standard tools.

    Avatar
    LSainsbury
    Member
    #308867

    Re: To be SBS2003…or not to be…that is the question!

    Ser Olmy;278659 wrote:
    Whoever installed it must have decided to run setup.exe manually from the Exchange CD instead. Which works just fine.

    Fair comment – the customer isn’t using Exchange on this server either – the services re disabled.

    Ser Olmy;278659 wrote:
    You don’t need to have a “MyBusiness” OU just because you have Small Business Server. You can create any AD objects you like using the standard tools.

    Yep – I know they can be anywhere.

    What migration issues would I be likely to run into – if and when?

    Might be easier to start from scratch – there’s only 7 or so computers…

    Avatar
    Ossian
    Moderator
    #189052

    Re: To be SBS2003…or not to be…that is the question!

    tbh, if you have any doubts about the previous install, I would automatically go for a fresh install and manually copy files / some profile folders onto the new server – emails can be exported to PST and local profiles can be exported with Migwiz. For 7 users the extra time is probably less important than the potential risk of a migration going wrong later

    Avatar
    universal
    Member
    #388521

    Re: To be SBS2003…or not to be…that is the question!

    LSainsbury;278719 wrote:
    What migration issues would I be likely to run into – if and when?

    Might be easier to start from scratch – there’s only 7 or so computers…

    You’re not likely to run into any problems at all, but it might be a good idea to re-enable the Exchange services and uninstall he product.

    Are you planning to migrate users and data to a new server and a more recent OS?

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.