Edit Form People Picker Empty

Happy Friday everyone,

I wanted to let you know of a current issue that we are seeing in our SharePoint Foundations 2013 farms. Right now as far as I can tell this shows up if you have the July, August, or September 2014 CU added to your SharePoint Farm

You can read about it here:

http://social.technet.microsoft.com/Forums/sharepoint/en-US/17db4d9a-590f-4d4d-ab83-9d7d50cf6e31/sharepoint-2013-july-2014-cu-people-picker-fields-empty-in-edit-forms?forum=sharepointadmin

The TL:DR version is the people picker is blank when you go and open an existing item in a list using the edit form. This is kind of a pain because we use this type of field EVERYWHERE in our farms.

I want to get the word out to as many people as possible at this point and my next plan is to open a support ticket with MS support.

Feel free to post more comments below and let me know what your experience is with this. As I have more details and a fix, I will post it here.

Thanks,

BJ

Hey everybody! Come out and join me for lunch and SharePoint

It finally happened. I am taking the plunge and agreed to do my first user group presentation. Believe you me, I am just as nervous thinking about it as you are. But I am also very excited at the opportunity.

I will be presenting “SharePoint Campfire Stories” on September 23rd from 11:30am until 1pm at the Small Business Development Center. Come on out and let’s share funny, sad, and maybe even interesting things I have run across in my 6 years as a SharePoint admin.

There will be something for everyone here. I will try to cover things that can help beginners new to SharePoint as well as those of us who have a few battle scars in the war of SharePoint.

My general outline will be on general gotchas and other fun and interesting experiences that I have seen while installing, maintaining, and of course patching and maintaining SharePoint from old versions like Wssv2, all the way up to SharePoint 2013.

Everyone is in for a treat because I recently finished a migration for SharePoint 2013 Foundations that I have some tips to share as well.

Go here for a signup

https://www.eventbrite.com/e/chattpac-user-group-lunch-9232014-tickets-13033933847

If you have any questions, feel free to let me know through the comments below or send me a tweet @bjfentress.

Thanks and see you there!

-BJ

Add domain to people picker in Foundations 2010 and 2013

Hello everyone,

Recently I ran across a scenario where I needed to add in a new domain full of new users to my SharePoint Foundations farm.

Originally in my test setup we were dealing with a one way domain trust between my original dev forest and the newly created forest, so I went to searching and found the following article:

http://jantjesworld.blogspot.com/2013/06/configuring-peoplepicker-in-sharepoint.html

So I went in and followed the steps in his article and everything seemed to work just fine. That is until we went to production with this same scenario and discovered that we weren’t using a one way trust, but a two way trust.

After many hours of research and even a support ticket with Microsoft, we finally found our answer. And so far from the research I have done, there are many people who have figured out the one way trust issue, but no one has specifically noted what to do in a two way trust. That’s what I’m here for. :)

In a one way trust your PowerShell should include accounts that have permissions in the domain or forest so they can cross properly. In my case though with a two way trust the login information is not needed. Also with a two way trust, I did not need to set an encryption key.

For the new two way trust, all I had to enter was:

Stsadm -o setproperty -pn peoplepicker-searchadforests -pv “forest:Contoso.com; domain:Fabrikam.com” -url http://myintranet

I’m not sure if it was necessary, but after running this I did reset my web servers just for good measure and then, viola! I am now able to see my existing domain users as well as the new domain users in my people picker settings in SharePoint Foundations.

I have also tested this on both 2010 and 2013 versions of the product and it worked like a charm. My last bit of advice in this scenario is to make sure that you work closely with your Active Directory admin on this and ask many detailed questions…

It will go far and save you many headaches and possibly even a support call with Microsoft.

Thanks,

BJ

Create search in SharePoint Foundations 2013 without GUID

When SharePoint Server 2013 was first released, I was curious what new things I could do with it. I saw the new search capabilities, a different look and feel, a similar management interface, and several other BI things that made me happy. I then also realized that I support SharePoint Server and also the free version SharePoint Foundations. In SharePoint Foundations you get SOME of the things that makes SharePoint great (like Search for example), but with Foundations there are usually strings attached to that functionality.

In SharePoint, if you create your farm by clicking on all the defaults and using the wizards your databases look like this:

clip_image001

