WinPE network adapter only works after manual drvload, despite driver present in SCCM boot image
Below are three sanitised versions suitable for an SCCM community forum. They retain the technical evidence needed for troubleshooting without disclosing internal server names, domains, IP addresses, MAC addresses, package IDs, or the organisation’s identity. Hi, I am building an SCCM OSD environment and have encountered an issue where the wired network adapter is not initialised automatically after WinPE loads. Environment Microsoft Configuration Manager Current Branch 2603 Current Windows ADK and WinPE add-on x64 WinPE boot image PXE-enabled Distribution Point Lenovo ThinkBook 14-IIL, Type 20SL Realtek PCIe GbE network adapter Realtek driver: rt640x64.inf Driver version: 10.43.723.2020 Symptoms The device successfully: Contacts the correct PXE server Downloads the x64 boot image Starts WinPE Reaches the Configuration Manager screen However, the Task Sequence Wizard does not continue. The task-sequence log shows that WinPE repeatedly fails to download the PXE variable file from the PXE server: Unable to download PXE variable file. Exit code=14. Failed to download PXE variable file after 6 retries. PxeGetPxeData failed with 0x8004016c. Running ipconfig at this point shows no active Ethernet adapter. Troubleshooting completed I have: Imported the Realtek PCIe GbE driver into SCCM Added the driver to the x64 boot image Confirmed the driver is listed under the boot image’s Drivers tab Reloaded the boot image using the current Windows ADK Updated the Distribution Point Confirmed the boot image is distributed successfully Confirmed the PXE copy of the WIM has a current timestamp Mounted the distributed WIM and confirmed the driver is present: Driver: oem5.inf OriginalFileName: rt640x64.inf ProviderName: Realtek ClassName: Net Version: 10.43.723.2020 The driver does not appear to bind or initialise automatically during WinPE startup. Manual workaround If I copy the complete Realtek driver folder to a USB drive and run: drvload "D:\LAN_V02\rt640x64.inf" wpeutil InitializeNetwork`` The driver loads successfully, the device receives a valid DHCP address, and it can reach the SCCM server. The task sequence then proceeds successfully if the driver is loaded before the PXE variable-file retries expire. Question Why would a network driver work correctly when loaded manually with drvload, but not initialise automatically when the same driver is confirmed as present in the distributed WinPE boot image? Is there a recommended way to make this driver load automatically that will scale across multiple laptop and desktop models? I would prefer to avoid: A model-specific prestart command Manually loading drivers from USB Adding complete model driver packs to the boot image Any advice on WinPE driver ranking, Plug and Play initialisation, driver versions, or recommended SCCM boot-image practices would be appreciated.
SCCM - 23/24H2 to 25H2 Upgrade
Hello SCCM Community! Having an issue with upgrading devices from 23 and 24H2 to 25H2, I am downloading the newest version in SCCM under Windows Servicing and Feature Upgrades and deploying it to the targeted collection, but nothing shows in Software Center. Upon checking the UpdatesDeployment log, it shows Actionable Updates = 0 in one of the lines, but I'm wondering why WUA is determining updates do not apply to the machine. I believed this could be a GPO restriction but I've confirmed that there are no conflicting GPOs or Registry Edits. Any suggestions? Thanks!
SYSTEM CENTER IMPLEMENTATION & LICENSING Guide
Dear Microsoft Community, Our organization is planning to deploy a comprehensive IT management solution using the Microsoft System Center Suite. The goal is to streamline infrastructure operations, enhance backup and recovery, manage both virtual and physical resources, oversee endpoints, and maintain security and compliance. We need guidance regarding the number and type of licenses required, specifically Client Management Licenses (CML), Server Management Licenses (ML), and System Center Suite licenses.Agents will install on 2 DC's but will not get configurations
Hello, I have 2 DC's that when i install the MECM agent on them, they will install but will not get the configuration files and when i open the client on the machines its missing the configurations tab and the action tab only has 2 actions. also, on the general tab of the client, the Client Certificate says "none" I know the easy answer is this is a "boundary issue" but it is not. i have other servers with the same IP address range and they have no issue getting the client fully configured. It is not a local firewall issue as i tried turning it off and got the same results. in the ccmsetup logs i am seeing this "Failed to get MDM_ConfigSetting instance, 0x80041013" can anyone please help figure out what is going on here?? thanks in advance
Windows 11 23H2 Cumulative Updates not shown in WSUS/SCCM
Hi everyone, I want to start rolling out devices in my company with Windows 11 23H2 via SCCM. However, I first need to update the existing 23H2 image with the November 24 cumulative update (KB5046633). In SCCM and WSUS, I can't find the 23H2 product categories for synchronization, but 24H2 is showing up. What could be the reason for this?Update 2309 for Microsoft Configuration Manager current branch is now available.
Site infrastructure Introducing SQL ODBC driver support for Configuration Manager Starting with Configuration Manager 2309 release, Configuration Manager requires the installation of the ODBC driver for SQL server 18.1.0 or later as a prerequisite, SQL ODBC Download. This prerequisite is required when you create a new site or update an existing one and on all remote roles. Important Microsoft ODBC Driver for SQL Server 18.1.0 or later needs to be installed on Site Servers and site system roles before upgrading to 2309 version. Do not uninstall SQL native client 11 until we call out in further communications. Configuration Manager doesn't manage the updates for the ODBC driver, ensure that this component is up to date. For more information, see SQL ODBC driver for the site server Option to schedule Scripts execution time Starting in Configuration Manager current branch version 2309, you can now schedule scripts' runtime in UTC. The run Script Wizard now offers a scheduling option that enables administrators to schedule the execution of scripts. It provides a convenient way to automate the running of scripts on managed devices according to specified schedules. For more information, see Schedule scripts' runtime External service notification Run details from Azure Logic application. Starting in Configuration Manager current branch version 2309, when Azure Logic App generates notifications related to specific events, CM can now capture and display these notifications. This integration enables the monitoring of Azure Logic App notifications directly within the MCM console, providing a centralized location for tracking critical events, taking appropriate actions and maintains a high level of operational efficiency. For more information, see External service notification. New Site Maintenance task “Delete Aged Task Execution Status Messages” is now available on primary servers to clean up data older than 30 days or configured number of days Starting in Configuration Manager current branch version 2309, you can now enable this feature by utilizing the Site Maintenance Window or using PowerShell Commandlet. By default, it has been set to run on Saturday and delete the data older than 30 days. It does so by cleaning up [dbo].TaskExecutionStatus Table Example : PowerShell Commandlet: Set-CMSiteMaintenanceTask -Sitecode "XXX" -MaintenanceTaskName "Delete Aged Task Execution Status Messages" -DaysOfWeek Friday For more information, see Delete Aged Task Execution Status Messages. Software updates Update Orchestrator Service (USO) for Windows 11 22H2 or later with windows native reboot experience In Configuration Manager current branch version 2309, when installing software updates from Configuration Manager, administrators can now choose to use the native Windows Update restart experience. To use this feature, client devices must be running Windows build 22H2 or later. From the Computer Restart client device settings, ensure that Windows is selected as the restart experience. Branding information is included in the Windows restart notification for updates that require restart. For more information, see Device restart notifications Maintenance window creation using PS cmdlet We've extended the Offset parameter for Maintenance windows. The cmdlet New-CMMaintenanceWindow is used to create a maintenance window for a collection. Earlier the Offset parameter could be set only between 0 and 4. Now it has been extended between 0 to 7. Example : PowerShell Commandlet: New-CMSchedule -Start (Get-Date) -DayOfWeek Monday -WeekOrder Second -RecurCount 1 -OffSetDay 6 OS deployment OSD preferred MP option for PXE boot scenario Starting in Configuration Manager current branch version 2309, Preferred Management Point (MP) option will now allow PXE clients to communicate to an initial lookup MP and receive the list of MP(s) to be used for further communication. When the option is enabled, it allows an MP to redirect the PXE client to another MP, based on the client location in the site boundaries. For more information, see Install-and-configure-distribution-points Enable Bitlocker through ProvisionTS In Configuration Manager current branch version 2309, Escrowing recovery key to Config Manager Database is now supported using ProvisionTS. ProvisionTS is the task sequence that is executed at the time of provisioning. As a result, device can escrow the key to Config Manager Database instantly. For more information, see Preprovision-BitLocker-in-Windows-PE Windows 11 Edition Upgrade using CM Policy settings Starting in Configuration Manager current branch version 2309, administrator can now create a policy using edition upgrade in Configuration Manager to update the Windows 11 edition. For more information, see Upgrade Windows devices to a new edition Windows 11 Upgrade Readiness Dashboard Starting in Configuration Manager current branch version 2309, administrators can use this dashboard to devise their windows 11 upgrade strategy and discover the devices in the organization, which are ready for Windows 11 Upgrade. This Dashboard also provides a count by installed Feature update version and a view of all Windows devices inside the organization. Administrators can create a collection of Windows 11 ready for upgrading devices and roll out feature updates to them. For more information, see Manage Windows 11 readiness dashboard , For Co-managed devices, see Use Windows compatibility reports for Windows 10 and Windows 11 updates in Intune Cloud-attached management New Cloud Management Gateway (CMG) creation via Console Starting in Configuration Manager current branch version 2309, We have enhanced security of web (server) app for the creation of CMG. For new CMG creation, users can select tenant and the app name using the Azure AD tenant name. After selecting tenant and app name the sign-in button appears, follow rest of the process as per the setup CMG. Note Pre existing CMG customers must update their web server app by navigating to Azure Active Directory Tenants node --> select the tenant --> select the server app --> click on "update application settings". For more information, see Configure Azure Active Directory for CMG New Cloud Management Gateway (CMG) creation via PowerShell You can now create CMG Server app via PowerShell cmdlet, you need to specify TenantID in the argument: PowerShell Commandlet: Set-UpdateServerApplication – 'TenantID' If you try to create the CMG before updating RedirectUrl, you get an error "Your server Application needs to be updated". PowerShell command: Set-UpdateServerApplication to update your App, and then try again to create CMG. Note For new customers, before creating CMG, create Azure AD web server app and execute the new PowerShell commandlet script. Deprecated features Configured resource access policies will block Configuration Manager 2403 upgrade, remove existing policies and move the slider to Intune. Please action before January 2024, read the FAQ. For more information, see Removed and deprecated features for Configuration Manager. For more details and to view the full list of new features in this update, check out our What’s new in version 2309 of Microsoft Configuration Manager documentation. Other updates Patching guidance for MCM customers migrating to Azure Migrating to Azure? Managing your on-prem infrastructure through Microsoft Configuration Manager (MCM) ? Have you figured out how you would patch your infrastructure on Azure? This article provides steps that you can follow to patch your migrated virtual machines on Azure. Note: MCM manages both devices and servers. This blog provides guidance for servers migrating to Azure. For devices, please refer to Microsoft Intune. Azure Migration tool has been helping you to programmatically create Azure virtual machines (VMs) for Configuration Manager and install the different site roles with default settings. Validation of the new roles, followed by removal of the on-premises site system role enables MCM in Azure, provides you all the on-premises capabilities and experiences in Azure. Additionally, you can leverage native Azure Update Manager to manage and govern update compliance for Windows and Linux machines across your deployments in Azure, on-premises, and on the other cloud platforms from a single dashboard, with no operational cost for managing the patching infrastructure. Azure Update Manager shares similarities with the update management component of MCM, designed as a standalone Azure service to provide SaaS experience on Azure to manage hybrid environments. Both MCM in Azure and Azure Update Manager can fulfil your patching requirements and the ultimate choice depends on your specific needs and preferences. MCM in Azure would allow you to continue using existing investments in Microsoft Configuration Manager and familiar processes for maintaining the patch update management cycle for Windows virtual machines. On the other hand, through Azure Update Manager, you can achieve consistent management of VMs and operating system updates across your cloud and hybrid environment. Moreover, you would not need to maintain Azure virtual machines for hosting the different Configuration Manager roles and would not need a MCM license, hence reducing the total cost for maintaining the patch update management cycle for all machines in your environment. For more details, please refer the actual CM on Azure FAQ For assistance with the upgrade process, please post your questions in the Site and Client Deployment forum. Send us your Configuration Manager feedback through Feedback in the Configuration Manager console. Continue to share and vote on ideas about new features in Configuration Manager. Thank you, The Configuration Manager team Additional resources: What’s New in Configuration Manager Documentation for Configuration Manager Microsoft Configuration Manager announcement Microsoft Configuration Manager vision statement Evaluate Configuration Manager in a lab Upgrade to Configuration Manager Configuration Manager Forums Configuration Manager Support Report an issue Provide suggestions
Use Intune RBAC for tenant attach with Configuration Manager Technical Preview 2106
Update 2106 for the Technical Preview Branch of Microsoft Endpoint Configuration Manager has been released. You can now use Intune role-based access control (RBAC) when displaying the Client details page for tenant attached devices in the Microsoft Endpoint Manager admin center.
