System Center Dudes https://www.systemcenterdudes.com SCCM Blog | Configuration Guides, Reports and Troubleshooting posts. Wed, 20 Jun 2018 11:59:33 +0000 en-US hourly 1 https://www.systemcenterdudes.com/wp-content/uploads/2015/06/logo-166x150.png System Center Dudes https://www.systemcenterdudes.com 32 32 67897261 SCCM Java Inventory and Metering https://www.systemcenterdudes.com/sccm-java-inventory-and-metering/ https://www.systemcenterdudes.com/sccm-java-inventory-and-metering/#respond Wed, 20 Jun 2018 11:59:33 +0000 https://www.systemcenterdudes.com/?p=59652 After January 2019, businesses will need a commercial license to receive updates for Oracle Java SE products. This means that if you’re using Java in your environment, chances are that your management will need to know how many licenses to buy and how many PC has Java installed but don’t use it. The bad news is that SCCM Software Metering cannot do a reliable job to track Java Usage since the executable file always runs on computers. The good news is that there’s a way to track Java usage using Oracle tools… but it’s not straightforward. After searching, I found an awesome script made ... Read More

The post SCCM Java Inventory and Metering appeared first on System Center Dudes.

]]>
After January 2019, businesses will need a commercial license to receive updates for Oracle Java SE products. This means that if you’re using Java in your environment, chances are that your management will need to know how many licenses to buy and how many PC has Java installed but don’t use it.

SCCM Java Inventory

The bad news is that SCCM Software Metering cannot do a reliable job to track Java Usage since the executable file always runs on computers. The good news is that there’s a way to track Java usage using Oracle tools… but it’s not straightforward.

After searching, I found an awesome script made by Steve Jesok that do exactly what I needed. Unfortunately, the blog post is a bit old and don’t have detailed information on how to implement it.

We will guide you through the process and we’ll also provide a free report to help you track your java usage using SCCM.

Important Info
Java Usage Tracker requires a commercial license for use in production. To learn more about commercial features and how to enable them, see Oracle Java SE Advanced & Suite Products.

Process Overview

Here’s a high-level process overview. It’s quite simple as the PowerShell script, configuration item and report are already created. You only have to import everything on your SCCM server.

  • Download Java inventory .zip file
  • Import Configuration Data in SCCM
  • Modify Configuration Baseline
  • Deploy Configuration Baseline
  • Import Report

Download SCCM Java Inventory .zip file

I cannot say this enough, all the magic behind this solution is possible because of Steve Jesok script. Download the .zip file from the MNSCUG website or from our direct link (backup link…) and save it on your computer.

Import Java Configuration Data

Once you have downloaded the .zip file, extract it so you have a .cab file. We will use the .cab file to create a Configuration Item in SCCM.

  • In the SCCM Console, go to Assets and Compliance / Compliance Settings / Configuration Items
  • Right-click Configuration Items and select Import Configuration Data

SCCM Java Inventory

  • Click Add

SCCM Java Inventory

  • Select the JavaUsageTracking.cab file

SCCM Java Inventory

  • Click Next

SCCM Java Inventory

  • Click Next

SCCM Java Inventory

  • Validate and close the wizard

SCCM Java Inventory

  • The Java Logging Configuration Item has been created

SCCM Java Inventory

  • Right-click the Java Logging Configuration Item and select Properties
  • By default the Configuration Item cannot run on Windows 10, select the Supported Platforms and enable Windows 10. Select Other Operating System that you want to support.

SCCM Java Inventory

  • You should also have a Java Usage Tracking Configuration Baseline created by the import process

SCCM Java Inventory

  • Right-click the baseline and select Deploy

SCCM Java Inventory

  • Click Browse and select a test collection

SCCM Java Inventory

Java Configuration Baseline – Test and verification

We will now evaluate the Java Configuration Baseline on our test computer.

  • Log on your test computer
  • Open Control Panel / Configuration Manager applet
  • In the Configurations tab, select the Java Usage Tracking baseline and select Evaluate

SCCM Java Inventory

  • Once Evaluate, click View Report
  • The report will show Non-Compliant but this is normal

SCCM Java Inventory

  • Validate the presence of the usagetracker.properties file that has been created by the baseline. The file should be in the C:\Program Files (x86)\Java\Jre[yourversion]\lib\management folder

SCCM Java Inventory

  • The script also logs its action in the SCCM log directory – CM_JavaUsageLogging.log

SCCM Java Inventory

  • The CM_JavaUsageTracking WMI class has been created

SCCM Java Inventory

  • Launch any application that needs Java or visits any web page that needs Java.
  • After a couple of minutes, you should have some data in the WMI classes. This confirms that the monitoring process is fully functioning

SCCM Java Inventory

Collect information using Hardware Inventory

Now that our data is in WMI, we need to instruct SCCM to gather this information in its next hardware inventory cycle.

  • Open the SCCM console and go to Administration \ Client Settings
  • Select your Default client setting and select Properties
  • Select Hardware Inventory and select Set Classes

SCCM Java Inventory

  • In the Hardware Inventory Classes window, click on Add

SCCM Java Inventory

  • Click Connect and enter the test computer name and leave the default WMI Namespace (root\cimv2)
  • A list of the inventory classes will show, find CM_JavaUsageTracking, check it and click Ok

SCCM Java Inventory

  • You can leave the inventory classes in the Default Client settings or you can enable it in a custom one if you have one
  • Make sure that the client setting is deployed to your test collection and initiate a Hardware Inventory from the Configuration Manager applet

SCCM Java Inventory

  • As in any Hardware Inventory cycle, you can validate that the new classes get inventoried in the InventoryAgent.Log

SCCM Java Inventory

  • The CM_JavaUsageLogging.log in the SCCM logs folder should show activity

SCCM Java Inventory

Java Data Verification

  • In the SCCM Console, right-click your test computer and select Start / Resource Explorer
  • You should see the CM_JavaUsageTracking classes under Hardware

SCCM Java Inventory

  • If you are familiar with SQL, a new v_GS_CM_JavaUsagetracking view has been created

SCCM Java Inventory

Report

Now that our Java tracking data is gathered by SCCM we have built an SSRS report to show which computer has run Java. You can download the free Asset – Java Inventory and Metering report by visiting our product page. Leave us your comments if you are using our report so that we can improve it over time.

Important Info
This report will work only if the above steps have been made. If you try to run the report without creating the Java view, the report will fail

SCCM Java Inventory

Note: There is a rating embedded within this post, please visit this post to rate it.

Share this Post

The post SCCM Java Inventory and Metering appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/sccm-java-inventory-and-metering/feed/ 0 59652
How to install SCCM 1802 Update Rollup 1 (KB4163547) https://www.systemcenterdudes.com/how-to-install-sccm-1802-update-rollup-1-kb4163547/ https://www.systemcenterdudes.com/how-to-install-sccm-1802-update-rollup-1-kb4163547/#comments Tue, 12 Jun 2018 17:26:02 +0000 https://www.systemcenterdudes.com/?p=59864 The first Hotfix Rollup for SCCM Current Branch (1802) is now available. This post is a complete SCCM 1802 Hotfix Rollup 1 (KB4163547) installation guide. If you’re looking for a complete SCCM Current Branch installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be running SCCM 1802 to apply this update. Installing SCCM upgrades is important for your infrastructure. It fixes a lot of issues from SCCM 1802, which some of them are important. New Update and Servicing Model If you’re not familiar with the new SCCM servicing ... Read More

