Install of new Config Manager (MECM) - Issues with RDC library
Hello. We installed SCCM 2012 a few years ago. In recent years, this has really only collected dust and been little used. But now, it has been decided that we will set up new hardware with server 2022 where SCCM 2022 will be installed. What we've done is uninstall the old instance so we can start with a clean one. I see that the entries we had on our DCs - in "System/System management" disappeared after we removed roles and uninstalled SCCM2012. I have followed a step by step guide to install new standalone instances on 2 sites.(https://www.youtube.com/watch?v=wCElfLBLyX0) Everything apparently goes well with new users, SQL installation, rights etc., until MS Config Manager Setup Wiazard has to do a Prerequisite Check.. There are 2 things wrong here: Microsoft Remote Differential Compression (RDC) library registered Microsoft Remote Differential Compression (RDC) library must be registered for Configuration Manager site server installation. Details at https://go.microsoft.com/fwlink/?linkid=2186120. Existing Configuration Manager server components on site server. A site server or site system role is already installed on the computer selected for site server installation. Remove the site or site system role from the computer, or select another computer for site server installation. I have tried uninstalling and reinstalling the "Remote Differential Compression" feature a few times but still get the same error despite having it installed. I can understand that I get errors on the Exisiting configuration manager server, as we have had one installed. But a bit strange to get that message when it is uninstalled. So I'm kind of stuck on these error messages... Does anyone know how I can move forward?How can I change SCCM client setting?
Hello Team, I don't have a lot of experience with Configuration Manager and for this reason I'm asking about your help.We have new Configuration Manager environment and I'm able to install CM client on servers which are in AD. These servers are new or there were no CM clients installed before - everything is working fine. Couple days ago we migrated some old servers to AD. I can see these servers on CM console but I can't see that there are already CM client installed. On this servers CM client is already installed as they were before in different AD and they were managed by different CM. Now I need to change CM client settings to point to new CM instance. Could you tell me please if it is possible and how to do this or I need to uninstall client and then install CM client once again? Regards, Sebastian
HAADJ and Intune with OKTA
My question is the following, Is it possible to use OKTA(Third party) as an authentication/Identity provider with Hybrid Azure ID join tenant and enroll devices to Intune? We need to adjust our environment to be able to utilize Intune. To elaborate, Please find the below: -In this environment, We can run AD Sync and sync devices to Azure as Hybrid Azure ID joined. Same steps required here: Configure Hybrid Join in Azure Active Directory | Okta - Sign in Settings in AD(Entra) Connect to "Do not configure" as recommended by Microsoft for Third party federation scenarios (Confirm if this the preferred scenario for AD connect with OKTA). -Hybrid Entra ID join is currently being achieved with GPOs and not using SCP (Targeted deployment) -Autoenrollment to MDM is enabled via GPO and correctly distributed to device/user. Behavior: -Devices show up in Azure however according to MS Intune pre-requisites, UPN in cloud and on-premises should match and mobility license should be assigned in cloud. The situation currently is the domain on-premises is contoso.com and users are provisioned via OKTA to cloud to have contosocorp.com, So upon login they get redirected to contosocorp.com thus having a mismatch in credentials. (in a test environment(without Okta), alternate UPN suffix in domains and trusts is added and UPN is changed to match cloud ---> this worked). -In order for Intune to enroll devices, The login credential should match and a login event to the windows device must appear in Azure Sign in logs(This is confirmed as a pre-requisite by Microsoft), Which is not the case here. -Okta is set to Universal Sync which is not recommended by Okta as not compatible with AD sync according to the following https://help.okta.com/en-us/content/topics/provisioning/azure/haad-join/prereqs-haad.htm#Prerequi2. -If we do use both Okta and AD connect, a user will be provisioned twice in cloud, Once with the contoso.com(without Okta) and once using contosocorp.com(using Okta - will include licensing). -Questions are as following: 1-Any workarounds to use Intune to enroll devices without UPN matching in the current scenarios. 2-If we are to UPN match on Prem and cloud -> How can this be achieved without deprovisioning OKTA(Or removing Provisioning type: Universal sync)? 3-How can we avoid duplications (since both Okta and AD sync will provision users in 365) 4- Perhaps there could be a way to enroll the devices only to Intune but not the users?? Guidance will be very much appreciated. Thank you.
SCCM SMS_Execute is not installed after server upgrade from 2019 to 2022
Hi We have recently upgraded our servers from 2019 to 2022 and after this upgrade we have got the couple of issues as below: 1. SMS_Execute is not installed on MPs 2. Client is unable to interact with server and missing the apps some users not able to see any apps in software center, please suggest how to fix this,,''
