Archive for September, 2015

SCCM 2012 R2 SP1 & PXE-E53 Error(s)

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

IMG_1755

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)

9-21-2015 12-03-34 PM

, , , , , , ,

Leave a comment

SCCM 2012 R2 SP1 and User Device Affinity

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.

Boot Image UDA

That’s it!

, , , , , , ,

Leave a comment

Deploy JAVA & Disable JAVA’s AutoUpdate

The following will allow you to deploy JAVA, using an MSI, with the ability to disable JAVA’s AutoUpdate feature.

  1. Download JAVA manually from here
    1. You can download 64 and 32 bit version
  2. Next, run the installation file, but do not click anything else after the first screen
  3. Go to C:\Users\YourUserName\AppData\LocalLow\Oracle and find the extracted MSI file
  4. Copy the MSI to another location and use ORCA to modify the MSI fi le
    1. ORCA can be downloaded from here
  5. Go to the Properties table and change the properties highlighted in the screenshotJAVA No AutoUpdate
  6. Save the MSI and you’re now ready to deploy JAVA

, , , , ,

Leave a comment

Windows 10 Licensing On A Windows Server 2012 R2

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.

 
Note: Windows Server 2008 is not supported for Windows 10 licensing, this was made clear on my call to Microsoft Support!
 
After installing the Volume Activation feature, the following must be done to prepare Windows Server 2012 R2 to licensing Windows 10 clients.
  1. Add a Windows Server 2012 R2 HotFix, which can be found here
    1. Reboot server
  2. Add a SRV record to any of your primary domain controllers
    New SRV Record
  3. Wait for all domains to synchronize DNS information
  4. Install the correct KMS host server key
    1. You’ll need to go to licensing.microsoft.com and download the proper KMS host server key
    2. 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
    3. Use the following commands, in an elevated CLI, to register and activate the KMS host server key
      1. SLMGR /ipk CCCCC-XXXXX-PPPPP-KKKKK-MMMMM
      2. SLMGR /ato
  5. 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 belowNslookup for SRV
  6. These steps will allow you to install the proper host server key and allow your Windows 10 clients to get licensed.

, , , , ,

Leave a comment