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
Apr 26, 20191 min read

Can't believe how stupid I am

According to my wife I don’t say this often enough and this is a perfect opportunity to do so… I was wrong! What I did didn’t make the TSenv interface available sooner than normal. What it did just made it persistent so it didn’t disappear when it normally do.


That being said, it is still possible to use the TSEnv to pass a variable from an old media scenario to a TS.


The plus side to the matter, that the env is available as default, is that you don’t have to modify the boot images in any manual way at all in order to utilize it.

Just start a script with the prestart command, wait for the TSEnv to be ready, do some stuff, and set a tsvariable.


I know prestart commands only run once but this is just an example:


https://github.com/MattiasC85/Scripts/blob/master/OSD/Wrapper.ps1


An IRL scenario might be to write the version of the script to a variable and thus be able to correct the issues that you’ve already fixed in the newest version of it but without the need to block all old boot medias.


104 views0 comments

Commenti

bottom of page