Howdy – So while I have neglected the blog for the last month I can say I have not neglected writing. Quite the opposite. I have been working with the fine folks at Petri.com to write some content for them. In no way does the mean I am abandoning this blog just that is my reason for the neglect for the last month. 🙂 And while we are talking about neglect my YouTube channel has also been neglected because my mic broke. Supposedly the new one is in the mail. I am not holding my breath, though.
I love teaching. I have often said that if everything in life paid the same, I would be a High School teacher and coach the volleyball team. But, since that isn’t how things work I have found a better outlet for my desires to teach. SharePoint classes.
As many of you know, I have been teaching SharePoint Administrators all over the world since 2004. Wow, I think that makes me really old at this point. 🙂 But over those years I have easily taught 10,000+ people the fun that is SharePoint.
So it is high time I get off my butt and return to the classroom. And to prove I am not old I am going to embrace that fancy internet thing and teach the class live, online. Recorded demos are for wimps.
The class will be ten sessions the week of Dec 5, 2016, and will also include six hands-on labs that are written to be run in your own environment, not a pre-made fantasy VM. That way you can use them for as long as you want, not just for a week.
If you are interested, please take a look at the class site SharePoint Administrator Training. It includes a detailed breakdown of the schedule, the modules, and hands-on labs. Also, as a thank you, you can get a 17% discount for the course by using the code “Blog” at checkout.
I will admit it; I put this off for as long as I could. Why? Because I just wasn’t really sure what went into getting connected to my O365 subscription and I knew that there wasn’t a lot of cmdlets there. Good news I have solved both of these problems for you. The following will get you up and running with O365, Exchange Online, Skype for Business Online (Lync Online) and SharePoint Online.
Also, Microsoft does have a website that covers getting started with PowerShell. http://powershell.office.com/ You can find most of this stuff written there, just not with my fun comments along the way.
Making sure you are ready
You need to have local administrator access to install the following items.
Your PowerShell execution policy needs to allow remote scripts
Open PowerShell by right-clicking and running as administrator.
Get-ExecutionPolicy will tell you what you currently have. Restricted will not work.
If you are Restricted, then you will have to lower your policy. I recommend the following.
You need to be an O365 administrator to run all of the cmdlets.
The things you need to install
There are four pieces that you need to install. And the good news is they are all next, next, finish. 🙂 Only decision you need to make is do you want the 32bit or 64bit versions. The good news is the 32bit stuff is deprecated so I am 99% sure you want the 64bit.
It would be rather rude if I didn’t help you also get logged in since that is probably a little more confusing than the next, next, finish of above. Remember you don’t have to connect to everything, every time. If you just need to create a Site Collection, then you can just do steps 1, 2, & 5. Also, a reminder I do a MUCH BETTER job explaining this stuff in the video.
Open PowerShell as an administrator
Set a variable with your credentials. That way you don’t have to keep typing in that long and secure(?) username and password.
$credential = get-credential
Connect to the Management of O365
Connect-MsolService -Credential $credential
Connect to Skype for Business Online (aka Lync Online). For these cmdlets, you are using PowerShell Remoting and running the cmdlets against the server in the cloud. So make sure when you are done you kill your session. If not you can lock out yourself or others until the sessions expire.
Use the following to remove your session when you are done working with Skype
That will do it. You can now PowerShell against O365 until the cows come home. I have some videos/posts in the hopper that will take a deeper dive into using this stuff. This post was just to make sure you could get started.
Seems like something reasonable anyone using Azure would want to do. After all, one of the draws of “the cloud” is automation. So I thought I would throw together a quick video and blog post on how to do it.
The long story short is it really only takes two cmdlets:
But unfortunately, it isn’t always quite that simple.
Why two modules?
The AzureRM module is the latest greatest and installs the Azure Resource Manager cmdlets. That is all of the fancy new stuff. The easiest way to equate it, though not completely accurate, is it is the same as the new portal.azure.com environment. Anything, new and fun going forward is being done with Azure Resource Manager. 1,398 cmdlets to play with.
The Azure module is the old service manager cmdlets. Anything that you do in the Azure portal that is called Classic or old is what this module represents. While if you are new to Azure you should be able to avoid most of this stuff some features haven’t made their way to the RM module yet so good to go ahead and install these. 708 more cmdlets to enjoy.
If you want a better explanation of what the module are and do, then you can read this Microsoft Azure documentation. It does a good job of explaining what it is doing but it doesn’t do a very good job of explaining how to install things. So that is where this blog post picks up.
Step 1: Permissions
To install these modules, you will need to run your PowerShell session as an Administrator. Also, you will have to be running an execution policy of RemoteSigned or less. For Windows Server 2012 R2 this is the default. If you are installing on your Windows 10 machine though the default is restricted so you will need to change it.
To find your current policy you can use:
If it is set to Restricted, then you will need to run the following cmdlet to change it with following:
Unfortunately, the Azure cmdlets will only run with RemoteSigned or greater permissions so you will have to leave this changed going forward.
Step 2: Installing the Modules
Now that you have permissions set you can simply run the following:
If this is the first time installing a remote module, then you will need to type Y to accept the NuGet module.
Then you will need to type Y again to say you trust the repository.
Once that finishes you will need to install the old modules (which are updated) with:
Install-Module Azure -AllowClobber
The reason for -AllowClobber is the two seems to bicker. So I just let the Azure module win and move on.
You will have to type Y again to say you trust the repository.
After a couple of minutes, you will have both modules installed and you will be ready to go.
Step 3: Logging in
Seems like a great next step.
To login to AzureRM use the following:
Now you will need to enter your Username and Password in the popup authentication box. After a few flashes, you are in.
To login to Azure Service Manager use the following:
The same process of logging into the authentication box that popups up and you are in business.
Step 4: The scripts that made me figure all of this out.
Running resources in Azure cost money and I don’t think anything quite runs up your bill like Compute. Unfortunately for me the main thing I do with Azure is use Infrastructure as a Service (IaaS) and incur all of those Compute charges. Since my money tree still isn’t growing in the back yard I try to minimize this spend. To do that I have created scripts for starting and stopping my Virtual Machines (VMs).
That script will deallocate your VMs compute resources (release its IP Address for example) which will save you compute charges. You will still incur storage charges, though. If you don’t want to deallocate the compute resources then you can add the -StayProvisioned option.
If you are still rocking Old School aka Classic VMs then you will use this to start those VMs:
There are about a million (2,106) more things you can do now that you are connected to your Azure account with PowerShell so go forth and learn. Other resources to help you out if you aren’t terribly comfortable with Azure and or PowerShell yet.
Looking at my YouTube content it has been brought to my attention on Twitter that I don’t have a video that people expect. How to install SharePoint Server 2016 on Azure IaaS. Whoops. I realized that I have all of the pieces I just haven’t put the story together. So before I bust out the camera, microphone, and makeup (just kidding) I thought I would put together a blog post that gives you the plan in the short term.
In Azure, you will need to create a minimum of three VMs and you will need to put those VMs in the same Resource Group to make your life easier.
Create a Domain Controller VM
Create a new resource group
Give it a static IP
Update Azure Networking with static IP for DNS
Will be a domain controller for your new forest and DNS server
There you go. If you want a guide through the whole process, there it is. The good news is I see how that is annoying and that the SharePoint videos are shown with Hyper-V. So next week I will sit down and reshoot all of this 100% from Azure.
If you do watch any of these and have ideas or suggestions on what I should do differently or better, I am all ears.
As you probably know last week the September 2016 Cumulative Updates were released. Before you go installing them there are some things you need to know.
If you are the type who reads all of the KBs associated with the updates and the warnings they contain then kudos to you but since most people just download and install we need to have an intervention. Why? Because this update makes some pretty significant changes under the hood to SharePoint. And while those updates are important for SharePoint going forward (some are guessing this CU will be required to get future updates) they make the patching process take FOREVER this time around. It took me close to 3 hours to patch my single server test environment with no content. That is crazy long. And it isn’t just running psconfig it is all parts. Here are some of the outliers.
Running sts2016-kb3118289-fullfile-x64-glb.exe took 1 hour and 32 minutes
Step 9 of config wizard took 31 minutes (August update it took 7)
Step 10 of config wizard took 18 minutes (August took 1 minute)
So the reason I point out these long times is it is real easy to think something is broke. Which might cause you to do something like use Task Manager to kill off one of these process which would lead to fire. So be calm and patient as you work through the process.
More bad news if you have on-prem MySites. Part of those is a site collection called https://sitemaster* gets created to allow for fast site collection creation. Well, that site collection causes a warning because it doesn’t get upgraded. My gut tells me this isn’t an issue and I am trying to confirm that but still another uneasy feeling when you are done.
Do you have challenges with what is the correct way to install SQL Server for SharePoint? What features do you have to select? How should you configure the service accounts?
Or maybe installing SharePoint is fine but you don’t understand things like Max degree of parallelisms or what holes to punch in the firewall? No problem.
I have created two separate videos for installing SQL 2014 and SQL 2016 for SharePoint. Both videos use the 180-day trial so you can play along at home without a license. Good news is the steps are exactly the same if you are using a real license.
Neither video is going to make you an expert but they will get you to a solid point that makes SharePoint happy.
In case you are wondering this is completely different than the Quick and Dirty install video. This video goes through all of the steps to build a production grade install of SharePoint.
What? That seems really confusing. How do you do on-prem SharePoint 2013 on Azure? You use IaaS (Infrastructure as a Service) of course.
In this video, we start with nothing and build out all of the pieces to install SharePoint Server 2013. While the video shows it how to do everything in Azure you can adapt the steps to do an install inside your own network just as easy.
We create a VM DC1 and set a static IP
We make changes to the Azure Virtual Network
We DCPromo the server and create a new Contoso.com domain
That should do it. Walk through all of that content and you can have a SharePoint 2013 Server up and running in Azure. Pretty awesome!
For this video, there is also a premium guide available. The premium guide just documents all of the steps in an easy to following guide with numbered steps, bolded actions, and screenshots. Additionally, it includes automated PowerShell scripts that allow you to avoid all of the typing demonstrated in the video. Finally, there is a script and Excel file that will create the active directory accounts for you. It is preconfigured to create all of the accounts in the video but is easy to update to add additional accounts for testing or to change the names to meet your domain standards. For more information, check out http://www.boldzebras.com/youtube
Let me know what you think and if you have suggestions for future videos.
What fun. For some reason this weekend I got inspired to do a quick and dirty install of SharePoint. I originally wanted to call it what not to do but that seemed to negative.
The idea is I plow through a way to get SharePoint 2013 up and running in Azure as quick as possible. The video turned out to be about 27 minutes to show what took me 1 hour 7 minutes to do. I also incorporated something new on this video. I run a stopwatch the whole time that you can see you know how long things are taking in real time vs. produced video magic. I take a lot of pride in cutting out every second or ten of screen waiting time to make the videos as short as possible. Hopefully you enjoy the timer that shows that off better.
In case you are wondering what a quick and dirty install using Azure looks like here is the outline:
Create a domain controller on Windows 2012 R2
Set a static IP
Update the virtual network to reflect the IP
Create two service accounts
Create a SQL 2012 SP3 Standard VM using template
Add it to the domain
Update security to give domain admin system administrator role
Create a SharePoint Server 2013 VM using template
Create the farm using configuration wizard
Configure the service apps using the wizard
At the end show you the train wreck it creates in SQL
Keeping up with the cumulative updates (CU) and service packs for SharePoint has always been fun. There is always the question of what build are you on and what build should you be on.
To help keep track of the build numbers Todd has always had a great resource available at his blog. http://www.toddklindt.com If you look up in navigation you will see he has SharePoint 2010, SharePoint 2013, and SharePoint 2016 builds all covered. He has the build numbers, the links to the various Microsoft Knowledge Base articles for what is in that build, links to download the updates, and finally any notes or bugs he knows about for a given resource. The site is top notch.
Since Todd has all of those bases covered I thought I would try to help out by creating videos on how to install each of the CUs and any added information I could share. To make it easy to find I have put all of the 2016 update videos in a playlist. That will always give you easy access to the latest and greatest. As of right now I have covered June, July, and August 2016. The nice thing is there is some variety in there.
·The July 2016 cumulative update for SharePoint Server actually shows up in Windows Update so if you aren’t paying attention you can actually install it on accident. This video shows you that process and how to tell if that is what happened to you.
As additional updates roll out I will continue to create videos. In theory they should all be the same steps with just different bits but we all know SharePoint better than that. There will be curve balls.
In each video I also try to discuss that you shouldn’t just apply and update because it is available. You need to have a rhyme and a reason and even then it can be dicey. You have been warned.
Also, with my updates I concentrate on how to install it and just work through the process. This method while effective does lead to downtime. If you are looking for Zero Downtime Patching (ZDP) then you should watch this fine video by Microsoft. They have a multi-server farm in Azure and walk you through how to patch with no downtime. Pretty cool stuff if you have a farm of that size.
I think between watching that video and one of mine you should have a great understanding of how patching really works in SharePoint. They show you the uber complex process but without all of the context and I show you the simple process but try to break down each step a little better. A winning combination. J
Shane Young here to make all of your SharePoint and Azure dreams come true.