The post How to install SCCM 1802 Update Rollup 1 (KB4163547) appeared first on System Center Dudes.

]]>
Consulting Services
Need help to upgrade or migrate your site ? Consult our fixed price consulting plans to see our rates !

The first Hotfix Rollup for SCCM Current Branch (1802) is now available. This post is a complete SCCM 1802 Hotfix Rollup 1 (KB4163547) installation guide. If you’re looking for a complete SCCM Current Branch installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be running SCCM 1802 to apply this update.

Installing SCCM upgrades is important for your infrastructure. It fixes a lot of issues from SCCM 1802, which some of them are important.

New Update and Servicing Model

If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all.

You may wonder what’s the difference between a Cumulative Update (CU) and an Update Rollup (UR)/Hotfix RollUp (HR) :

A CU is a new servicing baseline. A post-CU1 hotfix requires CU1 first, whereas a post-UR1 hotfix doesn’t require UR1. Like CU, UR is cumulative which means that UR1 will include previous hotfixes.

*If you are running SCCM 1511, 1602, 1606,1610, 1702, 1706 and 1710 you first need to upgrade to 1802 prior to applying this Hotfix Rollup, see our blog which covers the upgrade process. Once completed, the Hotfix Rollup will be available under Update and Servicing node.

List of SCCM 1802 Hotfix Rollup 1 Fixes

This hotfix rollup brings many fixes in all areas of SCCM.

Consult the Microsoft support page for a full list of fixed issues.

Before you begin

Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear on your console once synchronized.

When you install an in-console update: (New Versions, CU, UR, KB)

  • It automatically runs a prerequisite check. You can also run this check prior to starting the installation
  • It installs at the central administration site (if you have one), and at primary sites automatically. You can control when each primary site server is allowed to update its infrastructure by using Service Windows for site servers
  • After a site server updates, all affected site system roles (including instances of the SMS Provider) automatically update. Configuration Manager consoles also prompt the console user to update the console, after the site installs the update
  • If an update includes the Configuration Manager client, you are offered the option to test the update in pre-production, or to apply the update to all clients immediately
  • After a primary site is updated, secondary sites do not automatically update. Instead, you must initiate the secondary site update

In this post, we’ll be updating a standalone Primary Site Server, console and clients.

Reminder
It’s a best practice to have some exclusions for your antivirus/anti-malware software on the SCCM server. Here a list of exclusions from SCCM 2012, which is still valid for CB as far as we know. You could also consider disabling the AV prior to installing the update and re-enable it once completed.
Before installing, check if your site is ready for the update :
  • Open the SCCM console
  • Go to Administration \ Cloud Services \ Updates and Servicing
  • In the State column, ensure that the update is Available

SCCM 1802 Hotfix Rollup KB4163547

Important Info
KB4132447 was released for First wave installation of SCCM 1802. It can be ignored if you have it listed as Ready to Install
  • If not already downloaded, hit Download
  • If it’s not available, right-click Updates and Servicing and select Check for Updates

SCCM 1802 Hotfix Rollup KB4163547

  • The update state will change to Downloading
  • You can follow the download in Dmpdownloader.log

The update files are stored in the EasyPayload folder in your SCCM Installation directory

SCCM 1802 Hotfix Rollup KB4163547

SCCM 1802 Hotfix Rollup 1 Installation Guide

Step 1 | SCCM 1802 Hotfix Rollup Prerequisite Check

Before launching the update, we recommend to launch the prerequisite check:

  • Open the SCCM console
  • Go to Administration \ Cloud Services \ Updates and Servicing
  • Right-click the Configuration Manager 1802 Hotfix (KB4163547) update and select Run prerequisite check

SCCM 1802 Hotfix Rollup KB4163547

  • Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check

SCCM 1802 Hotfix Rollup KB4163547

  • You can  monitor prerequisite check by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
  • When completed the State column will show Prerequisite check passed

SCCM 1802 Hotfix Rollup KB4163547

Step 2 | Launching the SCCM 1802 Hotfix Rollup 1

We are now ready to launch the SCCM 1802 Hotfix Rollup. At this point, plan about 30 minutes for the update installation.

  • Right-click the Configuration Manager 1802 update and select Install Update Pack

SCCM 1802 Hotfix Rollup KB4163547

  • On the General tab, click Next

SCCM 1802 Hotfix Rollup KB4163547

  • In the Client Update Options, select the desired option for your client update
    • This new feature allows updating only clients member of a specific collection. Refer to our post here

SCCM 1802 Hotfix Rollup KB4163547

  • On the License Terms tab, accept the license terms and click Next

SCCM 1802 Hotfix Rollup KB4163547

  • On the Summary tab, review your choices and click Next

SCCM 1802 Hotfix Rollup KB4163547

  • On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated

SCCM 1802 Hotfix Rollup KB4163547

  • During installation, the State column changes to Installing
  • You can  monitor installation by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1802 Hotfix Rollup KB4163547

  • … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log

SCCM 1802 Hotfix Rollup KB4163547

Warning
We’ve done numerous SCCM  installation/upgrade. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update could be stuck in “Prerequisite check passed” status and all other options grayed out. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key!
  • When completed, you’ll notice the message There are no pending update package to be processed in the log file
  • Refresh the Updates and Servicing node, the State column will be Installed

Updating the consoles

Important Info
The console update didn’t work automatically for us.

We had the following error in the log.

We are aware of at least one other instance of the error so far.

The workaround is to install the MSP located in %Program Files%\Microsoft Configuration Manager\Bin\i386\ConsoleUpdate manually.


Since 1602, the console has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.

  • Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console

SCCM 1802 Hotfix Rollup KB4163547

  • Click OK,  console update will start automatically

SCCM 1802 Hotfix Rollup KB4163547

SCCM 1802 Hotfix Rollup KB4163547

SCCM 1802 Hotfix Rollup KB4163547

  • Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version

Verification

Consoles

After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 5.1802.1082.1807 Note that the Site Version is not changed to the Hotfix Rollup version. This is normal.

SCCM 1802 Hotfix Rollup KB4163547

Clients

The client version will be updated to 5.00.8643.1813 (after updating, see section below)

SCCM 1802 Hotfix Rollup KB4163547

SCCM 1802 Hotfix Rollup 1 Client Package distribution

You’ll see that the 2 client packages are updated:

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1802 Hotfix Rollup KB4163547

  • Check if both packages were updated, if not, select both packages and initiate a Distribute Content to your distribution points

Updating the Clients

Our preferred way to update our clients is by using the Client Upgrade (You can refer to our complete post documenting this feature) feature:

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Sites
  • Click the Hierarchy Settings in the top ribbon
  • Select Client Upgrade tab
  • The Upgrade client automatically when the new client update are available checkbox has been enabled
  • Review your time frame and adjust it to your needs

SCCM 1802 Hotfix Rollup KB4163547

Monitor SCCM Client Version Number

You can see our SCCM Client version reports to give detailed information about every client’s versions in your environment. It’s the easiest way to track your client updates.Collections

You can also create a collection that targets clients without the latest client version. I use it to monitor which client hasn’t been updated yet.

SCCM 2012 - System Health Configuration Manager SS

Collections

Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.8643.1813'

Share this Post

Note: There is a rating embedded within this post, please visit this post to rate it.

