Actually, a better solution would be to get a couple of paper MCP's, sign up for being a MCSP and get the software for free. A couple grand for some tests and a couple grand for your MCSP and you are there. And now you do not have to live with all of the limitations of SBS.
And in all honesty, from the amount of people that I personally know that have hit the "SBS wall", I would have a tough time saying "the vast majority of SBS installations would never face that task". Why set yourself up for failure? > You know what they say: opinions are like, well never mind... > > Personally, I think SBS is a fantastic product, provided you keep it's > limitations in mind up front. Yes, it would be a pain to upgrade, but my > guess is that the vast majority of SBS installations would never face that > task. > > Most small companies (10-15 employees) could never afford to buy Win2k, E2K, > and ISA server, let alone SQLServer. SBS gives them all this for the price > of Win2K server alone! > > -----Original Message----- > From: Greg Deckler [mailto:greg@;infonition.com] > Sent: Tuesday, November 05, 2002 1:22 PM > To: Exchange Discussions > Subject: Re: Moving E2k storage group to new Server > > > Well, the easiest way to do this is to install another E2K server and simply > move the mailboxes to the new server. Now, the only thing that might throw a > wrench into this for you is running sbs2k. And, I have repeatedly stated > this and let me go on record as stating that SBS is a terrible product that > should never be installed anywhere in the entire world because of the > serious limitations that it imposes on organizations. This is a perfect > example as to why an organization should NEVER install SBS. And if there are > any companies out there that have consultants recommending SBS, fire them > immediately and get somebody competant. > > One of the big problems with SBS is that it uses the Standard Edition of > Microsoft Exchange, which has the nasty limitation of not being able to > support multiple Exchange servers. > > From Microsoft docs: > "Exchange 2000 on a Small Business Server installation is restricted from > being part of a larger Exchange server organization. Because Small Business > Server 2000 is installed as the root of the Active Directory forest, you > cannot install the Exchange 2000 component into an existing organization." > > Also from Microsoft docs: > "Full installation of Windows 2000 is required. It is not possible to > upgrade Microsoft BackOffice Small Business Server to the Windows 2000 > operating system; however, if your hardware meets the system requirements > (http://www.microsoft.com/windows2000/advancedserver/evaluation/sysreqs/) > for Windows 2000, you can install the full product. > > The current plan for the next release of Small Business Server is to base > the product on the Windows 2000 operating system. For more information about > Small Business Server, see the Small Business Server Web site > (http://www.microsoft.com/smallbusinessserver/default.htm)." > > What this means in a nutshell is that I don't have a solution for you. I > have searched Technet and have not been able to find an acceptable upgrade > path from SBS to anything useable. Essentially, since you are running SBS, > you cannot install a new E2K server into the organization and simply move > the user mailboxes. And, in all honesty, I have not found an acceptable way > to upgrade SBS to W2K enterprise. > > If anyone has a solution out there for upgrading SBS to enterprise versions, > I'd love to see it. There HAS to be a way, Microsoft could not have been > THAT bone-headed. On the other hand, they released SBS so I guess I wouldn't > put anything past them. > > One thing you might try is backing up your stores, installing a new non-SBS > server with full W2K and E2K and restoring to that server. > > Avoid SBS like the plague, it is a terrible, terrible product and Microsoft, > in good conscience, should NEVER have released it upon an unsuspecting > public. > > > Exchange is working fine on the server its just that the raid set on > > this dodgy ibm server keeps going critical after a reboot(keep getting > > the runaround from ibm) and we want the customer to purchase a better > > server but there is a lot of mail stored on it and i was just > > wondering how easy/hard would it be to move the mail to another > > server. Also is their any repercussions moving mail from sbs2k to a > > win2k o/s. > > > > Thanks > > > > Damian. > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
