{"id":2495,"date":"2017-04-09T22:34:22","date_gmt":"2017-04-09T20:34:22","guid":{"rendered":"http:\/\/blog.hosebei.ch\/?p=2495"},"modified":"2017-04-09T22:34:22","modified_gmt":"2017-04-09T20:34:22","slug":"configmgr-windows-10-servicing-step-by-step","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=2495","title":{"rendered":"ConfigMgr – Windows 10 Servicing – Step by Step"},"content":{"rendered":"

Today I would like to show you, how you can implement an Upgrade of a Windows 10 Installation through the Servicing Option.
\nI always think of two things, when I have to decide to use an Upgrade Task Sequence or the Servicing Model, and those are:<\/p>\n

  • Do I want to use the Option that the clients will download the Windows 10 Sources from the Microsoft Update Servers?<\/li>\n
  • When I use an Upgrade Task Sequence, I can copy most of the steps from the regular OSD Task Sequence<\/li>\n

    But for this blog post, I would like to show my setup for the servicing model.<\/p>\n

    First of all, I have already written a post about the Update process in a slightly overview manner, you will find this post here: My old post<\/a><\/p>\n

    The first step would be to determine which packages you would like to implement for the upgrade. Based on the fact, that I use English as base language, I will add the Feature on Demand (FoD) packages, and I will also add the feature package NetFx3. My Setup does also contain the German Langauge, which requires me to add the corresponding Language Pack and FoD Packages. The following picture shows the folder of my Packages which I want to include within the Windows 10 Installation:
    \n    \"\"<\/a>
    \n<\/p>\n

    When this is done, you will have to decide, where you would like to store the packages and also some script files on the System Disk of the current Client. I have decided to create a folder named C:\\LP, which is hidden, and two subfolders called LP and Scripts, I would also recommend to modify the default User Permissions, if you don’t want that standard users can change the scripts.
    \n    \"\"<\/a>
    \nTo achieve the copy jobs which are required, I will come back to those scripts later, I have decided to use Configuration Items, rather than an Application or an Old-School Package within the Software Library. But this will require that my clients are able to access those files, because they will not download it from a Distribution Point. I am using Distributed File Services (DFS) to have a single UNC Path, where the clients can download the packages (with BITS of course).
    \nI have decided where my package location resides and have copied all the required packages and scripts to this location:
    \n    \"\"<\/a><\/p>\n

    Then I went on and created a Configuration item named “Windows 10 Servicing CI”:
    \n    \"\"<\/a>
    \nI only selected Windows 10 (x64):
    \n    \"\"<\/a>
    \nWithin the next step of the Wizard, click on “New…” to add a setting, and the following Windows appears:
    \n    \"\"<\/a>
    \nMake sure to have selected the “Setting Type” Script, and as “Data Type” “String”, as shown in the picture above. Afterwards click on “Add Script…” within the Discovery Script Section, and the following script block windows will appear:
    \n    \"\"<\/a>
    \nMake sure that “Windows Powershell” is selected as script language. The script will simply check both file locations, and if the size is not the same, the CI will be reported as non-compliant. You may want to extend the detection script to your needs, as example if you have multiple languages and want to copy only some languages to the client. I have used the following script for this purpose (you will find a zip Download at the end of the blog as well):
    \n#Variables
    \n$LocalFolderLP = \"C:\\LP\\LP\"
    \n$PathToLanguagePacks = \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\"<\/p>\n

    $Compliance = \"Non-Compliant\"<\/p>\n

    #Receive transferred jobs, but not yet finished
    \n$bitstransfers = Get-BitsTransfer -AllUsers
    \nforeach($bitsjob in $bitstransfers) {
    \n if($bitsjob.Jobstate -eq \"Transferred\") {
    \n #End old Transfers due script execution errors
    \n Complete-BitsTransfer -BitsJob $bitsjob
    \n }
    \n}<\/p>\n

    #Start Main Script
    \nIf((Test-Path $LocalFolderLP) -eq $false) {
    \n $Compliance = \"Non-Compliant\"
    \n}
    \nelse {
    \n #Measure both Locations
    \n $SizeOfLPsSource = Get-ChildItem -Path $PathToLanguagePacks -Filter *.cab | Measure-Object -property length -sum
    \n $SizeOfLPsDestination = Get-ChildItem -Path $LocalFolderLP -Filter *.cab | Measure-Object -property length -sum
    \n If($SizeOfLPsSource.sum -ne $SizeOfLPsDestination.Sum) {
    \n $Compliance = \"Non-Compliant\"
    \n }
    \n else {
    \n $Compliance = \"Compliant\"
    \n }
    \n}
    \n#Return the result
    \n$Compliance<\/code><\/p>\n

    Close this Windows by a click on “OK”. Then go ahead and click on “Add Script…” witin he Remedation Script section, and add the following script to the script block:<\/p>\n

    #Copy the Language Pack Files
    \nFunction Start-LPBitsJob([System.IO.FileInfo]$CABFileToCopy, [string]$LocalLPFolder) {
    \n $BitsJob = $null
    \n $BitsJob = Start-BitsTransfer -Source $CABFileToCopy.FullName -Destination $LocalLPFolder -TransferType Download -Asynchronous -DisplayName "CAB Downloads"
    \n}<\/p>\n

    #Variables
    \n$LocalFolderLP = "C:\\LP\\LP"
    \n$PathToLanguagePacks = "\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703"<\/p>\n

    #Start Main Script
    \nif((Test-Path $LocalFolderLP) -eq $false) {
    \n New-Item $LocalFolderLP -ItemType Directory
    \n}
    \n$MakeHidden = Get-Item "C:\\LP" -Force
    \n$MakeHidden.Attributes="Hidden"
    \nif((Test-Path $LocalFolderScripts) -eq $false) {
    \n New-Item $LocalFolderScripts -ItemType Directory
    \n}<\/p>\n

    $CABFilesToCopy = Get-ChildItem -Path $PathToLanguagePacks\\* -Include *.cab
    \nforeach($cabFile in $CABFilesToCopy) {<\/p>\n

    if($cabFile.length -ne (Get-Item ($LocalFolderLP + "\\" + $cabFile.Name)).Length) {
    \n #Write-Host "not same"
    \n Start-LPBitsJob $cabFile $LocalFolderLP
    \n }
    \n else {#Write-Host "same"
    \n }
    \n}<\/p>\n

    $AllBitsDownloads = Get-BitsTransfer -Name "CAB Downloads"
    \n$DLFinishedLoop = $false
    \nwhile ($DLFinishedLoop -eq $false) {
    \n $DLFinished =$true
    \n foreach($BITSDownload in $AllBitsDownloads) {
    \n if($BITSDownload.JobState -ne "Transferred") {
    \n $DLFinished = $false
    \n }
    \n }
    \n if($DLFinished -ne $false) {
    \n $DLFinishedLoop = $true
    \n }<\/p>\n

    sleep 1
    \n #write-host "loop"
    \n}<\/p>\n

    #Now finish all Transfers
    \n$AllBitsDownloads | Complete-BitsTransfer<\/code><\/p>\n

    As you can see, I’m using a BITS Transfer to download the packages and all packages are checked (based on the size), and a specific package is only downloaded if required. For more information about starting a BITS download through Powershell consult this Microsoft document: Using Windows PowerShell to Create BITS Transfer Jobs<\/a>
    \nYour remediation script block should look like this:
    \n    \"\"<\/a>
    \nWhen this is done, we can switch to the “Compliance Rule” Tab and click on “New…”:
    \n    \"\"<\/a>
    \nFill the opened window with the required information, make sure to check the Box at “Run the specified remediation script when the setting is noncompliant”<\/strong>:
    \n    \"\"<\/a>
    \nBy clicking on OK twice, the first setting within the configuration item is finished. Now it is time to add the setting to copy the setupconfig.ini file, which is required to instruct the Windows Upgrade to use the downloaded packages and to execute a script after the installation. For more information about the setupconfig.ini refer to this Microsoft Document:     Use Setupconfig.ini to install Windows<\/a>
    \nMy SetupConfig.ini is quite simple, I’m still using the same as outlined in the     old post<\/a>.
    \nNow a click on “New…” will open again a new setting:
    \n    \"\"<\/a>
    \nIn the opened window, fill out the settings as shown below:
    \n    \"\"<\/a>
    \nAdd the following script to the Discovery section:<\/p>\n

    #Path to setupconfig File
    \n$SourceFileLocation = \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\\SetupConfig.ini\"<\/p>\n

    $Compliance = \"Not-Compliant\"
    \nif((Test-Path -Path \"$env:SystemDrive\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\\setupconfig.ini\") -eq $false) {
    \n $Compliance = \"Not-Compliant\"
    \n}
    \nelseif((Get-Item \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\\SetupConfig.ini\").Length -ne (Get-Item \"$env:SystemDrive\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\\setupconfig.ini\").Length) {
    \n $Compliance = \"Not-Compliant\"
    \n}
    \nelse {
    \n $Compliance = \"Compliant\"
    \n}
    \n$Compliance<\/code><\/p>\n

    My remediation script, which will copy the setupconfig.ini to the correct place does not change the folder permissions of the WSUS folder. I would recommend for your environment to change the folder, or at least the file permission, that a regular user can’t modify the setupconfig.ini File. This is my remediation script for the ini file:<\/p>\n

    if((Test-Path \"C:\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\") -eq $false) {
    \n New-Item -Path \"C:\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\" -ItemType Directory
    \n}
    \nCopy-Item -Path \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\\SetupConfig.ini\" -Destination \"$env:SystemDrive\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\\SetupConfig.ini\" -Force<\/code><\/p>\n

    When you have added both scripts, switch to the Compliance Rules Tab, and add a new rule by a click on “New…”, fill out the opened rule window as in the following picture:
    \n    \"\"<\/a>
    \nMake sure again to have ticked the box to run the remediation script.
    \nAnd the last CI setting will copy the scripts that are required to be executed after the Windows Upgrade is done, but before a user can logon. The process is the same like for the two settings we already have created. Here is the Discovery Script which I’m using:<\/p>\n

    $LocalFolderScripts = \"C:\\LP\\Scripts\"
    \n$SourceFileLocation = \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\"<\/p>\n

    $Compliance = \"Not-Compliant\"<\/p>\n

    $AllLocalScripts = Get-ChildItem -Path $LocalFolderScripts\\* -Include *.bat,*.vbs,*.ps1
    \n$AllSourceScript = Get-ChildItem -Path $SourceFileLocation\\* -Include *.bat,*.vbs,*.ps1
    \nif($AllLocalScripts.Count -ne $AllSourceScript.Count) {
    \n $Compliance = \"Not-Compliant\"
    \n}
    \n$SizeOfScriptsSource = Get-ChildItem -Path $SourceFileLocation\\* -Include *.bat,*.vbs,*.ps1 | Measure-Object -property length -sum
    \n$SizeOfScriptsDestination = Get-ChildItem -Path $LocalFolderScripts\\* -Include *.bat,*.vbs,*.ps1 | Measure-Object -property length -sum
    \nif($SizeOfScriptsSource.sum -ne $SizeOfScriptsDestination.sum) {
    \n $Compliance = \"Not-Compliant\"<\/p>\n

    }
    \nelse {
    \n $Compliance = \"Compliant\"
    \n}
    \n$Compliance<\/code><\/p>\n

    And this is the remediation script:<\/p>\n

    Function Start-BitsJob([System.IO.FileInfo]$FileToCopy, [string]$LocalFolder) {
    \n $BitsJob = $null
    \n $BitsJob = Start-BitsTransfer -Source $FileToCopy.FullName -Destination $LocalFolder -TransferType Download -Asynchronous<\/p>\n

    while (($BitsJob.JobState -eq \"Transferring\") -or ($BitsJob.JobState -eq \"Connecting\")) { sleep 5;} # Poll for status, sleep for 5 seconds, or perform an action.<\/p>\n

    Switch($BitsJob.JobState)
    \n {
    \n \"Transferred\" {Complete-BitsTransfer -BitsJob $BitsJob}
    \n \"Error\" {$BitsJob | Format-List } # List the errors.
    \n default {\"Other action\"} # Perform corrective action.
    \n }
    \n}<\/p>\n

    $LocalFolderScripts = \"C:\\LP\\Scripts\"
    \n$PathToLanguagePacks = \"\\\\deheim.hosebei.ch\\hosebeiDFSroot\\Deployment\\OS\\Windows 10\\LanguagePacks\\1703\"<\/p>\n

    if((Test-Path \"C:\\LP\\Scripts\") -eq $false) {
    \n New-Item -Path \"C:\\LP\\Scripts\" -ItemType Directory
    \n}<\/p>\n

    $ScriptFilesToCopy = Get-ChildItem -Path $PathToLanguagePacks\\* -Include *.ps1,*.vbs,*.bat
    \nforeach($ScriptFile in $ScriptFilesToCopy) {
    \n if($ScriptFile.length -ne (Get-Item ($LocalFolderScripts + \"\\\" + $ScriptFile.Name)).Length) {
    \n #Write-Host \"not same\"
    \n Start-BitsJob $ScriptFile $LocalFolderScripts
    \n }
    \n else {#Write-Host \"same\"}
    \n}
    \n<\/code><\/p>\n

    When you have finished adding the third setting, your Configuration Item should look like this:
    \n    \"\"<\/a>
    \nIf you click on Next, the wizard will show you the created Compliances Rules according to the settings, make sure that “Remediate” is on Yes:
    \n    \"\"<\/a>
    \nFinish the wizard by clicking on Next twice and close it afterwards. Now we need to create a Baseline and just add our Compliance Item to it:
    \n    \"\"<\/a>
    \nAfter a click on OK, the baseline is created and ready to be deployed on a collection. Within the deployment wizard of the baseline, make sure to tick the check box at “Remediate noncompliant rules when supported”:
    \n    \"\"<\/a>
    \nNow everything is quite good and you can create a collection based on the baseline:
    \n    \"\"<\/a><\/p>\n

    And here is my batch file which I run after the Windows 10 Upgrade:
    \nmkdir C:\\LP\\1703_OK
    \npowershell.exe -NoProfile -ExecutionPolicy Bypass -File \"C:\\LP\\Scripts\\Remove-Apps.ps1\"<\/code><\/p>\n

    The PowerShell Script “Remove-Apps.ps1” removes Universal apps which I don’t want on the clients. This is the content of Remove-Apps.ps1:<\/p>\n

    #Initalize Array
    \n$AppstoRemove = New-Object System.Collections.ArrayList<\/p>\n

    #Add Apps to Array
    \n$AppstoRemove.Add(\"Microsoft.NetworkSpeedTest_1.0.0.23_x64__8wekyb3d8bbwe\") #NetworkSpeedTest
    \n$AppstoRemove.Add(\"46928bounde.EclipseManager_2.2.1.31_neutral__a5h4egax66k6y\") #Eclipse Manager
    \n$AppstoRemove.Add(\"6Wunderkinder.Wunderlist_3.6.25.0_x64__b4cwydgxqx59r\") #Wunderlist
    \n$AppstoRemove.Add(\"Microsoft.MicrosoftOfficeHub_17.8017.5925.0_x64__8wekyb3d8bbwe\") #Get Office Sneak App
    \n$AppstoRemove.Add(\"Microsoft.BingTranslator_4.7.0.0_x64__8wekyb3d8bbwe\") #Bing Translator
    \n$AppstoRemove.Add(\"D5EA27B7.Duolingo-LearnLanguagesforFree_2017.112.1.0_x64__yx6k7tf7xvsea\") #Language Learning App
    \n#$AppstoRemove.Add(\"Microsoft.SkypeApp_11.12.112.0_x64__kzf8qxf38zg5c\") #Skype for Business App
    \n#$AppstoRemove.Add(\"Microsoft.Office.OneNote_17.7967.57741.0_x64__8wekyb3d8bbwe\") #OneNote App<\/p>\n

    $AppstoRemove | Remove-AppxPackage<\/code><\/p>\n

    You might want also to configure the Language settings as they were before. Then you can use the solution from Roger Zander, to apply Language Settings with an XML: Windows 10 MUI challenge<\/a>
    \nHere you will find a Zip-File with all my scripts used within this blog:     Windows 10 Upgrade Scripts<\/a><\/p>\n

    Now you can deploy the upcoming release to your clients, just like a regular update.<\/p>\n

    If you think this post was useful, please leave a comment, and if you see issues or you can recommend better techniques, leave a comment as well, or get in touch with me on twitter<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Today I would like to show you, how you can implement an Upgrade of a Windows 10 Installation through the Servicing Option. I always think of two things, when I have to decide to use an Upgrade Task Sequence or the Servicing Model, and those are: Do I want to use the Option that the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,27,33,41,43],"tags":[],"class_list":["post-2495","post","type-post","status-publish","format-standard","hentry","category-configmgr","category-operating-system-deployment","category-sccm","category-updates-management","category-windows-10"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2495","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2495"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2495\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}