Posts Tagged Windows 10
In SCCM 2012, you may encounter the following PXE error message:
PXE-E53: No boot filename received
PXE-M0F: Exiting Intel Boot Agent
Selected boot device failed. Press any key to reboot….
Unfortunately, there are many instances that will generate the error message above; one of those instances is when you’ve not set your Windows PE x86 to deploy in your distribution point.
Yes, even if you’re using Windows PE (x64), you must enable the (x86) version. (see below)
Posted by edwgon in deployment, Microsoft System Center Configuration Manager 2012 R2 SP1, UDA on September 17, 2015
I’m using the Boot Image to set User Device Affinity (UDA) to devices managed by SCCM 2012 R2 SP1.
First, here’s how we script looks to:
Dim userDA, smsUserMode Set env = CreateObject("Microsoft.SMS.TSEnvironment") ' We enable UDA variable here - before assigning user smsUserMode = "Auto" env("SMSTSAssignUsersMode") = smsUserMode userDA = Inputbox("Type a valid Active Directory user account." & vbCrLf & vbCrLf & _ "Format: DOMAIN\Username", "Name of primary user for device...") env("SMSTSUdaUsers") = userDA ' writing to log wscript.echo "User device affinity set to " & env("SMSTSUdaUsers") wscript.echo "We're going to set UDA by setting SMSTSAssignUsersMode variable to: " & env("SMSTSAssignUsersMode")
I’m going to save this script on a shared network location. This code is widely used by many people, and I’m not the creator of it; I’ve just slightly modified it.
Next, I’m going to customize the Boot Image file in SCCM, see screenshot.
Recently I began to get ready for Windows 10, and part of that process was to get our licensing servers up to date. Since I was getting multiple answers on Microsoft TechNet forums, I decided to open a call with Microsoft Support and get a definitive answer – all information below has been confirmed with Microsoft.
First, Windows Server 2008 R2 will be able to provide licenses for your Windows 10 fleet, with a catch. Microsoft will be deploying a Hotfix for Windows Server 2008 R2 in a month or two, maybe a bit longer, so if your organization can wait, then just hold on tight.
- Add a Windows Server 2012 R2 HotFix, which can be found here
- Reboot server
- Add a SRV record to any of your primary domain controllers
- Wait for all domains to synchronize DNS information
- Install the correct KMS host server key
- You’ll need to go to licensing.microsoft.com and download the proper KMS host server key
- For Windows 10 licensing on a Windows Server 2012 R2 server, we’ll need the following key: Windows Srv 2012R2 DataCtr/Std KMS for Windows 10
- Use the following commands, in an elevated CLI, to register and activate the KMS host server key
- SLMGR /ipk CCCCC-XXXXX-PPPPP-KKKKK-MMMMM
- SLMGR /ato
- After allowing all DCs to synchronize, we’re going to run a command to make sure that the new KMS server is ready to authenticate clients
a. nslookup -type=srv _vlmcs._tcp
b. Copy and paste the command in step 5a onto a desktop and results should be as shown in the screenshot below
- These steps will allow you to install the proper host server key and allow your Windows 10 clients to get licensed.