Ok The Guru Needs Help!!!!

I have to say I side with Microsoft on this one. It can't be done without an extraordinary amount of hacking and that is by design. Everything about SBS has been tagged and modified, from the underlying NT Server with it's trusts disabled to the Exchange Server that will only install on the SBS version of NT.

Personally, I don't have anything derogatory to say about Small Business Server. For the small single-server environment for which it was designed, it is a very cost-effective bundle of software. Yeah, it can be a pain (like conflicting with the system partition on Compaq hardware and the limits on database size, etc.) but you get what you pay for.

Speaking of which, the points you're offering is amusing but you're basically making a public solitication for assistance with violating a software license and I don't know how prudent that is... most hackers are a little more discreet.

SBS v4.5 will upgrade to SBS 2000 when it's available and that, in my estimation, would be the proper (and legal) approach.

paul

Well there is no "Cracking" involved, both are legit copies with the proper licenses. The organization expects to grow beyond the limitations of SBS and HAS paid for 2000 server. SO, I want to make this as easy as possible, if that's a crime through me in jail.!!!

I believe if you check the licensing, you'll find that an "upgrade" from SBS to Windows2000 Server requires purchase of the full version of W2K Server rather than the upgrade version. I'm not a big fan of many of Microsoft's licensing provisions, and this is one I'm really not fond of, but I stand by my observation about the implications of what you're trying to do.

It's really not a matter of throwing you in jail - it's a matter of your customer being fined for license violations.

I stand by my observation.

paul

I assume that you have tried to install the w2k in its own dir, and this failed. I also assume that you have this in a domain and or as the PDC with no BDC. You said that you don't care for any of the extra software, just the basic OS and exchange. Hence, here is my recommendation. As far as I know, this is all legal since you own both copies and are replacing, not upgrading the software.
Install nt4 on a separate system as a BDC and promote it to PDC. Make sure that the domain is sync. Hoping that the data files are on a different drive then the OS, delete the part. that has the OS on it using fdisk and a boot floppy. Load the wk2 server, and join it to the nt4 network. Promote it to primary. Remove and uninstall the temp. server. If you then want AD on the w2k system, set it up and install it using the wizard.
If you don't have the data files on a separate part, copy them to a new HDD for temp storage, and copy back when new install is complete. Use CACLS to make a bat file of who has what rights to what dirs, then use it to restore the rights afterwards. (this should retain all rights if done properly).
If your concerned about the file shares, make a backup of the following reg. entrees and restore in the w2k server. HK_L_M\system\controlset001\services\lanmanserver\shares.

In all my limited knowledge, I believe that there are too many places for the w2k server to find the remains of the sbs. If you were to remove all refs from this, you would have tohave a clean install anyhow as this would include most of the os of sbs.
Although this is a very roundabout and extensive way of upgrading your server, I think that this has the most chance of surviving an upgrade from sbs to w2k.
Hope this iswhat your looking for.
-Juan

Seems like your simplest approach would be to Load Win2K on a New server setup a new domain and start fresh. The environment should be small enough that account building shouldn't be a major issue which for the most part would be the only reason to do an "upgrade" rather than start fresh. Since this is a growing company and Win2K is more hardware intensive purchasing a new system is most likely a good option anyway. Backup the data and then move it to the new environment once all data and accounts are moved to your satisfaction, Fdisk and reformat the SBS systems and then bring them back in as backup servers in win2k if they can handle it or demote them to desktop computers and replace with new machines. Big benefit to the domain change ismaking a clean break and no chance of corruption. Doubt you have to worry about changing too many machines configuration since they are on SBS now either.

This question was closed by the author