Saturday 13 May 2017

Disable and Remove SMB1 via ConfigMgr Compliance Settings

In the wake of the recent WannaCry worm wreaking havoc across the globe, I thought I'd knock up a quick set of Configuration Manager compliance settings and a baseline to easily disable and remove SMB1 from devices within an environment.

Just as I started to gather the information I would need about the various settings, I noticed that Alex Pooley had already documented what I was about to do.

You can find his blog post with his methods here:

There's not much value in me repeating all of the steps in this post, refer to the excellent work that Alex has already done.
However, I've made some minor changes to some of the PowerShell, set names consistently, tested it and exported it as a cab file for easy import into other environments.

Download from the TechNet Gallery here

This baseline will perform the following:
  • Disable SMB1 on Windows 8 & Server 2012 or newer
  • Remove SMB1 on Windows 8.1 & Server 2012 R2 or newer
  • Disable SMB1 Client on Windows 7 & Server 2008 R2
  • Disable SMB1 Server on Windows 7 & Server 2008 R2
Importing the cab file should give you a new folder named Security with 4 CI's within it.

These CI's are mainly using PowerShell scripts to discover and then remediate the various SMB1 configurations on the relevant Operating Systems except for the disabling of SMB1 (Server) for Windows 7/Server 2008(R2) which uses a registry value check and set.

These 4 CI's are wrapped into a Baseline called "Disable SMB1" that you can find in the folder named Security. This baseline then needs targeting at a collection that you would like to disable/remove SMB1 from.

I've run it across my estate, but I do only have 2012 R2 and Windows 10 devices. A few devices are reporting script timeout errors and I still need to dig into those further, but overall it runs fine and successfully disables SMB1.

Tuesday 12 April 2016

OMS and Solution Data Flow

Since the beginning Operations Management Suite (OMS) and System Center Operations Manager (SCOM) have been able to work in conjunction, by that I mean you could have SCOM and it's agents reporting data up via the management group into OMS for analytics.

In fact, way back at the very start before it was OMS, that was the only method, but I digress.

We also have direct connected agents for those environments where SCOM isn't present, but OMS can still add great value giving the flexibility for customers who don't want/require the overhead of managing SCOM.

In the early days, if you were doing a Hybrid SCOM/OMS deployment, all was fine, just allow your designated SCOM Management Servers to access the OMS service on the Internet and watch the data flow.

However, as some of the new solutions started to emerge, the data volumes and frequencies meant that going via the SCOM Management Servers wasn't always practical, so certain solutions bypassed the management servers and attempted to upload their data directly to the OMS service.

Not all environments allow direct internet access so thankfully we got the ability to specify a proxy server for the agent, and recently we saw Microsoft introduce the concept of the OMS Log Analytics Forwarder.

So how do you know or decide when/where to use the OMS Forwarder, Proxy or just let the SCOM Management Group (MG) handle things?

Well, there is a nice table on the following TechNet documentation article that halfway down shows you the various solutions, whether they can upload via a SCOM MG or require direct upload (which can be done via proxy/forwarder).

Because I found the layout of the table a little "meh" and as I'm  much more of a visual person, I decided to try and map the data out in Visio, more for my quick reference than anything.

N.B. I've only focused on the Windows based agents here, Linux is basically direct agent based only.

OMS Solution Data Flow
Basically, everything agent based bar Alerts, Capacity and Configuration Assessment can be done via direct OMS agent and therefore either direct to OMS, via proxy or via a forwarder.

A gateway is great for areas of your network which may not have internet connectivity (air gapped etc) or maybe you just want to streamline your connections to one device and out rather than multiple servers hitting your proxy server.

The other thing to note is the AD Replication and Wire Data solutions, along with IIS, Windows Security and Windows Firewall log collection don't go anywhere near a SCOM environment. So even if you are using your SCOM environment in a hybrid deployment with OMS, take note that you still need to handle the data upload for these solutions as you would if they were direct attached agents.

I've also included an embedded Excel version of the table that allows you to quickly filter the data to see what the requirements are.

Friday 1 January 2016

What's coming for System Center in 2016?

So, 2015 has drawn to a close and 2016 has been ushered in.

