This user hasn't shared any biographical information
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 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.
The following will allow you to deploy JAVA, using an MSI, with the ability to disable JAVA’s AutoUpdate feature.
- Download JAVA manually from here
- You can download 64 and 32 bit version
- Next, run the installation file, but do not click anything else after the first screen
- Go to C:\Users\YourUserName\AppData\LocalLow\Oracle and find the extracted MSI file
- Copy the MSI to another location and use ORCA to modify the MSI fi le
- ORCA can be downloaded from here
- Go to the Properties table and change the properties highlighted in the screenshot
- Save the MSI and you’re now ready to deploy JAVA
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.
Using VMware PowerCLI, PowerShell, there’s a nifty way to get a list of all VMDKs associated with a virtual machine(s).
Here’s the command:
For this sample, I chose to output the following fields:
Here’s how I was able to install MS-DOS 6.22 on my iMac using Parallels 10.
I’m not going into details on how to create the virtual machine using Parallels, it’s easy to figure that out.
Here is the hardware configuration for the MS-DOS 6.22 virtual machine.
CPU & Memory
In the past few weeks, I started working with NMIS. The application does a great job monitoring all sorts of devices. I decided to use the free version, so support is mainly based on whatever is found on the web or from NMIS’ email group.
- A working NMIS environment
- I downloaded the NMIS appliance and got the application to work in an hour.
- A working installation of a mail daemon in the linux box where NMIS is running
- For my environment I used sendmail, so most of these steps are related to sendmail.
- A working installation of Exchange server
- Logon to the linux server where NMIS is running from
- Go to /etc/mail directory
- run vi sendmail.cf
- You can use any file editor, I just prefer vi
- If using vi type: /DSsmtp
- / does a search for string DSsmtp
- Once that line is found, then you’ll want to change it to: DSsmtp.YourDomain.com
- Save the file and reload sendmail services
In this post, I’m going to go over the deployment of AutoDesk Building Design Suite Premium 2015 using SCCM 2012.
- You’re going to use AutoDesk BDSP setup wizard to create the ‘image’ folder using AutoCAD’s own image building process. This process will allow you to perform a standard, or custom, installation of AutoDesk’s applications and features, so I’m not going into details about this. At the end of this process, AutoDesk’s wizard will create a SMS_SCCM scripts folder which contains text files that will allow you to install and un-install BDSP; we’re going to use these text files for the deployment.
- The SCCM client imposes a folder size on C:\Windows\ccmcache folder, so we’re going to have to use another script to call the installation process scripts created in step 1.
Here’s what I use for a Detection Method, basically I’m looking for BDSP executable files on the target computer.
This process works well for my environment.
Make a note that this installation may take hours (2-4)…
Ever since we upgraded to Windows 7 Enterprise, our branch office users started complaining about extremely slow logon and logoff. In some instances, a user logon or logoff could take over ten minutes!
- Folder redirection (Desktop, Favorites, Links, Documents, Pictures, Videos, Searches and Contacts folders are redirected to a file server in our datacenter)
- Roaming profiles (Users’ roaming profile folders are located on a file server in our datacenter)
- Offline Files (Users’ home folders were set as offline files/folders)
As of 9/30/2014, the AppData re-direction workaround broke Internet Explorer browsing – pages take a very long time to load while browsing using IE (10 and up). I opened a case with Microsoft and it looks like the slow down of IE is by design because we’re re-directing AppData and AppData, in our environment, isn’t on a local server to the users’ network. We moved AppData to our central file server located on our data center in a co-location. Again, this bit of information isn’t found on Microsoft’s documentation, so be careful before you go re-directing AppData!
We’re now looking into possibly removing roaming profiles and AppData re-direction because this is affecting productivity for our users.
In this article I’m going to show how to create a SCCM 2012 task sequence to deploy Windows Server 2008 R2 using Microsoft Deployment Toolkit 2013.
- Make sure to have an Operating System Images and an Operating System Installers ready for Windows Server 2008 R2 already installed in SCCM
- Download, install and configure Microsoft Deployment Toolkit 2013 (Make sure to perform these steps on the SCCM server!)
- Make sure MDT is properly installed
- Make sure MDT is properly installed
- Once you make sure that MDT is properly installed, then you need to create a MDT package in SCCM
- Basically, from the MDT installation folder, you’re going to copy the following folders to a network share that you’ll use to create the SCCM package: Control, Scripts, Servicing and Tools
- Once in the create package wizard, make sure you select This package contains source files and point it to the network share you created in step 2.1
- In the Program Type screen, select Do not create a program
- Once finished, make sure to Distribute Content
- Make sure these steps are done properly or you’ll have major issues with the rest of this how-to. I found some great information about creating an MDT package on this link
- Click on Create MDT Task Sequence
- In the Choose Template screen, select Server Task Sequence
- In the General screen, provide a name and description for the task sequence
- In the Details screen, provide the domain and domain account that will be used to join such domain. Also provide organization name and product key number for the installation of the server OS
- In Capture Settings screen, select This task sequence will never be used to capture an image
- In Boot Image screen, select your WinPE boot image, in my case that will be Boot image (x64)
- In MDT Package screen, you’re going to select the MDT package created earlier in this how-to (this portion will either make or break this how-to)
- In OS Image screen, select the Windows Server 2008 R2 WIM file (Described in requirements step 1)
- In OS Image Index, select the version of server you want to run, in my case it will be Sever 2008 R2 Enterprise
- In Client Package, select the SCCM client package that you’ve been using in your environment
- In Settings Package screen, in my case I selected just any package from the list…because I’m going to disable these tasks later on
- In Sysprep Package, there’s only one option already selected, so just hit Next button
- Hit Next until you get to Finish
Also, pay close attention to the following fields in Apply Operating System Image section:
- Destination – Logical drive letter stored in a variable
- Variable name – System
- System is used for drive letter, in this case C:
Next, we’re going to configure the Apply Windows Settings section.
Here, you’re going to type your company’s name and user name for this server, also you’ll need the server’s product key numbers.
In our environment, we have a licensing server, so I set the Licensing server field to Do not specify. Make sure you set the Time Zone as well.
Now, we’re going to Apply Network Settings to our server installation.
This section will allows us to join this server to the domain. You can specify your domain name and the domain organizational unit (OU) where the server account can be placed.
The account used to join the server to the domain can be just a regular domain account.
We’re now going to load drivers to our server installation, this is a nice to have option, but not required. Obviously, you have to have the driver packages created previously.
Next, we’re going to load the SCCM client to our server installation. In this section, I’m loading the default SCCM client, which comes with SCCM installation, and I’m also installing a hotfix for the SCCM client.
This section is pretty much self explanatory, just select the server roles and features you want to add then continue.
I have disabled some section (New Computer Only and Capture the Reference Machine) on purpose, you don’t have to to that.