In. exe /download configuration. msc). Select Create. Select Windows > Windows enrollment > Enrollment Status Page. Configuration Manager doesn't validate this URL. Please navigate to Admin-> Configurator Enrollment-> Choose the Default User->Save the Default user. Go to Devices > macOS > macOS enrollment. pkg on devices. I checked the client PC has over 100+GB free space so space could not be the case? Failed to check enrollment url, 0x00000001: execmgr 28/04/2022 14:43:20 18632 (0x48C8) Failed to check enrollment url, 0x00000001: execmgr 28/04/2022 14:43:20 4908 (0x132C) Policy arrived for parent package SIT0001A program ANSYS_STUDENTDISCOVERY_2022R1_WINX64. Computer Configuration > Administrative Templates > Windows Components > MDM > Enable Automatic MDM Enrollment Using Default Azure AD Credentials. Create a DNS CNAME alias. No, not yet solved. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. 3. log clearly states why it's not enabled: Workload settings is different with CCM registry. exe on the machine, bitlocker encryption starts immediately. Server assigned ClientID is GUID: Approval status 1. The caveat to all of this is tracking down devices, as we have some that have been offline for over a year and a half. MDM enrollment hasn't been configured yet on AAD, or the enrollment url isn't expected. In SCCM under devices look for the column AAD Device ID and see if its blank, if it is, then check AAD for that device name and see if its synced from your on prem AD. Force encryption without user interaction. it seems that all co-management policies are duplicated in the SCCM database. yourdomain. Click on the Accounts option from the setting page. MCSE: Data Management and Analytics. Hotfix replacement information. All installed the April monthly updates as normal through SCCM\Software Center, when it comes to the 20H2 they show show as Compliant while on 2004. NET client libraries, we get a nice. Select the Network tab, and. Select your Azure environment from the following list: Azure Public Cloud. Select the Network tab, and. How to Fix SCCM ConfigMgr Software. Let’s see how to Install band Update Package ConfigMgr 2006 Hotfix to fix the co-management issue. The macOS agent can be pushed down as an application to Mac devices that have gone through profile enrollment. Go to Administration Updates and Servicing. . log that in Location update from CTM, there are 3 matching DPs. To add Microsoft Intune subscription in configuration manager, follow these steps. SCCM 2107 - Windows 21H2 and Failed to check enrollment url, 0x00000001: We are testing to deploy Windows 10 21H2 and getting the following error in WUAHandler: Successfully completed scan. Check IIS authentication settings: Open the Internet Information Services (IIS) Manager on the Windows Server 2012 R2 machine. You can find the third-party software update catalogs in Configuration Manager with following steps: Launch the SCCM Console. 1048. I don't get that message for all Baseline/CIs. In SCCM under devices look for the column AAD Device ID and see if its blank, if it is, then check AAD for that device name and see if its synced from your on prem AD. I've started lately a POC for SCCM&Intune co-management and noticed a wired issue with the enrollment process - while some devices enrolled without issues, others just don't. I enable co-management with Intune with global admin, and auto enrolled computers successfully, , after that I changed the global admin password, the auto enrolled cannot work again. In this process we need prerequisites to check both IIS and BITS roles in SCCM's server Server manager. Let’s check the hotfixes released for the Configuration Manager 2111 production version. 168. Attempt enrollment again. Navigate to \ Administration \Overview\ Site Configuration\Sites. All workloads are managed by SCCM. CoManagementHandler 15. Select Cloud Services. The. 130. Select Next. In this case, event ID 75 and event ID 76 aren't logged. This is why we are trying to enroll the computers with a Device Credential. All workloads are managed by SCCM. log which should state that all the workloads are management via SCCM and that the device is not MDM enrolled. Configure SCCM Software update point in SSL. SCCM 2010. Select Cloud Services. If I manually run the MBAMClientUI. How to Fix SCCM ConfigMgr Software Distribution Notification Issues. The security message shown to these end users will include a Learn more link that redirects to your specified URL. System Center Configuration Manager is either installed, or traces of a previous install are. In both cases, the feature will basically create a scheduled task to enroll the PC at next logon. Threads 5,882 Messages 22,906 Members 13,075 Latest memberHello. If I let a machine get the policy for the gateway via the company intranet and then disconnect the client will work fine and accept deployments from the SCCM site. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0)<BR />Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0)<BR />Device is not MDM enrolled yet. Check the following in the registry: HKEY_LOCAL_MACHINESOFTWAREMicrosoftDusmSvcProfiles If any of the adapters are set to metered they will appear under the profiles key and have a property named "UserCost" with a non-0 value. Choose Prepare with: Automatic Enrollment. Challenge with On-Prem Active Directory registered devices not enrolled in Intune, but those devices showing in Intune dashboard managed by Config Mgr (SCCM) instead of Co-managed. Users see the message "Looks like your IT admin hasn't set an MDM authority. But for some of the machines showing Non-Compliant for "Compliance 1 -Overall Compliance" report. SCCM 2012 with CU3 applied - its an all in one server with all roles except for: Asset Intelligence, Endpoint Protection, both Enrollment points, Fallback status*, OOB Service, State migration and System Health Validator *Although, it probably should be the Fallback status point, but one thing at a time! AD Schema was extended & verified. SCCM Software Updates not installing to endpoints. Could not check enrollment url, 0x00000001: (this looks like an intune reference we do not use). Finally had a meeting with an escalation engineer that found the issue. I already did; MDM scope to all in AAD ; MDM scope to all in. Follow the steps to complete the hotfix installation on the secondary server: Launch SCCM console. Another easy way to find TPM status on a computer is by using SCCM Task Sequence. I can see the device in the Intune Portal. Step 3 - Install the Configuration Manager Policy Module (for SCEP certificates only). Click Sign In to enter your Intune credentials. All workloads are managed by SCCM. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Value of CoManagementFlags retrieved: 0x2001 CoManagementHandler 12/09/2022 13:59:57. Check in Control Panel on the client. List of SCCM 2111 Hotfixes. You can create custom collections in Configuration Manager, which help determine the status of your co-management deployment. Michael has written an excellent post on Autopilot troubleshooting. I think the issue is we use Crowdstrike, but in our SCCM Client settings, we have a Endpoint Protection policy that is set to "Yes" for "Manage Endpoint Protection Client on Client computers". The Configuration Manager console now allows wildcards when defining Microsoft Defender Attack Surface Reduction (ASR) rules. How to Fix SCCM ConfigMgr Software Distribution Notification Issues. B. Right after the end of the application install section of my Task Sequence, I get the below pictured message. 2022 14:14:24 8804 (0x2264) Could not check enrollment url, 0x00000001: CoManagementHandler 15. Right after the end of the application install section of my Task Sequence, I get the below pictured message. The graphs can help identify devices that might need attention. According to the log, all client displayed “Could not check enrollment url, 0x00000001”. Step 3. Under Properties, click on Enablement tab, here you can see Automatic enrollment in Intune is having 3 options : All: Using this setting will enroll all devices in SCCM to enroll in Intune. Go to Start and click Start Menu -> Settings. To fix this issue in a stand-alone Intune environment, follow these steps: In the Microsoft Intune admin center, chooses Devices > Enrollment restrictions, and then choose a device type restriction. 90. 1. Failed to check enrollment url 0x00000001. Delete stale registry keys. In the Create Antimalware Policy dialog. It should be noted that in the past with the help of the members of this forum, I was able to establish a secure connection between the. Attempt enrollment again. Before installing, check if your site is ready for the update: Open the SCCM console. UpdatesDeploymentAgent 17/05/2022 14:19:33 7956 (0x1F14) CEvalO365ManagementTask::Execute() UpdatesDeploymentAgent 17/05/2022 14:28:08 7956 (0x1F14) Failed to check enrollment url, 0x00000001: UpdatesDeploymentAgent 17/05/2022 14:28:08 7956 (0x1F14) Intune Enrollment using Group Policy | Automatic Enrollment AVD VMs See this article. • Delete the enrollment ID folder. Devices are member of the pilot collection. device now Hybrid joined again and registration date is todays date and time / MDM set to none. CNAME. ”. This message is shown on Apple Configurator when the MDM server is not reachable or the correct host. Reseat the memory chips. Once this is done, try enrolling the devices again. When I add computers to comgnt Collection, the device appears in Intune console, but locally nothing happends and sccm client see that comgnt isn't yet enabled. If the Configuration Manager client is already installed, skip to Step 2. For more information, see Install in-console updates for System Center Configuration Manager. Windows 10 1909 . After some retries the device is synced to AAD, and it then writes this, but then nothing happens after that. Failed to check enrollment url, 0x00000001: UpdatesDeploymentAgent 2021-10-26 16:02:50 4264 (0x10A8) Device is not MDM enrolled yet. 4. On-premises BitLocker management using System Center Configuration Manager Microsoft BitLocker Administration and Monitoring (MBAM) And recently they've posted an updated blog post here where they go into detail about how BitLocker Management in Microsoft Endpoint Manager has evolved (both in Intune and ConfigMgr). In this blog post, i will discuss about 2 options 1) configuration baseline and 2) Scripts. 6. I agree with RahuJindal, but this issue was fixed in windows 10 1803. - All the devices are domain joined and synced to AAD (Hybrid Azure AD joined) - All users are licensed - Auto-enrollment settings verified (followed this article) When we are imaging brand new machines, we have trouble getting them co-managed without reinstalling the SCCM client. log to make sure the client push was successful. Launch the ConfigMgr console. All installed the April monthly updates as normal through SCCMSoftware Center, when it comes to the 20H2 they show show as Compliant while on 2004. WUAHandler 5/15/2023 7:35:54 PM 5576 (0x15C8) Failed to check enrollment url, 0x00000001: WUAHandler 5/15/2023 7:35:54 PM 5572 (0x15C4) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. 4) Performed in-depth analysis on IIS 7. log returned with below info. Write down the enrollment ID somewhere, you will need it for the cleanup. Use the following steps to cloud attach your environment with the default settings: From the Configuration Manager console, go to Administration > Cloud services > Cloud Attach. Devices are member of the pilot collection. I've also worked through the spiceworks post to no avail. Let me add a little information from the official article. All the software is installed, all the settings are there, bitlocker is. 1. On the Site Bindings window, click on Close. If you do not see a Trusted Platform Module device, this might be true for one of the following reasons:The site system roles for on-premises MDM and macOS clients: enrollment proxy point and enrollment point As previously announced, version 2203 drops support for the following features: The ability to deploy a cloud management gateway (CMG) as a cloud service (classic) . To fix the issue, use one of the following methods: Set MFA to Enabled but not Enforced. Select Create. All workloads are managed by SCCM. pem file. com, but also use name@us. You can change this setting later. Click Add Site System Role in the Ribbon. Check comanagementhandler. log on. Windows Update for Business is not enabled through ConfigMgr WUAHandler 12/14/2021 11:45:57 AM 88736 (0x15AA0) Let’s see how to install SCCM 2111 Hotfix KB12896009 Update Rollup on the secondary server. Solution: To fix this issue in a stand-alone Intune environment, follow these steps: In the Microsoft Intune admin center, chooses Devices > Enrollment restrictions > choose a device type restriction. There are multiple methods that you can use to check the TPM status on a computer. In this case, the device gets the policy or profile on its next scheduled check-in with the Intune service. msc), and check for a Trusted Platform Module under Security Devices. Check “Certificate Enrollment Web Service”. When this option is set, delta download is used for all Windows update installation files, not just express installation files. siteserver -ignorecertchainvalidation -u ‘DOMAINUsername’” where DOMAINUsername is an. SCCM 2111 Hotfix KB12959506 to fix a. . [Optional] Upload a wireless profile, so the iOS device (s). Step 3: Verify whether Directory user enrollment has been enabled. Update July 21 by Scott Williams – References tab on an SCCM 2203 Task Sequence. In Basics, enter the following properties: Name: Name your profile so you can easily identify it later. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. Trying to push a simple powershell script to the device from Intune but do not see any actions on the client side. Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:The most common enrollment options for Windows 10 devices is to use auto-enrollment. We already have pre-existing hybrid domain join. For example if users at Contoso use [email protected] you enable MDM automatic enrollment, enrollment in Intune will occur when: A Microsoft Entra user adds their work or school account to their personal device. Check Disk Space: Verify that the SCCM client has sufficient disk space to install updates. To give our Hybrid Azure AD joined device a trial by fire, we will edit its local group policies to automatically enroll into Intune. That can be seen in the ConfigMgr settings. By default this interval is 60 minutes. Step-by-step example deployment of the PKI certificates for System Center Configuration Manager:. To do this let’s use @_Mayyhem awesome SharpSCCM tool via: SharpSCCM. For more information, see Assign Intune licenses to your user accounts. Check for any firewall or network configuration issues that may be affecting the connection. Wait 2-3 minutes or so and check OMA-DM log again. Make sure the Directory is selected for Authentication Modes. On the CA Server launch the Certification Authority management tool and look at the properties of the CA Server itself, on the security tab make sure yours looks like this, (Domain computer and domain controllers should have the ‘request certificates‘ rights). Enter remote Management Point (MP) server FQDN and click next. Right-click Configuration Manager 2211 update and click Run Prerequisite Check. In Co-management settings we have it set to upload all Devices. danno New Member. I have collected the know issues from the community and the hotfixes released for the 2203 version of ConfigMgr. When you are using SCCM co. txt. Azure AD “Mobility (MDM and MAM)” groups are not required (if using SCCM) Azure Active Directory has a section called “Mobility (MDM and MAM)” and this is where you can control which groups are allowed for Intune MDM or MAM enrollment. Could not check enrollment url, 0x00000001: WUAHandler 6/6/2023 9:26:00 PM 3832 (0x0EF8) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business. Make a note of the enrollment ID somewhere, you will need the ID later in the process. msc), and check whether the computer has a TPM device. a. You can encounter loads of different issues, and I can’t list them all here, but these are the most common. Navigate to Software Library > Overview > Software Updates. Failed to check enrollment url, 0x00000001: The OneTrace log file viewer (CMPowerLogViewer. Bitlocker Management Control Policy. 3. Microsoft switched the name to System Center Configuration Manager in 2007. Click Save. If you check the CoManagementHandler. Choose Properties > Edit (next to Platform settings) > Allow for Windows (MDM). Temporarily disable MFA during enrollment in Trusted IPs. msc. Failed to check enrollment url, 0x00000001: WUAHandler 1/21/2022 9:21:10 AM 2488 (0x09B8) SourceManager::GetIsWUfBEnabled - There is no Windows Update for. Computer Configuration –> Policies –> Administrative Templates –> Windows Components –> MDM –> Enable automatic MDM enrollment using default Azure AD credentials. This event indicates a failed auto-enrollment. msc does not show a device, open Device Manager (devmgmt. Give it a name such as Auto-enrollment Intune and edit the Group Policy. This leads me to look at the software update logs on the client to see what is going wrong. In the IIS Website and Virtual application name fields, leave both to the default values. The renewal process starts at the halfway point of the certificate lifespan. Go to Administration \ Overview \ Updates and Servicing node. log of the client: AADJoinStatusTask: Client hasn't been registered yet. A. This can help streamline the enrollment process of macOS devices, ensuring that both profile and agent are installed without needing to manually run the . The following steps will help you to complete Windows 10 Intune Enrollment. This is the default configuration when co-management is set up. You can watch the process in the “C:\Windows\CCM\CoManagementHandler. Link the Group Policy to the OUs with the computers who should auto-enroll into Intune. Howerver, we have some that have not completed the enroll. This issue occurs when integrated Windows authentication is tried by the Configuration Manager client against Microsoft Entra ID while the verified domain isn't federated. For version 2103 and earlier, expand Cloud Services and. Configure MDM. To enable co-management, follow these instructions: In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select the Cloud Attach node. log file I see it tries alot of times, but can't because the device is not in AAD yet. Below images are for your. You can create custom collections in Configuration Manager, which help determine the status of your co-management deployment. This means that the device has no ADE settings assigned to them. g. Checking for device in SCCM. If you go to the PC's sccm client does it show the enrollment item within the configuration tab? Reply Client is registered. In the Configuration Manager console, go to Administration > Site Configuration > Servers and Site System Roles, then click the < SiteSystemName > right-hand pane. Let’s check the ConfigMgr 2203 known issues from the below list. Read More-> SCCM Deprecated Features | Removed Features. I would not make changes in the configmgr database without guidance from MS. Cheers! Grace Baker Hexnode MDm• Go to Task Scheduler Library > Microsoft > Windows > EnterpriseMgmt. log”. I know that there is a section in the SCCM monitoring workspace for this but my main question is whether there is a reg key or WMI item that I can pull using PowerShell to confirm if a computer is co-managed. MachineId: A unique device ID for the Configuration Manager client . I checked the WUAHandler log against one for a PC that has actually been installing updates, and the only line that's different is this: This line. If the certificate shows as expired, you may have to renew it and import into Intune portal. 2. In the CoManagementHandler. Check Connectivity: Ensure that the SCCM client has a stable network connection to the SCCM server. req” and “-encr. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. Go to the General tab, specify or verify the WSUS configuration port numbers. Cause 2: Missing "NT AuthorityAuthenticated Users" in the "Users" group of the certificate server or any other default permissions. Let ask you this , is this your personal lab or company? Because if personal usually you have to designate fallback space point “fsp” and depends when you install this roles on which site for example in you case ccmsetup. In Workspace ONE UEM, enter the Azure AD Primary domain and save the settings. please check the following information: Check if there's any GPO which configured for MDM enrollment assigned to this device. I already did; MDM scope to all in AAD ; MDM scope to all in. exe SCCM01 P01 invoke client-push -t 192 . Uncheck “Certification Authority”. In the CoManagementHandler. . Check out our troubleshooting doc on common errors while enrolling iOS devices using Apple Configurator. On the Default Settings page, set Automatically register new Windows 10 domain joined devices with Azure Active Directory to = Yes. If it isn’t set to 10, then set it to 10 using ADSIedit. If I manually run the MBAMClientUI. 2022 14:14:24 8804 (0x2264) Could not check enrollment url, 0x00000001: CoManagementHandler 15. Natiguate to the bottom of the Dashboard, in the Cloud Management Gateway Statistics section. If a device doesn't check in to get the policy or profile after the first notification, Intune makes three more attempts. Joining internet clients to CMG Bulk Registration not working with Enhanced HTTP. Click on Security tab, select the Domain Computers group and add the permission of Read and Autoenroll , do not clear Enroll. - All the devices are domain joined and synced to AAD (Hybrid Azure AD joined) - All users are licensed - Auto-enrollment settings verified (followed this article)When we are imaging brand new machines, we have trouble getting them co-managed without reinstalling the SCCM client. If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site. log Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not MDM enrolled yet. My test PC is in a workgroup and has never. Sometimes software will stop distributing. On any machine where enrollment fails, follow these steps logged in as Administrator: Open Microsoft Management Console and go to Local Computer (run → mmc → Add/Remove snap-ins → Certificates → Computer Account → Local Computer). Select Next. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. it seems that all co-management policies are duplicated in the SCCM database. Navigate to Administration > Overview > Updates and Servicing Node. Click Next . 4. All workloads are managed by SCCM. Info button on settings / user accounts has now disappeared. Mar 3, 2021, 2:40 PM. I installed SCCM/MECM with version 2203. All workloads are managed by SCCM. This purpose of this mini. Enroll the Device Trust certificate on domain-joined Windows. The update is available if you have opted in through a PowerShell script to the early update ring deployment of #MEMCM 2107. Finally had a meeting with an escalation engineer that found the issue. No traces of recent changes and issues. Unfortunately, Google was unhelpful. Microsoft Virtual Academy. Although the computers were installed using the SCCM operating system distribution, there is no active CLIENT. 9058. log shows. In the Configuration Manager console, go to the Administration workspace, and select the Client Settings node. We have discovered multiple computers in our environment that show in the Success column when we check the Windows Updates deployments' compliance, but they've been skipping updates for months. Although both commands are supported, only one command can be used at a time in a trustpoint. Could not check enrollment url, 0x00000001: BitlockerManagementHandler 19/12/2022 11:23:11 4260 (0x10A4) Starting timer task. In the Home tab, in the Create group, click Import. Select Apple Push MDM Certificate to check the status of certificate. Even though it states and Internet FQDN, you'll have to configure that for the Site System role. Prajwal Desai He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information. All workloads are managed by SCCM. This setting is optional, but recommended. Usually a reboot will speed up the join process on the device, but only. When you are trying to onboard your device with Autopilot and somehow the Intune enrollment is not succeeding: “Mismatch between ZTD Profile and enrollment request intent” 0x8018005. Event 13: Certificate enrollment for Local system failed to enroll for a DomainControllerCert certificate with request ID 757 from srv1. Identify the issue. . Then on a. Click Review + Save. If th e Info tab is missing from the connection box, this device is not enrolled in Intune yet. You could simply just trick it to believe that it's on the internet by adding e. Cheers! Grace Baker Hexnode MDmHere’s how to do that: Press Win + R on your keyboard and enter services. If you have testing equipment for the hardware, use them to detect any hardware malfunctions By Prajwal Desai September 26, 2021. Challenge with On-Prem Active Directory registered devices not enrolled in Intune, but those devices showing in Intune dashboard managed by Config Mgr (SCCM) instead of Co-managed. In this article. You don't have to restart the computer after you apply this hotfix. We use co managed in sccm not via gpo. Set this configuration at the primary site and at any child secondary sites. The cause is that the first time we tried to activate the cloud attach, the operation did not complete. Check the power supply. : ️ On Windows 11 and Windows 10 1803+, CA is available for. 2. 1018Configure SCCM Software update point in SSL. log which should state that all the workloads are management via SCCM and that the device is not MDM enrolled. Launch Configuration Manager console. WUAHandler 5/15/2023 7:35:54 PM 5576 (0x15C8) Failed to check enrollment url, 0x00000001: WUAHandler 5/15/2023 7:35:54 PM 5572 (0x15C4) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. However, I suspected it could be MP issue but we verified that MP control. Our intent is to rely on MECM to start the onboarding process. Under Device Settings, specify the Polling interval for modern devices (minutes). exe) may terminate unexpectedly when opening a log file. Here’s how to enable SCCM co-management. Failed to check enrollment url, 0x00000001: WUAHandler 12/14/2021 11:45:57 AM 26552 (0x67B8). If tpm. 2022 14:14:24 8804 (0x2264) Loaded EnrollPending=1, UseRandomization=1, LogonRetriesCount=0, ScheduledTime=1632425152, ErrorCode=0x0, ExpectedWorkloadFlags=1, LastState=101, EnrollmentRequestType=0 CoManagementHandler 15. Below images are for your. Hello and thankyou for the response, So far i have followed the instructions How to Install Clients on Mobile Devices and Enroll Them by Using Configuration Manager in conjunction with Step-by-Step Example Deployment of the PKI Certificates for Configuration Manager: Windows Server 2008 Certification Authority. Configuration Manager . Configure Automatic enrollment in Intune. Failed to check enrollment url, 0x00000001: ; The OneTrace log file viewer (CMPowerLogViewer. Set it to 0, restart the DusmSvc service (Data Usage) and. Now we will enable co-management in the Configuration Manager console. 3. If the status of the certificate shows as Active, it’s all good. When the Configuration Manager console is installed on a computer with an x86 processor, it doesn't detect the installation state of console extensions. We are only using co-management licensing through CM. Click Save. Challenge with On-Prem Active Directory registered devices not enrolled in Intune, but those devices showing in Intune dashboard managed by Config Mgr (SCCM) instead of Co-managed. • Delete all the existing tasks the enrollment folder. All workloads are managed by SCCM. In every case where SCCM stops working properly is after I did an update. Re-load the. Unable to verify the server’s enrollment URL. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. If it is, then remote into said device and run "dsregcmd /status" and see what kind of errors you get. All SCCM clients are reporting to specific site system are inactive in console. Failed to check enrollment url, 0x00000001: The OneTrace log file viewer ( CMPowerLogViewer.