The post How to install SCCM 1802 Update Rollup 1 (KB4163547) appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/how-to-install-sccm-1802-update-rollup-1-kb4163547/feed/ 3 59864
Create Office 365 Installer using SCCM https://www.systemcenterdudes.com/create-sccm-office-365-installer/ https://www.systemcenterdudes.com/create-sccm-office-365-installer/#comments Wed, 06 Jun 2018 17:52:48 +0000 https://www.systemcenterdudes.com/?p=59352 There have been many different posts about deploying Office 365 with SCCM. The majority of them used the Office Configuration tool in a more or less creative way. An easier method has been available for awhile to help SCCM admins to create the “perfect” Office 365 package. The SCCM Office 365 Installer is a new feature released in SCCM 1702. SCCM Office 365 Installer provides an easy-to-use wizard to define every related item for an Office 365 application. Whether you are new to creating Office 365 package or simply want to refresh an older package, this solution will ease every step of ... Read More

The post Create Office 365 Installer using SCCM appeared first on System Center Dudes.

]]>
There have been many different posts about deploying Office 365 with SCCM. The majority of them used the Office Configuration tool in a more or less creative way.

An easier method has been available for awhile to help SCCM admins to create the “perfect” Office 365 package. The SCCM Office 365 Installer is a new feature released in SCCM 1702. SCCM Office 365 Installer provides an easy-to-use wizard to define every related item for an Office 365 application.

Whether you are new to creating Office 365 package or simply want to refresh an older package, this solution will ease every step of creating an Office 365 package.

In this post, we will detail how to use the Office 365 Installer creation wizard.

If you are looking for How to Update Office 365 using SCCM, see our previous post.

Prerequisites

  • SCCM Current Branch 1702 and up

Create SCCM Office 365 Installer Package

  • Browse to Software Library / Office 365 Client Management

SCCM Office 365 Installer

  • Select Office 365 Installer

SCCM Office 365 Installer

  • Define the Name and Network path to store the content for the Office 365 installation

SCCM Office 365 Installer

  • Select Manually specify the Office 365 client settings

SCCM Office 365 Installer

Important Info
You can specify an XML file, but using the wizard is much more intuitive

You can get the Office 365 Deployment tool to help create the XML file from the Microsoft download page or the Office 365 Configuration XML editor

  • Select
    • Suite:
    • Applications :
      • Acces
      • Excel
      • OneDrive for Business(Groove)
      • OneDrive (Desktop)
      • OneNote
      • Outlook
      • PowerPoint
      • Publisher
      • Skype for Business
      • Word
    • Additional products:
      • Project
      • Visio
      • Remember that licenses are required even if installed
Important Info
Be careful about OneDrive for Business(Groove). This is usually no longer used and confusing because of the naming.

OneDrive (Desktop) is the one to be used

SCCM Office 365 Installer

    • Select
      • Architecture
        • 32-bit
        • 64-bit
      • Version: leave blank for the latest release
      • Channel:
        • Monthly
        • Semi-Annual Channel (Targeted)
        • Semi-Annual Channel
        • More details on Office 365 channels on Microsoft documentation
      • Languages
      •  Properties
        • Accept EULA
        • AutoActivate
        • Shared Computer Activation
        • Pin icons to the taskbar (Win7/8.x only)
Important Info
 Microsoft still recommend x86 over x64 in many cases. See details on Microsoft documentation 

SCCM Office 365 Installer

  • A prompt will display when selecting the Accept EULA

SCCM Office 365 Installer

  • Select to deploy the application now or not. Deploying it now will also ask to distribute the content.

SCCM Office 365 Installer

  • Summary

SCCM Office 365 Installer

  • Progress, this will actually download the content to install Office 365. It will take some time.

SCCM Office 365 Installer

  • Completion

Result

The content folder has the Office Deployment tool, configuration.xml and actual bits of the Office click-to-run installer

SCCM Office 365 Installer

Configuration.xml has almost all the required information in it.

SCCM Office 365 Installer

Important Info
The only thing that is not part of the configuration.xml is the Display Level.

We recommend adding Display Level=”None”, so there is no prompt for a user or to run in a Task Sequence.

SCCM Office 365 Installer

For more details about the configuraiton.xml, see Microsoft Documentation.

  • An application is automatically created at the root of Software Library / Application Management / Applications

SCCM Office 365 Installer

  • The Detection method is automatically populated.

SCCM Office 365 Installer

This is by far the easiest method to create an SCCM Office 365 application or package. No problem of syntax in the Configuration.xml, no problem to define the Detection Rule.

SCCM Office 365 Inventory Report

Remember to look at our free Office 365 report to keep track of your deployed version and channel.

SCCM Office 365 inventory report

 

Share this Post

The post Create Office 365 Installer using SCCM appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/create-sccm-office-365-installer/feed/ 5 59352
SCCM Windows 10 1709 to 1803 Upgrade Guide https://www.systemcenterdudes.com/sccm-windows-10-1803-upgrade/ https://www.systemcenterdudes.com/sccm-windows-10-1803-upgrade/#comments Wed, 30 May 2018 16:15:28 +0000 https://www.systemcenterdudes.com/?p=58250 Microsoft published the Windows 10 1803 feature update (aka April 2018 Update), in the Semi-Annual Channel on April 30th, 2018. You may need to deploy it to your Windows 10 computer to stay supported or to benefits from the new features. Before deploying a new Windows 10 feature upgrade, you need to have a good plan. Test it in a lab environment, deploy it to a limited group and test all your business applications before broad deployment. Do not treat a feature upgrade as normal monthly software updates. Treat it as a new operating system as if you were upgrading Windows 7 ... Read More

The post SCCM Windows 10 1709 to 1803 Upgrade Guide appeared first on System Center Dudes.

]]>
Microsoft published the Windows 10 1803 feature update (aka April 2018 Update), in the Semi-Annual Channel on April 30th, 2018. You may need to deploy it to your Windows 10 computer to stay supported or to benefits from the new features.

Before deploying a new Windows 10 feature upgrade, you need to have a good plan. Test it in a lab environment, deploy it to a limited group and test all your business applications before broad deployment. Do not treat a feature upgrade as normal monthly software updates. Treat it as a new operating system as if you were upgrading Windows 7 to Windows 10.

This blog post will cover all the task needed to deploy the new Windows 10 1803 using SCCM:

  • Check if you have an SCCM Supported version
  • Upgrade your Windows ADK
  • Create a Servicing Plan to update your existing Windows 10
  • Import the OS in SCCM to use with your deployment Task Sequence
  • Create a Windows 10 Task Sequence for new computers
  • Create a Windows 10 Upgrade Task Sequence for Windows 10 (and Win 7 or 8.1 computers)
  • Update your Automatic Deployment Rules and Software Update groups
  • Import your ADMX

Check SCCM Version for SCCM Windows 10 1803 Upgrade

For Windows 10 1803 April 2018 Update, you need at least SCCM 1802 in order to support it as a client. See the following support matrix if you’re running an outdated SCCM version and make sure to update your site.

Windows ADK

Before capturing and deploying a Windows 10 1803 image, make sure that you’re running a supported version of the Windows ADK. Windows recommends using the Windows ADK that matches the version of Windows you’re deploying. If you’re already running an ADK version on your SCCM server, see our post on how to install a new version.

Upgrade Method – Task Sequence or Servicing Plan ?

In order to upgrade an existing Windows 10 (1709 and less) to Windows 1803 you have 2 choices. You can use an upgrade Task Sequence or you can use Servicing Plans. There a strong debate over which is the best methods. We prefer to use Upgrade Task Sequence for the simple reason that it’s more customizable. You can run pre-upgrade and post-upgrade task which will be mandatory if you have any sort of customization to your Windows 10 deployments.

