At a client recently, I was tasked to create an inventory of all the Active Directory Groups that give access to a SharePoint site! I built it mostly from scratch, so here it is as well as some explanations to help you use it:

The Script:

function WriteLogs ($message) {
    $message | Out-File $logfile -append
}

$logfile = "C:\ADGroupInventory\grouplist.txt"
Write-Host "Starting Group Script inventory"
$was = Get-SPWebApplication

foreach ($wa in $was)
 {        
  $webappUrl = $wa.url
  Write-Host "Starting to look in $webappUrl"
  $spWebApp = Get-SPWebApplication $wa.url        
  foreach($site in $spWebApp.Sites)
  {
    $siteurl = $site.url
    Write-Host "Going into SiteCollection $siteurl"
    $group = $site.RootWeb.SiteUsers
    foreach ($grp in $group)
    {
     # Ensure the item is a domain group
     if($grp.IsDomainGroup -eq "True")
     {
      $groupname = $grp.name
      WriteLogs "$groupname"
     }
    }
  }    
 }

 

How to use it.

First of all, change the $logfile variable to a folder that exists to make sure the logs work. Second, in the Central Administration, give yourself "Full Control" in the Web Application User Policy. This will make sure that you won't have any access denied when you go through each and every site collection in your farm. Afterwards, open SharePoint Management Shell as an Administrator, and run the script. Depending of the size of you farm, it shouldn't take too long, and you should see progress of every site being scanned on the screen. At the end, you will have a text file looking like this:

Get all the Active Directory groups in your SharePoint Farm

You will notice in the screenshot that some group names are repeated, as well as some of them are in capital and some of them are lowercase. So, I used NotePad++ to get all the unique group names! First of all, go in Edit > Convert Case to > Upercase!

To get unique lines, you will need the TextFX plugin. This used to be included in older versions of Notepad++, but if you have a newer version, you can add it from the menu by going to Plugins -> Plugin Manager -> Show Plugin Manager -> Available tab -> TextFX -> Install. In some cases it may also be called TextFX Characters, but this is the same thing.

After the plugin is installed, go in TestFX Tools and check the "sort ascending" and "sort outputs only UNIQUE" lines. Afterwards, click the "Sort lines case insensitive at column". (make sure that you do Ctrl+a in the file to select all the lines before clicking).

 

Now, your Notepad++ will only show the unique group names in your SharePoint Farm!

 

 

Drop a comment if this helped!

Leave a comment and don't forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don't forget to check out SharePoint Community.Net for more great SharePoint Content.

Easily Compare Office 365 Plans

Categories: SharePoint 2013
Comments: 2

Last week I attended and spoke at an amazing new conference in Toronto called CollabCon. The organizing was great, speakers were amazing and attendees were really fun and engaging & I highly recommend that if you’re from Canada, you should attend the 2016 event. However, this is not what this blog post is aboutJ. While at the conference, Microsoft had a booth and they gave away a small pamphlet in which you could easily compare Office 365 plans. I found the pamphlet a lot easier to read and view the differences between plans than the web version which you can find here.

Here is what the pamphlet contains:

What is Office 365?

Compare Office 365 Plans

Office 365 for Small & Midsize Business

Compare Office 365 Plans

Enterprises & Non Profits

Compare Office 365 Plans

Government and Education

Compare Office 365 Plans

What do you think about this pamphlet? Do you find it more useful than the web version? Do you have a site where it’s easier to compare? Let me know in the comments!

To visit CollabCon click the logo below

To visit the web version of the O365 Plan Compare click the logo below

I was at a client recently and was trying to add a new SharePoint Server to the farm, and everything went well until I tried to run the SharePoint Products Configuration Wizard. The error was:

Task configdb has failed with an unknown exception Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly ‘Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′ or one of its dependencies. The system cannot find the file specified.

 123014_0212_Configurati1

The problem is that the rest of the farm had the PowerPivot enabled, and therefore the PowerPivot Addin is required. Unfortunately, This Add-in is not verified at the begging of the SharePoint Products Configuration Wizard standard check, so that is why you get to this error. A recommended best practice is to install spPowerPivot.msi on all servers in the SharePoint farm for configuration consistency, including application servers and web-front end servers. The installer package includes the Analysis Services data providers as well as the PowerPivot for SharePoint 2013 configuration tool. To fix the problem, simply download the installer file from Microsoft Download Center: Microsoft® SQL Server® 2014 PowerPivot for Microsoft SharePoint®, run it on your server and then re-run the SharePoint Products Configuration Wizard. Everything should work perfectly!

