https://worldofeuc.com logo
Join Slack
Powered by
Another O365 on Server 16 post. Is there anything ...
# microsoft-365
n
Another O365 on Server 16 post. Is there anything that anyone can think of that you need to do differently to get SSO working? We use Okta Silent Activation, and it works fine in our W10 image, but we are prompted to login to O365 apps in our S16 image. They have the same Office registry keys, same install, etc. I am struggling to figure this out at this point.
d
PRT?
n
No PRTs involved thanks to Okta, which makes troubleshooting this an absolute mess
s
just prompted on the first launch? or on every launch?
pub desktop?
n
First screen, then it'll grab the license files. I assume since this is broken that in 27-35 days, we'll be prompted again. Had the issue in W10 at first.
Yeah, S16 published desktop
I see this screen in my nightmares now
s
then the activation window comes up?
after you click sign in
n
If I click sign in, I get the auth window to enter my e-mail, then it processes and activates
s
what if you cancel out of it and close that office app, and then reopen, does it let you open without a signin?
n
Nah, shows unactivated
s
so prob not the same as the one i saw here: https://worldofeuc.slack.com/archives/CLSHNTWLW/p1721058832898839
n
weird, I can't click on that
s
n
So those two screens you posted are what we're seeing. Did you have to setup a GPO to force Edge to auto login for some reason?
s
yeah, the last message is what i applied the 'DisableOneAuth' registry item
on net new profiles, i'd get those prompts, but if i closed out of it and reopened word, it auto autoactivate and open
if urs doesn't do that, something tells me SSO isn't quite working
that reg fix is prob worth a try tho
n
trying it now
dafuq kind of magician are you, Steve
s
lol
n
That key showed up in 4 Google results, all of them garbage
s
yeah, Microsoft is keeping that oen close to home for some reason
n
Launched Word, activated right away. Didn't need to do anything else
no way can I roll this out without info from MS, though
s
i may have some deets, one sec
it was a microsoft recommended fix
I pressed them for more details and they wouldn't share exactly when and when not to apply it, but here is the comm email from them.
n
That they called out S19 concerns me ,since this is S16
s
yeah, i poked and prodded to get more info and they came back with
n
They value your time and business, so it must be real
Gonna open a ticket to see if they can at least confirm that this is what we need, but you're a life saver. We're getting hammered on this from leadership.
j
Proxy? I had SSO trouble a long time ago because a proxy. But why would it work in W10 and not S16.
n
All go through the same proxy, so that should be fine, too.
Hmm, closed my desktop, relaunched... prompted to sign in, though it's a different sign in screen
s
whats the screenshot
n
Let me grab it, trying something
s
your retaining those shared act lic files in the profile right?
n
We are not, because Okta Silent Activation pulls new licenses each login
Okay, second launch looks good. I forgot that we are killing that Identity reg key as part of CPM exclusions, so I did not have this new key back in there.
🤘 1
Just bonkers that this works completely differently from W10, and I hate O365 licensing.
j
Hard to get in place but when it works, it is stable :)
💯 1
n
Tested this all afternoon, and it seems to be working well. Going to extend it to UAT next week. @Steve Noel, I owe you lunch.
s
All good, we're all a team here. glad it's working, only took me a week of troubleshooting and 2 painful calls with Microsoft, haha. Cheers!
11 Views
Open in Slack
PreviousNext
Powered by