Home - SharePoint Joel's SharePoint Land

7/2/2009

NZ Community SharePoint Conference 09 Recap

Well done Chandima, Debbie Ireland, and Mark Orange. I am so pleased with the fantastic and up beat crowd here in Wellington. It’s very refreshing. The energy around SharePoint world wide is so up beat.

We opened up the conference with those 3 as MCs and doing the chand and mark show. Most conferences of this size are run by events companies. This one is run by SharePoint geeks, it’s a rich social experience.

Above, @chandimak, Mark Orange, Debbie Ireland – All SharePoint MVPs right before the keynote kickoff.

Michael Sampson handing me a signed copy of his new book “SharePoint Roadmap to Collaboration.” Check it out at http://www.sharepointroadmap.com. The book launched on day one of the conference.

I had a side meeting with Steve Smith around his end user adoption training materials/kit app. It’s really cool. He gave a preview to the crowd here. A sneak peak…

I had 3 presentations on day 1.

Keynote with a modified version of my 10 Steps to Successful SharePoint deployments with a Kiwi slant.
SharePoint Best Practices to Infrastructure Fundamentals and Information Architecture
Large Scale SQL SharePoint Deployments – a SharePoint SQL database focused session on scale and performance

At Day 2 I joined the Ask the Experts Panel. Good group of experts. From left to Right (Mark Orange (missing from photo), @SteveSmithCK @Chandimak, @joeloleson (me), @PaulCulmsee, and @pstork

They had a special treat a sea urchin called Kina. It smelled foul, very fishy, but I downed a big slice of the stuff. None of the other speakers joined me.

The exhibit hall is great. A few companies I hadn’t spend much time with yet. The surf board and smoothies booth is awesome. Haven’t seen that idea anywhere else. Lot of Good SharePoint partners to meet with. Quest is well represented, as is AvePoint, Mimosa, Intergen, K2, and more…

Everyone is having a great time. Tons of good content. Do a twitter search for #NZSPC and you can see what everyone is chatting about…

You can also find a stream of photos out on flickr on the conference.

What about the non conference stuff?

The Speaker dinner was great. Steaks, Fish, and an assortment. Last night a few of us went to the national museum Te Papa and saw a ton of whale and fish skelletons as well as a giant squid. We also went on a little ride and earthquake simulator. After that a few of us speakers ended the night at Macs.

Posted at 6:40 PM by Joel Oleson | Permalink | Email this Post | Comments (0)

6/24/2009

Preparing for Upgrade to 2010 Today - Part 1 Preupgradecheck

I’ve been pretty upgrade focused lately. I was presenting to the Puget Sound User Group this last week and polled the audience and asked how many had installed SP2. A lot of hands went up. I asked how many had run the preupgradecheck and all hands went down.

I’ve been thinking what could people do today with the knowledge of what the upgrade check provides.

stsadm –o preupgradecheck

The preupgradecheck command is read only. It creates a nice XML and HTML report based on the Preupgradecheck.xml files as referenced below. OssPreUpgradeCheck.xml and WssPreUpgradeCheck.xml

I’m including the Pre-Upgrade Check Report inline with some minimal obfuscation of URLs…

This is what it looks like when it succeeds on a SharePoint Server 2007 64 bit Windows Server 2008 box, that has no custom site definitions, but does contain a few custom site templates and custom features.

---------------------------------------------------------------------

SharePoint Products and Technologies Pre-Upgrade Check Report

Start time: Tuesday, June 23, 2009 12:43:04 PM
End time: Tuesday, June 23, 2009 12:43:59 PM

Information Only

Information Only : Search content sources and start addresses

The following is a list of the content sources and start addresses for each shared service provider in the farm.
SSP Name = SharedServices1
Content Sources =
Content source "Local Office SharePoint Server sites" contains a total of 0 items from the following start addresses

http://portal/

This is an informational rule for upgrade planning. For more information about this rule, see KB article 957409 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Informational rule to list the Office Server Search topology information

The Office Server Search topology in this farm consists of the following components:
1 shared service providers.
SSP Name = SharedServices1
Index Server = WORKFLOWS
IndexSize = 614332 bytes
Items In Index = 0
SSP DB Name = WORKFLOWS \ SharedServices1_DB
SSP DB Size = 12910592 bytes
Search DB Name = WORKFLOWS \ SharedServices1_Search_DB
SSP DB Size = 4456448 bytes
This is an informational rule for upgrade planning. For more information about this rule, see KB article 957408 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Servers in the current farm

The following is a list of all the servers that has Sharepoint installed in the current farm. This list does not include dedicated SQL servers.

SERVER1
SERVER2
SERVER3

The preupgrade checker needs to be run on each of these servers in order to get a complete list of issues that might affect upgrade. For more information about this rule, see KB article 954758 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : The components from this farm

This sharepoint software currently running on this farm is 12.0.0.6421. The farm contains the following components:

3 servers
1 web applications
4 content databases, approximately total size = 321847296 bytes
9 Site collections

For more information about this rule, see KB article 954759 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Supported upgrade types

The current farm supports the following upgrade types:

Inplace Upgrade
Content Database Attach

For more information about this rule, see KB article 954760 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Site Definition Information

The following site definitions are either installed on this farm or referenced by the content:

name = STS, language = 1033, template id = 1, count = 8, status = Internal
name = MPS, language = 1033, template id = 2, count = 0, status = Internal
name = CENTRALADMIN, language = 1033, template id = 3, count = 1, status = Internal
name = WIKI, language = 1033, template id = 4, count = 0, status = Internal
name = BLOG, language = 1033, template id = 9, count = 0, status = Internal
name = absence, language = 1033, template id = 75811, count = 1, status = Installed
name = BDR, language = 1033, template id = 7, count = 1, status = Installed
name = BT, language = 1033, template id = 75801, count = 1, status = Installed
name = DR, language = 1033, template id = 75803, count = 1, status = Installed
name = KB, language = 1033, template id = 75806, count = 1, status = Installed
name = OFFILE, language = 1033, template id = 14483, count = 0, status = Installed
name = OSRV, language = 1033, template id = 40, count = 1, status = Installed
name = projchange, language = 1033, template id = 75818, count = 1, status = Installed
name = SPS, language = 1033, template id = 20, count = 0, status = Installed
name = SPSPERS, language = 1033, template id = 21, count = 0, status = Installed
name = SPSMSITE, language = 1033, template id = 22, count = 0, status = Installed
name = SPSTOC, language = 1033, template id = 30, count = 0, status = Installed
name = SPSTOPIC, language = 1033, template id = 31, count = 0, status = Installed
name = SPSNEWS, language = 1033, template id = 32, count = 0, status = Installed
name = CMSPUBLISHING, language = 1033, template id = 39, count = 0, status = Installed
name = BLANKINTERNET, language = 1033, template id = 53, count = 0, status = Installed
name = SPSNHOME, language = 1033, template id = 33, count = 0, status = Installed
name = SPSSITES, language = 1033, template id = 34, count = 1, status = Installed
name = SPSCOMMU, language = 1033, template id = 36, count = 0, status = Installed
name = SPSREPORTCENTER, language = 1033, template id = 38, count = 0, status = Installed
name = SPSPORTAL, language = 1033, template id = 47, count = 0, status = Installed
name = SRCHCEN, language = 1033, template id = 50, count = 0, status = Installed
name = PROFILES, language = 1033, template id = 51, count = 1, status = Installed
name = BLANKINTERNETCONTAINER, language = 1033, template id = 52, count = 0, status = Installed
name = SPSMSITEHOST, language = 1033, template id = 54, count = 1, status = Installed
name = SRCHCENTERLITE, language = 1033, template id = 90, count = 0, status = Installed

JOEL: You can see there are a couple of FAB 40 site templates above.

After upgrading the current farm to the new version of sharepoint, any sites that uses one of the internal site definitions will be upgraded if necessary. Custom site definitions will need to be upgraded using a Upgrade Definition File. For more information about this rule, see KB article 954761 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

JOEL: Note the info on the custom site definition requirement for the upgrade definition file.

Information Only : Language pack information

After upgrading the current farm to the new version of sharepoint, any sites that uses the language packs will not work until the new version of the language packs are installed.The following language packs are installed on this farm:

English (1033), global server language

For more information about this rule, see KB article 954763 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Feature Information

The following features are either installed or referenced by the content

Name = [PublishingStapling], Feature id = [001f4bd7-746d-403b-aa09-a6cc43de7942], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [BasicWebParts], Feature id = [00bfea71-1c5e-4a24-b310-ba51c3eb7a57], Reference count = [7], Scope = [Site], Status = [Installed]
Name = [XmlFormLibrary], Feature id = [00bfea71-1e1d-4562-b56a-f05371bb0115], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [LinksList], Feature id = [00bfea71-2062-426c-90bf-714c59600103], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [workflowProcessList], Feature id = [00bfea71-2d77-4a75-9fca-76516689e21a], Reference count = [18], Scope = [Web], Status = [Installed]
Name = [GridList], Feature id = [00bfea71-3a1d-41d3-a0ee-651d11570120], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [WorkflowHistoryList], Feature id = [00bfea71-4ea5-48d4-a4ad-305cf7030140], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [TeamCollab], Feature id = [00bfea71-4ea5-48d4-a4ad-7ea5c011abe5], Reference count = [18], Scope = [Web], Status = [Installed]
Name = [GanttTasksList], Feature id = [00bfea71-513d-4ca0-96c2-6a47775c0119], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [PictureLibrary], Feature id = [00bfea71-52d4-45b3-b544-b1c71b620109], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [IssuesList], Feature id = [00bfea71-5932-4f9c-ad71-1557e5751100], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [DiscussionsList], Feature id = [00bfea71-6a49-43fa-b535-d15c05500108], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [ContactsList], Feature id = [00bfea71-7e6d-4186-9ba8-c047ac750105], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [TasksList], Feature id = [00bfea71-a83e-497e-9ba0-7a5c597d0107], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [WebPageLibrary], Feature id = [00bfea71-c796-4402-9f2f-0eb9a6e71b18], Reference count = [18], Scope = [Web], Status = [Installed]
Name = [AnnouncementsList], Feature id = [00bfea71-d1ce-42de-9c63-a44004ce0104], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [DataConnectionLibrary], Feature id = [00bfea71-dbd7-4f72-b8cb-da7ac0440130], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [CustomList], Feature id = [00bfea71-de22-43b2-a848-c05709900100], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [DocumentLibrary], Feature id = [00bfea71-e717-4e80-aa17-d0c71b360101], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [SurveysList], Feature id = [00bfea71-eb8a-40b1-80c7-506be7590102], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [EventsList], Feature id = [00bfea71-ec85-4903-972d-ebe475780106], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [DataSourceLibrary], Feature id = [00bfea71-f381-423d-b9d1-da7a54c50110], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [NoCodeWorkflowLibrary], Feature id = [00bfea71-f600-43f6-a895-40c0de7b0117], Reference count = [19], Scope = [Web], Status = [Installed]
Name = [FeaturePushdown], Feature id = [0125140f-7123-4657-b70a-db9aa1f209e5], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ReviewWorkflows], Feature id = [02464c6a-9d07-4f30-ba04-e9035cf54392], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [MySiteQuickLaunch], Feature id = [034947cc-c424-47cd-a8d1-6014f0e36925], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [BizAppsListTemplates], Feature id = [065c78be-5231-477e-a972-14177cc5b3c7], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [OsrvLinks], Feature id = [068f8656-bea6-4d60-a5fa-7f077f8f5c20], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [PremiumWeb], Feature id = [0806d127-06e6-447a-980e-2e90b03101b8], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [OsrvTasks], Feature id = [0b4aad40-406f-425c-bdd9-5894c42cffcb], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [SlideLibrary], Feature id = [0be49fe9-9bc9-409d-abf9-702753bd878d], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [PremiumWebApplication], Feature id = [0ea1c3b6-6ac0-44aa-9f3f-05e8dbe6d70b], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [ContentLightup], Feature id = [0f121a23-c6bc-400f-87e4-e6bbddf6916d], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [MySiteCleanup], Feature id = [0faf7d1b-95b1-4053-b4e2-19fd5c9bbc88], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [OssNavigation], Feature id = [10bdac29-a21a-47d9-9dff-90c7cae1301e], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [SpsSsoLinks], Feature id = [11df38ab-5bbb-4304-9da8-221c5c4100b0], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PageConverters], Feature id = [14173c38-5e2d-4887-8134-60f9df889bad], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [LocalSiteDirectoryControl], Feature id = [14aafd3a-fcb9-4bb7-9ad7-d8e36b663bbd], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [SearchAndProcess], Feature id = [1dbf6063-d809-45ea-9203-d3ba4a64f86d], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [DMContentTypeSettings], Feature id = [1ec2c859-e9cb-4d79-9b2b-ea8df09ede22], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PublishingTimerJobs], Feature id = [20477d83-8bdb-414e-964b-080637f7d99b], Reference count = [4], Scope = [WebApplication], Status = [Installed]
Name = [Publishing], Feature id = [22a9ef51-737b-4ff2-9346-694633fe4416], Reference count = [2], Scope = [Web], Status = [Installed]
Name = [PublishingB2TRHop2SiteFilesUpgrade], Feature id = [24d7018d-bf48-4813-a28d-dbf3dba173b1], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [ReportListTemplate], Feature id = [2510d73f-7109-4ccc-8a1c-314894deeb3a], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [TransMgmtLib], Feature id = [29d85c25-170c-4df9-a641-12db0b9d4130], Reference count = [9], Scope = [Web], Status = [Installed]
Name = [SPSearchFeature], Feature id = [2ac1da39-c101-475c-8601-122bc36e3d67], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [S2SearchAdmin], Feature id = [2b1e4cbf-b5ba-48a4-926a-37100ad77dee], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [WebPartAdderGroups], Feature id = [2ed1c45e-a73b-4779-ae81-1524e4de467a], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [UpgradeOnlyFile], Feature id = [2fa4db13-4109-4a1d-b47c-c7991d4cc934], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [RedirectPageContentTypeBinding], Feature id = [306936fd-9806-4478-80d1-7e397bfa6474], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [GlobalWebParts], Feature id = [319d8f70-eb3a-4b44-9c79-2087a87799d6], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [Analytics], Feature id = [395702f0-184c-46a2-9bb5-0a64b048738c], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ExcelServerSite], Feature id = [3cb475e7-4e87-45eb-a1f3-db96ad7cf313], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [BDR], Feature id = [3f59333f-4ce1-406d-8a97-9ecb0ff0337f], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [BizAppsSiteTemplates], Feature id = [4248e21f-a816-4c88-8cab-79d82201da7b], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [BizAppsCTypes], Feature id = [43f41342-1a37-4372-8ca0-b44d881e4434], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [OSearchEnhancedFeature], Feature id = [4750c984-7721-4feb-be61-c660c6190d43], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [MySiteHost], Feature id = [49571cd1-b6a1-43a3-bf75-955acc79c8d8], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [FeaturePushdownTask], Feature id = [4d0d9bec-5103-4663-b88d-27cfab1029ff], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [BaseWebApplication], Feature id = [4f56f9fa-51a0-420c-b707-63ecbb494db1], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [NavigationProperties], Feature id = [541f5f57-c847-4e16-b59a-b31e90e6f9ea], Reference count = [2], Scope = [Web], Status = [Installed]
Name = [AnalyticsLinks], Feature id = [56dd7fe7-a155-4283-b5e6-6147560601ee], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [BizAppsFields], Feature id = [5a979115-6b71-45a5-9881-cdc872051a69], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [GradualUpgrade], Feature id = [5b1e6e3b-83c2-483b-8500-16a025777ed1], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [PortalLayouts], Feature id = [5f3b0127-2f1d-4cfd-8dd2-85ad1fb00bfc], Reference count = [7], Scope = [Site], Status = [Installed]
Name = [SpellChecking], Feature id = [612d671e-f53d-4701-96da-c3a4ee00fdc5], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SlideLibraryActivation], Feature id = [65d96c6b-649a-4169-bf1d-b96505c60375], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [MySiteLayouts], Feature id = [6928b0e5-5707-46a1-ae16-d6e52522d52b], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [CTypes], Feature id = [695b6570-a48b-4a8e-8ea5-26ea7fc1d162], Reference count = [9], Scope = [Site], Status = [Installed]
Name = [MySite], Feature id = [69cc9662-d373-47fc-9449-f18d11ff732c], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [MySiteNavigation], Feature id = [6adff05c-d581-4c05-a6b9-920f15ec6fd9], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [SignaturesWorkflow], Feature id = [6c09612b-46af-4b2f-8dfc-59185c962a29], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [RecordsManagement], Feature id = [6d127338-5e7d-4391-8f62-a11e43b1d404], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [LegacyDocumentLibrary], Feature id = [6e53dd27-98f2-4ae5-85a0-e9a8ef4aa6df], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [Reporting], Feature id = [7094bd89-2cfe-490a-8c7e-fbace37b4a34], Reference count = [5], Scope = [Site], Status = [Installed]
Name = [SPSDisco], Feature id = [713a65a1-2bc7-4e62-9446-1d0b56a8bf7f], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [IPFSAdminWeb], Feature id = [750b8e49-5213-4816-9fa2-082900c0201a], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjMilestones], Feature id = [75a0fea7-0017-4993-85fe-c37971507bbc], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AVMAbsencesList], Feature id = [75a0fea7-040e-4abb-b94b-32f1e7572840], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AVMListInstances], Feature id = [75a0fea7-056a-445f-9a78-db1b38bb0b74], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [DocumentReviewModules], Feature id = [75a0fea7-07c7-453d-866c-979c401d0105], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ResourceTypesList], Feature id = [75a0fea7-08d9-4a8f-b1cd-953d4f15467f], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CallCenterCustomer], Feature id = [75a0fea7-0cb9-4862-8e76-9f5e149236f5], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [KnowledgeBaseKeywordsList], Feature id = [75a0fea7-12fe-4cad-a1b2-525fa776c07e], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjChangeCRList], Feature id = [75a0fea7-1651-4b91-8cdf-3f24e57526ed], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [DRProvisioningFeature], Feature id = [75a0fea7-24d7-4907-81ec-2d71dd3dfde9], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjProjects], Feature id = [75a0fea7-2791-45a2-896f-e538f91032d8], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [BugList], Feature id = [75a0fea7-2d1e-451a-b445-16bc346d7d8e], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [LendingLibraryTransactionsList], Feature id = [75a0fea7-30ba-45d8-bf12-3c0855491ad1], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ResourcesList], Feature id = [75a0fea7-377d-4b4f-b864-984379ed0f42], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [BugTrackingListInstances], Feature id = [75a0fea7-37d2-484b-b362-dcff1538e2a4], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [HelpDeskTasks], Feature id = [75a0fea7-3b2a-4838-8a0c-57ba864feed3], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [DocumentReviewDiscussionList], Feature id = [75a0fea7-3cc9-4c20-bf74-9bfa9fd5d614], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [BugCategoriesList], Feature id = [75a0fea7-42e8-4527-8313-f63c4c49a7e6], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [SalesOpportunitiesList], Feature id = [75a0fea7-4d56-4479-a469-230a0eb68184], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [RecruitingCandidatesList], Feature id = [75a0fea7-518a-485e-841d-ababd2145e27], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CompProcCompReg], Feature id = [75a0fea7-5797-48cd-958d-805cbf270087], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [LendingLibraryList], Feature id = [75a0fea7-5dd8-40af-b960-12af3053f5ec], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [AssetTrackingAssetsList], Feature id = [75a0fea7-625d-4b31-be9e-24cee53d0d72], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [RecruitingCandidateFeedbackList], Feature id = [75a0fea7-6e3f-4d4a-8f78-245bda567b60], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [HelpDeskSupportFaqList], Feature id = [75a0fea7-70e3-40b1-b395-c06f85d0d158], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [EPPersonalEvents], Feature id = [75a0fea7-7478-44e1-8b39-d600e3f4f53f], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [DocumentReviewDocsForReviewList], Feature id = [75a0fea7-775b-4ae1-bbc6-ad5ef0d22413], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AVMModules], Feature id = [75a0fea7-7851-4350-a082-3b2476621a57], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [RecruitingRequisitionsList], Feature id = [75a0fea7-7afc-4a13-b91a-7dc661f04785], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [KnowledgeBaseListInstances], Feature id = [75a0fea7-7c51-4a75-92c1-cbaccb371622], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AssetTrackingProposalsList], Feature id = [75a0fea7-7ce3-4ba1-84b7-4bd9da4c9468], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [SalesAccountsList], Feature id = [75a0fea7-7f1b-4b63-a41c-2a2a55fa2709], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CallCenterServiceRequestsList], Feature id = [75a0fea7-8464-4a6e-9d51-f370bb34ee9c], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [KBProvisioningFeature], Feature id = [75a0fea7-84d9-447d-b9ec-bc49570874db], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [KnowledgeBaseModules], Feature id = [75a0fea7-85b8-4e88-8a0b-3a04a572e20c], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjChangeModules], Feature id = [75a0fea7-8b9f-489a-a971-497418e43698], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AVMAbsenceTypeList], Feature id = [75a0fea7-8d3c-455d-89d3-4ece8739402d], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [AssetTrackingCategoriesList], Feature id = [75a0fea7-92c2-4fdf-9b21-8cfbb6d3b240], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ProjIssues], Feature id = [75a0fea7-9454-48ab-883d-ede5b98710d6], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ERExpenseFormsList], Feature id = [75a0fea7-9507-49c7-a473-0ce55c18ef89], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [BugTrackingModules], Feature id = [75a0fea7-9d96-4f02-a800-a3512154efcd], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [InventoryTrackingInventoryList], Feature id = [75a0fea7-a64d-4dfa-a39f-d0076127771e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CompProcTasks], Feature id = [75a0fea7-ada5-4d30-a123-330bff54d0be], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [InventoryTrackingTransactionsList], Feature id = [75a0fea7-ada9-4441-893d-39ec3b945c91], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [PostProvisioningFeature], Feature id = [75a0fea7-b0ef-434e-90d6-ce997d970564], Reference count = [5], Scope = [Web], Status = [Installed]
Name = [EPPeopleList], Feature id = [75a0fea7-b4c2-46ca-b4b1-819331cf2e4b], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [AVMResponsibilityAdoptionList], Feature id = [75a0fea7-b5a0-47d5-90e6-4b3205b02278], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjChangeRisksList], Feature id = [75a0fea7-bfc1-42fe-b08b-ae44bca6a536], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ProjTasks], Feature id = [75a0fea7-c256-49cb-bf7f-de124ca9bf13], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [TSAimage], Feature id = [75a0fea7-c54f-46b9-86b1-2e103a8fedba], Reference count = [5], Scope = [Web], Status = [Installed]
Name = [DocumentReviewListInstances], Feature id = [75a0fea7-c671-4696-ac6f-5decfca3173e], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [EPEventsList], Feature id = [75a0fea7-c966-4e74-b74e-8f77e7bae175], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [SalesLeadsList], Feature id = [75a0fea7-ca3c-4d71-9d2c-5efc8e68a5a8], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ProjChangeListInstances], Feature id = [75a0fea7-caef-4454-be97-4bf0e784650a], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [TSATypes], Feature id = [75a0fea7-cd50-401e-af0e-782f3662a299], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [ProjChangeRequestStatusList], Feature id = [75a0fea7-d01e-48b3-ba36-8cbbdfeef1d6], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [KnowledgeBaseKnowledgeBaseList], Feature id = [75a0fea7-d31d-491a-9177-f0e461a81e3f], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [HelpDeskInIssuesList], Feature id = [75a0fea7-d6d3-47bc-95be-1b26b5927180], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [HelpDeskExpertsList], Feature id = [75a0fea7-e63b-4059-8f5a-ce9cbbadad2a], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [EPAnnouncementsList], Feature id = [75a0fea7-ebe9-4501-8897-74c984588afa], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [RecruitingInterviewCalendarList], Feature id = [75a0fea7-f13a-4670-8b69-97e90d05f7c8], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ITTeamBugList], Feature id = [75a0fea7-f780-458c-b53d-441b33a9ac32], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ListPropertyFeature], Feature id = [75a0fea7-fe65-41c3-a965-c5df83fb098b], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [HelpDeskServiceRequestsList], Feature id = [75a0fea7-fe9d-4119-9615-2c2ef22d6fdb], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ReservationsList], Feature id = [75a0fea7-ff19-4b2e-953b-bea234eba14a], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CompProcProjects], Feature id = [75a0fea7-ff47-418f-8bfc-9498b0bc1a85], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [CompProcIssues], Feature id = [75a0fea7-ffa9-4c2d-8b20-88401290692e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [OSSSearchSearchCenterUrlSiteFeature], Feature id = [7ac8cc56-d28e-41f5-ad04-d95109eb987a], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [OSSSearchSearchCenterUrlFeature], Feature id = [7acfcb9d-8e8f-4979-af7e-8aed7e95245e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [ViewFormPagesLockDown], Feature id = [7c637b23-06c4-472d-9a9a-7c175762c5c4], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [MigrationLinks], Feature id = [7fe16263-b3fd-454f-a3e8-ed05fdf2adb6], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ReportCenterCreation], Feature id = [8156ee99-ddfb-47bb-8835-7ae42d40d9b9], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [EnhancedHtmlEditing], Feature id = [81ebc0d6-8fb2-4e3f-b2f8-062640037398], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [TransMgmtFunc], Feature id = [82e2ea42-39e2-4b27-8631-ed54c1cfc491], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PremiumSite], Feature id = [8581a8a7-cf16-4770-ac54-260265ddb0b2], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [MySiteBlog], Feature id = [863da2ac-3873-4930-8498-752886210911], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [Navigation], Feature id = [89e0306d-453b-4ec5-8d68-42067cdbf98e], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [MasterSiteDirectoryControl], Feature id = [8a663fe0-9d9c-45c7-8297-66365ad50427], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [WikiWelcome], Feature id = [8c6a6980-c3d9-440e-944c-77f93bc65a7e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [LocalSiteDirectoryMetaData], Feature id = [8f15b342-80b1-4508-8641-0751e2b55ca6], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [S2SiteAdmin], Feature id = [90cd055f-f21f-42c5-b3fe-bb67173583d4], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [SkuUpgradeLinks], Feature id = [937f97e9-d7b4-473d-af17-b03951b2c66b], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PublishingWeb], Feature id = [94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb], Reference count = [2], Scope = [Web], Status = [Installed]
Name = [BaseSiteStapling], Feature id = [97a2485f-ef4b-401f-9167-fa4fe177c6f6], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [BDCAdminUILinks], Feature id = [99ee0928-7342-4739-865d-35b61ea4eaf0], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [BaseWeb], Feature id = [99fe402e-89a0-45aa-9163-85342e865dc8], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [Hold], Feature id = [9e56487c-795a-4077-9425-54a1ecb84282], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [IPFSWebFeatures], Feature id = [a0e5a010-1329-49d4-9e09-f280cdbed37d], Reference count = [7], Scope = [Web], Status = [Installed]
Name = [ipfsAdminLinks], Feature id = [a10b6aa4-135d-4598-88d1-8d4ff5691d13], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SitesList], Feature id = [a311bf68-c990-4da3-89b3-88989a3d7721], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [PublishingPrerequisites], Feature id = [a392da98-270b-4e85-9769-04c0fde267aa], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [PremiumSiteStapling], Feature id = [a573867a-37ca-49dc-86b0-7d033a7ed2c8], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PublishingResources], Feature id = [aebc918d-b20f-4a11-a1db-9ed84d79c87e], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [BulkWorkflow], Feature id = [aeef8777-70c0-429f-8a13-f12db47a6d47], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ProfileSynch], Feature id = [af847aa9-beb6-41d4-8306-78e41af9ce25], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [BaseSite], Feature id = [b21b090c-c796-4b0f-ac0f-7ef1659c20ae], Reference count = [5], Scope = [Site], Status = [Installed]
Name = [OSearchBasicFeature], Feature id = [bc29e863-ae07-4674-bd83-2c6d0aa5623f], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [SRPProfileAdmin], Feature id = [c43a587e-195b-4d29-aba8-ebb22b48eb1a], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ReportCenterSampleData], Feature id = [c5d947d6-b0a2-4e07-9929-8e54f5a9fff9], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [TranslationWorkflow], Feature id = [c6561405-ea03-40a9-a57f-f25472942a22], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [ExpirationWorkflow], Feature id = [c85e5759-f323-4efb-b548-443d2216efb5], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [IPFSSiteFeatures], Feature id = [c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5], Reference count = [7], Scope = [Site], Status = [Installed]
Name = [OSearchCentralAdminLinks], Feature id = [c922c106-7d0a-4377-a668-7f13d52cb80f], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [OffWFCommon], Feature id = [c9c9515d-e4e2-4001-9050-74f980f93160], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [DeploymentLinks], Feature id = [ca2543e6-29a1-40c1-bba9-bd8510a4c17b], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [Fields], Feature id = [ca7bd552-10b1-4563-85b9-5ed1d39c962a], Reference count = [9], Scope = [Site], Status = [Installed]
Name = [DataConnectionLibraryStapling], Feature id = [cdfa39c6-6413-4508-bccf-bf30368472b3], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [AddDashboard], Feature id = [d250636f-0a26-4019-8425-a5232d592c09], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [PublishingLayouts], Feature id = [d3f51be2-38a8-4e44-ba84-940d35be1566], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [BulkWorkflowTimerJob], Feature id = [d992aeca-3802-483a-ab40-6c9376300b61], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [SearchServerWizardFeature], Feature id = [e09cefae-2ada-4a1d-aee6-8a8398215905], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [ExcelServerWebApplication], Feature id = [e15ed6d2-4af1-4361-89d3-2acf8cd485de], Reference count = [3], Scope = [WebApplication], Status = [Installed]
Name = [ExcelServer], Feature id = [e4e6a041-bc5b-45cb-beab-885a27079f74], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [RelatedLinksScopeSettingsLink], Feature id = [e8734bb6-be8e-48a1-b036-5a40ff0b8a81], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [LocalSiteDirectorySettingsLink], Feature id = [e978b1a6-8de7-49d0-8600-09a250354e14], Reference count = [6], Scope = [Site], Status = [Installed]
Name = [SearchWebParts], Feature id = [eaf6a128-0482-4f71-9a2f-b1c650680e77], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [OSearchPortalAdminLinks], Feature id = [edf48246-e4ee-4638-9eed-ef3d0aee7597], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [StapledWorkflows], Feature id = [ee21b29b-b0d0-42c6-baff-c97fd91786e6], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [UserMigrator], Feature id = [f0deabbb-b0f6-46ba-8e16-ff3b44461aeb], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SharedServices], Feature id = [f324259d-393d-4305-aa48-36e8d9a7a0d6], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [MobilityRedirect], Feature id = [f41cc668-37e5-4743-b4a8-74d1db3fd8a4], Reference count = [14], Scope = [Web], Status = [Installed]
Name = [PublishingSite], Feature id = [f6924d36-2fa8-4f0b-b16d-06b7250180fa], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [ListTargeting], Feature id = [fc33ba3b-7919-4d7e-b791-c6aeccf8f851], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [OSearchSRPAdminLinks], Feature id = [fcd4c704-ed7a-42fb-ab30-2bb0ab6494c8], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [PublishingB2TRSiteFilesUpgrade], Feature id = [fd3dd145-e35e-4871-9a6d-bf17f28a1c19], Reference count = [0], Scope = [Site], Status = [Installed]
Name = [IssueTrackingWorkflow], Feature id = [fde5d850-671e-4143-950a-87b473922dc7], Reference count = [5], Scope = [Site], Status = [Installed]
Name = [S2BaseSiteStapling], Feature id = [fea264c1-79e3-4cad-b60b-fa9cc3522cac], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SiteSettings], Feature id = [fead7313-4b9e-4632-80a2-98a2a2d83297], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ContentTypeSettings], Feature id = [fead7313-4b9e-4632-80a2-ff00a2d83297], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [AdminLinks], Feature id = [fead7313-ae6d-45dd-8260-13b563cb4c71], Reference count = [1], Scope = [Web], Status = [Installed]

