top of page

OUR PRECONDITIONS

  • 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.

Search
Writer's picturesomeguy100

Tab complete any .NET type as a param to a powershell script

There are a plenty of examples online of how to use validateset in a powershell script.

And I do know that [System.ConsoleColor] works using tab complete by default.

But I’m in the middle of a powershell WPF-POC and noticed that [System.ConsoleColor] doesn’t by far include the wide ranges of colors available and it bothered me so…


The following example is only showing how to apply this to [System.Drawing.Brushes] but I bet you could use the same technique to any other .NET type as well.


Hopefully it’ll save someone the time it took for me to google it and pick up the vital parts :)


62 views0 comments

Comments


bottom of page