While System Center Configuration Manager may have managed to squeeze out of the gates early, we already knew that the wider System Center suite (along with Windows Server as well) wouldn't be seeing a generally available release until 2016.

We still don't have a confirmed date as of yet, but with licensing details (here and here) having been announced and the previews being at the Technical Preview 4 (TP4) stage, if I was a betting man I would place it towards Q3 of 2016 for release.

Based on the TP4 release, what do we know at present?

The Technical Preview is available to download from here:

Well the core components that were in the 2012 R2 release are mainly still staying around to get an upgrade in the 2016 release.

These are:
  • Virtual Machine Manager
  • Operations Manager
  • Data Protection Manager
  • Service Manager
  • Orchestrator
  • Service Management Automation
  • Service Provider Foundation

If that's what's in, what if anything is not getting a refresh for 2016?

Well, App Controller has been deprecated, but this has been known for a while.
The on-premises functions are basically replaced with Windows Azure Pack and, let's be honest, not many people used it for deploying VM's into Azure

A little more surprising, well for me at least, is the removal of Service Reporting.
This was used in conjunction with Windows Azure Pack and gave the ability when used with VMM and SCOM to provide usage monitoring and reporting for billing purposes.

The suggestion from Microsoft is to utilise a third-party utilisation/billing system. So if you needed this functionality I'd suggest starting to look at things like Cloud Cruiser (which has an express "free" version for Windows Azure Pack only deployments).

There are also some other side features/addons for System Center that have finally had the curtains drawn on them:
  • Service Manager:
    • IT GRC Process Management Pack
    • Cloud Service Process Pack
  • Operations Manager:
    • Visio Management Pack Authoring
  • Virtual Machine Manager:
    • Server App-V Support
    • Citrix XenServer Support
    • Vmware vCenter 4.1 & 5.1 Support (5.5 and 5.8 are still supported)

So there's no doom and gloom, a bit of fat trimming, but nothing scary.

Source: Features Removed from System Center Technical Preview

On a positive note, what's new?

Well as expected, all components will be getting Windows Server 2016 support, both from an underlying OS to install on as well as a supported OS for management, monitoring and deploying (where applicable). Also SQL 2014 will be supported as a target for component installation.

Virtual Machine Manager (VMM) is getting the biggest amount of new features, which is quite understandable since it is driven by new features that come in the virtualisation and storage parts of Windows Server 2016.

A high level summary of these features are:
  • Management capabilities for Guarded Hosts and Shielded VM's
  • Consistent naming of VM Network Adapters
  • Easier Logical Switch creation
  • Conversion of standard switches created outside of VMM into Logical Switches
  • Better failure reporting on failed logical switch creation/modification tasks
  • Enhanced Quality of Service (QoS) for storage
  • Support (finally!!) for creating storage tiers for Storage Spaces
  • Support for Storage Spaces Direct
  • Mixed Cluster Support and Rolling Upgrades
  • VM Static Memory Configuration while VM is running
  • Hot  add/remove network adapters
  • New VM Checkpoint support ("Production" checkpoints in Server 2016)

Operations Manager (SCOM) so far in TP4 doesn't have a huge list, but what we are seeing are more and more cool features being lit up within Operations Manage Suite, of which SCOM can extend and integrate to.
A high level summary of these features are:
  • Updates and Recommendations of management packs running in the SCOM environment
  • Further management pack catalog improvements (including mpb support)
  • Monitoring support for Nano Server
  • Maintenance Mode Schedules
  • Performance Improvements

Data Protection Manager (DPM) again doesn't have a massive new feature set in TP4.

A high level summary of these features are:
  • Protect mixed mode clusters
  • New form of change tracking to replace VSS snapshot-based backups - Resilient Change Tracking (RCT)
  • Storage Spaces Direct (S2D) support
  • Virtual TPM support for protection of Shielded VMs

Service Manager (SCSM) has a few new bits in TP4.

A high level summary of these features are:
  • The default Self-Service Portal will be the new HTML5 portal introduced in Update Rollup 8 for 2012 R2 and replaces the Silverlight & SharePoint based portal
  • Support for presence awareness and IM with Lync 2013 & Skype for Business
  • Performance Enhancements
    • ECL Logging can be optionally disabled
    • Grooming improvements for ECL logs
    • Reduction in lag for Incident Workflows (batch size increased)
    • AD Group expansion integrated into AD Connector tasks
    • SQL AlwaysOn installation changes