JOEL: This feature list is very important. In the future if you get any missing feature errors, you’ll want to refer back to this list with named features.

Please install each of the missing features. Otherwise, the content using these features will not function properly. For more information about this rule, see KB article 954762 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Alternate Access Mapping Url(s) within the current environment that should be considered when upgrading.

The following Alternate Access Mapping Url(s) were found in the existing environment:

name = [Central Administration], zone = [Default], public Url = http://portal:333/, internal Url = http://portal:333/
name = [SharePoint - 80], zone = [Default], public Url = http://sharepoint.microsoft.com:80/, internal Url = http://sharepoint/

For more information about this rule, see KB article 954764 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Lists and Libraries

http://workflows:333/HelpFold [5804 Items]

JOEL: This is great info. Obviously this is one reason why you might run this report more often! Knowing your large lists and managing them. The SPDiag tool is another one you might use to help identify large lists.

For more information about this rule, see KB article 956201 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Customized list views that will not be upgraded.

A list view using custom Collaborative Application Markup Language (CAML), a list view not associated with a Feature, or a list view associated with a custom Feature, will not be upgraded to the new XSLT-based list view. A list view that is not upgraded will still render properly in Windows SharePoint Services 4.0, but it will not inherit any benefits of the new XSLT-based list view, such as SharePoint Designer customization support, conditional formatting and improved developer experience with XSLT standard-based language support. The following list views will not be upgraded:

