Ryan Dennis is a SharePoint Solution Architect with a passion for SharePoint and PowerShell
Today I had the privilege of presenting at SPS Cincinnati for the 5th time!
SPS Cincinnati holds a special place in my heart, as it was the first event I ever spoke at. My session was one of my favorites, an ECM talk based on a real-world scenario of leaving the file share mentality, and moving onto an ECM solution in SharePoint Server.
Over the last two days, I’ve had the privilege of presenting at the Dog Food Conference for the 3rd time!
My presentations were focused more on the business user, or power user in both cases. The first day, I presented a new topic that I hadn’t yet shared with the world. Day 2 was one of my favorite sessions, an ECM talk based on a real-world scenario of leaving the file share mentality, and moving onto an ECM solution in SharePoint Server.
I finally had some time to build my first SharePoint 2016 virtual environment, using the IT Preview bits w/ SQL Server 2014. Being a PowerShell guy, one of the first things I did – after running AutoSPInstaller of course – was open up PowerShell to start exploring the module snap-in. The first thing I wanted to take a look at was the number of cmdlets, because I knew there would be at least a few more than SharePoint 2013. Of course there are! There are actually 115 new cmdlets.
How did I figure that out (aside from checking out the aforementioned MSDN link)? Simple, run:
Get-Command -Module Microsoft.SharePoint.PowerShell | Measure-Object
Running the above returned 825. Eight hundred and twenty five commandlets! Very cool, but now I’m curious what are some of the new nouns that we administrators can run PoSh against? Taking a quick glance through the cmdlet list on MSDN, it was pretty obvious and expected to see lots of Azure, Office 365, and Project Server.
Sure, I can see an absolute need for those things. But out of curiosity, what do we have that’s not in those categories? Here are some of the commands that I am curious about, but haven’t been able to dig into yet. Also interesting is that the Help information for the cmdlets doesn’t appear to be baked into the snap-in yet:
Out of the list above, there are some interesting capabilities. I could guess as to what some of these might do, but instead – I’ll look into them some more with a plan of updating this post with some more detail. That is of course unless Microsoft (or other community contributors) releases some Help information on them.
Happy PowerShelling!
The WordPress.com stats helper monkeys prepared a 2014 annual report for this blog.
Here’s an excerpt:
The Louvre Museum has 8.5 million visitors per year. This blog was viewed about 77,000 times in 2014. If it were an exhibit at the Louvre Museum, it would take about 3 days for that many people to see it.
I have been quietly working on a Codeplex solution for about a month. The reason I started down this path was to give myself a goal that I could shoot towards from an application development perspective. The application that I ended up building is one that should fill a couple of gaps, primarily from an administration perspective – for on-premise SharePoint 2013 deployments. While every SharePoint Site Collection must live in a Content Database, it is sometimes not thought about up front/during the initial roll-out of a SharePoint farm. What may end up happening is your company might have 1 Content Database, with dozens/hundreds/thousands of site collections stored in it. These can grow to be very large, making maintenance a nightmare from a SQL Server perspective – but also making upgrades & migrations difficult. Continue reading “SharePoint Content Database Manager”
SharePointRyan 
You must be logged in to post a comment.