Pointing Workstations to a WDS server in a different Subnet

If you want workstations in a certain subnet to access a WDS server in a different subnet, you need to add Options 66 and 67 to the Workstations' DHCP server's scope options, as below:

Option 66:
WDS server name (FQDN)

Option 67:
Path of the wdsnbp.com file with the RemInstall share as root: example, boot\x64\wdsnbp.com

One limitation I have read about is that you then can't choose between x64 boot image and x86 boot image. In the example above it would only work for 64-bit workstations.

Changing Default Keyboard to a different language through GPO (Windows 10)

After deploying Windows 10 (it only comes in en-US from VLSC) I was struggling to get the input language changed to en-UK as default. That is, at logon screen, and once user is logged on - with no option to change it to anything else. It seemed the Logon screen would always also show the en-US option (even when specifiying en-UK in MDT task sequence).

All online sources seemed to point to registry keys in 2 locations: HKEY_USERS\.DEFAULT\Keyboard Layout\Preload and HKCU\Keyboard Layout\Preload.

From what I understands, the first location (.\default) is loaded at the logon screen, and the second one relates to actual logged in users.

As suggested by online blogs, I created 2 registry changes in GPO, one in Computer configuration/Preferences/Windows Settings/Registry and the other in User Configuration/Preferences/Windows Settings/Registry.

I chose to update the first keyboard (value 1, order 1) to en-UK and all-out delete the second keyboard (value 2, order 2).

One relates to HK_U\.DEFAULT and the other to Current User:

However I also had to add the following GPO settings: Restrict the UI Language Windows uses for all logged in users -> Disabled (not sure why) and Disallow copying of user input methods to the system account for sign-in -> Enabled.

After doing all this and setting the GPO to "Enforced" (as I didn't want any subsequent GPO to change these settings), it seemed to copy the correct registry keys, although the Login screen change sometimes took a couple of reboots.

Not sure why M$ doesn't make it easier to just enforce a particular keyboard input!