Ok, here it goes:
1. Before we had WSS 2.0. Client wanted to upgrade to WSS 3.0 even if they're in
a SBS 2003 environment we managed to upgrade their Sharepoint site to 3.0
2. We made a backup of WSS 2.0, created a VM of Server 2003 standard, and
installed WSS 2.0, set same settings as the one in SBS.
3. Restored the backup copy of the site to the new server 2003 standard using
stsadm.
4. Installed WSS 3.0 side-by-side with 2.0 in the SBS 2003 server.
5. Did the in-place ugprade of 2.0 in the 2003 standard server to WSS 3.0.
6. Then made a backup of WSS3 in Server 2003.
7. Restored the backup of WSS3 from server 2003 to SBS.
8. Changed Alternate Access Mappings of WSS3 to use http://companyweb
9. Turned off WSS 2.0 in SBS2003.
10. All is working even in RWW.
Then they wanted to upgrade their site so that it utilizes the BLOG template.
1. So we created a new WSS 3 site in SBS server, named: http://server:8888
2. Used Sharepoint Site Migration Manager by Metalogix to migrate all contents
from the http://companyweb site to http://server:8888
3. Once all contents, lists, etc. are migrated over we switched the Alternate
Access Mappings. so from http://server:8888 TO http://companyweb AND from
http://companyweb TO http://server:8888
4. Both sites are accessible, they use the old http://companyweb (now
http://server:8888) as a test site.
Is that clear enough?
So now, we noticed that the search function is not working on the current
http://companyweb site BUT it is WORKING on the http://server:8888 site. Why is
that?