For example, Windows 10 is resetting pretty much anything related to regional settings, keyboard, start menu and taskbar customization. Things are getting better from one version to another but if you’re upgrading from an older build, let’s say 1511, expect some post-configuration tasks… and the only way to do that is using a task sequence.

Servicing Plan has the simplicity, you set your option and forget, as for Automatic Deployment Rules does for Software Updates. We yet did not have any client that doesn’t want any control over Windows 10 upgrade in their organization. We totally understand the point of Servicing Plan and they’ll be useful in a couple of releases when Windows 10 upgrades will be an easy task… but for now, it’s not, unfortunately.

Using Upgrade Task Sequence and for new Windows 10 Computer (Operating System Deployment)

As stated in the previous paragraph, it’s possible to upgrade an existing Windows 10 computer using an upgrade task sequence. This method is useful if you need to run pre and post actions in your upgrade process.

If you need to upgrade older operating system (Windows 7,8.1) refer to the Create SCCM Task Sequence Upgrade Windows 7 to Windows 10 1803 section

You will also probably want to create or modify your existing task sequence deployed to new computers to receive the latest Windows 10 1803 version.

Import Windows 10 1803 Operating System

We will now import the Windows 10 1803 WIM file for Operating System Deployment.

We will be importing the default Install.wim from the Windows 10 media for a “vanilla” Windows 10 deployment. You could also import a WIM file that you’ve created through a build and capture process. This WIM wile will be used for new computers, to upgrade an existing Windows 10, you need to import an Operating System Upgrade Packages. We will cover this in the next section.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Images
  • Right-click Operating System Images and select Add Operating System Image

SCCM Windows 10 1803 Upgrade

  • On the Data Source tab, browse to your WIM file. The path must be in UNC format

SCCM Windows 10 1803 Upgrade

  • In the General tab, enter the Name, Version and Comment, click Next
    • It’s normal that you see Windows 10 Education even if you are importing Enterprise edition as this WIM contains multiple indexes. You’ll need to choose the right one in your deployment Task Sequence

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your information and click Next. Complete the wizard and close this window

Distribute your Windows 10 1803 Operating System Image

We now need to send the Operating System Image (WIM file) to our distribution points.

  • Right-click your Operating System Image, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 1803 Upgrade

Add Operating System Upgrade Packages

We will now import the complete Windows 10 media in Operating System Upgrade Packages. This package will be used to upgrade an existing Windows 10 or a Windows 7 (or 8.1) device to Windows 10 using an Upgrade Task Sequence.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Upgrade Packages
  • Right-click Operating System Upgrade Packages and select Add Operating System Upgrade Packages

SCCM Windows 10 1803 Upgrade

  • In the Data Source tab, browse to the path of your full Windows 10 media. The path must point to an extracted source of an ISO file. You need to point at the top folder where Setup.exe reside
  • In the General tab, enter the Name, Version, and Comment, click Next

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your information and click Next and complete the wizard

Distribute your Operating System Upgrade Packages

We now need to send the Operating System Upgrade Package to your distribution points.

  • Right-click your Operating System Upgrade Package, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 1803 Upgrade

Create SCCM Task Sequence Upgrade for Windows 10 1803

Let’s create an SCCM task sequence upgrade for a computer running a Windows 10 device. Once again, this Task Sequence could be used for Windows 7 or 8.1.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Upgrade an operating system from upgrade package

SCCM Windows 10 1803 Upgrade

  • In the Task Sequence Information tab, enter a Task Sequence Name and Description

SCCM Windows 10 1803 Upgrade

  • On the Upgrade the Windows Operating System tab, select your upgrade package by using the Browse button
  • Select your Edition Index depending on the edition you want to deploy

SCCM Windows 10 1803 Upgrade

  • On the Include Updates tab, select the desired Software Update task
    • All Software Updates will install the updates regardless of whether there is a deadline set on the deployment (on your OSD collection)
    • Mandatory Software Updates will only install updates from deployments that have a scheduled deadline (on your OSD collection)
    • Do not install any software updates will not install any software update during the Task Sequence

SCCM Windows 10 1803 Upgrade

  • On the Install Applications tab, select any application you want to add to your upgrade process

SCCM Windows 10 1803 Upgrade

  • On the Summary tab, review your choices and click Next and click Close

Edit the SCCM Windows 10 1803 Task Sequence Upgrade

Now that we have created the upgrade task sequence, let’s see what it looks like under the hood. SCCM 1802 brings new built-in checks to improve deployment success.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click your upgrade task sequences and select Edit

As you can see, it’s fairly simple. SCCM will take care of everything in a couple of steps :

SCCM Windows 10 1803 Upgrade

  • The Upgrade Operating System step contains the important step of applying Windows 10
  • Ensure to choose the right Edition since the WIM file contains multiple indexes

SCCM Windows 10 1803 Upgrade

Deploy the SCCM Windows 10 1803 Upgrade Task Sequence

We are now ready to deploy our task sequence to the computer we want to upgrade. In our case, we are targeting a Windows 7 computer.

  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Deploy

SCCM Windows 10 1803 Upgrade

  • On the General pane, select your collection. This is the collection that will receive the Windows 10 upgrade. For testing purposes, we recommend putting only 1 computer to start

SCCM Windows 10 1803 Upgrade

  • On the Deployment Settings tab, select the Purpose of the deployment
    • Available will prompt the user to install at the desired time
    • Required will force the deployment at the deadline (see Scheduling)
  • You cannot change the Make available to the following drop-down since upgrade packages are available to clients only

SCCM Windows 10 1803 Upgrade

  • On the Scheduling tab, enter the desired available date and time. On the screenshot, we can’t create an Assignment schedule because we select Available in the previous screen

SCCM Windows 10 1803 Upgrade

  • In the User Experience pane, select the desired options

SCCM Windows 10 1803 Upgrade

  • In the Alerts tab, check Create a deployment alert when the threshold is higher than the following check-box if you want to create an alert on the failures

SCCM Windows 10 1803 Upgrade

  • On the Distribution Point pane, select the desired Deployment options. We will leave the default options

SCCM Windows 10 1803 Upgrade

  • Review the selected options and complete the wizard

SCCM Windows 10 1803 Upgrade

Launch the Upgrade Process on a Windows 10 1709 computer

Everything is now ready to deploy to our Windows 10 computers. For our example, we will be upgrading a Windows 10 1709 to Windows 10 1803. This task sequence can also be used on a Windows 7 or 8.1 devices to install Windows 10 1803.

  • Log on our Windows 10 computer and launch a Machine Policy Retrieval & Evaluation Cycle from Control Panel / Configuration Manager Icon

SCCM Task Sequence Upgrade

  • Open the new Software Center from the Windows 10 Start Menu
  • You’ll see the SCCM upgrade task sequence as available. We could have selected the Required option in our deployment schedule, to launch automatically without user interaction at a specific time
  • When ready, click on Install

SCCM Windows 10 1803 Upgrade

  • On the Warning, click Install

SCCM Windows 10 1803 Upgrade

  • The update is starting, the task sequence Installation Progress screen shows the different steps

SCCM Windows 10 1803 Upgrade

  • The WIM is downloading on the computer and saved in C:\_SMSTaskSequence
  • You can follow task sequence progress in C:\Windows\CCM\Logs\SMSTSLog\SMSTS.log
  • After downloading, the system will reboot
  • The computer restart and is loading the files in preparation for the Windows 10 upgrade

