Interesting. Thanks for the tip. I'll have the team give it a try. FWIW, I've used the "existing account" with the same Site Server Installation account for MP and DP setups in other untrusted domains without fail, so I'm not sure that using "new account" will work, unless it works a bit differently for the SUP than for the other two. Thanks,-S
Subject: Re: [mssms] SUP in untrusted domain From: [email protected] Date: Sun, 13 Apr 2014 08:33:09 -0700 To: [email protected] Let me add. Even if we had used the same accounts before, if we picked existing account selection it would always fail. BTW, always do 'new user' when running the wizard, selecting existing user never worked for us. Cesar A.Meaning is NOT in words, but inside people! Dr. Myles MunroeMy iPad takes half the blame for misspells. On Apr 13, 2014, at 3:39 AM, Jason Wallace <[email protected]> wrote: OK can we just check that the username and password which you have registered at the SCCM server side is the username and password for the untrusted domain or the local admin of the machine due to become a SUP On 11 Apr 2014, at 15:21, "s kissel" <[email protected]> wrote: Thanks for that! I applied the hotfix, but it was not able to solve the problem. Regards,-S Date: Thu, 10 Apr 2014 12:02:20 -0700 Subject: Re: [mssms] SUP in untrusted domain From: [email protected] To: [email protected] Found it. KB2522623. Test, maybe different issue than ours On Apr 10, 2014 11:58 AM, "elsalvoz" <[email protected]> wrote: We were encountering the same issue and had to install a hotfix on the systems in all of our non-trusted domains to fix it. It is due to Kerberos. I will find the kb when I get back to the office. On Apr 10, 2014 11:19 AM, "s kissel" <[email protected]> wrote: Hey all, Trying to setup a SUP in an untrusted domain, but getting error in WSUSCtrl.log indicating:System.Data.SqlClient.SqlException (0x80131904): Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.~~ The site server has an MP and DP, both setup with a site server installation account.When setting up the SUP, used the same site server installation account, set WSUS to 8530 as per other SUPs in hierarchy, "selected Allow intranet-only client communications," no proxy. Have tried with the checkbox "Use credentials to connect to the WSUS server" enabled and deselected. When enabled, I used the same site server installation account which I believe is dbo on the wsus database back at the primary - In either case, the error above is the same What am I missing? Thanks,-S
