Posts Tagged Windows 10
During my project to upgrade all our Windows 7 Enterprise SP1 (64bit) devices to Windows 10 Enterprise 1809 (64bit), I ran into a compatibility issue during the task sequence. Windows 7 video drivers were detected as incompatible during the in-place upgrade to Windows 10, so I had to find a way to remove the drivers during the SCCM task sequence.
This is the batch file code I used to disable, then remove video drivers from the task sequence.
REM Driver is disabled
devcon disable =display
REM Driver is removed here
devcon remove =display
REM reg add command replaces whatever value is in the SearchOrderConfig with the appropriate value to tell the system NOT to go to windows update for driver updates
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching /t REG_DWORD /v SearchOrderConfig /d 0x0 /f
REM Driver package is removed here
FOR /F “tokens=4 delims= ” %%A IN (‘devcon driverfiles ^=display ^| FINDSTR “Driver installed from”‘) DO devcon.exe dp_delete -f %%A
The following shows where in the task sequence I add the video driver removal step. Also, note that I have a step to copy devcon.exe utility which is not on Windows 7 by default.
I’ve extensively tested this on my DELL devices and it works perfectly.
While attempting to perform an in-place upgrade from Windows 7 Enterprise to Windows 10 Enterprise I came across Error Code 0x80004005.
Looking at C:\WINDOWS\CCM\Logs\smsts.log gave me the clues on the error message.
There are many posts on how to fix this particular error message; it seems that this error code is pretty generic and it shows up on several instances in many SCCM operations – this document particularly deals with a task sequence for an in-place operating system upgrade.
Since this was an in-place Windows upgrade, I needed to find out more detailed information and I was able to get it from C:\$WINDOWS-BT\Sources\Panther this folder contains a list of .XML files that collect compatibility data that is collected during the upgrade process.
I opened the last XML file and this gave me the actual clue as to what was failing during the upgrade process – video drivers were the culprit!
Now I know what’s going on during the task sequence and I can attempt to fix this issue.
I’ll blog about how to fix this issue in a new post, stay tuned!
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.