I’m back with ConfigMgr OSD Troubleshooting & OSD Known Issues Guide Part 2. Let’s understand how to fix the ConfigMgr OSD error that is so complex and confusing. It was really frustrating to troubleshoot and find the root cause of the issue.
We are back with another issue during TS where we were trying to deploy “Windows 10 V 1909″ and it was failing to enable “.NET 3.5“.
- We are continuing the previous blog “OSD Known Issues and Troubleshooting“
Read all about it.
- Whitepaper https://www.anoopcnair.com/download-whitepaper-on-top-10-best-practices-on-windows-10-osd-with-sccm-configmgr/
- Best Practices https://www.anoopcnair.com/windows-10-osd-best-practices/
- Below was the error printed in the SMSTS log.
Running action: Run Command Line- .Net 3.5 Sub Features Failed to run the action: Running action: Run Command Line- .Net 3.5 Error 2146498529 SSL, using authenticator in request. In SSL, but with no client cert Set a global environment variable_SMSTSLastActionRetCode=2146498529
- The box below the screenshot should be checked through the TS step enable .NET 3.5.
After trying everything I posted to our Forum “How To Manage Devices”. Got ideas about offline and DISM from Ankit, Jitesh, and Rajul. I have mentioned the fix too in the forum but we will discuss it here as well. https://forum.howtomanagedevices.com/endpointmanager/osd/enable-net-3-5-in-windows-10-using-ts-package-application-offline-media-script-online/#comment-4206
ConfigMgr OSD Troubleshooting
Following are the troubleshooting steps performed to fix the SCCM OSD error.
- PS Script
- Offline Installer
MS Says you need internet to enable the legacy version of “.NET” because it requires CAB Files to download. If you read the https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10.
Not only that. You need a specific SXS folder based on the OS version. For example, we can’t use the SOURCE/SXS from Windows 10 V 1806 if we want to enable .NET on Windows 10 V 1909. I am assuming this was done to reduce the image size.
The easiest version of the fix was to inject it in WIM itself using DISM but my hands were tied as I don’t manage the OSD part (TS, Boot Image, Boot Media, WIM, etc). I can only troubleshoot.
After continuous OSD troubleshooting, we decided that it’s not related to SCCM, and let’s see it from a core OS perspective.
Started reading logs collected from the failed machines.
- All logs with their description – In-depth:- https://www.anoopcnair.com/configmgr-client-logs-details-sccm-client-log/
- Log reading tips https://www.anoopcnair.com/sccm-logs-files-list-of-configmgr-log-files/
Came to one CBS log at the location “C:\Windows\Logs\CBS”. It clearly says trying to download supporting files from MS Site over the Internet.
Asked the firewall team to whitelist the URL and boom. We are back in business.
- SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide with SMSTS.log
- Learn How to Troubleshoot SCCM Task Sequence Debugger
My name is Deepak Rai, and I am a Technical Lead on SCCM and Intune with more than 14 years of experience in IT. My main domain is SCCM (AKA ConfigMgr, CB, MECM, etc.), Intune, and Azure (Runbooks). I have worked on several platforms (Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec, NDMP devices Like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, HP storage works 4048 MSL G3, Data Deduplication related troubleshooting.) in these 13 years but at last ended up to the technology from which I started as IT Engineer (SCCM).