WSL MCC setup requires a runtime account with proper formatting for setting MCC scheduled tasks

Hi marty5 ,

Make sure that the gMSA password is correct otherwise you could try with the local account to install and run MCC
1 - First, create a new global security group for allowing access to gMSA password. Then, create a Microsoft Connected Cache-specific gMSA. Finally, add the machines that will be running MCC to the global security group so they can access the gMSA's password during MCC installation. The examples below use PowerShell cmdlets to create and provision the gMSA.
Please note: You must substitute the appropriate domain information for your organization.
Example: Creating a new global security group named “mccAllowedRunners”
> New-ADGroup mccAllowedRunners -path 'OU=Groups,OU=test,dc=Contoso,DC=com' -GroupScope Global
Example: Creating a MCC-specific gMSA account and giving newly-created global security group permissions to retrieve the gMSA password
> New-ADServiceAccount -name mccRunner -DNSHostName mccRunner.Contoso.com -PrincipalsAllowedToRetrieveManagedPassword mccAllowedRunners
Example: Adding relevant machine accounts to the newly-created global security group
> Add-ADGroupMember -identity "mccAllowedRunners" -members "mccMachine1$"
2 - Add gMSA account to the Windows 11 or Windows Server 2022 machine(s) that will be hosting MCC
> Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0
> Install-ADServiceAccount -Identity mccRunner
> Test-ADServiceAccount mccRunner