• The old network infrastructure, referred to as OldNet:
    Doesn’t support 802.1x.
    Two domains on different VLAN’s with a one way trust, referred to as Enterprise and Educational.
    The two domains have their own network infrastructure, different IP Helpers, DNS, DHCP and so on.

  • The new infrastructure, referred to as NewNet:
    802.1x is required using CISCO ISE and Layer 3 switches.
    Only one fallback net with its own IP range, common for both domains, which also supports WebAuth guest access.
    The two domains still have their own IP range, DHCP, DNS etc. but will use the same PXE-server since PXE boot is taking place on the fallback network.

  • Both the old and the new network infrastructure will be used to deploy Windows 10 x64 and Windows 7 x86.

  • MAB will not be used during OSD, the network team don’t want to spread a special OSD VLAN so clients will get an IP address according to its current location and only certificate-based authentication is allowed.

  • The task sequence needs to support both the new computer and refresh scenario as well as BIOS to UEFI conversion regardless of the currently installed operating system.
    The scripts used for managing 802.1x needs to support Windows 7 and its PowerShell version.

  • someguy100

Create a custom status message and use its data as arguments to a server side command.

Updated: Mar 9, 2020

Status filter rules has been around for ages so that's not what this post is about. This post is about using the same functionality but whenever you want to by sending a MessageID of your choice, customizing the information sent and using that information as arguments to a command.

Most rules I’ve seen have been triggered by a fail or success event during a sequence and has been used to send or create some kind of report of the outcome.

Event Fail=11170

Event Succeeded=11171

The commandline for the script could look like this:

“TSOutcome.vbs /ComputerName:%msgsys /ProgramSuccess:Yes”

Useful? Sure, but very limited and %msgsys is a predefined variable.

Status message variables: https://docs.microsoft.com/en-us/previous-versions/system-center/configuration-manager-2007/bb693758(v=technet.10)

But what if you want to do something else in the middle of an OSD, like setting variables to the Computer-Resource running the TS?

Well, you can.

There are a number of tools out there that can help you.

StatGen by 2Pint Software (although it’s not working too well in WinPE with multiple MP’s) and the tool we use, OneVinn’s SCCM Console Extension which is great, just to mention two.

So went back and took a look at some stuff I played around with some time ago and here’s the result.

This command:

With this rule:

Will look like this in the log:

But the strings will still be passed to the command and this is the result:


And please think about security, escape characters etc, and try to use named arguments if you decide to use this method.

If you can trigger a script from a computer in WinPE and even before starting the TS, anyone can!

“-MP” needs to be set if running outside a TS or if the computer hasn’t got the Advanced client installed (Not tested)

If you just want to write something custom in the log then just leave the messageID alone and pass some insertionsstrings as arguments, the default prop-textfile will do the rest :)

1,096 views3 comments

©2018 by 802.1x and SCCM - For better, For worse. Proudly created with Wix.com

This site was designed with the
website builder. Create your website today.
Start Now