SCCM Windows 10 1803 Upgrade

  • WinPE is loading

SCCM Task Sequence Upgrade

  • The upgrade process starts. This step should take between 60-90 minutes depending on the device hardware
  • Windows 10 is getting ready, 2-3 more minutes and the upgrade will be completed

SCCM Task Sequence Upgrade

  • Once completed the SetupComplete.cmd script runs. This step is important to set the task sequence service to the correct state

SCCM Task Sequence Upgrade

  • Windows is now ready, all software and settings are preserved

SCCM Windows 10 1803 Upgrade

Danger
If you’re happy with the results and don’t want to use servicing plans, stop reading here. If you want to know more about servicing plans, keep reading.

Use SCCM Windows 10 1803 Servicing Plans

If you’re already running Windows 10 in your organization, Servicing plans is a simple method to upgrade to an up-to-date Windows 10 version. If it’s the first time you are using Windows 10 servicing plans, follow our previous post that explains the requirements to set up your Software Update Point.

We’ll start by making sure that the latest Windows 10 1803 Feature Upgrade is synchronized on our server:

  • Go to Software Library \ Windows 10 Servicing
  • Right-click Windows 10 Servicing, select Synchronize Software Updates

SCCM Windows 10 1803 Upgrade

  • As for any Software Update synchronization process, follow the progress in Wsyncmgr.log in your SCCM installation directory
  • Once completed, go to Software Library \ Windows 10 Servicing \ All Windows 10 Updates
  • You should have your Windows 10 1803 Upgrade packages listed

SCCM Windows 10 1803 Upgrade

Create Windows 10 1803 Servicing Plans

Now that we have Windows 10 1803 upgrade packages synchronized in SCCM, we can create a servicing plan for our “outdated” Windows 10 devices (1511,1607,1703,1709). Servicing Plan and Automatic Deployment Rules shares the same engine so you won’t be disoriented by servicing plans if you’re familiar with ADRs.

Warning
Servicing plans are designed to upgrade Windows 10 from one build to another build only. You can’t use that to upgrade Windows 7 to Windows 10. If you need to upgrade your Windows 7 to Windows 10 use an Upgrade Task Sequence instead.

Looking at the Windows 10 Servicing dashboard ( Software Library \ Windows 10 Servicing), you can see your Windows 10 expiration statistics :

SCCM Windows 10 1803 Upgrade

  • Go to Software Library \ Windows 10 Servicing \ Servicing Plan
  • Right-click Servicing Plan and select Create Servicing Plan

SCCM Windows 10 1803 Upgrade

  • In the General pane, give a Name and Description, click Next

SCCM Windows 10 1803 Upgrade

  • On the Servicing Plan tab, click Browse and select your Target Collection

SCCM Windows 10 1803 Upgrade

  • In the Deployment Ring tab:
    • Specify the Windows readiness state to which your servicing plan should apply. Refer to the Microsoft documentation if you are unfamiliar with servicing channels.
    • Specify how many days you want to wait before deploying

SCCM Windows 10 1803 Upgrade

  • In the Upgrade tab, specify the Language, Required and Title of the upgrade packages you want to deploy. The language feature is available in SCCM 1602 and later.
    • Language : English (will contain en-us AND en-gb)
    • Title : 1803 or 1803, en-us (if you want en-us only)

SCCM Windows 10 1803 Upgrade

  • Use the Preview button to ensure that you are targeting the right version (We are targeting Windows 10 1803 Enterprise en-us devices)

SCCM Windows 10 1803 Upgrade

  • In the Deployment Schedule tab, select the desired behavior

SCCM Windows 10 1803 Upgrade

  • In the User Experience tab, select the desired options

SCCM Windows 10 1803 Upgrade

  • In the Deployment Package tab, select Create a new deployment package and enter your Package Source path

SCCM Windows 10 1803 Upgrade

  • In the Distribution Points tab, select your distribution point

SCCM Windows 10 1803 Upgrade

  • In the Download Location tab, select Download software updates from the Internet

SCCM Windows 10 1803 Upgrade

  • In the Language Selection tab, select your language

SCCM Windows 10 1803 Upgrade

  • In the Summary tab, review your settings and close the Create Servicing Plan wizard

SCCM Windows 10 1803 Upgrade

  • Right-click your newly created Servicing Plan and select Run Now

SCCM Windows 10 1803 Upgrade

  • Check the RuleEngine.log file to see the progress. This process takes a while.

SCCM Windows 10 1709 Upgrade

  • A Software Update Group and Deployment Package will be created. The size of the package will be around 2-3gb per language
  • You can also see that the deployment gets created in the Monitoring / Deployments section
  • Ensure that your Deployment Package (specified in the Servicing Plan) has been distributed to your Distribution Points

SCCM Windows 10 1803 Upgrade

Windows 10 1803 Servicing Plan Deployment

Now that the deployment is triggered for clients, we will launch the installation manually using software center.

SCCM Windows 10 1803 Upgrade

  • Initiate a Software Update Deployment Evaluation Schedule using the Configuration Manager icon in Control Panel
  • Open the Software Center / Updates, Feature Update to Windows 10 Enterprise 1803, en-us is listed
  • Select it and select Install
  • Accept the warning by clicking Install

SCCM Windows 10 1803 Upgrade

  • The computer will restart after about 5 minutes
  • The whole upgrade process takes about 60 to 90 minutes and your device will be rebooted multiple time

SCCM Windows 10 1709 Upgrade

  • Once completed, log on the computer using your account. Windows is happy to tell you that it’s updated

SCCM Windows 10 1709 Upgrade

  • We are now running Windows 10 Enterprise version 1803 (Build 17134)

  • Back in the Software Library \ Windows 10 Servicing \ Servicing Plan node
  • Our machine is now listed as Windows 10 version 1709 and is no longer listed as Expire Soon in the Windows 10 Servicing node
  • The Service Plan Monitoring section can be used to monitor compliance and you can use the Deploy Now button to deploy the same service plan to a new collection

SCCM Windows 10 1803 Upgrade

Create Software Update Group

One important thing in any OSD project is to make sure that every machines deployment are up to date. Before deploying Windows 10 1803, make sure that your Software Update Point is configured to include Windows 10 patches.

Once Windows 10 is added to your Software Update Point, we will create a Software Update Group that will be deployed to our Windows 10 deployment collection. This way, all patches released after the Windows 10 media creation (or your Capture date) will be deployed during the deployment process.

To create a Windows 10 Software Update Group :

  • Open the SCCM Console
  • Go to Software Library / Software Updates / All Software Updates
  • On the right side, click Add Criteria, select Product, Expired and Superseded
    • Product : Windows 10
    • Expired  : No
    • Superseded : No
    • Title contains 1803
  • Select only the latest Cumulative Updates that apply  (x64 or x86) and select Create Software Update Group

SCCM Windows 10 1803 Upgrade

  • Once created, go to Software Library / Software Updates / Software Update Groups
  • Right-click your Windows 10 SUG and deploy it to your OSD deployment collection

Import ADMX File

If you’re responsible for managing group policy in your organization. Ensure that you import the latest Windows 10 1803 ADMX file on your domain controller. See our SCCM Windows 10 1803 Resources for more information about this.

Bonus Ressources

Need a report to track your Windows 10 devices? We developed a report to help you achieve that :