SCSM also had some updates in TP3 that get carried across:
  • Write collision avoidance to help deal with conflicting changes
  • AD Connector no longer performs a full sync after changing target domain controller
  • MPSync jobs are now more reliable
  • Further performance improvements for connectors
  • AD Connector sync schedules can now be configured to a schedule you choose.
The latest #LyncUp call also announced that the Service Request area enumeration list will get moved into an unsealed management pack (sounds like a small change, but is long overdue!)

Service Management Automation (SMA) has the following planned:
  • Support for PowerShell 5.0
  • PowerShell ISE add-on
  • Native PowerShell script support
  • Designate a runbook worker
  • Caching of Runbooks for more predictable execution

Orchestrator (SCORCH)… don't be expecting anything new for this component in the 2016 release, other than splash screens being changed to say 2016 and some updates to the Integration Packs to support the other System Center 2016 components.

We have however seen the "beta" release of the migration tools for Orchestrator that will allow runbooks to be migrated to Azure Automation.

I have a previous post on the migration tools:

Source: What's New in System Center Technical Preview

In Summary...

The core of System Center remains the same in the 2016 release, with improvements, some new features and OS support but with a strong focus on Cloud based service integration with Azure and Operations Management Suite (which includes Automation, Backup and Site Recovery under that umbrella).

