Monday, February 27, 2012

SharePoint 2007 to 2010 Help Desk Upgrade

Scenario
  • You have installed the HelpDesk Fab 40 Template
  • You are performing a database attach upgrade from SharePoint 2007 or WSS 3.0 to SharePoint Server or Foundation 2010 and have run test-spcontentdatabase
Issue
  • The test-spcontentdatabase report contains the following errors (the cooresponding feature names have been added):
    • Category        : MissingFeature - HelpDeskModules
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-02cb-4f87-bb11-1ffde748a953].
      Remedy          : The feature with Id 75a0fea7-02cb-4f87-bb11-1ffde748a953 is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances, HelpDeskServiceRequestsList
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-fe9d-4119-9615-2c2ef22d6fdb].
      Remedy          : The feature with Id 75a0fea7-fe9d-4119-9615-2c2ef22d6fdb is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances, KnowledgeBaseKeywordsList
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-12fe-4cad-a1b2-525fa776c07e].
      Remedy          : The feature with Id 75a0fea7-12fe-4cad-a1b2-525fa776c07e is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances, HelpDeskTasks
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-3b2a-4838-8a0c-57ba864feed3].
      Remedy          : The feature with Id 75a0fea7-3b2a-4838-8a0c-57ba864feed3 is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-97c5-4487-88e4-70fde8f79b25].
      Remedy          : The feature with Id 75a0fea7-97c5-4487-88e4-70fde8f79b25 is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances, HelpDeskSupportFaqList
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-70e3-40b1-b395-c06f85d0d158].
      Remedy          : The feature with Id 75a0fea7-70e3-40b1-b395-c06f85d0d158 is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskExpertsList, HelpDeskListInstances
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-e63b-4059-8f5a-ce9cbbadad2a].
      Remedy          : The feature with Id 75a0fea7-e63b-4059-8f5a-ce9cbbadad2a is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary.
    • Category        : MissingFeature - HelpDeskListInstances
      Error           : True
      UpgradeBlocking : False
      Message         : Database [MOSS_ContentDB] has reference(s) to a missing featu
                        re: Id = [75a0fea7-d31d-491a-9177-f0e461a81e3f].
      Remedy          : The feature with Id 75a0fea7-d31d-491a-9177-f0e461a81e3f is r
                        eferenced in the database [MOSS_ContentDB], but is not instal
                        led on the current farm. The missing feature may cause upgrad
                        e to fail. Please install any solution which contains the fea
                        ture and restart upgrade if necessary
      •
  • There will also be some MissingSetupFile - Need to install messages as well.
Resolution
  • The following solution is to get existing sites working.  To create new sites using the fab 40 templates, you may download and install the 2010 upgraded versions
    • I would recommend starting from a blank site template to build a tailored solution instead of using these templates due to the issues we've had modifying and upgrading them
  • The solution is to copy and then install the missing features
    • Copy the erroring feature folders from the 12 hive on the 2007 server to the 14 hive on the 2010 server
      • ...\12\template\features
      • ...\14\template\features
      • The ones we copied were: HelpDeskExpertsList, HelpDeskInIssuesList, HelpDeskListInstances, HelpDeskModules, HelpDeskServiceRequestsList, HelpDeskSupportFaqList, HelpDeskTasks, HelpLibrary 
    • Install the features on the 2010 server from PowerShell (SharePoint 2010 Management Shell)
      • Ex: install-spfeature -path "helpdeskservicerequestslist"
        • Do this for each of the folders copied earlier
Posted by at 1 comment:
Labels: , , , ,

Wednesday, February 15, 2012

Android: Upload documents, images, list items, or metadata to SharePoint

Scenario
  • You are developing an Android OS application on an Android tablet or Android phone and need to upload a document or photo to a SharePoint list or library.
Issues
  • NTLM authentication is not natively supported
  • SOAP protocal is difficult to implement
  • REST interface is limited
  • Need to batch upload multiple documents and set metadata while reducing bandwidth
  • Need to thread multiple uploads
Resolution
  • Kiefer Consulting, Inc. has experienced SharePoint and Mobile development teams that can help address these issues.
Posted by at No comments:
Labels: , , , ,

User Profile properties from a User or Group Column

Scenario
  • You have user profile properties (Company, Role, Contact Info, etc.) in a user's SharePoint profile.  You have a People Picker (User or Group) Field in a list and select that user.  You would also like the selected user's profile properties to be automatically saved to columns in the list.