Asset – Windows 10 SCCM Report

 

Share this Post

The post SCCM Windows 10 1709 to 1803 Upgrade Guide appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/sccm-windows-10-1803-upgrade/feed/ 3 58250
How to use SCCM Management Insights in SCCM 1802+ https://www.systemcenterdudes.com/sccm-management-insights/ https://www.systemcenterdudes.com/sccm-management-insights/#respond Tue, 15 May 2018 18:24:21 +0000 https://www.systemcenterdudes.com/?p=57527 Starting with SCCM 1802, a new SCCM feature provides information about the current state of your environment. SCCM Management Insights analyze data from your site and help you understand your environment and take action based on the insight. This feature is quite… basic… for now but we understand where the PG team is heading with that and it will be a valuable feature in the upcoming releases. SCCM Management Insights Basics For now, there are 6 available rules: Application without deployment, Cloud Services, Collections, Simplified Management, Software Center and Windows 10. Each rule is evaluated weekly. You can re-evaluate a rule ... Read More

The post How to use SCCM Management Insights in SCCM 1802+ appeared first on System Center Dudes.

]]>
Starting with SCCM 1802, a new SCCM feature provides information about the current state of your environment. SCCM Management Insights analyze data from your site and help you understand your environment and take action based on the insight. This feature is quite… basic… for now but we understand where the PG team is heading with that and it will be a valuable feature in the upcoming releases.

SCCM Management Insights Basics

For now, there are 6 available rules: Application without deployment, Cloud Services, Collections, Simplified Management, Software Center and Windows 10.

Each rule is evaluated weekly. You can re-evaluate a rule on demand by right-clicking the rule and selecting Re-evaluate.

The logs file for Management Insight is SMS_DataEngine.log which is located on your SCCM server.

Applications without deployment

Applications without deployment

Lists the applications in your environment that do not have active deployments. This rule helps you find and delete unused applications to simplify the list of applications displayed in the console.

  • Go to Administration \ Management Insights \ All Insights
  • Select Application without deployment, right-click and select Show Insight

SCCM Management Insights

  • A new pane open, select Application without deployments and select More Details

SCCM Management Insights

  • The list of applications without deployment is shown

SCCM Management Insights

Use this list to clean up unwanted collections or use our script to automatically delete empty collections without deployments.

Cloud Services

Set of rules to help integrate cloud services to your SCCM infrastructure.

  • Go to Administration \ Management Insights \ All Insights
  • Select Cloud Service, right-click and select Show Insight

SCCM Management Insights

  • A new pane open with a set of 4 rules :

SCCM Management Insights

Assess co-management readiness

Helps you understand what steps are needed to enable co-management based on 3 rules. In our example the rules show that we need to take some action for Co-Management Readiness :

  • Upgrade your clients to the latest Windows 10 version – Windows 10, version 1709 is needed for co-management. In our example, our clients are compliant
  • Configure Azure Service for use with Configuration Manager – Azure AD cloud service with integrated multi-factor authentication protects sensitive data and applications both on-premises and in the cloud. In our example, we need to take some action, client on the Action Needed pane to see details
  • Enable your devices to be hybrid Azure Active Directory-joined – Azure AD-joined devices allow users to sign in with their domain credentials while ensuring devices meet the organization’s security and compliance standards. In our example, we need to take some action, client on the Action Needed pane to see details

SCCM Management Insights

Collections

Empty Collections

Lists collections in your environment that have no members. This rule is very useful as collections are one of the more resource intensive objects in your SCCM infrastructure.

  • Go to Administration \ Management Insights \ All Insights
  • Select Collections, right-click and select Show Insight

SCCM Management Insights

  • A new pane open, select Empty Collections and select More Details
  • The list of empty collection is shown

Use this list to clean up unwanted collections or use our script to automatically delete empty collections without deployments.

Simplified Management

Non CB-Client Versions

Lists all clients whose versions are not at the Current Branch client version. (Prior vSCCM 1511)

  • Go to Administration \ Management Insights \ All Insights
  • Select Simplified Management, right-click and select Show Insight

SCCM Management Insights

  • A new pane open, select Non CB-Client Versions and select More Details

SCCM Management Insights

  • The list of outdated clients is shown

SCCM Management Insights

Use this list to update your clients to the latest version. If you want to build a collection based on that, see our SCCM Set of Operational collections which included an All Clients Not Latest collection.

Software Center

  • Go to Administration \ Management Insights \ All Insights
  • Select Software Center right-click and select Show Insight
  • A new pane open with a set of 2 rules :

SCCM Management Insights

Direct users to Software Center instead of Application Catalog

Check if users have installed or requested applications from the Application Catalog in the last 14 days. Support for the Application Catalog website ends with the first update released after June 1, 2018.

If you are not compliant on this one, we recommend redirecting users to Software Center instead of the Application Catalog.

Use the new version of Software Center

Since 1802, the previous version of Software Center is no longer supported.

Set up clients to use the new Software Center by enabling the client setting Computer Agent / Use new Software Center

SCCM Management Insights

Share this Post

The post How to use SCCM Management Insights in SCCM 1802+ appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/sccm-management-insights/feed/ 0 57527
Configure Start Menu Windows 10 1703 and above https://www.systemcenterdudes.com/configure-start-menu-windows-10-1703-and-above/ https://www.systemcenterdudes.com/configure-start-menu-windows-10-1703-and-above/#comments Fri, 04 May 2018 11:14:35 +0000 https://www.systemcenterdudes.com/?p=54916 Sometimes Microsoft makes small changes under the hood and can hardly be tracked unless an issue comes up to flag that changes. The configuration of the Start Menu and Taskbar for Windows 10 has been since the beginning a great challenge for administrators and it doesn’t look that this will change anytime soon. Microsoft added the following note to the start menu layout modification documentation A simple note, with great implication! Following our previous posts on Windows 10 Customization and how to modify the taskbar configuration, we will detail how to configure the start menu and taskbar with that latest ... Read More

The post Configure Start Menu Windows 10 1703 and above appeared first on System Center Dudes.

]]>
Sometimes Microsoft makes small changes under the hood and can hardly be tracked unless an issue comes up to flag that changes. The configuration of the Start Menu and Taskbar for Windows 10 has been since the beginning a great challenge for administrators and it doesn’t look that this will change anytime soon.

Microsoft added the following note to the start menu layout modification documentation

Note
In Windows 10, version 1703, Export-StartLayout will use DesktopApplicationLinkPath for the .url shortcut. You must change DesktopApplicationLinkPath to DesktopApplicationID and provide the URL.

A simple note, with great implication!

Following our previous posts on Windows 10 Customization and how to modify the taskbar configuration, we will detail how to configure the start menu and taskbar with that latest indication from Microsoft.

Prerequisites

  • Windows 10 1703 and above
Windows 10 1803
Early test indicate that Windows 10 1803 is no different and this applies to it.

Configure Start Menu Windows 10

  • Setup a Windows 10 start menu as we would like to have as default
 Configure Start Menu Windows 10
  • Start a PowerShell command window as administrator
  • Enter the following command line to export the Start Menu
    • Export-StartLayout -path C:\temp\StartMenu.xml
  • A StartMenu.xml is generated in the specified directory
    • Application links are using the DesktopApplicationLinkPath

  • In Powershell, enter the following command :
    • Get-StartApps

Configure Start Menu Windows 10

  • This returns the list of all applications in the Start Menu
  • Locate the application that uses the DesktopApplicationLinkPath and take note of the AppID