e9afb583-078b-4a12-9fb9-5f434028d575-----sites/templates/customdocreview/Lists/Tasks/RssView.aspx(RssView)
d4e70223-969b-4330-9dc3-a07ed7abce24-----sites/templates/customdocreview/Lists/Tasks/AllItems.aspx(All Tasks)
942f49ca-3003-4a9b-8096-e4c03148582d-----sites/templates/customdocreview/Documents/Forms/Combine.aspx(Merge Documents)
2fd53f14-8dba-4d16-b314-ffbe5cb641f4-----sites/templates/customdocreview/Lists/Tasks/active.aspx(Active Tasks)
230d45c9-cc7e-4ddd-ac3c-410350a62259-----sites/templates/customdocreview/Lists/Tasks/byowner.aspx(By Assigned To)
2e067eb5-7fc8-4889-8396-7ece3152016e-----sites/templates/customdocreview/Documents/Forms/repair.aspx(Relink Documents)
420fa06e-809a-446b-bb62-a1073f77d7a5-----sites/templates/customdocreview/Lists/Reviewers/AllItems.aspx(All Items)
73bef784-d288-41f3-b828-4acb8ac5f1f1-----sites/templates/customdocreview/Lists/Products/AllItems.aspx(All Items)
94c047f5-5eaa-4304-a898-eec60c2341f1-----sites/templates/customdocreview/Lists/Tasks/MyItems.aspx(My Tasks)
2fd038ec-2568-4eb6-9104-417c0b9a10a2-----sites/templates/customdocreview/Documents/Forms/WebFldr.aspx(Explorer View)
bfe0e9e8-8d5f-429a-a726-73a0563f3ca8-----sites/templates/customdocreview/Lists/Tasks/MyGrTsks.aspx(By My Groups)
adcb52b7-aabf-4389-ae1c-96e0a46c7a30-----sites/templates/customdocreview/_catalogs/masterpage/Forms/AllItems.aspx(All Master Pages)
d41719b2-1217-4dd0-8faa-01de8e36dc2e-----sites/templates/customdocreview/Lists/Durations/AllItems.aspx(All Items)
0a37d35b-3573-4be1-8655-bd4903eee9c5-----sites/templates/customdocreview/Lists/Workflow History/AllItems.aspx(All History)
9fa96eff-8a78-46cf-bdbc-6f59de3cf952-----sites/templates/customdocreview/Lists/Tasks/duetoday.aspx(Due Today)

