Forum Discussion

OnPremBeatsCloud's avatar
OnPremBeatsCloud
Copper Contributor
Aug 15, 2024

Need to know if CM site server account supports UTF-8, longer byte limits, and more

We are using MECM/SCCM with two domains - my primary domain I run, and a customer domain that has a management point VM set up in it. That Management Point is connecting back to my main domain via a service account.

 

The admins of the customer domain are moving to a new HR product, Workday, and wish to know the following as part of their migration.

 

  • Can your service, CM, consume display name as UTF8?
  • Can CM consume display name with a 1,024 byte limit?
  • Could CM consume a custom attribute for name data (instead of display name)?
  • Can CM use SAML, OIDC (OpenID Connect), or Azure for authentication or provisioning?

I have examined the SCCM prerequisites and cannot find specific details on this. Is there any way I can find out the answers to this? I am assuming the answer is no for all of this - but in the interest of being thorough for the other domain's admins, I want to at least ask and confirm.

Site Setup and client deployment
  • OnPremBeatsCloud's avatar
    OnPremBeatsCloud
    Nov 25, 2024
    1. I came across this link - which says that indeed, UTF8 is primarily used almost everywhere except a few places: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/unicode-and-ascii-support
    2. The customer domain sent us a test/fake list of AD accounts to import that contained all sorts of international UTF8 characters in the DisplayName, givenName, and sn AD attributes - and it turns out that by default (which we are doing) that MECM does not use any of those attributes at all. Whoops, and duh on my part. So it looks as if this won't be a problem, since we have no plans to enable any of those atypical attributes in MECM anyway.
  • OnPremBeatsCloud's avatar
    OnPremBeatsCloud
    Copper Contributor
    Nov 25, 2024
    1. I came across this link - which says that indeed, UTF8 is primarily used almost everywhere except a few places: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/unicode-and-ascii-support
    2. The customer domain sent us a test/fake list of AD accounts to import that contained all sorts of international UTF8 characters in the DisplayName, givenName, and sn AD attributes - and it turns out that by default (which we are doing) that MECM does not use any of those attributes at all. Whoops, and duh on my part. So it looks as if this won't be a problem, since we have no plans to enable any of those atypical attributes in MECM anyway.

Resources