Things not to do when figuring MOSS out…

So I decided that it wouldn’t be a bad idea to really get at the guts of MOSS and figure out just how PSConfig works and what the different application pools are useful for.

So the first lesson learned of the day is that the web application for Office Server really should never be toyed – if you delete it you might as well just reinstall MOSS all together :)

Second lesson learned of the day, there is no real good way of migrating MOSS from one SQL server to another without rebuilding the server’s MOSS instance and then reattaching the content databases and if you’re lucky, getting the SSP’s in as well.

Any other lessons learned out there that anyone else would like to share?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s