It is highly recommended that you manually upgrade all custom list views to the new XSLT-based list views. The new XSLT-based list view is going to be the default view used in Windows SharePoint Services 4.0, replacing the existing list view in Windows SharePoint Services 3.0. For more information about this rule, see KB article 956450 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Customized field types that will not be upgraded.

A field type using custom Collaborative Application Markup Language (CAML) in itsRenderPattern element will not be upgraded as an XSLT-based field type. Fields based on this custom field type will be rendered without any custom formatting in Windows SharePoint Services 4.0. The following field types will not be upgraded:

HoldsField(Hold Status)
HoldStatusField(Hold Status)
HTML(Publishing HTML)
Image(Publishing Image)
Link(Publishing Hyperlink)
SummaryLinks(SummaryLinks)
LayoutVariationsField(Variations)
ContentTypeIdFieldType(Content Type ID)
BusinessData(Business data)
TargetTo(Audience Targeting)

It is highly recommended that you manually upgrade all custom field types to the new XSLT-based field types in order to have full rendering and customization support. For more information about this rule, see KB article 956451 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Modified authorized types for workflow in web.config

Web.config file(s) on this server contain modified authorized types for workflow. Upgrade will replace these file with new versions, and all modifications will be lost. Declarative workflows that use added authorized types will fail. Authorized types that were manually disabled will be enabled. The following files will be replaced:
C:\inetpub\wwwroot\wss\VirtualDirectories\8080\web.config
The following lines have been removed:
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.Runtime" TypeName="CorrelationToken" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Guid" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="DateTime" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Boolean" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Double" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="String" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="Hashtable" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="ArrayList" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Diagnostics" TypeName="DebuggableAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="CompilationRelaxationsAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="RuntimeCompatibilityAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Int32" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="TimeSpan" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.ObjectModel" TypeName="Collection`1" Authorized="True" />
The following lines have been added:
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
It is highly recommended that you track modifications in these files and reapply them after upgrade. For more information about this rule, see KB article 965449 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Informational rule to list the Windows SharePoint Services Search topology information

The Windows SharePoint Services Search topology in this farm consists of the following components:
1 search service instances
Search server:
Name = PORTAL
Index Size = 0 bytes
No search database
Content Databases:
This is an informational rule for upgrade planning. For more information about this rule, see KB article 957407 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

--------------------------------------------------------------------------

Here’s a Failed PreUpgradeScan

SharePoint Products and Technologies Pre-Upgrade Check Report

Start time: Tuesday, June 23, 2009 11:52:12 AM
End time: Tuesday, June 23, 2009 11:53:46 AM

Information Only

Information Only : Search content sources and start addresses

The following is a list of the content sources and start addresses for each shared service provider in the farm.
SSP Name = SharedServices
Content Sources =
Content source "Local Office SharePoint Server sites" contains a total of 9 items from the following start addresses

This is an informational rule for upgrade planning. For more information about this rule, see KB article 957409 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Informational rule to list the Office Server Search topology information

The Office Server Search topology in this farm consists of the following components:
1 shared service providers.
SSP Name = SharedServices
Index Server = HOME
IndexSize = 4716700 bytes
Items In Index = 20
SSP DB Name = home \ SharedServices_DB
SSP DB Size = 11730944 bytes
Search DB Name = home \ SharedServices_Search_DB
SSP DB Size = 134348800 bytes
This is an informational rule for upgrade planning. For more information about this rule, see KB article 957408 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Servers in the current farm

The following is a list of all the servers that has Sharepoint installed in the current farm. This list does not include dedicated SQL servers.

home

Information Only : The components from this farm

This sharepoint software currently running on this farm is 12.0.0.6421. The farm contains the following components:

1 servers
3 web applications
4 content databases, approximately total size = 9161015296 bytes
11 Site collections

For more information about this rule, see KB article 954759 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Supported upgrade types

The current farm supports the following upgrade types:

Inplace Upgrade
Content Database Attach

For more information about this rule, see KB article 954760 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Site Definition Information

The following site definitions are either installed on this farm or referenced by the content:

name = STS, language = 1033, template id = 1, count = 6, status = Internal
name = MPS, language = 1033, template id = 2, count = 0, status = Internal
name = CENTRALADMIN, language = 1033, template id = 3, count = 1, status = Internal
name = WIKI, language = 1033, template id = 4, count = 0, status = Internal
name = BLOG, language = 1033, template id = 9, count = 0, status = Internal
name = OSRV, language = 1033, template id = 40, count = 1, status = Installed
name = SRCHCENTERLITE, language = 1033, template id = 90, count = 2, status = Installed
name = Unknown, language = 1033, template id = 21, count = 1, status = Missing