Configure Start Menu Windows 10

  • Go back to the XML exported previously and replace the DesktopApplicationLinkPath by the DesktopApplicationID

Once this is completed it can be added to your task sequence like we explain in previous posts.

Important Info
If you wish to manage the Taskbar like we explained in our previous post, note that the DesktopApplicationLinkPath must be used as the DesktopApplicationID will not work.

Configure Start Menu Windows 10

Please don’t shoot the messenger 🙂

More details available on Docs.Microsoft.com

Share this Post

The post Configure Start Menu Windows 10 1703 and above appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/configure-start-menu-windows-10-1703-and-above/feed/ 15 54916
List of Windows 10 1803 Resources for SCCM Administrators https://www.systemcenterdudes.com/windows-10-1803-sccm-resources/ https://www.systemcenterdudes.com/windows-10-1803-sccm-resources/#comments Tue, 01 May 2018 14:26:14 +0000 https://www.systemcenterdudes.com/?p=56564 Each new Windows releases brings its daily tweet-storm. Yesterday, we saw multiple tweets about the new Windows 1803 (April Update) release and what’s coming with it (ADK, Baseline, ADMX…). All this new information may be difficult to assimilate and follow. This post will describe all the information you need to know if you’re planning to deploy Windows 1803 in your organization as an SCCM administrator. We will update this post as new information is released. Windows 10 1803 New Features First, we like to check What’s new in Windows 1803. This article aims IT professionals so you can see if ... Read More

The post List of Windows 10 1803 Resources for SCCM Administrators appeared first on System Center Dudes.

]]>
Windows 10 1803 SCCM Resources

Each new Windows releases brings its daily tweet-storm. Yesterday, we saw multiple tweets about the new Windows 1803 (April Update) release and what’s coming with it (ADK, Baseline, ADMX…). All this new information may be difficult to assimilate and follow. This post will describe all the information you need to know if you’re planning to deploy Windows 1803 in your organization as an SCCM administrator. We will update this post as new information is released.

Windows 10 1803 New Features

First, we like to check What’s new in Windows 1803. This article aims IT professionals so you can see if this Windows version has some interesting features for your organization.

You can also see this Microsoft article to see what’s been removed from Windows 1803.

Windows ADK

A new version of the Windows ADK is available. This ADK is backward compatible. Which means that you can deploy older versions of Windows with it but it’s recommended to match your Windows version with your ADK version. Follow our upgrade post if you already installed an older ADK version on your SCCM server.

SCCM OS Deployment Support

The SCCM documentation state that only SCCM 1802 supports the new Windows 1803 ADK and Windows 1803 deployment. Follow our upgrade post if you are running an older version of SCCM.

SCCM Client on Windows 1803

The SCCM client on Windows 1803 is supported on SCCM 1802 only.

ISO Download

The Windows 1803 ISO should be available in about a week is now available in the Volume Licensing Service Center. If you can’t wait to use it and have an MSDN subscription, you can download it from MSDN. If you don’t have an MSDN Subscription, you can download it using the Media Creator Tool. Note that the Media Creator Tool won’t allows downloading the Enterprise version.

If you’re managing more than one language, download the Windows 1803 Language pack while you’re in the download portal. As stated in this blog post, look for Released Mar ’18 language packs which are Windows 10 v1803.

SCCM Operations

We already created multiple posts on how to manage a new Windows 10 version using SCCM.

Overview of the task should include:

  • Windows ADK Upgrade
  • Import new Windows 1803 ISO
  • Import Language Pack
  • Create Servicing plans and/or Upgrade Task Sequences

Security Baseline

Microsoft announced the final release of the security configuration baseline settings for Windows 10 1803. If needed, download the new security baseline and follow our post on how to use it.

ADMX

For now, there’s no ADMX available for Windows 10 1803. This should be available at the same time the ISO gets released on VLSC.

The Windows 1803 ADMX template is now available and can be downloaded from Microsoft.

Remote Server Administration Tool (RSAT)

RSAT is now available for Windows 10 1803. There’s a couple of fixes coming based on the Microsoft blog post.

Microsoft Deployment Toolkit (MDT)

MDT8450 is supporting Windows 1803. If you need the latest MDT version, no need to update.

Share this Post

The post List of Windows 10 1803 Resources for SCCM Administrators appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/windows-10-1803-sccm-resources/feed/ 10 56564
How to configure SCCM Phased Deployments https://www.systemcenterdudes.com/sccm-phased-deployments/ https://www.systemcenterdudes.com/sccm-phased-deployments/#respond Mon, 23 Apr 2018 15:08:14 +0000 https://www.systemcenterdudes.com/?p=55816 Beginning with SCCM 1802, there’s a new pre-release feature that allows Phased Deployments. This feature allows automating a coordinated, sequenced rollout of a task sequence across multiple collections. For now, you can create phased deployments with two phases but will be extended for multiple phases in the future. This can be helpful to test certain deployment where you want to deploy to a test collection first and then a broader collection. All this happen automatically when using phased deployments. Enabling SCCM Phased deployments Since Phased deployments is a pre-release feature, we need to first enable it before we can use it. Go to Administration ... Read More

The post How to configure SCCM Phased Deployments appeared first on System Center Dudes.

]]>
Beginning with SCCM 1802, there’s a new pre-release feature that allows Phased Deployments. This feature allows automating a coordinated, sequenced rollout of a task sequence across multiple collections. For now, you can create phased deployments with two phases but will be extended for multiple phases in the future. This can be helpful to test certain deployment where you want to deploy to a test collection first and then a broader collection. All this happen automatically when using phased deployments.

Warning
Phased deployment of task sequences does not support PXE or media installation.

Enabling SCCM Phased deployments

Since Phased deployments is a pre-release feature, we need to first enable it before we can use it.

  • Go to Administration / Site Configuration / Sites / Hierarchy Settings
  • In General, make sure you have check Consent to use Pre-release features

SCCM Phased Deployments

  • Once enabled, go to Administration / Update and servicing /Features
  • Click Phased deployment and right-click on it and choose Turn on

SCCM Phased Deployments

  • Close and re-open the SCCM Console

Creating a Phased Deployments

For now, phased deployment is only possible on Task Sequence. We assume that it will be possible in application and package deployments in further versions.

  • Go to Software Library / Operating Systems / Task Sequences
  • For this test, we will use an existing Task Sequence that basically installs an application. If you don’t have any task sequences, you can create a new one.
  • Right-click your Task Sequence and select Create Phased Deployment

SCCM Phased Deployments

  • In the General pane, enter a Name and Description for your phased deployment
  • On the bottom, select your 2 collections to deploy

SCCM Phased Deployments

  • Set the success percentage of the first phase before going to phase #2. This basically tells SCCM to create the second deployments when deployment success reaches 95%
  • In the second box, select to wait for a number of days or not before creating the second deployment
  • In the third box, select when to begin the deployment. For now, it’s not possible to start a deployment at a specific time

SCCM Phased Deployments

  • In the Phases pane, you can re-order, Add or Edit your deployments. For now, the Add button is disabled, you can’t add more than 2 phases

SCCM Phased Deployments

  • If you click Edit, you can change the options of the selected Phase

SCCM Phased Deployments

  • Complete the wizard and click Close

SCCM Phased Deployments

Monitor SCCM Phase Deployments