Drop a comment if this helped!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

While (trying) to install SharePoint Server Reporting Services at one of my clients, I got into some pretty nice errors (SSRS Errors, Gotta catch ‘em all!). This one was the one that made me crazy for a few weeks because I never found out why I was having it, however I found out a way to fix it that worked, so I will share it with you in order to not lose hair over it like me. The error is basically getting a The remote server returned an error: (500) Internal Server Error whenever you click on either “System Settings” or “Manage Jobs”

The error:

The remote server returned an error: (500) Internal Server Error

This doesn’t tell us much, however when we go into Event Viewer we find two event IDs that are related to this and they both have similar messages.

Event ID 1310.

Event ID 6398

The thing we find in common in both those errors is “Could not find permission set named ‘ASP.Net'”. After countless hours spent on google, bing and even yahoo and after even some of the best SharePoint people I know couldn’t find the issue, I discovered a way to make it work. Is this the best way? Probably not. I hope that it will help people that were in the same situation at me and want to get SSRS Working. Here are the steps.

What you probably already done to get to the error:

  • Install Reporting Servers + Addin
  • Run the PowerShell commands (Install-SPRSService & Install-SPRSServiceProxy & get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Start-SPServiceInstance)
  • Create the SSRS Service Application.

What I did to fix it:

  • Delete the SSRS Service Application as well as Databases.
  • Run the following PowerShell command: “get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Stop-SPServiceInstance”
  • Run the following PowerShell command: “Install-SPRSService –Uninstall’
  • Run the following PowerShell command: “Install-SPRSServiceProxy –Uninstall’
  • Go to Control Panel, Select SQL Server and then click REPAIR. Do a full repair of the SSRS + Addin feature (you shouldn’t have anything else installed on the server anyway, so just select all)
  • Run the PowerShell commands (Install-SPRSService & Install-SPRSServiceProxy & get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Start-SPServiceInstance)
  • Create the SSRS Service Application.

Now everything should work! Drop a comment if this helped!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

Last week, Microsoft did a pretty big announcement that will probably impact all organizations around the globe. Starting July 1st, the on-premise User CAL pricing will increase 15%.

CAL prices to increase

With this move, Microsoft further delivers its message of “Mobile First, Cloud First”, by encouraging companies of going with the cloud licensing options (Office 365 Enterprise, Enterprise Mobility Suite and Enterprise Cloud Suite) that offer both online services and on-premises server software!

At first, this may seem like a bad move by Microsoft, who has been criticized of pushing the cloud and forgetting about on premises. However with the new on premises SharePoint, Exchange and Lync versions coming out this year, and with Hybrid promising to be a big part of SharePoint 2016, it might be a good time to review your licensing agreement, so you’re not blocked from going Hybrid only by your licensing team in the coming years! For more information, and how it affects you, make sure you talk to your account managers!

Make sure you spread the news about the Microsoft User CAL Increase on twitter by clicking on the birdie below:

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

While configuring SharePoint Server Reporting Services (SSRS) at my client, I had a really strange problem on one of the farms… I couldn’t get the SSRS Addin to install. I tried rebooting, repairing but nothing. After digging out in the logs, I found this funny error message:

CA MSG : rsCustomAction.exe failed to configure, Error code is: 1

CustomAction RSSP_CAInstall_64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

rsCustomAction.exe failed to configure, Error code is: 1

Also, for the information I was running SQL 2012 SP1 + Windows Server 2012 R2. You might also see something like this in the logs:

Long Story Short, after a lot of googling and asking for help from SQL & SharePoint masters, I found out that the bug is because I had a line commented in the web.config file of a web application. As strange as this may sound, after deleting the commented line, the install went through perfectly. I couldn’t find any official documentation on this, so if this worked for you please share it in the comments!

Drop a comment if this helped!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