JOEL: Note the status of Missing for the unknown feature. This section is a failure. (I added the red text)

Please install the missing site definitions in order for the content to be displayed and upgraded correctly. After upgrading the current farm to the new version of sharepoint, any sites that uses one of the internal site definitions will be upgraded if necessary. Custom site definitions will need to be upgraded using a Upgrade Definition File. For more information about this rule, see KB article 954761 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Language pack information

English (1033), global server language

For more information about this rule, see KB article 954763 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Feature Information

The following features are either installed or referenced by the content

Name = [BasicWebParts], Feature id = [00bfea71-1c5e-4a24-b310-ba51c3eb7a57], Reference count = [9], Scope = [Site], Status = [Installed]
Name = [XmlFormLibrary], Feature id = [00bfea71-1e1d-4562-b56a-f05371bb0115], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [LinksList], Feature id = [00bfea71-2062-426c-90bf-714c59600103], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [workflowProcessList], Feature id = [00bfea71-2d77-4a75-9fca-76516689e21a], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [GridList], Feature id = [00bfea71-3a1d-41d3-a0ee-651d11570120], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [WorkflowHistoryList], Feature id = [00bfea71-4ea5-48d4-a4ad-305cf7030140], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [TeamCollab], Feature id = [00bfea71-4ea5-48d4-a4ad-7ea5c011abe5], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [GanttTasksList], Feature id = [00bfea71-513d-4ca0-96c2-6a47775c0119], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [PictureLibrary], Feature id = [00bfea71-52d4-45b3-b544-b1c71b620109], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [IssuesList], Feature id = [00bfea71-5932-4f9c-ad71-1557e5751100], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [DiscussionsList], Feature id = [00bfea71-6a49-43fa-b535-d15c05500108], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [ContactsList], Feature id = [00bfea71-7e6d-4186-9ba8-c047ac750105], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [TasksList], Feature id = [00bfea71-a83e-497e-9ba0-7a5c597d0107], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [WebPageLibrary], Feature id = [00bfea71-c796-4402-9f2f-0eb9a6e71b18], Reference count = [10], Scope = [Web], Status = [Installed]
Name = [AnnouncementsList], Feature id = [00bfea71-d1ce-42de-9c63-a44004ce0104], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [CustomList], Feature id = [00bfea71-de22-43b2-a848-c05709900100], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [DocumentLibrary], Feature id = [00bfea71-e717-4e80-aa17-d0c71b360101], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [SurveysList], Feature id = [00bfea71-eb8a-40b1-80c7-506be7590102], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [EventsList], Feature id = [00bfea71-ec85-4903-972d-ebe475780106], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [DataSourceLibrary], Feature id = [00bfea71-f381-423d-b9d1-da7a54c50110], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [NoCodeWorkflowLibrary], Feature id = [00bfea71-f600-43f6-a895-40c0de7b0117], Reference count = [11], Scope = [Web], Status = [Installed]
Name = [OsrvLinks], Feature id = [068f8656-bea6-4d60-a5fa-7f077f8f5c20], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [OsrvTasks], Feature id = [0b4aad40-406f-425c-bdd9-5894c42cffcb], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [ContentLightup], Feature id = [0f121a23-c6bc-400f-87e4-e6bbddf6916d], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [OssNavigation], Feature id = [10bdac29-a21a-47d9-9dff-90c7cae1301e], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [SPSearchFeature], Feature id = [2ac1da39-c101-475c-8601-122bc36e3d67], Reference count = [2], Scope = [WebApplication], Status = [Installed]
Name = [S2SearchAdmin], Feature id = [2b1e4cbf-b5ba-48a4-926a-37100ad77dee], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [Analytics], Feature id = [395702f0-184c-46a2-9bb5-0a64b048738c], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [OSearchEnhancedFeature], Feature id = [4750c984-7721-4feb-be61-c660c6190d43], Reference count = [2], Scope = [WebApplication], Status = [Installed]
Name = [AnalyticsLinks], Feature id = [56dd7fe7-a155-4283-b5e6-6147560601ee], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [CTypes], Feature id = [695b6570-a48b-4a8e-8ea5-26ea7fc1d162], Reference count = [11], Scope = [Site], Status = [Installed]
Name = [OSSSearchSearchCenterUrlSiteFeature], Feature id = [7ac8cc56-d28e-41f5-ad04-d95109eb987a], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [OSSSearchSearchCenterUrlFeature], Feature id = [7acfcb9d-8e8f-4979-af7e-8aed7e95245e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [WikiWelcome], Feature id = [8c6a6980-c3d9-440e-944c-77f93bc65a7e], Reference count = [0], Scope = [Web], Status = [Installed]
Name = [S2SiteAdmin], Feature id = [90cd055f-f21f-42c5-b3fe-bb67173583d4], Reference count = [2], Scope = [Web], Status = [Installed]
Name = [OSearchBasicFeature], Feature id = [bc29e863-ae07-4674-bd83-2c6d0aa5623f], Reference count = [2], Scope = [WebApplication], Status = [Installed]
Name = [OSearchCentralAdminLinks], Feature id = [c922c106-7d0a-4377-a668-7f13d52cb80f], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [Fields], Feature id = [ca7bd552-10b1-4563-85b9-5ed1d39c962a], Reference count = [11], Scope = [Site], Status = [Installed]
Name = [SearchServerWizardFeature], Feature id = [e09cefae-2ada-4a1d-aee6-8a8398215905], Reference count = [1], Scope = [Site], Status = [Installed]
Name = [SearchWebParts], Feature id = [eaf6a128-0482-4f71-9a2f-b1c650680e77], Reference count = [4], Scope = [Site], Status = [Installed]
Name = [OSearchPortalAdminLinks], Feature id = [edf48246-e4ee-4638-9eed-ef3d0aee7597], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SharedServices], Feature id = [f324259d-393d-4305-aa48-36e8d9a7a0d6], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [MobilityRedirect], Feature id = [f41cc668-37e5-4743-b4a8-74d1db3fd8a4], Reference count = [2], Scope = [Web], Status = [Installed]
Name = [OSearchSRPAdminLinks], Feature id = [fcd4c704-ed7a-42fb-ab30-2bb0ab6494c8], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [IssueTrackingWorkflow], Feature id = [fde5d850-671e-4143-950a-87b473922dc7], Reference count = [2], Scope = [Site], Status = [Installed]
Name = [S2BaseSiteStapling], Feature id = [fea264c1-79e3-4cad-b60b-fa9cc3522cac], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [SiteSettings], Feature id = [fead7313-4b9e-4632-80a2-98a2a2d83297], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [ContentTypeSettings], Feature id = [fead7313-4b9e-4632-80a2-ff00a2d83297], Reference count = [1], Scope = [Farm], Status = [Installed]
Name = [AdminLinks], Feature id = [fead7313-ae6d-45dd-8260-13b563cb4c71], Reference count = [1], Scope = [Web], Status = [Installed]
Name = [Unknown], Feature id = [e978b1a6-8de7-49d0-8600-09a250354e14], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [29d85c25-170c-4df9-a641-12db0b9d4130], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [065c78be-5231-477e-a972-14177cc5b3c7], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [2ed1c45e-a73b-4779-ae81-1524e4de467a], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [8581a8a7-cf16-4770-ac54-260265ddb0b2], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [0806d127-06e6-447a-980e-2e90b03101b8], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [2510d73f-7109-4ccc-8a1c-314894deeb3a], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [c85e5759-f323-4efb-b548-443d2216efb5], Reference count = [6], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [6c09612b-46af-4b2f-8dfc-59185c962a29], Reference count = [6], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [e8734bb6-be8e-48a1-b036-5a40ff0b8a81], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [0be49fe9-9bc9-409d-abf9-702753bd878d], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [c9c9515d-e4e2-4001-9050-74f980f93160], Reference count = [6], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [4248e21f-a816-4c88-8cab-79d82201da7b], Reference count = [2], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [b21b090c-c796-4b0f-ac0f-7ef1659c20ae], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [99fe402e-89a0-45aa-9163-85342e865dc8], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [5f3b0127-2f1d-4cfd-8dd2-85ad1fb00bfc], Reference count = [2], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [43f41342-1a37-4372-8ca0-b44d881e4434], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [5a979115-6b71-45a5-9881-cdc872051a69], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [14aafd3a-fcb9-4bb7-9ad7-d8e36b663bbd], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [00bfea71-dbd7-4f72-b8cb-da7ac0440130], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [3cb475e7-4e87-45eb-a1f3-db96ad7cf313], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [02464c6a-9d07-4f30-ba04-e9035cf54392], Reference count = [6], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [c6561405-ea03-40a9-a57f-f25472942a22], Reference count = [6], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [a0e5a010-1329-49d4-9e09-f280cdbed37d], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [7094bd89-2cfe-490a-8c7e-fbace37b4a34], Reference count = [5], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [034947cc-c424-47cd-a8d1-6014f0e36925], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [6adff05c-d581-4c05-a6b9-920f15ec6fd9], Reference count = [1], Scope = [Web], Status = [Missing]
Name = [Unknown], Feature id = [6928b0e5-5707-46a1-ae16-d6e52522d52b], Reference count = [1], Scope = [Web], Status = [Missing]

[JOEL: This has a lot of missing Features. Apparently this may have came from an SPS 2003 or MOSS db being attached to a WSS farm. With the preupgradescan being ran against a WSS 3.0 SP2 plus Search Server express.

Robert Bogue has a decent list of the MOSS features with GUIDS. Searching for ‘6adff05c-d581-4c05-a6b9-920f15ec6fd9’ from Google or Bing results in a ‘6adff05c-d581-4c05-a6b9-920f15ec6fd9, MySiteNavigation’

The idea is you need to track down missing features that are referenced onto the farm.

This section is an obvious failure as well.]

Information Only : Alternate Access Mapping Url(s) within the current environment that should be considered when upgrading.

The following Alternate Access Mapping Url(s) were found in the existing environment:

