what happens to SPS Areas when upgraded to MOSS 2007?

Hello,

Our organization is heavily using areas and sub areas for business divisions (finance, IT and etc). We are planning to upgrade to MOSS 2007 .I know that SPS Areas no longer exist in MOSS 2007 and therefore they would be chnaged to subsites, but I don't know what is the disadvantage of this change in terms of hirarchy (taxonomy) to us

Any planning article on this

Thanks a lot

Answer this question

what happens to SPS Areas when upgraded to MOSS 2007?

Philli
One place you can look to find the mappings from bucket webs to the new paths is the Upgrade Area Url Mappings list. You can get to it here: http://[portal]/Lists/98d3057cd9024c27b2007643c1/AllItems.aspx. The guid in the url is a hard coded identifier that is used specifically for this hidden list. I've not had any issues in any of the upgrades I've done with Areas "disappearing" - they are simply "relocated" so that the physical path now reflects the logical path. If you have any issues with links pointing to the old bucket web there are techniques to fix this - check out this posting which may help: http://stsadm.blogspot.com/2007/10/apply-upgrade-area-url-mappings.html (just make sure you understand what it's doing before trying to use it).

Dedal

I had the same question and found the following at http://technet2.microsoft.com/Office/en-us/library/b28ba53d-a3e8-440f-9fcb-f592d858894a1033.mspx mfr=true

Changes to areas

Areas have been redesigned to be easier to edit and manage.

Change	Comments
Areas are now subsites	During upgrade, areas are converted to subsites of the portal. The home area becomes the top-level site in the site collection, and the next-level areas become subsites of that site, and so on. This changes the physical hierarchy for the portal to match the logical area hierarchy of the SharePoint Portal Server 2003 portal site, and also affects the URLs, as discussed below.
Portal URLs may have changed	URLs for sites and subsites in Office SharePoint Server 2007 are updated to match the physical hierarchy structure of the portal site. So rather than seeing http://portal_name/c2/area_name, you'll see http://portal_name/area_name or http://portal_name/sites/site_name.

Lucas Cond&#233;

eric,

can you verify if the webtemplate id in your upgrade definition files and new site defintion files is the same as the webtemplate id of your 2003 site definition files.

Thanks

Noel
bjorneb

Shane,

In my only upgrade experience the areas just seem to vanish!

The only references to the areas in the upgrade.log are like:

[SPManager] [DEBUG] [3/3/2007 12:26:25 AM]: [SPContentDatabase Name=SecondOp1_SITE Parent=SPDatabaseServiceInstance] Running 15 of 135 steps
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Begin Initialize()
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: End Initialize()
[SecurityUpgrade2] [3.0.12.2000] [INFO] [3/3/2007 12:26:25 AM]: Security upgrade step 2 : Sites and Webs.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Begin Upgrade()
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: ProcessSiteGroups...
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: ProcessWebAcls...
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Processing web Url=/, Id=c72a886a-5198-4d5f-a3f4-15e096c7dc3e, RootWeb=True, cACE=7
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Push sql command to the stack. Length=3830, Params=47.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Executing 1 sql commands.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Processing web Url=/C0, Id=ef2fc70c-ce2e-4929-84c0-f2b25a390f0e, RootWeb=False, cACE=5
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Push sql command to the stack. Length=2300, Params=30.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Executing 1 sql commands.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Processing web Url=/C0/Certified Partner, Id=8288d36f-15c6-4621-bbb1-8139cd843426, RootWeb=False, cACE=5
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Push sql command to the stack. Length=1014, Params=20.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Executing 1 sql commands.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Processing web Url=/C0/For private, Id=95edcc01-dbcc-49dc-8acd-ae1aa014d1b3, RootWeb=False, cACE=5
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Push sql command to the stack. Length=1014, Params=20.
[SecurityUpgrade2] [3.0.12.2000] [DEBUG] [3/3/2007 12:26:25 AM]: Executing 1 sql commands.

...

But I can't find <site>/C0/ ... <site>/C0/Certified Partner or any other of the areas on the upgraded site or elsewhere in the upgrade.log for that matter!

Any suggestions
kreativ

Thnx!

I felt alone in my frustration!

Do you have any experience in upgrading custom "site templates" mapped to the default site definitions (in my prescan these won't show up)

Erik Bo
Dipesh A.
Hi majidmo,

Did you resolve the problem of these bucket webs on migration eventually

Any follow up findings

Appreciate any responses.

-Jane
smgorden
I don't think this is true. I did an upgrade and c1, c2, .... turned to become sites of their own and were showing up every where. I am thinkin they decided against doing that so the the bookmarks will keep working.

SharePoint Portal 2003 upgrade is a mess because of this. You cannot delete C# sites and have to hide them from navigation.
kmazur
When you upgrade from SPS 2003 to MOSS 2007 the areas are converted to publishing sites. Also, as the article aboves says all of the buckets are removed. If you are not seeing this behavior then something is wrong. I have been involved in 100's of upgrades and I have not seen any issues with these 2 pieces of functionality.

Shane - SharePoint Help
daniel mark

Erik,

Are you using Site Definition or site templates stored in the SharePoint 2003 database.if you are using Site Defintion,you can create the upgrade definition files and upgrade them .I believe the Site Templates stored in the database will migrate over as it is.

Noel
drmcl
Noel,

Thank you for ypur interest!

The SPS2003 is populated with af number of custom site templates stored in one of the default site definitions (STS) and are "globalized" as "GLOBAL_#5" ...

Prescan identifies none of those site templates but in the upgrade.log I get WARNINGS like:

[SPContentDatabaseSequence] [WARNING] [3/3/2007 1_:28:01 AM]: WebTemplate ID 22 (lcid: 1030), provisioned in ContentDatabase SecondOp1_SITE, is missing.

In the upgrade.log I find references to GLOBAL_#1 like:

[SPXmlConfiguration] [DEBUG] [3/3/2007 2:15:22 AM]: Template upgrade: Upgrade XML: <WebTemplate ID="1" LocaleId="*" FromProductVersion="2" BeginFromSchemaVersion="0" EndFromSchemaVersion="0" ToSchemaVersion="2" />

[SPManager] [DEBUG] [3/3/2007 2:15:22 AM]: NeedsUpgrade [Websted for team - %LCID%1030 - %GTID%_GLOBAL_#1 - %TMPLID%STS#0

I find no references to the globalized and widely used GLOBAL_#5 ... 11

Does this information address your question / make any sense
what happens to SPS Areas when upgraded to MOSS 2007?

Answer this question