Please keep in mind, all of this is based on Technical Preview information (i.e. beta's) so is subject to change at any point.

Have your say

It's never too late to influence the future of System Center. If you have an idea or a request, make sure you head over to the Uservoice sites and make it heard!

Saturday 26 December 2015

Customising the Service Manager HTML5 Portal

Microsoft have released a new HTML5 Portal, released as Update Rollup 8 for Service Manager, and we again have a few different areas in which to do customisations.

In this post I will outline both the most common basic customisation you will want to do after installation (branding the portal for your organisation) and a slightly more deeper customisation (adding a new item to the side bar).

Basic Customisation:

After a default installation, one of the first things you're likely going to want to change is the basic info.

This consists of:
  • Site Tile (Default Contoso Service Desk)
  • Support Contact Information (Defaults to Contoso Support with a 12345 number).
This is done via the web.config file found in the root of the installation folder (by default C:\inetpub\wwwroot\SelfServicePortal).

Lines 18 - 37 are the ones to focus on (for now) and allow you to change the defaults to something more suitable for your environment.

  • Lines 20 - 23 alter the site title and basic contact information.
  • Line 25 usually gets set to French, so amend to reflect your preferred default language.
  • Line 27 should be changed if you have a custom template that needs using for logging a basic incident request.
  • Line 29 should have been set correctly during installation and will reflect the SCSM Management server to use for all SDK calls.
  • Line 30 controls how much data is pulled back from a query in a request offering
  • Lines 32 & 33 control the timeouts on the caching of information used by the portal (only play with when testing or have a specific need, these defaults should suffice for most)
  • Line 35 will control the upload of telemetry data to Microsoft.
    N.B. Please don't immediately go and turn this off as a knee jerk reaction to "Microsoft are invading my privacy!!". The more telemetry Microsoft can get around usage of the portal, the better they can make it!

Deeper Customisation:
One example of a more deeper customisation is modification of the side bar. For example there may be a requirement to add your own link to perhaps an external site.

In the following example, I'll add a link to the Configuration Manager Software Catalog.

Open the Sidebar.cshtml file in either notepad, or some other editor (Default location is C:\inetpub\wwwroot\SelfServicePortal\Views\Shared\Sidebar.cshtml)

The first DIV section controls the collapsed state of the sidebar (Usually line 13)
   <div class="side_nav_bar col side_menu">

Within this section adding the following code will add a new item:

       <div class="row side_nav_sccm" accesskey="S" tabindex="9" data-toggle="tooltip" title="Software Catalog">
           <span class="icon-Dictionary icon icon-pos icon-medium"></span>

  • Class="row side_nav_sccm" is used to name this section artefact
  • accesskey="" part to bind the icon to the S Key
  • tabindex="" assigns the order of which pressing the tab key cycles through the items.
  • title="" is the text shown as a tooltip when hovering over icon
The span class code is used to choose the icon displayed, in this example I've specified the Dictionary icon using icon-Dictionary which is the same icon used for accessing the Service Catalog at the top of the sidebar.

The list of icons already defined for use in the portal can be found in the main.css file in the .\Content\CSS folder from usually about line 2024. These are basically friendly name mappings for the character codes used within the fonts found in the .\Content\CSS\fonts folder.

You can either reference one of these friendly names, like I have in this example using icon-Dictionary, or dig deeper into the font file, find the icon you like and then create your own friendly name for reference.

TIP: If you can't convert the woff file to a ttf to be able to view it in Character Map, then you might want to check the OneDrive API GitHub site which hosts a copy.

** Updated 12/04/2016**
The link I had previously to the font for use in CharMap is now dead :(

However, thanks to Donato Pasqualicchio @ MSFT, here is a link to this useful cheat sheet for the font:

Back in the Sidebar.cshtml file that we're customising... 

The second DIV section controls the expanded state of the sidebar
   <div class="side_nav_bar_expand col side_menu">

Within this section add the following code to control how the button looks like in the expanded state, along with the URL to use when clicked.

<div class="row side_nav_sccm">
    <span class="icon-Dictionary icon-medium icon icon-pos"></span>
    <span class="icon-text icon-text-pos"><a href="http://ponconfigmgr01/cmapplicationcatalog/#/SoftwareCatalog" target="_blank">Software Catalog</a></span>

Class="row side_nav_sccm" is used to name this section artefact

The first bit of span class code is used to choose the icon displayed, so I've kept it the same as the icon in the minimised state (icon-Dictonary).

The second bit of span class code is used to define the text to show alongside the icon.
It's also here that I insert a URL that becomes the icon text and will open a new tab to the URL when clicked.

Save the sidebar.cshtml file, refresh the page and the new icon should be there and working!

I'm working on some further customisation posts, but feel free to post a comment if there is any specific customisation scenario you would like me to cover.

Wednesday 23 December 2015

Using Azure Automation DSC to configure and deploy the new SCSM Portal (Part 2)

So in the previous post I outlined creating a basic configuration file for DSC to deploy the new HTML5 Self-Service Portal for System Center 2012 R2 Service Manager.

Previous Post:

In this post I thought I'd produce a quick video showing adding a server as a DSC node, applying the Configuration to it and checking the configuration applied.

Also, after the video break, I thought I'd detail a couple of additions I made to the configuration that weren't in the first post.

So if you just watched the video you'll have noticed I added a bit more configuration using something called DSC Resources.

Specifically I used xWebAdministration and xNetworking, both of which can be found on the PowerShell Gallery.

The PowerShell Gallery is the central repository for PowerShell content. You can find new PowerShell commands or Desired State Configuration (DSC) resources in the Gallery.

xWebAdministration Module -
xNetworking Module -

Both these modules contain multiple resources that can be used to aid in configuration.

The cool thing here is modules can be either deployed directly from the PowerShell Gallery into your Azure Automation subscription, or along with custom resources, uploaded as a zip file via the Azure Portal.

You can find them within your Assets > Modules section of the portal.

I'm using from the xWebAdministration module the xWebsite resource to change the port of the default web site in IIS from port 80 to 81 so that I can reutilise port 80 for the new SCSM SSP.

I do this by creating a new xWebsite section named DefaultWebsite and then use the BindingInfo section to declare which port the web site (Identified in the Name = "Default Web Site" part) should be using.

xWebsite DefaultWebsite
    Ensure = "Present"
    Name = "Default Web Site"
    State = "Started"
    PhysicalPath = "C:\inetpub\wwwroot"
    BindingInfo = MSFT_xWebBindingInformation
        Protocol = "HTTP"
        Port = 81
    DependsOn = "[WindowsFeature]WebServer"

Deeper details and resources can be found on the projects GitHub site:

I'm then doing a similar thing with the xFirewall resource from the xNetworking module to create a new firewall rule

xFirewall SCSMSSPFirewallRule
    Direction = "Inbound"
    Name = "SCSM-SSP-Web-TCP-In"
    DisplayName = "SCSM SSP Web Server (TCP-In)"
    Description = "Allow incoming web site traffic to SCSM SSP."
    DisplayGroup = "PowerONPlatforms"
    Enabled = "True"
    Action = "Allow"
    Protocol = "TCP"
    LocalPort = "80"
    Ensure = "Present"

Deeper details and resources can be found on the projects GitHub site:

This is by no means a production ready example, but does give some basics around using some of the built in resources (WindowsFeature & Package) along with some custom resources (xWebAdministration and xWebsite) and where to go find them (PowerShell Gallery).

Also, please note the SCSM Portal still requires both modifications to the web.config file and the Update 1 hotfix installing afterwards.

Tuesday 22 December 2015

Using Azure Automation DSC to configure and deploy the new SCSM Portal (Part 1)

On Nov 10th Microsoft released a new HTML portal for System Center Service Manager 2012 R2.

The installation is fairly straight forward, however there are still some pre-requisites that need to be in place and I also thought it would be good to introduce delivering this via Azure Automation Desired State Configuration (DSC).

The main reason for looking to do this via DSC is also the ongoing maintenance.
Things happen. People can make mistakes, features and roles can be accidently removed.

DSC provides a set of configuration that;
  • should be applied to a server
  • will be applied to a server to bring it into compliance
  • will then continue to check the server for compliance
  • will attempt to remediate and bring it back into compliance should it drift.

So what do we need?

Well the new portal is an IIS site and therefore requires some windows features to be installed. These are:

  • Web-Server
  • Web-Filtering
  • Web-Basic-Auth
  • Web-Windows-Auth
  • Web-Mgmt-Console
  • Web-Mgmt-Compat
  • Web-Net-Ext45
  • Web-ASP
  • Web-Asp-Net45
  • NET-Framework-45-ASPNET
  • NET-WCF-HTTP-Activation45

These can be easily added using a single PowerShell line:
Add-WindowsFeature Web-Server,Web-Filtering,Web-Basic-Auth,Web-Windows-Auth,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Net-Ext45,Web-ASP,Web-Asp-Net45,NET-Framework-45-ASPNET,NET-WCF-HTTP-Activation45

But installation, as I mentioned, is only part of the story. Making sure these features remain in place is where DSC come in.

In DSC we create a "Configuration" file which lays out how the assigned server should be configured.
For Windows features there is a specific DSC Resource we use, aptly named, WindowsFeature.

For each windows feature that we require we use a block like this:

WindowsFeature WebServer
Ensure = "Present"
Name = "Web-Server"

So basically we name the code block with something meaningful (as we may reference later) with the WindowsFeature resource, use the Name property to specify the Windows Feature to check (Use Get-WindowsFeature in PowerShell to check for the name you require) and then use the Ensure property to state whether the named feature should either be present on the server or not (our intention).

Further properties and information can be found here:

So for all our Windows Feature requirements for the SCSM Portal we get:
#Install the required IIS features
WindowsFeature WebServer
Ensure = "Present"
Name = "Web-Server"
WindowsFeature WebFiltering
Ensure = "Present"
Name = "Web-Filtering"
WindowsFeature WebBasicAuth
Ensure = "Present"
Name = "Web-Basic-Auth"
WindowsFeature WebWindowsAuth
Ensure = "Present"
Name = "Web-Windows-Auth"
WindowsFeature WebMgmtConsole
Ensure = "Present"
Name = "Web-Mgmt-Console"
WindowsFeature WebMgmtCompat
Ensure = "Present"
Name = "Web-Mgmt-Compat"
WindowsFeature WebNetExt45
Ensure = "Present"
Name = "Web-Net-Ext45"
WindowsFeature WebASP
Ensure = "Present"
Name = "Web-Asp"
WindowsFeature WebASPNet45
Ensure = "Present"
Name = "Web-Asp-Net45"
WindowsFeature NETFramework45ASPNET
Ensure = "Present"
Name = "NET-Framework-45-ASPNET"
WindowsFeature NETWCFHTTPActivation45
Ensure = "Present"
Name = "NET-WCF-HTTP-Activation45"

Well, that's the Windows Features sorted.
Now please, bear with me here as so far it looks like a lot more work as opposed to that single PowerShell one liner...

Next is the installation of the SCSM Portal.

For this we utilise the DSC Package Resource and it looks something like this:

Name = "SCSM SSP"
Path = "C:\DSC\SSP\SetupWizard.exe"
ProductId = "17F5D20F-47FB-485E-8CFC-4768C3C3F460"
Arguments = "/Install:SelfServicePortal /silent /accepteula /CustomerExperienceImprovementProgram:No /EnableErrorReporting:No /SMServerName:$SCSMSDKServer /PortalWebSiteName:SCSMPortal /PortalWebSitePort:81 /PortalAccount:$Domain\$SCSMUser\$SCSMPassword"
Ensure = "Present"
DependsOn = @("[WindowsFeature]WebServer","[WindowsFeature]WebFiltering","[WindowsFeature]WebBasicAuth","[WindowsFeature]WebWindowsAuth","[WindowsFeature]WebMgmtConsole","[WindowsFeature]WebMgmtCompat","[WindowsFeature]WebNetExt45","[WindowsFeature]WebASP","[WindowsFeature]WebASPNet45","[WindowsFeature]NETFramework45ASPNET","[WindowsFeature]NETWCFHTTPActivation45")

So again, we provide a name for the Package Resource code block (SCSMSSP) and a more friendly name for the Name property.
The Path property denotes where the installation file resides.
The ProductId property is the unique GUID for the application to allow DSC to check for it's presence.
The Arguments property is used for any command line to be passed to control the installation.
Again, the Ensure property denotes if the software should be installed (present) or not installed (absent).

The DependsOn property allows us to specify various resources that DSC should first ensure are compliant before attempting to run this resource.

It's easy to specify a dependant resource, just wrap the DSC Resource type name in square brackets and then specify the name of that feature.
So WindowsFeature WebASPNet45 becomes [WindowsFeature]WebASPNet45.

One thing to note is that if you need to specify multiple dependencies then you need to specify them as a string formatted as an array.
Do this by putting each feature formatted as just discussed in quotation marks " " and separating with a comma. Finally enclose it as an array - @( ).

So if we required two features, WebMgmtCompat and WebASP we would have the following:

DependsOn = @("[WindowsFeature]WebMgmtCompat","[WindowsFeature]WebASP")

So we're almost there...

For those that were paying attention, you may have noticed that the arguments property string contained some variables.
This allows us to prompt when compiling the DSC configuration for various settings to prevent hard coding data and allow for reuse.
Just like normal PowerShell we put these at the beginning in a Param block.

[string] $SCSMSDKServer,
[string] $Domain
$SCSMSDKCred = Get-AutomationPSCredential -Name "SCSMSDKCredentialAsset"
$SCSMPassword = $SCSMSDKCred.GetNetworkCredential().Password

I'm also going to leverage the Credentials Asset feature of Azure Automation.
This allows you to securely store username and password combo's within Azure Automation as an asset to then be reused in Runbooks and DSC. Again, allowing us to avoid hardcoding sensitive data and not having to prompt for them at each compilation.

I'm using the Get-AutomationPSCredential command to retrieve it and then split the PSCredential object down to username and password.

However, because I'm utilising this for the command line arguments for the executable installation I can't use it as a PSCredential and have to supply a non encrypted password, hence the use of the .GetNetworkCredential().Password to pull the unencrypted password out of the object.

N.B. This has the side effect of storing the password in clear text within the MOF that gets compiled and pushed down to the DSC node.

Because of this, it also means that compilation of the configuration can not be done via the Azure Portal and only by PowerShell as you will need to add configuration to the compilation task to tell it to allow the use of plain text passwords. More on this later.

The final DSC Configuration script looks like this:

Configuration SCSMPortal
[string] $SCSMSDKServer,
[string] $Domain
$SCSMSDKCred = Get-AutomationPSCredential -Name "SCSMSDKCredentialAsset"
$SCSMPassword = $SCSMSDKCred.GetNetworkCredential().Password
Node "WebServer"
#Install the required IIS features
WindowsFeature WebServer
Ensure = "Present"
Name = "Web-Server"
WindowsFeature WebFiltering
Ensure = "Present"
Name = "Web-Filtering"
WindowsFeature WebBasicAuth
Ensure = "Present"
Name = "Web-Basic-Auth"
WindowsFeature WebWindowsAuth
Ensure = "Present"
Name = "Web-Windows-Auth"
WindowsFeature WebMgmtConsole
Ensure = "Present"
Name = "Web-Mgmt-Console"
WindowsFeature WebMgmtCompat
Ensure = "Present"
Name = "Web-Mgmt-Compat"
WindowsFeature WebNetExt45
Ensure = "Present"
Name = "Web-Net-Ext45"
WindowsFeature WebASP
Ensure = "Present"
Name = "Web-Asp"
WindowsFeature WebASPNet45
Ensure = "Present"
Name = "Web-Asp-Net45"
WindowsFeature NETFramework45ASPNET
Ensure = "Present"
Name = "NET-Framework-45-ASPNET"
WindowsFeature NETWCFHTTPActivation45
Ensure = "Present"
Name = "NET-WCF-HTTP-Activation45"
Name = "SCSM SSP"
Path = "C:\DSC\SSP\SetupWizard.exe"
ProductId = "17F5D20F-47FB-485E-8CFC-4768C3C3F460"
Arguments = "/Install:SelfServicePortal /silent /accepteula /CustomerExperienceImprovementProgram:No /EnableErrorReporting:No /SMServerName:$SCSMSDKServer /PortalWebSiteName:SCSMPortal /PortalWebSitePort:81 /PortalAccount:$Domain\$SCSMUser\$SCSMPassword"
Ensure = "Present"
LogPath = "C:\DSC\SSP\SSP_Setup.log"
DependsOn = @("[WindowsFeature]WebServer","[WindowsFeature]WebFiltering","[WindowsFeature]WebBasicAuth","[WindowsFeature]WebWindowsAuth","[WindowsFeature]WebMgmtConsole","[WindowsFeature]WebMgmtCompat","[WindowsFeature]WebNetExt45","[WindowsFeature]WebASP","[WindowsFeature]WebASPNet45","[WindowsFeature]NETFramework45ASPNET","[WindowsFeature]NETWCFHTTPActivation45")

Notice the Node reference?
The DSC Resources used are wrapped within a Node <Name> section.
This isn't mandatory, if you're only using this to configure a single server, but as a side effect of using Plain Text password and Azure Automation DSC this is required.

N.B. Thanks to @bgelens for pointing me at that requirement as I couldn't get it to work!!!

So I mentioned you can't just import and compile this within the Azure Portal.
You can still import it via the console, so go ahead and open your Azure Automation account | Click DSC Configurations | Add a Configuration | Browse to your Config File | Click OK.

PowerShell code to compile the DSC Configuration:

$ConfigData = @{
AllNodes = @(
NodeName = "*"
PSDscAllowPlainTextPassword = $True
$Parameters = @{
"DOMAIN" = "PowerON"
Start-AzureRmAutomationDscCompilationJob -ResourceGroupName $ResourceGroup -AutomationAccountName $AccountName -ConfigurationName $ConfigurationName -ConfigurationData $ConfigData -Parameters $Parameters

Main thing is the PSDscAllowPlainTextPassword. This flags the config to allow us to store the password in plain text within the MOF that gets downloaded to the DSC node, which we're doing by pushing the plain text password from the PSCredentialObject into a variable. 
(N.B. See update note below)

Make sure you replace the $ResourceGroup, $AccountName, $ConfigurationName with relevant variables as well as the Prameters (SCSMSDKServer & Domain).

All that is left is to assign this configuration to a node and sit back and watch the SCSM Portal install.
I've not covered that piece in this post, but will have a "part 2" soon, along with a quick video showing the process end to end.

Now read Part 2 -

** Updated 23/12/2015 **
Minor revision to installation command as I realised it wasn't using the RTW command line.  Replaced SDKServerName with SMServerName and added PortalWebSiteName switches.

**Updated 23/12/2015 **
Joe from the Azure Automation team left a comment regarding the transfer of the MOF file is fully encrypted, and I must admit I didn't realise that WMF5 also encrypted the MOF locally so any worries of plain text passwords isn't really a worry at all!