name = [Central Administration], zone = [Default], public Url = http://homesvr:34585, internal Url = http://homesvr:34585
name = [SharePoint - home80], zone = [Default], public Url = http://home, internal Url = http://home
name = [SharePoint - home80], zone = [Intranet], public Url = http://server, internal Url = http://server
name = [SharePoint - home80], zone = [Internet], public Url = http://homesvr:30000, internal Url = http://homesvr:30000
name = [SharePoint - search.perktime.org80], zone = [Default], public Url = http://search.perktime.org, internal Url = http://search.perktime.org

For more information about this rule, see KB article 954764 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Customized list views that will not be upgraded.

03555bfc-8ea5-4b12-aeb0-298d75f5afba-----Lists/2008 BDay/Allitemsg.aspx(All Items)

Information Only : Modified authorized types for workflow in web.config

Web.config file(s) on this server contain modified authorized types for workflow. Upgrade will replace these file with new versions, and all modifications will be lost. Declarative workflows that use added authorized types will fail. Authorized types that were manually disabled will be enabled. The following files will be replaced:
C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config
The following lines have been removed:
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.Runtime" TypeName="CorrelationToken" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Guid" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="DateTime" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Boolean" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Double" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="String" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="Hashtable" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="ArrayList" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Diagnostics" TypeName="DebuggableAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="CompilationRelaxationsAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="RuntimeCompatibilityAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Int32" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="TimeSpan" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.ObjectModel" TypeName="Collection`1" Authorized="True" />
The following lines have been added:
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
It is highly recommended that you track modifications in these files and reapply them after upgrade. For more information about this rule, see KB article 965449 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Information Only : Informational rule to list the Windows SharePoint Services Search topology information

The Windows SharePoint Services Search topology in this farm consists of the following components:
1 search service instances
Search server:
Name = home
Index Size = 39319432 bytes
WSS Search DB Name = home \ WSS_Search_home
WSS Search DB Size = 118947840 bytes
Content Databases:

home \ HOMEWEB1_SITE_Pair
home \ STS_NAME_1_Pair
home \ SharePoint_AdminContent_a6e6fabd-8bbc-482b-a596-9459367dc671

This is an informational rule for upgrade planning. For more information about this rule, see KB article 957407 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

Failed

Failed : This server machine in the farm does not have Windows Server 2008 or higher 64 bit edition installed.

Upgrading to Windows SharePoint Services 4.0 requires Windows Server 2008 or higher 64 bit edition.
Please upgrade the server machines in your farm to Windows Server 2008 64 bit edition, or create a new farm and attach the content from this farm. For more information about this rule, see KB article 954770 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

[Joel: Yep, the box needs to be 64 bit prior and Windows Server 2008 to upgrade. This is a failure. But remember we can run this command as often as we like as we correct our issues.

I’ll plan to discuss more about the usefulness of this report in a follow up in the continuing series on upgrade. ]

<update> Found a blog that includes a tool Gilham Consulting - on Removing Missing or Failed Features"To overcome this problem I have written a tool which allows to identify all features used in a site collection which are missing on the server: WssAnalyzeFeatures."

I hope this helps...

</update>

Posted at 5:48 PM by Joel Oleson | Permalink | Email this Post | Comments (6)

6/22/2009

Are you following the Iran Cyberwar? You can help every voice be heard and protect lives!

There is a revolution going on, on twitter right now!

I have been following the efforts on twitter to see that the peoples votes are counted. I personally haven’t gotten too involved in the various candidates. I do want to support the efforts that every vote is counted. With 17+ deaths for people that are simply wanting for their voice to be heard in non violence. I feel bad.

Security forces have attempted to prevent the flow of information by blocking cell phone, text messaging, email and web sites

What can you do to help those trying to have a voice?

If you set your current time zone on twitter to Tehran it will help obfuscate to help make it harder to track down the people who are twittering from Iran.

There are a bunch of good tips on Boing Boing in Cyberwar guide for Iran elections. Learn how to actually help the protesters…

I know I had tracked down some interesting people to follow on what’s going on , *Sorry, my bad* so this guidance is very important.

I’ve changed my twitter profile, as simple as that is. I hope it helps.

Amnesty International suggests you can also send emails to: info_leader@leader.ir to let them know your thoughts on what’s going on.

I’m a big fan of the student behind http://tehranbureau.com/iran-updates/

The updates are excellent and really makes me feel like I’m right there! The U.S. or someone needs to get this guy asylum or a visa!

Posted at 2:35 PM by Joel Oleson | Permalink | Email this Post | Comments (15)

6/18/2009

Could it really be? WebTrends for SharePoint!

I’ve been following WebTrends since the mid 90s. I know there are some good competitors out there these days. But I’ve been trying to get them to pay attention to SharePoint for some time. Just recently they posted an article/whitepaper on WebTrends for SharePoint that peaked my interest. It’s apparently a solution brief on using WebTrends with SharePoint.

“The Webtrends for SharePoint tags directly interact with the SharePoint Portal template structure, enabling rich data collection and analysis. Webtrends Analytics adds the depth of measurement and comprehensive reporting needed to identify the areas that are working and those that require refinements. Webtrends for SharePoint tracks SharePoint pages via a JavaScript tag that executes upon page load. It accumulates the parts of the SharePoint page into a quantifiable activity. The following key reports are available.”

So aparently WebTrends adds a bot in the SharePoint template that tracks the information that it needs.

Here are some of the Unique SharePoint Reports:

WebParts Viewed
Breadcrumbs Report
Document Actions
Activity by User
User Specific Document Action

They do call out some requirements. I’m not sure why they say Intranet. Seems this would also be useful for Internet sites:
• An existing or planned Webtrends Analytics implementation using Webtrends Professional Services.
• Minimum version of Microsoft Office SharePoint Services (MOSS) 2007. This offering is not available for MOSS version 2003 or prior.
• The recommended environment is an Intranet-based Microsoft Office SharePoint 2007 implementation using the standard Master templates and themes
• Webtrends SmartSource Data Collector (SDC) data collection method

Here’s the PDF again if you missed it.

Let me put out a disclaimer that I’m not associated with Webtrends or getting paid by them. I’m just excited to see them doing something. I still think the Nintex Reporting 2008 will give you much more detail around SharePoint as it is designed specially for it. The reporting in Quest Site Administrator, the company I work for is a good start at collecting information and includes 30 reports, but requires some extra effort to gather and report on what you’re looking for. I’d actually think that’s the case with nearly all of these products. It’s going to take some effort to gather what you’re interested in.

Posted at 12:00 PM by Joel Oleson | Permalink | Email this Post | Comments (14)

6/16/2009

STSADM Evolution

I like the STSADM Silverlight viewer, but the usefulness is limited by the scrolling you have to do. They need to all a button so we can take it full screen or stretch the corners. On my screen resolution, the little app is a small little box. I hope they don’t mind if I show you some screenshots of the tool and comment on the categories, which are great! I do find a lot of usefulness in the information, but the format keeps you from being able to fully explore the commands and what they do. Don’t be afraid to click around… I think it was the third time using this, that I tried clicking on the commands. I don’t remember it popping up the first time.

I refer to both the WSS 3.0 STSADM Technical reference and SharePoint Server 2007 STSADM Technical Reference. You can get the reference for the commands in the article “Index of STSADM operations.” (remember there are WSS and MOSS references, but the MOSS one is comprehensive)”

View All

Not in UI

WSS

MOSS 2007 (NOT in UI)

Ok, so what is not in the UI. The backup command? Well ok backup a site collection is. The VSS writer definitely isn’t in the UI. Adding content db? That’s in the UI, but adding wppacks aren’t. Removing a solution you can do through the UI. Right? Some of these commands are in the UI, hmmm. You can’t add it in the UI, but you can definitely deploy it and retract it. Getting and setting ports is definitely not in the UI, you can do it in IIS, but it’s much better to do it via stsadm based on past experience. Import and export are available to some extent in SharePoint designer with limitations. You can create the SSP from the UI and from psconfig you can create the admin vs. Maybe it’s not all that easy to find. :)

New in SP1

WSS: Left MOSS: Right

Rename site is a command for the hostname site collections. (Rare mostly only used with hosters.) TZ is a time zone command that was important when the servers and timer jobs got off back when we had leap seconds and weird stuff going on. TZmove is rarely if ever used these days.

New in SP2

Enumallwebs that’s a nice new command in SP2. Guess we could build a nice XML tree of our environment with that. Preupgradecheck. This is the future baby. Love this command. Love the reporting. Still waiting to do a full length report on that command and its awesomeness.

Variationsfixuptool – COOL. Setqueryprocessoroptions, very interesting. Sounds like some options :) I’ll have to dig into these. Woah! The setqueryprocessoroptions is incredible. After digging in I can see there is a ton of search optimization information in there.

stsadm –o setqueryprocessoroptions –ssp ssp1 –Securitytrimmingcachesize <don’t set this unless you know what you’re doing>

“Specifies an increase of the w3wp process memory usage. This increases the probability of finding security descriptors needed in local cache, thus decreasing the number of roundtrips to a computer running SQL Server and the amount of data requested from a computer running SQL Server. This value should be considered if the search corpus contains a large number of different Access Control Lists (ACL).”

Also, when looking at this handy little app, you should change the Operations view –o to the properties view –pv and you’ll see even more you didn’t know. Like the days-to-show-new-icon a property only exposed through STSADM

Not trying to be critical. It’s a great start for giving us some useful views on the commands. How much better would the app be if it gave us more real estate, and gave you not only a brief description, but the syntax and an example when you clicked on it. Great work guys. Keep it coming!

Posted at 9:35 PM by Joel Oleson | Permalink | Email this Post | Comments (10)

6/12/2009

New *FREE* Enhanced Discussion Board View for SharePoint

One of the things that I’ve had to dance around with Notes to SharePoint migrations (Steve Walch talks about this in Search of a better Discussion…) and even with SharePoint as a community platform for forums, is the challenged discussion list. Many people I’ve talked to thought the discussion lists got worse going from 2003 to 2007 and upgrade with some depreciated features was a struggle. If you are looking to enhance your discussion list, this is a great free alternative that enhances the existing discussion list. I don’t think it’s necessary to bash SharePoint to push a solution, but I do want people to know there are gaps and I’m excited to see the gaps filled.