Earlier this month, the great team at Microsoft Learning launched a new initiative called “The Know It. Prove It.” (KiPi) Challenge. During this month-long learning challenge, you’ll earn badges and points, compete against other learning challenges, and best of all, and learn the real-world skills that can make an impact in your job and career.

 A few things about the challenge:

  • There are 8 different learning tracks, ranging from Cloud Development to Web Development.
  • Each track consists of a learning module which is accessible from anywhere so learners can watch video tutorials and do assessments whenever is easy!
  • During The Know It. Prove It Challenge, you can track your progress, earn badges and points, compete against other challenges, and share experiences with others who have accepted the challenge.
  • Although the challenge officially kicked off on February 1st, it’s not too late to get started.

Let’s focus on the SharePoint & Office 365 tracks of the challenge. Here are their descriptions:

ChallengeCourse Titles
Office 365

Take this challenge to learn how to get the most out
of Office 365 services,security, and performance at
your small, medium, or large business.

• Office 365 Performance Management

• Expanding Office 365 with Enterprise Mobility Suite

• Managing Office 365 Identities and Services

SharePoint

Take this challenge to learn how to develop and
administer SharePoint sites to improve information
sharing and organization at your company.

• Manage SharePoint Online Documents and Lists

• Support Corner: Configure SharePoint Outbound Hybrid Search

• Office Guides: SharePoint Online Overview for IT Pros

• Office Guides: Apps for Office and SharePoint

• Tuning SQL Server 2012 for SharePoint 2013 Jump Start

• Developing Microsoft SharePoint Server 2013 Core Solutions Jump Start

• Developing SharePoint Server Advanced Solutions Jump Start

I find that MVA has done a very good job lately in giving out free learning resources to the community, and joining a challenge like this can motivate you to pass a Microsoft Certification exam in 2015! Also, if you’re a bit stressed for a Microsoft Certification, remember Second Shot Offer is back in 2015 for Microsoft Exams until May 31st, so in case you fail the first time, you can try a second one for free!

Furthermore, during the Know It. Prove It. challenge, you’ll also have an opportunity to connect with others just like you who are looking to accelerate their tech skills and this starts by completing your profile. After that, you’ll be able to track your progress, share your experiences with other members in the KiPi community. You’ll also receive badges and points, compete against others, and get encouragement to help keep you moving forward!

So don’t hesitate to participate in the challenge and learn more about SharePoint & Office 365 in order to boost your skills and career! Check out the website over here: knowitproveit.com

Last Friday afternoon, the SharePoint team at Microsoft made a few interesting changes on their blog about the future of Forms on SharePoint Lists (FoSL).

For some history on the subject, on January 31st 2014, Microsoft posted a blog post titled “Update on InfoPath and SharePoint Forms” in which they announced that InfoPath 2013 will be the last version of InfoPath, and they are currently working on a new version of FoSL for both SharePoint Server & Office 365. They promised an update at the SharePoint Conference 2014 in Vegas, and they delivered. Microsoft presented Session number SPC348 at SPC that showed us a new way of editing FoSL directly online! If you want to look at the session, you can find it here: SPC348: Update on InfoPath and SharePoint Forms

Fast forward to February 6th, 2015 and after 8 months without any news, Microsoft updated their blog post to include the following:

“As part of the update shared around the Evolution of SharePoint and the next SharePoint Server on-premises release, we are also updating the timelines for removal of InfoPath Forms Services components of SharePoint and SharePoint Online. Specifically, InfoPath Forms Services will be included in the next on-premises release of SharePoint Server 2016, as well as being fully supported in Office 365 until further notice. Customers will be able to confidently migrate to SharePoint Server 2016 knowing that their InfoPath forms will continue to work in their on-premises environments, as well as in Office 365.

The InfoPath 2013 application remains the last version to be released and will work with SharePoint Server 2016.”

So, while it’s a good thing that InfoPath 2013 will work in SharePoint Server 2016, and will make migrations so much easier, a lot of SharePointers remembered that FoSL vNext was supposed to be released with SharePoint Server 2016 so Microsoft probably didn’t finish it in time.

Those SharePointers were actually quite right, however it might be worse than they expected. In a less mediatized change on Friday, Microsoft did a huge change to their Office 365 Roadmap site. The Forms on SharePoint Lists moved from “In development” to “Cancelled”

