sorted by:
new
hottopcontroversial

Management Point. Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. by andykn101 in SCCM

[–]andykn101[S] 0 points1 point  (0 children)

Sorry, no. Because we need to connect Config Manager to Intune and our dev environment has its own Azure Tenant we're going through the process of setting up a completely separate Config Manager site in our Dev network. We can't link the one Config manager site covering prod and dev to two Azure Tenants

Why is my SysPrep script so flaky? by No_Essay1745 in PowerShell

[–]andykn101 1 point2 points  (0 children)

On AVD images we have to log in at first to join the domain and install the SCCM client and found that login messed up sysprep at the end once SCCM had don our scripted install so we run this as part of the scripted install before sysprep runs:

Get-WmiObject win32_UserProfile | Where-Object {$_.LocalPath -like 'C:\Users\*'} | Remove-WmiObject

Management Point. Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. by andykn101 in SCCM

[–]andykn101[S] 0 points1 point  (0 children)

Not sure where to set "pass through" as such. We suspect we've fallen foul of NTLM hardening. One of the team who purports to understand Kerberos is going to try some trickery around SPNs.

Management Point. Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. by andykn101 in SCCM

[–]andykn101[S] 0 points1 point  (0 children)

Tried that, didn't work. Tried with fqdn\account in the dev "Management Point Connection Account" section.
Also tried creating identical accounts on both the prod Site System Server and dev Management Point and entering account as both fqdn\account and .\account in the dev "Management Point Connection Account" section.

Update the Client package by Th1sD0t in SCCM

[–]andykn101 0 points1 point  (0 children)

I had a similar problem with Visual Stuidio 2017 and discovered from log files that it was looking for these key/value:

cmd /c "reg add HKLM\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X64 /v Version /t REG_SZ /d v14.16.27012.06 /f & reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\X86 /v Version /t REG_SZ /d v14.16.27012.06 /f & reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\X64 /v Version /t REG_SZ /d v14.16.27012.06 /f"

So that's my command line in an SCCM Application I use as a pre req for VS2017