I’ve been looking for the community to put something together for a couple of years. There was a codeplex project that was put together and apparently dropped as people got busy. Note the 1 1/2 star for the project that has no code with status as no yet defined!

I’m excited to see Quest showing off its colors and providing a free no strings attached Discussion View with collapsible threaded views and a whole lot more. Here’s a small screenshot of the discussion view with dummy data.

Note: “This WebPart leverages the existing discussion boards, so an empty discussion board has to be added first. You can also connect this webpart to an existing discussion board.”

The install is an .msi package that you’d run to install to the farm. You should definitely try this in a non production environment first. (Update: I’m working with Quest to provide a WSP alternative.)

See the web part in action in a video demo by Curtis Kelly.

A few of the features include:

1. Cross List display! You can view multiple discussion lists at once by specifying them in the Viewed Lists property. The lists that you view can reside in another site, another site collection or even another web application as long as they are in the same configuration database.

2. UI enhancements: It displays the discussions and their responses in a tree structure, making it much easier to find the relevant topic

3. Time Saver: A preview panel to view the content of the selected discussion or response quickly.

4. Customizable UI: The ability to select which field to be displayed in the tree view panel by using the Display Fields property. If not defined, only the Subject field will be displayed.

5. Extensible: The developer enhancement ability to filter the top level discussions by using CAML Filter expression.

6. Branding & Look and Feel: Allows you to customize the look and feel by using Skins.

7. Grouping: The ability to group the discussions by a specific field. For example, if your discussion list contains a Category field, you can group the discussions based on that field. This greatly enhances usability.

You can download the bits – FREE from SharePointForAll.com the Quest SharePoint Team Community site:

32-bit qDiscussion View (For WSS 3.0 or MOSS 2007)

64-bit qDiscussion View (For WSS 3.0 or MOSS 2007)

Provide feedback and get support through the qDiscussion Board forum.

If you like this design, you’d be pleased with the other webparts that are designed to help you build composite applications on SharePoint, right through the web UI. This functionality comes out of a set of Quest Webparts. Watch a Webparts demo or download the Quest WebParts trial. Now available in Starter Bundle, Starter Bundle Plus, SI Bundle for Databases, Full Package

Posted at 11:34 AM by Joel Oleson | Permalink | Email this Post | Comments (23)

6/11/2009

Expo Governance Q&A

I got a ton of questions during the expo sessions. These set of questions were based on the keynote on 10 Steps to successful deployment. The recordings are available to those registered.

1) Can you provide a link to a planning template? 2) Is there a framework or guide for governance? I am looking for templates?

Do we separate SharePoint Web Apps compensate for different requirements from different areas?

The web applications will allow you to have different policies for different web applications. It’s great for separating the requirements of an Intranet portal from your my sites or collaboration sites.

i have a questions, how i do to learn a bit more a bout sharepoint??? for example, basic knowledge

Start with http://sharepoint.microsoft.com

Should site collections encompass functions or departments?

All of the above. Site collections can be used for an individual, a team, project, group, department, or an entire enterprise repository. It really depends on the requirements. Remember quota, list, and database scale and pay attention to the capacity boundaries. Information architecture should seriously consider the software boundaries.

Currently we plan on using SharePoint only for Team Collaboration. We have a separate Corporate Intranet site. What things should we be aware of when designing the Team site collections (IT, Corporate, Large Program etc) to make sure we don't have to redesign them if we bring Intranet in SharePoint in the future.

You need to make some difficult decisions around what object is a site collection. Redesign involves splitting up databases more than involves consolidating. The site collection is the most scalable object, keep that in mind. More is better than less for collaboration.

I am new to sharepoint and want to learn from basic. I have experience in asp.net C# of 5 years. Could you suggest me some tutorial or online training?

Developers should study the SDK and articles on MSDN
Paul Andrew the Dev Audience Product Manager has a great blog post Getting started with SharePoint Development.
SharePointDevwiki.com
http://sharepoint.microsoft.com

Quick question about where data is stored. Using WSS 3.0. Is it stored locally on the server or can it be stored on a network share/drive?

By default it’s in the content database. There are ISV solutions that support external blob storage (an API was created in Sp1).

How do you go about security planning? I've heard from MS support that you can only have 200 SharePoint groups in a site collection. I see that a limitation.

Not sure where you got 200, there is a 2000 recommendation on the capacity boundaries document on TechNet.

What is the best way to sync a SharePoint production environment down to a development or test environment?

Database attach method by making copies of your content databases. There are 3rd party options with people like syntergy or repliweb. Content deployment features can move out content from authoring, but not really the right solution for bringing back from prod to dev or test. Server Images can simplify this process as well. Using solutions make this much easier.

Is there an easy possibility to manage Active Directory Users and Groups from within Sharepoint?

Not out of the box. Look at ILM 2 from Microsoft
“With ILM “2”, end users can easily perform self-service tasks such as group and distribution list management with self-help tools integrated into a SharePoint-based console as well as directly in Microsoft Office Outlook.
ILM “2” provides IT professionals with the tools they need to manage identities through a SharePoint-based policy and workflow management console.”

What tips do you have for smaller businesses who are deploying sharepoint and encouraging adoption?

5 Ways to Drive Adoption (Small Business Computing)

What advice do you have for multi-lingual global rollouts of SP?

Deploy multiple language packs.
Read this whitepaper on multi lingual deployment
Figure out if the requirement is for the UI or for the content. Also determine if the cost will outweigh the work. I would actually discourage many who did go the route of variations to avoid it, and live with a common UI and have multi lingual content or simply different site collections with multiple language packs.

If just breaking into Sharepoint, what would be a good area to start in....Content Management....developer.....Administrator.....power user"

Pick your favorite. There is lots of room. Surprising numbers of jobs for experienced administrators and experienced developers. Power users will definitely be more likely to keep their jobs or get pay increases.

"What functionality that I will loose if I migrate a site to a different site collection.

If you use import export, you will lose your alerts and your workflows from within the site collection, but as well you’ll have to figure out navigation, security
Benefits can be much greater… you get quota, web part galleries, master page galleries, usage reporting, storage manager, etc…

Should I have provision site collections for groups that have potential of growing large. Thanks.

Yes, you may consider even putting those site collections in dedicated databases if they are going to get REALLY Large.

We have WSS 3.0 and are considering MOSS. Do you recommend a separte new installation of MOSS with a migration strategy for WSS or a straight upgrade of WSS to MOSS? Thanks

I recommend a strategy to upgrade your existing WSS 3.0 to MOSS. It will enhance your existing environment.

I have some teams that want to develop custom web parts, I am not a developer so I would have no way of saying this is good or bad code, all I could do is make sure it works today in qa and prod. Do you think I should have this kind of dev work hold off till I can get the execs to buy in with a develpoer that understands SharePoint?

You should be sure to run tools like FXCOP and SpDisposeCheck. I’d recommend training for anyone doing SharePoint development. I’m glad to hear you have a separate dev and QA environment.

"Hi Joel,
We considered using separate web apps for TeamSites vs Portals but we found that business units were reluctant to manage multiple web presence sites for their team and there was also a concern about duplicating content which is relevent to both the team itself and also for customers/visitors/users of that Business Unit's services. How could this be addressed ?"

I recommend separate web apps for quota templates, policies, and keeping like objects together for policy and storage reasons providing more flexibility. Having them all in one web app will cost more for management and overhead and reduce flexibility. Use links to consolidate documents.

Could you please have Joel post the Sharepoint Training resources that he referenced during the Q&A sessions. (Critical Path, SharePoint Solutions, etc) Thanks

I mentioned

How do my developers learn about Feature Stapling?

Both Andrew Connell and Eric Shupps discuss this in detail on their blogs. You may follow up with them for more detail.

When not to use SP Designer?

When you aren’t building design (masterpages), webparts, or workflows. Or if you aren’t trained to do those things. Designer is a powerful tool and can be dangerous in the wrong hands.

"What is the best migration strategy? Are there any templates available where business can use during data organization period?

Check out what NOT to store on SharePoint
Check out my deck on File Share to SharePoint where I discuss categories.

Migration from HTML to SharePoint 2007, SharePoint 2003 to SharePoint 2007?
Look at Migration Manager from Quest, but you’ll also find there are many solutions for doing migration. With many HTML sites, it’s better to redesign with a master page and move the content into document or page libraries.

Taxonomy question: We're grappling with the importance of taxonomy. Content types, if my understanding is correct, can help support taxononmy in a deployment... This is pretty easy win in a single site collection portal but how do you grapple with this in collaboration areas with many site collections as content types cannot be enforced out of the box across multiple site collections? Or, do you not worry so much about taxonomy in collaboration areas?

It’s true that in collaboration, the content types and properties aren’t as important. You can incorporate the right columns in a site template or in a feature. There is a codeplex solution for pushing out content types across site collections called spconfigurator at http://codeplex.com/spconfigurator. Taxonomies are definitely much more critical in structured document management or portals.

How can i ensure that the workflow functionality continue to work if the content db splitted into different servers while deployment

Workflow won’t break. SharePoint is designed to work with many servers on both the Front end and Backend. The workflows are in the content database and ran with timer jobs.

How should we approach enterprise search to formulate appropriate policies

Determine requirements and consider indexing and global aspects. Governance is a very important aspect of planning for your enterprise search strategy.

Half way down the road on a SP single server deployment, we went with a Departmental Sites route, and navigation to documents, forms etc is getting out of control. Do you think it is doable to redesign the entire structure? I'm finding the out of the box CQWP is almost unusable when doing cross site queries and improving navigation is tricky without getting lots of "weeds" complaining!

Yes, I think not only will CQWP be a challenge, but also URL lengths, including lack of quotas and ownership. There is a reorg wizard which you should look at, but also consider putting structured data in separate web applications from unstructured web applications where you should plan to host many site collections.

In an organization that has decided to do application hosting internally within SharePoint and has clear roles (admin vs developer, etc) how do you see the best organizational structure? Should developer and admin teams be separated with different management or brought together under a unified reporting relationship?

If you use AD groups how do you manage Security in SP itself?

Add security groups to the SharePoint permissions levels then manage the groups through AD Users and Computers or interface as implemented

what will make migration to 2010 difficult ?