Issue
  • You cannot do this out of the box.
Resolution
  • Kiefer Consulting, Inc. has developed a custom workflow that will allow you to do this. 
    Contact me if you need this.
Posted by at No comments:

Monday, January 16, 2012

Lync Attendee Install - Join a Lync Meeting - Public Users

Scenario
You have been invited to a Lync meeting where you will be using microphone, speakers, screen sharing, webcam, whiteboarding, document annotation, or other attendee features and have not yet installed the Lync Attendee client software.

Resolution
Install the Lync Attendee client. 

IMPORTANT: If you have the full version of Lync installed and do not have a Lync login, you will need to uninstall Lync before installing Lync Attendee.  Otherwise, you may use your Lync login with the full version of Lync to join the meeting.
  • Navigate to the URL provided by your meeting organizer (this person has a Lync account)
  • Select the View alternatives for joining the meeting hyperlink
  • Select the Lync Attendee hyperlink
  • Click the Run option at the bottom of your browser
  • Proceed through the installer wizard until you click Finish
  • Close the browser and any Lync windows already opened
  • Re-navigate to the meeting URL provided by your meeting organizer
  • This time you should see the Microsoft Lync Attendee client open up
  • Select the Join as Guest option and enter your display name
  • Always trust and Connect when prompted to Sign In
  • You should now be in the meeting. 
  • See documentation here for using specific features or configuring Lync Attendee
Posted by at No comments:
Labels: , , ,

Tuesday, November 15, 2011

SharePoint 2010 SQL AutoGrowth Settings

Scenario
  • You would like your SharePoint 2010 and Reporting Services (SSRS) databases to perform well by avoiding excessive database auto-growth and disk fragmentation. Note that this is in addition to other SQL performance tuning steps such as splitting up the tempdb across physical files and optimizing SQL Server disk access speeds.
Solution

Note: The following settings are initial baselines.  You should adjust the Initial Size and Autogrowth settings appropriately.  Monitoring and reporting on auto-growth is vital to this process.

Also, make sure you have a SQL Server Maintenance plan in-place to backup your transaction logs every 5 to 60 minutes.  If you don't do this, you must do full backups from SQL Server, not SharePoint to avoid using up all your disk space.  The interval chosen for you transaction log backups will be the maximum data loss interval in-case of failure.
  •  Change Initial Size and Autogrowth Settings
    • Right click the database in SQL Server Management Studio
    • Click Properties
    • Select Files, change as in the table below, and click OK
      • If blank, leave as-is or set to the auto growth setting
Database
File
Initial Size
Autogrowth
master
Data
10MB
10MB
Log

10MB
tempdb
Data
20MB
20MB
Log

10MB
spfarm_AdminContentDB
Data
500MB
100MB
Log

10%
spfarm_BusinessDataCatalogDB
Data
10MB
10MB
Log

10MB
spfarm_ConfigDB
Data
250MB
100MB
Log
500MB
50MB
spfarm_EnterpriseSearch
Data
50MB
20MB
Log

20MB
spfarm_EnterpriseSearch_CrawlStore
Data
250MB
250MB
Log

50MB
spfarm_EnterpriseSearch_PropertyStore
Data
50MB
20MB
Log

20MB
spfarm_MetaDataDB
Data
50MB
20MB
Log

20MB
spfarm_MySites_Content
Data
250MB
250MB
Log

100MB
spfarm_PerformancePointDB
Data
50MB
50MB
Log

20MB
spfarm_ProfileDB
Data
100MB
50MB
Log

20MB
spfarm_SecureStoreDB
Data
10MB
10MB
Log

10MB
spfarm_SocialDB
Data
10MB
50MB
Log

30MB
spfarm_StateServiceDB
Data
100MB
20MB
Log

20MB
spfarm_SyncDB
Data
100MB
20MB
Log

20MB
spfarm_UsageAndHealthDB
Data
150MB
50MB
Log

20MB
spfarm_WebAnalyticsReportingDB
Data
20MB
20MB
Log

20MB
spfarm_WebAnalyticsStagingDB
Data
20MB
20MB
Log

20MB
spfarm_WordAutomationDB
Data
20MB
20MB
Log

20MB
spfarm_WWW_Root_Content
Data
1,000MB
500MB
Log
100MB
100MB
ReportSerer
Data
50MB
50MB
Log

20MB
ReportServerTempDB
Data
20MB
20MB
Log

10MB

Posted by at No comments:
Labels: , , , , ,
Subscribe to: Posts (Atom)