This message was deleted.
# citrix-vad
s
This message was deleted.
d
I should have check Slack on Friday..I got messaged to look at a similar situation on my weekend. I was able to duplicate it and then it cleared up on the account I was working with. Difference being we are all persistent and the only users that we saw with issues were a couple of employee (non-client) accounts that had their logon token expire and weren't able to get them to renew. Won't be able to work with the broken accounts, if they are still broken until Monday (tomorrow).
g
Just looking into this again now. It might be related to a change enabling acceptance of "terms and conditions" that was executed last week her. I just to some exception rules added for the Citrix machines, so I'm just doing some testing to see if that is the issue. If not, then something must have changes elsewhere, either on our side or on Microsofts side.
It is confirmed, they enabled a requirement to accept "terms of use" via Azure Conditional Policy. For some reason that breaks sign-in from Office apps from the VDI. SSO for browsers works as intended. We are still looking into possible solutions, including verifying trusted sites and intranet sites.
d
Interesting. I'll be looking at my users in a moment. I don't think we made any changes, but there is potential that one of my co-workers did make changes while I was out. Thanks for the follow up.
p
Experiencing what sounds like a very similar issue for one of our customers. ADFS which has been working fine suddenly stops working, user i'm talking to first noticed it this modnay. I'll have to check with my azure guys if the terms of use requirement is set up and see if disabling the requirement fixes it
d
No changes were made here. I have had now a total of 5 instances and a full profile rebuild is the only thing I have been able to do that fixes the issue. I'm missing something and most users won't give me the time to work it either...not that I haven't broken the profiles of the users I was working on trying to fix anyway by "randomly" deleting things that looked like they could be related. Trying to get a more accurate approach to troubleshoot the next one we have, but it's starting to be a trend.
g
FYI, this issue was eventually tracked down to a Azure Condiational access policy with "terms of use" that is applied to some groups of users. A support case has been opened with MS for this case.