Description: The article is about using the portal office 365 to manage the cloud. The author shows us how to operate that software. He gives us many details and notifications for our own operation. People can benefit a lot after reading this article and successfully manage that software.
You are looking at the sky because today we’re going to talk about managing the cloud. Today I have the distinct honor of introducing you to Jim Emond. He’s a second M secure infrastructure PFE extraordinaire and he’s going to talk to us about managing the cloud or managing office 365 with SCCM.
I promise the solar eclipse want to fake anything. It looks like you’re in your home office today. I try to work from home as much as possible considering I’m on the road most of the time. You and me are the same. I think this is week 10 where I’ve traveled. Next week I’m not going anywhere and I am excited about it.
We talked briefly before and one of the things that you asked me was I want you to do powerpoints or demos. I said I love demos. I’m excited to see what you brought with you. I always prefer demos. I assume that one of the reasons why we’re doing this in your home office is you’ve probably got some great Azure connectivity and you’ve got some cool stuff to show. I have your connectivity but this one is running on my home lab. But it can run or function the same up in his. I’m going to let you get to it. I love demos and I’m not going to hold anybody back.
We’re going to move on to the demo portion of today’s conversation. I want to start by showing you inside the SCCM console. This is the office 365 client management power BI dashboard. From this dashboard,it is going to give you a high-level overview of the office 365 or click to run clients that you may have inside your environment. It’s going to show you your office 365 and the number of clients that you have or your office 365 explicit or click to run client version that you have.
If we scroll down a little bit you’re going to have multiple languages. It’s also going to show you all of that information at your fingertips. If we keep going down,it’s also going to show you all of the different channels that you have whether you’re doing current channel,deferred channel,first-run channel. You’ll be able to see all of this data on your fingertips.
You are not only going to see that inside the power BI console but also going to see your deployment statistics as they relate to your office 365 deployments within your environment,he number of successful runs errors and the number of machines that you have targeted. They may not have installed yet. You might wonder how can you get all this wonderful data to appear your power BI dashboard. There are a couple of minimal steps that are required in order to make all of these work.
The first thing that we need to do is we need to enable SEC and make sure they are able to download the office 365 click to run installers and or updates. In order to accomplish that,I’m going to select administration. If I go ahead and expand site configuration,select my site. As this populates,you can go ahead and select my site in middle window. You can click and select configure site components.
We’re going to select software update point. Once inside of our software added a point,we need to go to our products tab. If we go ahead and scroll down this list,you’ll see our office 365 client. That’s affectionately going to be called the click to run. That’s what we need to synchronize from the Microsoft Update catalog into the SCCM database in order to make all of this possible and capable.
I have pre-selected that and downloaded that data inside of SCCM so I’m going to cancel this quickly. We also need to enable the office 365 click to run client and make it be able to receive its updates from SCCM. There are several different ways to accomplish this goal. Prior to SCCM 1702,you had to download and enable the office comm the office management comm and you can do that inside of your configuration XML.
If we open this up,you’ll notice that I have the office comm,object set to true and that’s going to enable SCCM to be able to take over management of that office click to run client. If you already have office 365 deployed in your environment,you can very easily script this out and deploy that to append this configuration file. You can also control all of this directly inside of SCC and from your client settings. We will go to administration and then client settings. I’m going to open up the default client settings. You need to click and select properties.
On your software updates tab,if we select that and then scroll down a little bit,you’re going to notice the enable management at office 365 client agent. You can go ahead and set this to yes. Now you have two available ways in order to enable SEC them to manage the click to run client within your environment. If one of those previously mentioned ways don’t work,you can easily do it from a group policy perspective. Let me switch over to my domain controller.
I have pre-loaded the office 365 2016 administrative templates inside of my domain controller,but the line that I have highlighted is office 365 client management. If you open this up,all you have to do is set it to enable. What that’s going to do is it will set a registry key value on your clients. We have now given you two different ways to enable the office column object for the click to run client than office.
Let’s go ahead and demonstrate how you can build a deployment directly inside of SCCM in order to install office 365 err clicked around within your environment. If we go to software library and select office 365 client management,you’ll notice we have an office 365 installer. We need to select this plus button quickly,go ahead and give this a appropriate name. We’re going to demonstrate the office 365 current branch.
I need to give it a storage location quickly. The storage location is the location that aiccm is going to download the bits for installation and use for distribution. If I select that folder,it tells me that it must be empty. We’ll fix that quickly. We have a new folder to store all of our installation bits.
I’m going to select next and I’m going to manually specify the office 365 client settings. Within your environment,if you’re already running office 365 and maybe you already have it deployed and you’ve done some customizations to your configuration dot XML,you can easily select the option to import those pre-existing settings for your environment. For the purposes of this demonstration,we’re going to manually specify.
You can choose next and we can select all of the appropriate products that we want to do. You will notice on the bottom that you can also automatically install Visio or product project if you choose that. so I’m going to choose next.
We have our 32 bit option and 64-bit option. You can select your channel whether you’re doing current deferred,first release current or first release for a deferred. For the purposes of this demonstration,we’re going to do current and we’re going to choose the latest and greatest build. In the bottom,you have several different options you can accept the EULA the end-user license in your agreement.
You’re going to have to accept this whether it is on your endpoints or whether you do it from the server level. So we’re going to go ahead and select it from the server level. I’m going to go ahead and select Auto out activation. It’s automatically going to register and activate my office in solution.
You need to select next and I’m going to say yes. I want to deploy this application now. I’ve to select my collection in which I’m going to employ this application so I am going to deploy this to a device collection or system. I have a collection pre-built here,the Windows 10 office 365. You need to select OK and select next. This is getting the content out there on my distribution point.
You need to remember that from an SCCM perspective,a distribution point is nothing more than a fancy file server. This are my enforcement actions. I’m going to install this as required or making it available. For the purposes of this demonstration,we’re going to make it available. Am I scheduling? Because it’s available.
I’m not going to enforce policy or automatic installations.This is the notifications that my end user might see. For the purpose of this demonstration,we’re going to display in software Center and show all notifications. We don’t necessarily need alerts so I’m going to say next. This is a summary. You always want to read through your summary and make sure that you’re doing what you think you’re doing.
Most importantly you need to aware of the product that you’re deploying and even more importantly the collection in which you’re deploying it to. We hate to send a installation of Visio to your whole environment. That SCCM has automatically downloaded our installation bits. I can leave and look at the application which builds for us. In order to accomplish that I’m going to select software library,expand application management and select my applications top level.
We have built office 365 underscore 1704. Like any other application you can build inside of SCCM,it has all of the necessary properties,deployment types that you might require. If we cancel here,we’ll switch over to a client machine quickly so that you can see what that will look like for installation. You can go ahead and get this load. I have opened up the SCCM Software Center where all applications are going to be published for installation.
If I select this,I can simply select install. In a second you’re going to see the office click to run window pop up and it will begin the installation. A lot of my customers have asked me on the regular basis that what will happen if I have several different channels within my environment. For example my production environment is going to release ready. But for testing purposes,I need to choose current release.
You can accomplish that by simply setting a registry value which will tell SCCM and the office click to run client what branch it will be. In order to control that from SCCM,let’s switch back. You can do that in several different ways. You can accomplish this goal with group policy,a script or any other various ways. What I’m going to demonstrate for you is keeping everything within SCCM so I’m going to go to assets and compliance, choose expand compliance settings,select expand configuration items.
I made a little folder for office 365. I have my different configuration items that will deploy for my environment. We’re going to open up the current channel for a demonstration purpose. You’ll notice if we go to our settings tab and if I open this up,then this registry value in this location hockey local machine software Microsoft Office click to run configuration CD in base URL needs to equal this particular web address.
Does this mean that the office click to run Cline is going to go out to the web in order to download its updates? No. It means that we are specifying via this register setting for what updates the office 365 client will accept. That be current channel,feature release channel or deferred channel. That’s the way that we can identify it. If you want to get fancy you can go into SCCM and then build your collections based on those registry values and then do automatic deployment rules in order to keep your environment up-to-date as possible.
I’m glad that you’re enjoying it. I’m enjoying it. I don’t know what software you’re running during the presentation but when you click on something and you get that little pulse that shows you what you’re clicking on,that’s very cool too. It requires you to be able to multitask with both hands. It’s a setting within Windows. You can tell it anytime you press your control key. Then it’s going to give you that little accentuation mark. I didn’t know that.
The one last thing that I want to show you is this. I’ve shown you how to identify your release channel. I’ve shown you how to download and install it for deployment. I need to keep it up-to-date. We can do that in an automated fashion. If I go to my software library and select office 365 client management,you’ll notice that I have a create ADR,ADR stands for manic deployment rule. If we select this and give it an appropriate name and Channel,I’ve got a target a collection. I have a pre-built collection for office 365 current channel,you need to select OK.
I may have done this once or twice before. I already have a pre-existing ADR with that name so we can select next. We will see the success and error messages in that way SEC is aware that it installed successfully or if I had issues. I’m going to automatically approve my licensing at the server level so my end-users will be unaffected. I need to select my product. I’m going to do date release a revised. That is not necessarily required so we’ll skip that.
It will be superseded.For my product,I need to find office 365 client. I’m going to say superseded. I’m not getting any of the older patches. If I select my preview button,we will have all of the different office 365 channels available to use. If I want to filter this down, I can go ahead and add a title here. Let’s filter this down a little bit. It’s getting better shot. Now we choose preview.
My list is drastically shorter and I’m only going to show anything that has a current channel. By the process of filtering out,we can quickly and easily eliminate all of the ones that are not appropriate for my environment. Let’s select close. I’m going to set this up to run on a schedule. I want to update them by my environment monthly. I’m going to select the third Wednesday of every month. And I will select OK,select next.
My deployment schedule is my enforcement schedule of how quickly and how often I want these updates to install within my environment. I will select next. I want my users to be notified of anything that I’m doing within their environment. If that’s not appropriate for your environment,you can always hide all notifications if necessary. I will select next. We don’t need to lurks for what we’re doing for the purposes of this demonstration. I’m going to tell what deployment package I want to use. We’re going to select OK.
For the next download location,I’m going to pull these updates from the internet or Microsoft and select next. You can select any in all appropriate languages as they adhere to your environment. Now we get a summary page. As always I’m going to verify the collection in which I’m deploying to,what is going to be deployed and my schedule as well. If I select next now,SECM is going to go out there and download all of the appropriate updates for me. It will automatically deploy them within my environment as well. From a high level,you have now configured air environments. You are not only able to download and install office 365 click to run,you can also keep it updated in an automated fashion as well.
That’s very cool so we can treat office 365 endpoints like any other network endpoint essentially. It is correct. Is there a minimum version of SCCM that they need to be able to do this is functionality? Or is that widely available in the latest version?
Some of these capabilities are available in 1610 but to be able to accomplish everything that we go over in today’s demo,you will need to running 1702 minimal. That’s awesome. Is there a good website or document reference that you can share with us so that if somebody wants to learn more about this they can go read up on it?
I’ll be more than willing to add those different websites in the abstract section for our customers be able to reference. Thank you so much for that demo. That was awesome. Thank you very much for having me on the show and hopefully our customers get some benefit here. This is definitely informative.