I hope you’re as excited about Operations Management Suite as I am! It’s seriously one of the coolest cloud offerings Microsoft has released this year.

Microsoft is working on some great ways to integrate it to your on-premises System Center deployment (some integration features are in preview right now), but let’s get around to getting the Monitoring Agent deployed via SCCM.

For those of you that are already app deployment experts, here’s the quick and dirty:

Install String: MMASetup-AMD64.exe /Q:A /R:N /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=<workspaceID> OPINSIGHTS_WORKSPACE_KEY=<workspacekey> AcceptEndUserLicenseAgreement=1"

Uninstall String: MsiExec.exe /x{742D699D-56EB-49CC-A04A-317DE01F31CD} /qn

Detection Method: Windows Installer - {742D699D-56EB-49CC-A04A-317DE01F31CD}

You can find your Workspace ID and Key by logging in to your OMS Portal and navigating to settings. Find Connected Sources, and your Workspace ID and Keys will be listed below the Download Windows Agent buttons.

If you’re not an SCCM app deployment wizard, let me paint you a picture with words (and pictures):

Copy MMASetup-AMD64.exe into your sources share in SCCM.

Create a new application, and select manually specify.

Fill out all the details for MMA.

Leave this section at defaults, but add an icon if you’re fancy.

Add a deployment type.

Select Script Installer, and we’ll manually specify the deployment type information.

Give the deployment type a catchy name

Fill out the following:

Content Location – the full path to the sources share on your SCCM server

Installation Program - MMASetup-AMD64.exe /Q:A /R:N /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=<workspaceID> OPINSIGHTS_WORKSPACE_KEY=<workspacekey> AcceptEndUserLicenseAgreement=1"

Uninstall Program - MsiExec.exe /x{742D699D-56EB-49CC-A04A-317DE01F31CD} /qn

For the detection method, select Windows Installer, and use {742D699D-56EB-49CC-A04A-317DE01F31CD} as the product code (leave the brackets in!).

Configure the User Experience as below.

Next through the remainder of the dialogs, and you’ll be ready to distribute and deploy! You go!

Happy monitoring!

Here it is. We’ve waited through multiple releases of Windows 8 for a version of Windows that can truly replace Windows 7. Meet LTSB.

Microsoft has gotten super serious about their release cadence lately. You’ve seen it with Office 365, you’ve seen it with System Center, and we’re going to start seeing it with Windows 10 as it’s more widely adopted within business. Microsoft is transitioning away from a product generation-based release cycle to a more release-ready cycle. What does this mean for us as IT admins? It means regular new features, but also regular interruptions as Windows 10 updates its build, and also potential operational issues.

How often does Microsoft update Windows 10? The answer is in typical Microsoft fashion: “well, it depends..”. There are currently four public branches to Windows 10:

Insider Preview – gross, don’t even consider this for production.

Current Branch – The build that every regular consumer gets.

Current Branch for Business – The build that you get when you check the “defer upgrades” check box - regular people can get this too.

Long Term Servicing Branch (LTSB) – The Holy Grail, Mack Daddy, Big Kahuna, end all be all most awesomest Windows build for business. Only us IT professionals can get this because we're way cooler than everyone else.

Why is it so awesome? First of all, support. Microsoft has updates separated into two categories: Feature Upgrades and Servicing Updates.

Feature upgrades are the big upgrades, like the Windows 10 Anniversary Update due out next week, that contain all the shiny new features that Microsoft hypes up.

Servicing Updates are the security and OS patches we’re used to. These will continue to be released on Patch Tuesday (Microsoft wants me to call it update Tuesday instead) for builds of Windows that are still in support.

...

Still in support.. I know what you’re thinking. “I thought Windows 10 would be continuously supported since it’s continuously updated!”. This is where it gets weird.

Here’s Microsoft’s support lifecycle for the Current Branch for Business build of Windows 10:

Yep. This means that you effectively have MAYBE a year’s worth of support before you have to update your devices. It could be more, it could be less, depending on how often Microsoft releases their Feature Upgrades. They guarantee a minimum of 8 months of support.

Here’s Microsoft’s support lifecycle for the Long Term Support Branch build of Windows 10:

10 years. There’s really not much more to say than that.

LTSB (technically Windows 10 Enterprise 2015 LTSB, as of 7/29/16) also leaves out a majority of the “Modern” Windows functionality, such as the app store and most built-in Modern apps (like the Edge browser). You may still side-load Universal Windows Apps via powershell or MDM such as System Center Configuration Manager or Windows Intune.

You do have to be licensed for Enterprise editions of Windows to use LTSB; though this may get a lot easier with the introduction of Windows Enterprise as a Service, available from Cloud Service Providers (like the amazing people at Dalechek Technology Group) soon.

Microsoft suggests that there are “few, if any, scenarios where an organization would use LTSB for every PC”. Over the months of deploying LTSB, I’ve worked with many IT professionals that are crazy excited about deploying LTSB verywhere, when they would never consider deploying Windows 10 CBB.

I’ll fully admit that LTSB definitely isn’t the best choice for tablet devices such as Surface. On those platforms your users will definitely want regular new features and full-screen Modern App functionality. However, for the remainder of your regular workstations and business-critical Windows clients, consider LTSB. Hit me up in the comments if you’re as stoked as I am.

Now get out there and play with LTSB! See you next time.

Deploy Microsoft Operations Management Suite (MMS/OMS/MMA) Agent with SCCM

Windows 10 Enterprise LTSB – this is it.