SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL


[Microsoft.Office.Server.UserProfiles.Privacy] enumeration ints

Oh yeah, time for fun stuff!  There are only maybe 50 people on the entire planet that care about this but here goes nothing…

The Privacy class has enumerations which are fine for C# IDE coding but if you ever run a direct TSQL select against the SSP database those become hard to read.  [UserMemberships.ItemSecurity] on the Shared Service Provider database stores these raw integer values if you ever need to query Membership data directly.  And here they are:

Contacts 2
Manager 8
Organization 4
Private 16
Public 1


SharePoint admin nirvana: SPDash !!!

I love SharePoint, but servers can drive me crazy.  So many!  So check this out …  Allows lightening fast multiple server management. RDP doesn’t scale. Manage 10 servers easier than 1 with incredible "Grid" scripts that put everything on one page.


  • Do admin tasks faster
  • Scale up beyond RDP
  • Add new servers without fear


  • Pure XML config
  • Auto-detect SharePoint farm (machines + users)
  • Grid output, easy to read
  • Copy and paste to Excel

Real application screen-shots:

DevAdmin is how I think of my work. An administrator that uses development (script/code) to get more done with less. A developer that administers system capacity, performance, and scale. It’s a mix. And it’s a beautiful thing.
SharePoint farms have many servers with various services, applications, traffic patterns, and purposes. Having "grid" scripts like the below sample screen-shots can be a life saver. What’s a "grid"? Simple. I wanted to build a real-time Excel spreadsheet to display ALL configuration without RDP. RDP won’t scale. While great for 1-2 servers, it is awful for 10+ servers. Having confidence in your configs and knowing everything is 100% consistent are BIG steps forward for most admins.

FIXED – DeleteElementAddToMyColleaguesURL People Search

If you ever see the below People Search error go double check your indexed User Profile Properties.   I saw this recently and the root cause was a missing “Indexed” checkbox.   Enabling the Indexed checkbox for Account Name and crawling again fixed the issue.   Thanks to Puneet for the tip on this one.

System.NullReferenceException: Object reference not set to an instance of an object. at System.Xml.XmlNode.RemoveChild(XmlNode oldChild) at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.DeleteElementAddToMyColleaguesURL(XmlNode result) at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.CreateXmlDocument() at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SortBySocialDistance() at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.GetXPathNavigator(String viewPath)


© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