Really massive databases.
"Are there any huge ""DON'T DOs"" when deploying Project Server with MOSS?

I say be really careful. Is the environment MOSS or Project Server? If it’s project server, you can benefit from reporting, and the document repository and workflow in MOSS. But the other way around, I find it tough to justify.

I have heard that the farm administrator accounts must be the same as well as the app pool accounts must be the same. Is this true?"

No, it’s not true. They can be the same or different, but both require the proper permissions, obviously.

How do the Quest Software products assist with SharePoint governance?

Quest Site Administrator for SharePoint 1) Set Creation Policies on webs 2) Turn on Auditing across large numbers of site collections 3) Permissions (Security) and light document compliance reporting
Various Quest Migration tools – for consolidation to improve manageability (Notes, File Shares, Public Folders, erooms, etc…)
Quest Recovery Manager for SharePoint – helps you reduce the time to restore files, lists, sites, and site collections
Quest Webparts for SharePoint – reduce the amount of time it takes to build applications and reduce and potentially eliminate the amount of custom code required to build composite applications including systems integration (2-way)

"The best pratice for the content database size to 100GB
What is your thought?"

I think it’s a good target.

We use WSS3.0 for an extranet solution for project management as we onboard clients into our own ASP platform. As such, we have to maintain separation between sites/users/data to protect sensitive information. We are trying to use forms based authentication for external users to avoid their introduction (and licensing) in our AD environment. Since each site needs separate groups for separation of sites/users/data, how do you recommend scaling users/groups? Our external users will probably be less than 10 per site.

The forms based authentication can scale to million+ users. The user management on the backend is what you likely need to invest in. How you expire accounts, manage passwords, etc… ADAM Lightweight Directory Services might be another way to get something with forms with a bit more management. Look at the extranet toolkit.
thank you very much

What's Joel email?

first.last@quest.com You can email me from my blog or twitter me @joeloleson

Thanks a lot, great presentation

Posted at 6:59 PM by Joel Oleson | Permalink | Email this Post | Comments (16)

6/8/2009

Aussie Tour and SharePoint Morning with the Experts Event Details – July 7-10

I’ve been working with the Quest folks in Australia to put together a multi city tour and I’m happy to begin sharing the details. I’m speaking at the SharePoint Community Conference in Wellington, NZ

You can REGISTER NOW for the events in Sydney and Melbourne or get more details.

I’m planning on doing a session on “10 Steps to Successful Deployment” and “Preparing to Upgrade to SharePoint 2010 Today” including a presentation by Adam Cogan, Microsoft Regional Director and .NET MVP and Kathy Hughes SharePoint MVP in Sydney While being joined by an Expert Panel made up of Microsoft rep, SharePoint MVPs, experts.

Sydney, Australia Tuesday, July 7th (8AM-1PM)

Melbourne, Australia Thursday, July 9th (8AM-1PM)

These two events will be special half day events. Speakers sessions, and panels are still being put together.

As well special user groups meetings are being held in Brisbane and Perth. More details to follow.

BSPUG - SharePoint User Group - Brisbane, Australia Tuesday July 7th

PSPUG - SharePoint User Group - Perth, Australia Friday July 10th

I apologize I wasn’t able to fit in Canberra and Adelaide. I hope you can join me in one of the cities above. Next time I hope to make it to.

I am interested in getting the right Microsoft people, SharePoint experts, and MVPs on the panels. Ping me on twitter if you are interested @joeloleson

Joel

Posted at 3:09 PM by Joel Oleson | Permalink | Email this Post | Comments (26)

6/1/2009

Free Virtual Expo on SharePoint – June 10

Wanted to make sure everyone heard about the *Free* SharePoint expo going on in less than 2 weeks! It’s a free SharePoint expo focused on IT topics like backup/restore, governance and keys to successful deployments, plus BI and SharePoint. Great stuff.

I mentioned the Expo in my *NEW* weekly “This week in SharePoint with Joel” Broadcast #2 over at EndUserSharePoint.com I think this week turned out quite well especially for me cleaning house most of the week and jumping on twitter and the intertubes when I could sneak it in.

I’m most excited about our experts panel and Q&A session (Noon EDT) with Michael Noel, Bob Mixon, Mike Watson and Myself. That is SURE to be an interesting time. I’m looking for someone to stump this IT panel. In addition we’ll also be spending time in the virtual chat sessions. I hope to have some really engaging conversations with the community.

Quest Software's Virtual Expo 2009 for SharePoint

Registration Information…

Wednesday June 10

During this free online event, you can interact with our SharePoint experts and partners to learn how best to migrate to -- and manage -- this essential collaboration platform. Join us for live webcasts on topics such as governance and recovery, and visit the booths to download white papers, gather product information or chat with a technology specialist. This event is accessible via any web-connected computer.

8 a.m. to 4 p.m. EDT

7am – 3pm CDT

6am – 2pm MDT

5am – 1pm PDT

Very decent times across Europe

1PM London, England

This isn’t restricted to the U.S. I hope to see some people who can’t sleep and those looking to fit in some community time from home :)

10PM Sydney

4PM Dubai

9PM Tokyo

Live webcasts:

SharePoint Governance: 10 Steps to Successful Deployments
Leveraging SharePoint and Performance Point as a Business Intelligence Platform
Ask the Experts: Live SharePoint Q&A
A Simple Game Plan to Master SharePoint Recovery

Plus, by attending you can:

· Enter to win prizes given away throughout the day including SharePoint books, gift cards and more!

· Interactive"Networking Lounge" with SharePoint experts

View on-demand webcasts

Migration tools and best practices
Administration and auditing
Recovery from your existing backups
Developing robust applications on SharePoint with no coding
Managing SQL Server

Register Now…

Don’t miss the tweets #SPVirtualExpo

Posted at 11:32 PM by Joel Oleson | Permalink | Email this Post | Comments (28)

5/27/2009

Is Twitter Killing Instant Messaging?

As time goes on I become more and more of a fan/advocate/evangelist of twitter. It’s amazing how it’s been connecting me more realtime with people I’d never be in contact with, and allows me to really build community relationships. It’s really becoming powerful.

It’s probably not fair to compare Twitter to live messenger, but I think it’s fair time that MS take a wake up call or two from the potential of twitter and how it will impact the enteprise. I know the SharePoint team has to take it seriously. Obviously I’m a HUGE MS Fan, and I’m not loosing my MS Religion. Twitter is not political, and I hope that it stays that way.

5 reasons why I’m spending less time invested with instant messaging and spending that time with Twitter… Instant messaging isn’t dead, especially in the corporation, but it sure is taking some lumps and loosing some eyeballs for good reason. Hopefully this means innovation and we’ll see some magical integration. Do I hear a mashup?

Why didn’t cell phones replace LAN lines? We did make cordless LAN phones, but we never integrated the functionality to give you a LAN line when you walk into your office. There are some form factor decisions, but I think we could even get past that with the proper blue tooth devices. It’s always a challenge for the new technology to put out the old because that’s not the design.

(Love to hear how Bob Fox has seen a shift in his Messenger use vs.his Twitter life for example)

1. I choose how I get bombarded/interrupted. With Twitter I decide what comes to me as a text message (nothing), and what comes as an email, and what pops up on the screen. With the more real time nature of IM, I find the conversations are forced to happen more real time where my twitter conversations can happen naturally over days. My really real friends can text me if they HAVE to contact me super real time.

2. With Live Messenger the 100 or so contacts I have are overwhelming, it’s tough to find people that are even in my list. I know I’ve got groups, but the displays and profiles are not easy to manage. The APIs in twitter allow me to use a non proprietary client which puts me more in control of how I manage my account or accounts. (Thanks Windows Live for pulling all those people out of facebook. Still not sure whether I should have done that.)

3. My Mobile to Desktop and visa versa experience is so much more seamless in twitter. With the rich GUIs and the simple twitter API I find it much more smooth to get up and move from device to device. With IM, I have to finish a conversation before getting up from my desktop.

4. Instant Messaging isn’t as Social – The design of IM was never to meet new people, so that aspect isn’t really strong with IM. With twitter it’s the ability for other people to join in and enrich the conversation that really takes things to another level. That’s why I’d prefer to have public conversations in the public. If someone has a SharePoint question, it’s much better on a public forum like a newsgroup or twitter. :)

5. Instant Messaging Status hasn’t been flushed out… needs to evolve – I don’t want to be so accessible when I’m “Online.” I want to have different status’s to different people. Todd Bleeker has some really good ideas that fell on deaf ears when he mentioned this to the messaging team. I want to tell work people I’m OOF, I want to tell my top tier friends I’m online and accessible, and I want to say I’m away for the masses. Make sense? The away says don’t bother me unless you need to. With twitter I can spend as little or as much time as I need to looking at the tiered information of direct messages and replies and respond to those that make sense at the time. With multiple concurrent IM conversations I feel bad not responding, but often I will. I don’t want to have to. The line of text we now get in IM is a step toward the integration of the two and the ability to have a richer status. I can say I’m travelling and where I am, so work people will know I’m on the road, but how accessible I’m trying to be still isn’t conveyed. If you don’t know someone how approachable are you really? Via Twitter the non-invasive “you choose how to be impacted” technology says… you don’t mind being contacted.

Posted at 9:43 AM by Joel Oleson | Permalink | Email this Post | Comments (42)

RSS Feed

1 - 10

SharePoint Joel's SharePoint Land

7/2/2009

6/24/2009

SharePoint Products and Technologies Pre-Upgrade Check Report

SharePoint Products and Technologies Pre-Upgrade Check Report

6/22/2009

6/18/2009

6/16/2009

View All

Not in UI

New in SP1

New in SP2

6/12/2009

6/11/2009

6/8/2009

Sydney, Australia Tuesday, July 7th (8AM-1PM)

Melbourne, Australia Thursday, July 9th (8AM-1PM)

BSPUG - SharePoint User Group - Brisbane, Australia Tuesday July 7th

PSPUG - SharePoint User Group - Perth, Australia Friday July 10th

6/1/2009

Quest Software's Virtual Expo 2009 for SharePoint

Registration Information…

Live webcasts:

View on-demand webcasts

Register Now…

5/27/2009

Joel's Calendar

Recent Posts

‭(Hidden)‬ Admin Links