Just a little warning for you guys:
stsadm –o uninstall will uninstall SHAREPOINT from your server with NO WARNING.
That is bad. very very very bad.
funny enough, when you type stsadm –help, it doesn’t even list this command.
IF you should happen to accidently type this when, say, trying to uninstall a feature and accidently hitting enter too soon --(Hypothetically speaking of course…) you are pretty much in for a world of hurt.
You will have to re-install sharepoint,reconfigure Central Admin and SSP(s) and then re-attach your content db.
The difficulty here is that your content db will no longer be getting the profile synch b/c it is still associated with the old SSP in the database, even though through the UI, you can see that your web app is correctly associated with the new SSP after reinstall. I haven’t quite figured out how to fix this. Any insight into how to fix the association of a content db to an SSP would be much appreciated.
One amazing thing I did find, however, is that once site was up and running again, workflows seem to continue without a hiccup. I’m guessing this has something to do with the dehydration/rehydration of the workflow when it is waiting for the next step to happen.
Hope none of you will ever run into this!