With SharePoint Foundations 2013, we don’t really have the option to create search by scripting with PowerShell… or do we?

Originally my research pointed me to Gary LaPointe’s blog here.

Which is great because this is in PowerShell and I can understand this, but it still doesn’t give us what we are wanting in the end like this:

clip_image002

Fortunately I found the following post by Jasjit Chopra’s blog here.

Finally!!! What we have been searching for all along! One thing to note at this time is that I have tried this myself on two different farm configurations (a three tier farm and a single box farm) and in both cases the search service and databases were created with the clean names and the service functions just fine.

I’m doing my happy dance now… enjoy!

-BJ

SharePoint Saturday Atlanta 2014

Back on June 21st, I had the privilege of attending my first event of the year in Atlanta at the Georgia State University Student Center.

You can find out more about the event by going here.

The twitter feed for this event was #SPSATL and if you have a chance, I highly recommend you go back and check out all the content that was related to this one.

While I was there I had a chance to check out the following sessions:

“Anatomy of an Intranet” by Michael Greene Twitter Blog

“Use SharePoint as a viable Hybrid Approach to your Enterprise” by Eric Harlan Twitter Blog

“Windows Azure as a SharePoint Farm Restore Rehearsal Space” by Tyler Bithell Twitter Blog and Pablo Montequin Twitter

“The White Hat: hacking SharePoint On-Prem from Google Reconnaissance to Metasploit” by Joseph Irvine Blog

“Business Intelligence with SharePoint 2013 and SQL 2014″ by Ivan Sanders Twitter Blog

My personal favorite of the day was the session on hacking SharePoint by Joseph Irvine. It gave me chills as to some steps I should be doing with my own SharePoint farms, but also gave many examples of businesses and organizations that show they just click next, next, next and then quit maintaining their servers.

Shame on them and shame on me too! Security for the most part isn’t too difficult, it just takes extra time that most people don’t have the time for. Until they get hacked or pwned.

The folks in charge of putting on this event did a great job! I look forward to these events whenever I can go because they always line up good speakers who can give you FREE training on something you want to learn more about. If there is an event going on close to you in the future it’s worth a tank of gas and a Saturday of your time to better yourself. Now go sign up!! :)

To learn more about upcoming events for SharePoint Saturdays head on over to http://spsevents.org

-BJ

Grid View Issue Reappears with Performance Point 2013 post June 2013 CU

Hello again SharePointers!

I wanted to get the word out on another bug that seems to have reappeared in Performance Point in SharePoint Server 2013. Originally this issue popped up as a problem with the grid view being cut off towards the top. Example below:

clip_image001

This issue was corrected in the June 2013 CU for SharePoint Server here

But after testing both before SP1 (August 2013 CU) and after SP1 in my farms, I see the following issue pop up when multiple pages exist in the web part. This is referred to pagination I believe and causes a behavior that we see in our farm like the screenshot below:

clip_image002

For us it’s more of an issue about our users not being able to view the proper info they need. I have filed a case with Microsoft support and will keep everyone up to date on how it progresses.

Fortunately as I was typing out this post I got a message from someone that this is an official bug and will be submitted to the product group to be fixed.

So I am glad that it is not just my farms that see this issue… :) But I also hope that this provides some help for those of you seeing this issue as well. As soon as I get word on which CU this new fix will be in, I will let everyone know.

Thanks for visiting!

BJ

SharePoint 2013 SP1 kb2817429 fixes Dashboard Designer issue

Greetings!

I thought I would add to the hoopla currently going on around Service Pack 1 for SharePoint 2013 which was released this week. If you haven’t got it yet, go get it now and test it out on your farms! You can find it here.

One quick thing I also wanted to mention that I have verified with SP1 is that when you install this update it does fix the Dashboard Designer not loading error that I wrote about in my last two posts here and here.

One other tidbit I did notice after I patched my farms is that when you go into Central Administration and look at the patch numbers it erases all the annoying list of patches or cumulative updates applied to your farm previously. Kudos to the team for implementing this!

So a farm like this (Pardon the 2010 reference, I didn’t have a good 2013 one):

clip_image001

After the 2013 SP1 Install will look all nice and neat like this:

clip_image002

Enjoy and happy patching everyone!

-BJ

Follow

Get every new post delivered to your Inbox.