However, I suspected it could be MP issue but we verified that MP control. SCCM focuses on the management of Windows devices -- both client and server systems -- in enterprise environments, which some define as sites with more than 300 devices. The Website is automatically created during the management point setup or the initial SCCM setup. After initial testing, add more users to the pilot group. 06. The renewal process starts at the halfway point of the certificate lifespan. Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not MDM enrolled yet. EnrollmentRequestType=0 CoManagementHandler 15. 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. Configuration Manager uses the following Microsoft URL forwarding services throughout the product: Active Hubs. Select Next. In Settings, configure the following settings:For usage keys, a signature key and an encryption key, two requests are generated and sent. We would like to show you a description here but the site won’t allow us. 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. Link the Group Policy to the OUs with the computers who should auto-enroll into Intune. Applies to: Configuration Manager (current branch) Update 2111 for Configuration Manager current branch is available as an in-console update. MachineId: A unique device ID for the Configuration Manager client . After doing that SCCM will start to function properly. 2. Step 3 - Install the Configuration Manager Policy Module (for SCEP certificates only). All workloads are managed by SCCM. 1. Locationservices. I've got an operational Cloud Management Gateway setup with Enhanced HTTP using a wildcard certificate. The Configuration Manager Support Center Client Tools application terminates unexpectedly on a Windows 11 computer selecting different deployments. 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:. dat" does not exist. msc. Manually entering the SCCM client site code and clicking Find Site showed Configuration Manager did not find a site to manage. We would like to show you a description here but the site won’t allow us. Click Review + Save. On the Site Bindings window, click on Close. All workloads are managed by SCCM. Before you enable the option to use custom websites at a site: Create a custom website named SMSWEB in IIS on each site system server that requires IIS. A device that is successfully enrolled will be represented by a Microsoft Entra device resource with an update management enrollment for feature updates and have no Microsoft Entra device. Most Active HubsTo get it working I first use Microsoft normal click to run download tool setup. externalEP. I have check the IIS and i can see correct cert is binding to default site, I have reboot the iis. exe) may terminate unexpectedly when opening a log file. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Value of CoManagementFlags retrieved: 0x2001 CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not MDM enrolled yet. SCCM includes the following administrative capabilities: operating system. Another easy way to find TPM status on a computer is by using SCCM Task Sequence. As I am known, co-management and GPO enrollment are different enrollment methods. 1. The Invoke-MbamClientDeployment. For configuration baseline, we will use simple PowerShell script to detect the status of the schedule task and the same script can also be used in scripts feature. Some of the things that can be looked into are Intune licensing for the enrolling users on the devices in question, device platform restriction policies in Intune, MFA, Conditional access. If it is, then remote into said device and run "dsregcmd /status" and see what kind of errors you get. I have build a new SCCM environment XYZ. If Identity is MSA, then using Settings App -> Access Work or School -> Connect button. Microsoft Configuration Manager. Connect to “rootccmpolicymachine. Configuration Manager should be enrolling the devices into Intune since users do not have Intune licenses. Please examine the MDM logs on the device in the following location in Event Viewer: Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider > Admin. For more information, see Install in-console updates for System Center Configuration Manager. Now we will enable co-management in the. download your public key cert to download the Meraki_Apple_DEP_cert. . exe with the AutoEnrollMDM parameter, which will. crypto pki import name certificate. Navigate to Groups & Settings > All Settings > Devices & Users > General > Enrollment. 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. 2. 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. Failed to check enrollment url, 0x00000001: WUAHandler 12/14/2021 11:45:57 AM 88736 (0x15AA0) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Failed to check enrollment url, 0x00000001: WUAHandler 1/21/2022 9:21:10 AM 2488 (0x09B8) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. In this article. Check the Configmgr client app on the device which should show Co-management as Disabled and Co-management capabilities as 1. Select Cloud Services. Tenant Attach – Connect your SCCM site to Microsoft Intune for instant cloud console and troubleshooting power. Computer Configuration > Administrative Templates > Windows Components > MDM > Enable Automatic MDM Enrollment Using Default Azure AD Credentials. log Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not MDM enrolled yet. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. On the Site System Role tab, select Enrollment Point and Enrollment Proxy Point, click Next. In this process we need prerequisites to check both IIS and BITS roles in SCCM's server Server manager. Click secondary server and click on Recover Secondary Site from the ribbon menu. If I manually close it or wait it out, the system reboots and it appears my task sequence was successful. log shows. 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. In this blog post, i will discuss about 2 options 1) configuration baseline and 2) Scripts. Hello, We are trying to enroll devices in intune using MECMDevices are Hybrid azure AD joined. SCCM 2111 Hotfix KB12959506 to fix a. In the Configuration Manager console, click About Configuration Manager. Step 3: Registry Key Deletion Use the previous enrollment ID to search the registry:Oh I could've been clearer there, I mean step five of the section Mac Client Installation and Enrollment. 3. com. Read More-> SCCM Deprecated Features | Removed Features. Click on the Accounts option from the setting page. Feature Use this enrollment option when; You use Windows client. When this option is set, delta download is used for all Windows update installation files, not just express installation files. Step 3: Verify whether Directory user enrollment has been enabled. I have some suspicious lines in UpdatesDeployment. Set this configuration at the primary site and at any child secondary sites. Configuration Manager . To do this let’s use @_Mayyhem awesome SharpSCCM tool via: SharpSCCM. Select Create. -Under Software Center it is showing "Past due - will be installed". pkg on devices. In BitlockerManagementHandler. “Click the References tab on a Task Sequence, view content status on a package entry, then hit the back arrow to go back to. Run the Registry Editor as Administrator. I already did; MDM scope to all in AAD ; MDM scope to all in. Over 90% of our sccm clients are failing client check however, Client activity looks great. In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select the Cloud Attach node. 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. Initializing co-management agent. On the General tab, click Next. 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. CNAME. Please see the Microsoft article WSUS server location to understand how clients receive the WSUS server to scan against. We are only using co-management licensing through CM. Get help from your IT admin or try again later. In BitlockerManagementHandler. 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. To fix the issue, use one of the following methods: Set MFA to Enabled but not Enforced. If I manually run the MBAMClientUI. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. Microsoft Virtual Academy. msc), and check whether the computer has a TPM device. Dec 14, 2021 · Failed to check enrollment url, 0x00000001: WUAHandler 12/14/2021 11:45:57 AM 26552 (0x67B8) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. I have created sample windows 10 update. yourdomain. Let’s see how to Install band Update Package ConfigMgr 2006 Hotfix to fix the co-management issue. I imported the System Center ConfigMgr Baselines & those are evaluating fine on this 08 box. Uncheck “Certification Authority”. Select Review and then Save. Click Add Site System Role in the Ribbon. I have doubled check both CDP and AIA locations and verified that there is no typo. 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). Let’s check the hotfixes released for the Configuration Manager 2111 production version. The Configuration Manager console now allows wildcards when defining Microsoft Defender Attack Surface Reduction (ASR) rules. I’ve seen this issue normally when this is set to “Device Credential”. Failed to check enrollment url, 0x00000001: UpdatesDeploymentAgent 2021-10-26 16:02:50 4264 (0x10A8) Device is not MDM enrolled yet. We already have P1 licensing. The following are the troubleshooting tips to the errors that occur during the final leg of. On the Enrollment Point tab. 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. This is the default configuration when co-management is set up. 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. pem file. In the CoManagementHandler. Our intent is to rely on MECM to start the onboarding process. Step 4: Verify if the user is active in Workspace ONE. Current value is 1, expected value is 81 Current workload settings is not. . Sometimes software will stop distributing. Then select Allow for Windows (MDM). Win 10 Request CCM token to ConfigMgr via CMG. If the problem above exists, you see a red X in the "Certificate Name Matches" and the “SSL Certificate is correctly Installed” sections of the report. You do not have to restart the computer after you apply this hotfix. Most Active Hubs. 3. Microsoft Excel. Devices are member of the pilot collection. but I have one device Windows 10 22H2 keeps failing in joining the Intune. Microsoft TeamsWe have Win10 1809 LTSB machines that are discovering valid URLs for software updates on the SCCM Distribution Point: But trying to download them from an invalid WSUS URL over port 8530 instead of calling the DP URL: All other machines in the domain are successfully downloading updates from the DP. domain. Make sure the Directory is selected for Authentication Modes. 3. Login to domain controller and launch Group Policy Object (gpmc. constoso. In the Open dialog box, browse to the policy file to import, and then click Open. Go to the event log on the failing device. Select the OU where you want to apply GPO, right click and select Create a GPO in this domain and Link it here. 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. Go to Devices > macOS > macOS enrollment. To find out what happens in Intune go to Endpoint -> Devices -> Monitor -> Autopilot deployments (preview) 2. 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. Enroll the Device Trust certificate on domain-joined Windows. log file I see it tries alot of times, but can't because the device is not in AAD yet. This can help streamline the enrollment process of macOS devices, ensuring that both profile and agent are installed without needing to manually run the . Manually entering the SCCM client site code and clicking Find Site showed Configuration Manager did not find a site to. Failed to check enrollment url, 0x00000001: ; The OneTrace log file viewer (CMPowerLogViewer. Empty: The default state when devices are first synced from ADE into Systems Manager. 06. In this blog post, i will discuss about 2 options 1) configuration baseline and 2) Scripts. 1048. I've ran procmon to see if my antivirus is blocking the download but I don't see it accessing the "E:Program FilesMicrosoft Configuration ManagerAdminUIContentPayload" folder (location where the dmpdownloader. Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not MDM enrolled yet. The Auto Enrollment Process. Feature updates only: Check that the device is successfully enrolled in feature update management by the deployment service. After you run the prerequisite check, it takes a while to actually begin the checks. In this article. Step 1 - Install and Configure the Network Device Enrollment Service and Dependencies (for SCEP certificates only) Step 2 - Install and configure the certificate registration point. Failed to check enrollment url, 0x00000001: UpdatesDeploymentAgent 17/05/2022 14:28:08 7956 (0x1F14) Attachments. Uninstalling and re-installing. When you concurrently manage Windows 10 or later devices with both Configuration Manager and Microsoft Intune, this functionality is called co-management. Configure SCCM Software update point in SSL. If you've just synced your devices from the ADE server into Systems Manager, they will be labeled 'Empty'. dsregcmd /status between a fine working machine and the strange one shows no difference, except on malfunction device: TpmProtected : YES. Check in Control Panel on the client. All SCCM clients are reporting to specific site system are inactive in console. Before installing, check if your site is ready for the update: Open the SCCM console. All workloads are managed by SCCM. We've checked and they are Hybrid AD, and the SCCM server is showing the SCCM agent doing policy requests. with WSUS XYZ server. touchgfx stm32f407; possessive pronouns ppt grade 3; socket io connecting but not emitting;I have explained the same in the following blog post. 2022 14:14:. Check Disk Space: Verify that the SCCM client has sufficient disk space to install updates. log file after receiving a task sequence policy. Failed to check enrollment url 0x00000001. On the Proxy tab, click Next. All workloads are managed by SCCM. Configure Automatic enrollment in Intune. When this is the case, the solution is really simple, you need to delete the Autopilot configuration file that was deployed to your device. Log in to the. Select the Network tab, and. 1700; Site Version – 5. Select a server to use as a site system – Install a New SCCM Management Point Role. 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. msc -> Applications and Services Logs -> Microsoft -> Windows -> DeviceManagement-Enterprise-Diagnostics-Provider -> Admin. On the Home tab of the ribbon, in the Settings group, select Report Options. Right-click Configuration Manager 2211 update and click Run Prerequisite Check. IT admin needs to set MDM authority. Windows Update for Business is not enabled through ConfigMgr WUAHandler 11/9/2 Failed to check enrollment url, 0x00000001: The OneTrace log file viewer ( CMPowerLogViewer. Could not check enrollment url, 0x00000001: CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Device is not enrolled. The SCCM client installs as expected and shows active in the console but I cannot see the device inside Intune. Wait 2-3 minutes or so and check OMA-DM log again. algebra 2 workbook answers pdf. You can confirm that this is the case by running dsregcmd /status and observing the content of the MDM URL in the output. a. How to Fix SCCM ConfigMgr Software Distribution Notification Issues. exe ) may terminate unexpectedly when opening a log file. In this post, we will update a stand-alone primary site server, consoles, and clients. . Microsoft. Hi, I am having the same problem. arduino a technical reference pdf. The following steps will help you to complete Windows 10 Intune Enrollment. Give the name. SCCM 2006 clients fail co-management enrollment. This issue occurs in one of the following situations: The Cloud Management Azure service isn't configured in Configuration Manager. On your device, go to Settings > tap your name > iCloud > swipe the Find My iPhone button to Off. Go to Administration / Cloud Services / Co-Management and select Configure Co-Management. Check for anything it finds but is still left over in Settings > Apps > Apps & Features, and C:Program Files and C:Program Files (86) to uninstall or delete them. When I check the CoManagementHandler log, I keep seeing "Co-management is disabled but expected to be enabled. Select the General tab, and verify the Assigned management point. That scheduled task will start deviceenroller. log which should state that all the workloads are management via SCCM and that the device is not MDM enrolled. WUAHandler 2022-02-16 11:15:23 1800 (0x0708) Its a WSUS Update Source type ( {ED4A5F71-85D0-4B2C-8871-A652C7DCDA71}), adding it. Failed to check enrollment url, 0x00000001: ConfigMgr CB 2107 (public release) - HTTPS (PKI) enabled - Site Version -. The errors I am seeing seem to indicate a certificate trust issue but there should be no need for certs for this to work. I have set up a CMG recently and I am having trouble trying to install the SCCM agent over the internet using token based authentication. 2. log file I see it tries alot of times, but can't because the device is not in AAD yet. Also multiple times in execmgr. Could we know if we check the option of "Clients check the certificate revocation list (CRL) for site systems"(like the image shown below)? If we select it, please check out it and then try to use /nocrlcheck command line. Could not check enrollment url, 0x00000001: This line appears before each scan is ran. Then click on Ok. Installation Guide ️ ConfigMgr Out of Band Hotfix. Trying to get co-management up and running with 2111. While I was trying to upgrade 1810 from Console, I never seen any prerequisites warnings except SQL. Package for 1810 got downloaded under C:Program FilesMicrosoft Configuration ManagerCMUStaging already and same is available under C:Program FilesMicrosoft Configuration ManagerEasySetupPayload. log which should state that all the workloads are management via SCCM and that the device is not MDM enrolled. I recently helped an IT guy fix an issue where the SCCM client agent could not discover the site code. Let’s check the ConfigMgr 2203 known issues from the below list. The following SCCM patching logs are always going to help and understand the Windows patching from the Windows 10, Windows 11, or Windows Server side. 0x800706ba (WIN32: 1722 RPC_S_SERVER_UNAVAILABLE)). In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. log to check whether scan is completed or not. exe /download configuration. What we had. In every case where SCCM stops working properly is after I did an update. 3. 06. Click Sign In to enter your Intune credentials. • Delete all the existing tasks the enrollment folder. SCCM 2010. 4. In this case, the device gets the policy or profile on its next scheduled check-in with the Intune service. Mar 3, 2021, 2:40 PM. Re-load the. Right-click Configuration Manager 2111 update and select Run Prerequisite check. Michael has written an excellent post on Autopilot troubleshooting. MS case is still open. ”. Most of our SCCM clients enabled co-management just fine. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Value of CoManagementFlags retrieved: 0x2001 CoManagementHandler 12/09/2022 13:59:57. This is the time to create the Group policy. I will update this list whenever Microsoft releases new hotfixes for 2111. Continue to the next section. I will try to update this list whenever Microsoft releases new hotfixes for 2107. As SharpSCCM calls into the actual . Furthermore, run the gpupdate command on the client computer and check if the computer policy and user policy updates successfully or not. Check the Configmgr client app on the device which should show Co-management as Disabled and Co-management capabilities as 1. 3. exe SCCM01 P01 invoke client-push -t 192 . exe SCCM01 P01 invoke client-push -t 192 . 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). If it is, then remote into said device and run "dsregcmd /status" and see what kind of errors you get. 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. For version 2103 and earlier, expand Cloud Services and select the Co-management node. For more information, see Set up multifactor authentication. Event 6: Automatic certificate enrollment for local system failed (0x800706ba) The RPC. In the State column, ensure that the update Configuration Manager. Could not check enrollment url, 0x00000001: BitlockerManagementHandler 19/12/2022 11:23:11 4260 (0x10A4) Starting timer task. msc does not show a device, open Device Manager (devmgmt. [LOG [Attempting to launch MBAM UI]LOG] [LOG [ [Failed] Could not get user token - Error: 800703f0]LOG] [LOG [Unable to launch MBAM UI. When this option is set, delta download is used for all Windows update installation files, not just express installation files. I already did; MDM scope to all in AAD ; MDM scope to all in. Got to Task Scheduler Library > Microsoft > Windows > EnterpriseMgmt. SCCM Software Updates not installing to endpoints. Make sure the Directory is selected for Authentication Modes. Select the General tab, and verify the Assigned management point. Choose Prepare with: Automatic Enrollment. All SCCM clients are reporting to specific site system are inactive in console. Thank you for response, I done following settings in sccm server and clients 1. So far no computers enrolled into Intunes. a. Fix Intune Enrollment. 0 or later. CcmIsDeviceMdmEnrolled returned error 0x1, MDM Sync not executed. EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 13. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) Value of CoManagementFlags retrieved: 0x2001 CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0) 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. ️ Configuration Manager supports Windows Server. SCCM 2006 clients fail co-management enrollment. No, Microsoft is not replicating the entire SCCM DB to Intune!! The tenant architecture is an on-demand connection when you click on an item in the. Launch the Configuration Manager console. old. A Configuration Manager maintenance windows restrict the. The following fields are available in the WMI class: . That can be seen in the ConfigMgr settings. When the Configuration Manager console is installed on a computer with an x86 processor, it doesn't detect the installation state of console extensions. And this service called "ccmsetup" doesn't find the client install packaage on the SCCM. ran AAD connect to provision device back into Azure AD. 2022 14:14:24 8804 (0x2264) Auto enrollment agent is initialized. This hotfix replaces the following previously released hotfix. Follow the steps to complete the hotfix installation on the secondary server: Launch SCCM console. Admins can pre-stage their own setupconfig. Select Configure Cloud Attach on the ribbon to open the Cloud Attach Configuration Wizard. If I manually close it or wait it out, the system reboots and it appears my task sequence was successful. The Post Installation task Installing SMS_EXECUTIVE service. This step-by-step example deployment, which uses a Windows Server 2008 certification authority (CA), has procedures that show you how to create and deploy the public key infrastructure (PKI) certificates that Configuration Manager uses. Troubleshooting Step 3: Can the Client Find the WSUS/SUP Server? Another common reason that can cause clients to show unknown is being unable to locate a WSUS server to scan against. System Center Configuration Manager is either installed, or traces of a previous install are. And the client receives the corrupted policies. I recently helped an IT guy fix an issue where the SCCM client agent could not discover the site code. Hi, iìm afraid to set this: Use Client Settings to configure Configuration Manager clients to automatically register with Azure AD. Check the power supply. You may also need to choose a default user too. danno New Member. This causes the client to fail, because the website simply does not exist. CoManagementHandler 12/09/2022 13:59:57 1712 (0x06B0). Forcing it recursively. In Traditional SCCM/MDT deployments, you need to press the “F8” key in the WinPE stage to get command prompt support. Is there any difference between these failed clients and successful clients?. exe on the machine, bitlocker encryption starts immediately. Click on Security tab, select the Domain Computers group and add the permission of Read and Autoenroll , do not clear Enroll. 4. First time using this method and a few machines were successful with the process. 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. In Workspace ONE UEM, enter the Azure AD Primary domain and save the settings. How to Fix SCCM ConfigMgr Software Distribution Notification Issues. Forcing it recursively. Proceed to Step 2. After the SCCM 2207 console upgrade is complete, launch the console and check “About Microsoft Endpoint Configuration Manager“. Click on “Query” and paste the following query in the “query” windows and click on “Apply. I check for the config manager, if it's there I operate as follows -. log”. localCA1 (The RPC server is unavailable. Create auto-enrollment group policy for devices. Enable SCCM 1902 Co-Management. In.