Custom Notifications for an OS Upgrade Task Sequence

Custom notifications that can be used in an OS Upgrade task sequence in ConfigMgr.Contains PowerShell scripts and an example task sequence that demonstrates how to use them.

5 Star
2,375 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • _SMSTSOSUpgradeActionReturnCode.txt
    1 Posts | Last post October 25, 2019
    • The file _SMSTSOSUpgradeActionReturnCode.txt is created but not written.
      I set a large amount of disk and ram requirement to test it.
      Any Idea?
  • Error 4294770688 or 0xFFFD0000 received
    1 Posts | Last post September 20, 2019
    • Hello,
      I add the custom script into new task sequence, apparently it showing Error 4294770688 or 0xFFFD0000 in SMSTS log.
      But i do some customization on the file path which copied to %Windir%/windows/Temp/myfoldername. Manual test on the script it works but not during TS running.
      Here is the TS Run Command line script:
      ServiceUI.exe -process:TSProgressUI.exe "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -WindowStyle Hidden -NoProfile -ExecutionPolicy bypass -nologo -file Set-UpgradeSuccessfulNotification.ps1
  • MDT
    1 Posts | Last post July 04, 2019
    • Hi,
      Will this script work in an MDT environment?
  • Download
    1 Posts | Last post October 03, 2018
    • Hello
      I can not download the files, the grey box turn up and I agree to the therms and click accept, then nothing happens?
  • This looks great!
    2 Posts | Last post February 16, 2018
    • Trevor, I've never imported a TS .zip file before, so bare with me. When I try to import your .zip, I receive an 'import failure' indicating 'Cannot validate a dependency to Operating System Upgrade Package D1G003E0'.  
      I haven't setup any OS upgrade package yet, I'm assuming this is why I'm receiving this error.  Is it simply matter of setting one up first, then importing the .zip, or do I have to somehow reference the OS upgrade package when trying to import the TS? 
    • Disregard.  I simply imported with conflicts, and see that I need to point the TS steps to the powershell package.   Thanks for this setup!
  • Upgrading from 1.0 to 1.2
    2 Posts | Last post November 24, 2017
    • Can you verify that it is just script upgrades from 1.0 to 1.2?
      I looked at the example TS, but didn't see any changes
    • Yes just the scripts are updated. Nothing needs to be changed in the example task sequence.