Oh if only we could have this as a supported solution. Still this makes the side-by-side installation all the more practical. What is the main gain from having “Companyweb” as the address that resolves to WSS v3 vs. the original v2? You don’t gain any new WSS v3 functionality. What you do get is that any of the SBS embedded links such as the main one in RWW now will take users into WSSv3. This is the meat of the matter.
Chad, you are the man!
Companyweb & Sharepoint v3 – Part 5
a.k.a. – Living on the Edge. Just remember, there’s a reason it’s called the bleeding edge . . . Here’s your warning: In this post I am going to explain configuration changes I made to my own internal production environment to get http://companyweb to point to a new WSS v3 site. This configuration is not supported by Microsoft or myself. If you decide to try to replicate these settings in your environment, you are doing so at your own risk.
OK, let’s recap. We’ve talked about the benefits of Sharepoint v3? Check. We’ve talked about planning what we’re going to move, how we’re going to move it, and what we’re going to have to clean up after the move? Check. We’ve talked about prepping our environment so that WSS v3 search works? Check. We’ve talked about installing WSS v3 and accessing it via a common name? Check. Chad has warned everyone that just because he’s crazy enough to implement a non-supported configuration doesn’t me he’s recommending it or supporting it? Check.