https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# _general
s
This message was deleted.
r
There is a registry fix for that: HKLM/Software/Citrix/Graphics DisableAnnoyingJamesRankin DWORD 1 🤣
🙌 1
😂 2
😁 1
j
You had me hopeful for a second there
r
Haha, sorry.. Just messing with you
j
This is very annoying because one published desktop doesn't show the blue key, and a new one does. I'm thinking there must be something in the image or policies that is triggering it.....
Not the policies. Driving me insane now
n
I saw your tweet, and have seen that icon in posts before. The only thing I found today while searching was this: https://discussions.citrix.com/topic/386744-key-icon-displayed-when-logging-into-xendesktop/?do=findComment&comment=2034294
j
Yeah I read that, but it seems a little light on absolute info. I've tried setting all of the policies concerned on something not showing the blue keys, and none of them make it appear. Conversely, on my deployment that is showing the blue keys, no amount of policy tweaking or blocking gets rid of it. Which is driving me mad as the customer has another desktop published that doesn't do it 😞
So it turns out that this "blue key" is caused by logging on fairly soon after a provisioned machine boots up. Wait for about twenty minutes, and it stops happening 🙂 However, as I had my Delivery Group set to restart on logoff, I was seeing it constantly. Turn that off, and all is good. Weird!
n
I can't wrap my head around that solution.
j
It works though 🤷‍♂️
But it must be something in the image, because I've built other deployments recently that don't exhibit this problem. I did make the mistake of sucking up all the GPO settings into the image
n
I guess you could track it down by creating a handful of images, each with a small number of the policies applied, then logging in to see which exhibits the issue.
j
I could if I could be bothered to 😉 I remember seeing this in a managed service as well, they obviously didn't consider it an issue
n
You could write a blog about it and be the hero of the other folks who had the issue... lol
I did see at least 2 threads on Citrix's forum about it.
j
Yeah, I put a comment on one of the threads
Bloke I work with reckons he's stuck with it permanently on one of his deployments though.....more digging appears to be necessary
Actually he's mistaken - waiting for a period of time after boot works for him too
b
Are the machines hybrid joined to Azure AD? I have seen this when I don't run `dsregcmd /leave`on the golden image prior to sealing.
j
No, they're joined to an on premises AD
m
interested to know why having GPO in the master image is bad, I thought you wanted your master images in the same OU as your clones?
j
Things change. Digging out settings that suddenly became redundant, problematic or tattooed leads to extra image updates and more work. YMMV
m
is there any speed advantage to having the gpo cached in the image (assuming the cache is good and settings haven’t changed)?
I guess if the bulk of your settings are user based, probably not?
j
Minimal at best. Even the slightest change in the applied GPOs and pretty much the processing time is the same.
m
I might need to rethink how I do this then
build in an OU with blocked inheritance then push to the real OU at deploy with MCS
n
That's what I do, blocked inheritance for my master VM, but all QA/Prod VDAs are in OUs with the policies applied.
✅ 1
4 Views
Open in Slack
PreviousNext
Powered by