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
    • Oct 16, 2018
    • 1 min read

Out of memory



I've had meningitis twice so my memory is not as good as it could have been....

Forgot some other changes that I made in checkfornetwork.vbs.


1.

I try to restore the boot procedure if the script fails. Let's say that the sequence is initiated from software center and checkfornetwork.vbs somehow fails after the client has been rebooted into WinPE. That would cause a boot loop where the computer would load the WinPE-image over and over again even though there's a fully functioning OS installed.

The sub "Reboot" tries to set things straight. Works for both legacy/UEFI. (Even though checkfornetwork.vbs shouldn't fail since we got conditions that verifies that the computer model is certified before that. Which pretty much translates into "We've tested it and added drivers that should work")

2.

Detecting if "Enable command support" is enabled on the boot image and using it to determine if debug options should be shown in case of failurs.

I'll write another post on this in just some minutes, since I got a powershell equivalent as well.

39 views0 comments

Comments

bottom of page