According to the roadmap, cancelled means: “Previously planned updates that are no longer being developed or are indefinitely delayed“. So while that doesn’t mean InfoPath 2013 will still be  only option to edit forms until 2023, it does mean that a new version of FoSL will probably never arrive in SharePoint Server 2016, and we probably won’t see it in Office 365 in 2015.

Furthermore, for now, there are no sessions on FoSL on the Microsoft Ignite 2015 conference website, so that adds to the rumor that there is no planned release on anything new. (The only session about Forms in SharePoint only shows up because of the word “platforms”)

VLADI7 2-8-2015 8.29.12 PM

If you are curious to know how FoSL vNext was supposed to look like, here are some screenshots from SPC348.

Dual InfoPath and FoSL vNext on the ribbon:

SharePoint 206 FoSL

The new “Edit Form” view, directly in the browser:

SharePoint 206 FoSL

Moving stuff around in the form, as easy as drag & drop

SharePoint 206 FoSL

New way of viewing list items:

SharePoint 2016 & FoSL

So, even if there was an InfoPath Funeral at SPC14, InfoPath is now back from the dead and will probably be the only way to customize Forms on SharePoint Lists in SharePoint 2016. I really hope we will be able to learn more at the Microsoft Ignite conference this year in Chicago. Meanwhile, if you’re looking for an InfoPath alternative that works with any version of SharePoint and uses mobile apps to fill forms, you might take a look at third-party vendors such as Formotus.

Make sure to spread the word about the future of InfoPath on twitter by clicking on the birdie below:

tweet-button

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

Hello Canadian SharePointers,

KWizCom, a Canadian company that has been very active in the SharePoint Community in the past few years by sponsoring bloggers and various SharePoint Saturday events just shared one of the coolest promotions I have seen in a while in the Tech Space.

http://www.kwizcom.com/special-offers/canadieneh/

During the whole month of February, KWizCom would like to reward ALL Canadian SharePoint users with a production license of ANY KWizCom add-on of their choice! You simply got to send them an email, and you have it! If you’re looking for a SharePoint forms add-on, make sure you checkout my review on SharePoint Community: Review of KWizCom Forms Enterprise edition for SharePoint

To get your free license, just visit the page over here for all the details: http://www.kwizcom.com/special-offers/canadieneh/

What add-on did you pick?

While working on SharePoint 2010 to SharePoint 2013 migration, a site collection with Business Intelligence on it had quite a lot of bugs after being upgraded to 2013.. One of the bugs I found is that in a PowerPivot Gallery, whenever you want to create a new PowerPivot Gallery Document, you get this instead:

PowerPivot Resource File not found

$Resources:PowerPivotFeatures,ReportGalleryDocumentDisplayName;

$Resources:PowerPivotFeatures,ReportGalleryDocumentDescription;

 

After investigating, I found out that you get the same message when you look at the PowerPivot Gallery Document content type.

 

With the info we got in those screenshots it’s pretty clear that the problem is a resource file, but why? The problem is that Microsoft, decided to rename the resource file names between SharePoint 2010 and SharePoint 2013. If you go on SharePoint 2010 in “C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\14\Resources ” You will see that all the PowerPivot resource files are named “PowerPivotFeatures.resx” + language. You can view this in the image below.

 

However, in SharePoint 2013, when we navigate to the resource folder “C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\15\Resources” , we realize that Microsoft decided to change the name of the resource file to “PowerPivot_Features.resx” As you can see an underscore is now added to the name of the file as you can see in the picture below:

Since we got our Site Collection from SharePoint 2010 to SharePoint 2013, everything still references the old resource file, which does not exist since you migrated. Unfortunately, Microsoft did not automatically fix this when you attach the Database, or when you run the “upgrade-spsite” command.

 

I fixed the problem by simply copying all the “PowerPivotFeatures.resx” files from SharePoint 2010 to SharePoint 2013. Since the filenames are different, you won’t have to override any SharePoint 2013 ones. So when you copy them all, your folder will look something like the screenshot below. Notice the SharePoint 2013 resource files in blue and the 2010 ones in Orange.

 

I would do this during off hours as you may need an IISReset in order for SharePoint to pick up the new resource files.

Drop a comment if this helped!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.