18 December, 2012

New user account does not have a valid SID history - migrateuser: SharePoint 2007

Issue: While executing the SharePoint Migrateuser staadm command,
Stsadm –o migrateuser –oldlogin -newlogin
We run in to error: New user account does not have a valid SID history.
Resolution: Use the –ignoresidhistory switch at the end of the stsadm command to overwrite the SID history forcibly.
Stsadm –o migrateuser –oldlogin -newlogin
-ignoresidhistory
Some more reference which talk about the other resolutions:
http://blog.krichie.com/2008/06/27/using-stsadm-o-migrateuser-on-a-re-created-account

17 December, 2012

Real-Time Collaboration with Microsoft Office and SharePoint 2010


Of the Four Promises of SharePoint:

1. Enable Collaboration,
2. Manage Information,
3. Automate Processes and
4. Manage Business Performance.

SharePoint provides many capabilities for 1. Enabling Collaboration.

When collaborating on a document, it is common to email that document to one or more colleagues to update.  However, it can get very confusing determining who has the most up to date version of the document or how to reconcile updates across all the emailed versions.
The first step towards a more efficient collaboration is to work on the same content stored in a central location.  However, only one person can make their updates at a time. You might be familiar with this type of SharePoint collaboration that uses the check in and check out document feature within SharePoint document libraries.  This process fine for infrequently updated documents, but it can be inefficient when you have to wait for another person to check in their document before you can make your edits or on the occasion when that person might forget to check the document back into the library altogether.

You can come closer to a real-time collaboration by scheduling a virtual meeting with virtual meeting software like Microsoft LiveMeeting or GoToMeeting. However, this is not truly real-time collaboration since only one person can physically be in control of updating the document over the virtual meeting.

So how can you achieve true real-time collaboration while leveraging your current Microsoft Office and SharePoint infrastructure?

The current version of SharePoint 2010 (and SharePoint Online on Microsoft Office 365) and Office 2010 provide co-authoring capabilities for real-time collaboration. SharePoint 2010 Office Web Apps provide online versions of the popular Office applications of Word, Excel, PowerPoint and OneNote.

If you open an Excel spreadsheet or OneNote in Office Web App stored on SharePoint 2010 document library, the Office Web App will also allow your colleagues to open the same file at the same time via Office Web App to make updates.  When others join, you will see a notification that they have joined in editing the document at the same time.

When using the Office Web App for Excel, the quantity of editors is indicated in the lower right corner of your status bar. Click on the down arrow to view editors by name.

If you and your colleagues have the Office 2010 desktop applications, you can also co-author Word, PowerPoint and OneNote documents stored in a SharePoint 2010 library.  When they make updates, you will see their changes highlighted with their initials.

Number of editors is visible in bottom status bar in Word 2010 desktop application. Click to view editors by name.

To enable this capability within the documents of a SharePoint library you will need to:
  • Either enable SharePoint 2010 Office Web Apps within SharePoint 2010 (or SharePoint Online on Microsoft Office 365) or have the Office 2010 desktop applications installed
  • Store the Office documents within the SharePoint 2010 document library**
  • Enable Contribute or higher permissions for the participants to update documents within the SharePoint 2010 document library
  • Turn off Check In/Check Out capability in the document library
  • If you are collaborating with OneNote notebook documents, turn off document versioning (or limit it to a limited number of major versions)
Reference: www.abelsolutions.com

Managing Hyper-V with PowerShell and Hyper-V in Windows Server 2012 and Windows Server 2008 R2

Managing Hyper-V with PowerShell



How to Work with Hyper-V in Windows Server 2012 and Windows Server 2008 R2


SharePoint 2013 discontinued features and functionality

SharePoint 2013 has a number of changes since SharePoint 2010. This is a list of some of the features and discontinued functionality. If you want a quick look at what has been discontinued or modified – read further.
Some of the features that have been discontinued may continue to operate in SharePoint 2013.
Some of notes:
  • When you create a site, all Meeting Workspace site templates (Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace) are not available. I know some environments that heavily use workspaces and I’m keen to inform them about this change.
  • FAST for SharePoint has now been integrated into SharePoint 2013. So a lot of features have changed in this space. One of them is the Search RSS feeds being discontinued and another is the Web Analytics are part of the Search service.
  • Office Web Apps server has sort of divorced from SharePoint 2013. 2 years ago with SharePoint 2010 they were inseparable! So a lot of functionality has changed in this space. In case you didn’t know, you cant install Office Web Apps on the same server as SharePoint 2013, it doesn’t allow you to. It has to reside on a separate server.
Reference: JeremyTaylor.net

Question: Is it possible to set my newly created custom page in my SharePoint site as the home page.

Ans. Yes, it’s possible to use a custom page as a home page. You can set it in multiple ways:
  • If you have enabled the Publishing features on your site, or your site was created from a Publishing template, then you can just go to Site Actions, Site Settings and click Welcome Page, then select a page.
  • You can open the site in SharePoint Designer, right-click any .ASPX page, and select Set as Home Page.
  • If you're a developer, you can set the home page by using code. See the MSDN page "SPFolder.WelcomePage property" for more information.
  • If you're a SharePoint administrator, you can use a Windows PowerShell script to select a master page:
$web = $site.RootWeb
        (or $web = $site.OpenWeb("yoursubsite")
$folder = $web.RootFolder
$folder.WelcomePage = "SitePages/home.aspx"
        (or  $folder.WelcomePage = "default.aspx")
        (or  $folder.WelcomePage = "Shared%20Documents/mycustomwebpartpage.aspx")
$folder.update()
$web.Dispose()
$site.Dispose()