Now that our phase deployment is created, SCCM will basically create for you the deployments based on your settings. In the bottom, you have a new Phased Deployments tab which shows your newly created task. If you look in the Deployments tab, you’ll see that your first deployment has been created. The second one will be created automatically based on the success condition of the first one.

SCCM Phased Deployments

  • If you want to speed up the process or skip the first phase, you can right-click the Phase Deployment and select Move to next phase. It’s also possible to Suspend your deployment from there

SCCM Phased Deployments

  • If you select Move to next phase, a confirmation pop-up will show

SCCM Phased Deployments

To monitor Phased Deployments, you do as standard deployments. Simply go in Monitor / Deployments and you’ll see your 2 deployments with their statistics

SCCM Phased Deployments

There’s also a new SMS_PhasedDeployment.log file to monitor task done by the Phase deployment engine. By looking at the log file, we can see that the engine monitors for changes each minute.

SCCM Phased Deployments

This is a great feature with lots of potential… but for now, it lack certain key functionality in order to use them on a day to day basis (which is why it’s still in pre-release feature). We can’t wait to see where the dev team will bring this one.

Share this Post

The post How to configure SCCM Phased Deployments appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/sccm-phased-deployments/feed/ 0 55816
SCCM Windows 10 Deployment Guide https://www.systemcenterdudes.com/sccm-windows-10-deployment-guide/ https://www.systemcenterdudes.com/sccm-windows-10-deployment-guide/#comments Mon, 16 Apr 2018 12:51:34 +0000 https://www.systemcenterdudes.com/?p=23143 The race to update Windows 7 computers from your environment is entering its home stretch. Microsoft will end Windows 7 support on January 14th, 2020. If you still have Windows 7 computers in your company, it’s time to seriously plan your migration. If you’ve been reading our blog for a while, you may have seen a couple (!) of post regarding Windows 10 migration. We thought that regrouping all posts in a single one would save you time finding all needed SCCM Windows 10 deployments resources to start. If you are still running SCCM 2012 and have plans to deploy Windows 10, ... Read More

The post SCCM Windows 10 Deployment Guide appeared first on System Center Dudes.

]]>
The race to update Windows 7 computers from your environment is entering its home stretch. Microsoft will end Windows 7 support on January 14th, 2020. If you still have Windows 7 computers in your company, it’s time to seriously plan your migration. If you’ve been reading our blog for a while, you may have seen a couple (!) of post regarding Windows 10 migration. We thought that regrouping all posts in a single one would save you time finding all needed SCCM Windows 10 deployments resources to start.

SCCM Windows 10 Deployment Guide

If you are still running SCCM 2012 and have plans to deploy Windows 10, we recommend starting with part 2 of this guide. (Hint: Deploy SCCM Current Branch).

We will update this post as we add more Windows 10 deployments posts on our blog.

SCCM Windows 10 Deployment Guide

Share this Post

The post SCCM Windows 10 Deployment Guide appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/sccm-windows-10-deployment-guide/feed/ 4 23143
Configure Delivery Optimization in SCCM Task Sequence https://www.systemcenterdudes.com/configure-delivery-optimization-in-sccm-task-sequence/ https://www.systemcenterdudes.com/configure-delivery-optimization-in-sccm-task-sequence/#comments Fri, 13 Apr 2018 12:22:33 +0000 https://www.systemcenterdudes.com/?p=54653 Windows 10 brings a new feature to optimize network performance when it comes to Windows Update. This feature is called Delivery Optimization. Delivery Optimization is a cloud-based service that allows computers on the same network to share updates files to prevent reaching out to Windows Update directly or to a remote WSUS.  Windows 10 clients must have access to the internet to be able to leverage Delivery Optimization to establish a peer-to-peer connection to another Windows 10 computer. With that said, Delivery Optimization as the potential of doing the opposite of what it was designed for. By default, the Download mode is ... Read More

The post Configure Delivery Optimization in SCCM Task Sequence appeared first on System Center Dudes.

]]>
Windows 10 brings a new feature to optimize network performance when it comes to Windows Update. This feature is called Delivery Optimization. Delivery Optimization is a cloud-based service that allows computers on the same network to share updates files to prevent reaching out to Windows Update directly or to a remote WSUS.  Windows 10 clients must have access to the internet to be able to leverage Delivery Optimization to establish a peer-to-peer connection to another Windows 10 computer.

Important Info
If you are using SCCM to deliver Windows Updates, Delivery Optimization has no positive or negative impact on the network. SCCM bypass this feature, except for one case, if Express Updates are used.

We recommend looking at BranchCache or Peer-to-Peer to help with bandwidth management.

This great blog post resume and compare both solutions in details

With that said, Delivery Optimization as the potential of doing the opposite of what it was designed for. By default, the Download mode is configured in LAN Mode. This means that every computer going on the internet through a single IP address like many businesses do will be considered in the same LAN network. This means a remote office could be considered local, then try to share Windows Updates on the internal WAN and then choke the network.

In this post, we will detail how to configure Delivery Optimization in a Task Sequence to prevent using the LAN mode by default.

If you are looking for more Windows 10 customization and configuration tips, see our previous posts :

Delivery Optimization Default Configuration

By default, Delivery Optimization is On for PCs on my local network

SCCM Delivery Optimization Task sequence

If we run the PowerShell command Get-DeliveryOptimizationStatus we can see that the Download Mode is set to 1, which is the LAN Mode

SCCM Delivery Optimization Task sequence

Important Info
If the Download Mode is set to 99, the proxy is likely preventing Delivery Optimization to reach the cloud service. this means that delivery Optimization is kind of turned off.

For the complete list of Download Mode, see the following article on Docs.Microsoft.com

In the registry HKLM/Software/Microsoft/Windows/CurrentVersion/DeliveryOptimization/Config it should be the default

SCCM Delivery Optimization Task sequence

Turn off Delivery Optimization

Delivery Optimization can be turned off manually under Windows Settings/Update & Security/Windows Update/Advanced Options/Delivery Optimization

SCCM Delivery Optimization Task sequence

This can also be done by adding a Reg_Dword to HKML\Software\Microsoft\Windows\CurrentVersion\DeliveryOptimization\Config

  • Name : DODownloadMode
  • Value: 100

SCCM Delivery Optimization Task sequence

When modified by the registry, the Delivery Optimization service must be restarted to take effect.

SCCM Delivery Optimization Task sequence

It can also be enforced by a GPO :

  • Under Computer Configuration/Administrative Templates/Windows component/Delivery Optimization, enable the Download Mode and set it to Bypass(100)

SCCM Delivery Optimization Task sequence

How to configure SCCM Delivery Optimization Task sequence

We were asked in a project to update Windows 10 by using WSUS and that BranchCache would be leveraged to deliver updates more efficiently on the network.

When using BranchCache for Windows Update, Delivery Optimization must be set to ByPass for the Download Mode.

  • Add a Run Command line task
    • Name: Set DeliveryOptimization to ByPass
    • Command Line: Reg ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DeliveryOptimization\Config /v DODownloadMode /t REG_DWORD /d 100 /f

SCCM Delivery Optimization Task sequence

  • Add a Restart task to make sure the service is set in ByPass mode

SCCM Delivery Optimization Task sequence

 

Simple as that!

Share this Post

 

The post Configure Delivery Optimization in SCCM Task Sequence appeared first on System Center Dudes.

]]>
https://www.systemcenterdudes.com/configure-delivery-optimization-in-sccm-task-sequence/feed/ 1 54653