https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
l
Cloud cache or no ?
n
No Cloud Cache, though now that you mention it, I suppose I should actually be setting those settings in the GPO to Disabled?
I actually don't even see an option to enable CC in the GPO.
l
You have to put in a location so if you haven't that should be fine. Check the logs though.
n
Couldn't find "cloud" in the log, so I assume I'm all good there.
@Leee Jeffries, you may have saved the day again. If I manually stop the CCDS service, logoff is back to normal. Is there a preferred way to disable Cloud Cache that I'm not seeing? The docs make it seem like the Enabled registry key in the normal Profile and ODFC folders is what is enabling it, even if no location is specified.
...or not. Now my logoffs are instantaneous and I haven't changed a single thing.
And back to slow, so who the hell knows at this point.
l
Disable that service completely and retest. Disable in GPO if you have to.
I've not been in a situation where it kicks in without a location. @James Kindon
What do the logs say though?
n
The only CCD reference I see is:
Copy code
Configuration setting not found: SOFTWARE\FSLogix\Profiles\CCDLocations.  Using default:
l
That's it chap. If you populate that it works and otherwise it should not. Disabling the service won't harm you if this is not populated.
n
I'm going to disable the service via GPO and give it another go on Monday. I've had enough of this week and am going home now.
Have a good one!
👍 2
I know I've been all over the place in this thread, but the only consistent "fix" I've seen for this is to stop or disable the Print Spooler service. If I do that, the VDA logs off immediately like it normally would.
l
You said you were giving up? Have you checked event logs?
n
It was bothering me so I logged back on from home to test more. 😕
Event logs don't show much of anything to be honest. I actually don't see anything at all in terms of printing.
I even copied the vDisk and uninstalled the AV client to truly rule that out.
l
You are now down to procmon , analyse with a fast logoff and compare. Bummer.
n
Is there a good way to capture a ProcMon log when testing logging off? IIRC, if I logoff with that running it corrupts the log.
l
@Guy Leech looks at guys tweets. He has a tweet about doing this remotely using Powershell. I'm sure you'll get what you need. He may even be able to advise you as you've put in the leg work to pinpoint. He's a good Guy.
n
Found his tweet on the subject. Much appreciated! https://twitter.com/guyrleech/status/1125797449908609027
l
My pleasure bud. Follow guy, hes very knowledgeable.
n
Thought I already did, but apparently not. That's corrected, now onto testing.
l
Good luck man.
n
My keyboard's safety depends on this...
j
There are no processes like AV or similar halting the log off? The CC side of things 100% wouldn’t come into play with you specifying a location and removing the old path
l
I thought so here. If it's AV procmon will show you.
n
I ripped my Trend Client out of the image to test, same result. Slow logoff unless I kill the print spooler.
j
No one likes printers anyway
n
In the grand scheme of things, it's the logoff process, so I don't care as much as I would the logon, but I'd like to correct this. I don't want to resort to a logoff script terminating the spooler, either. That's kinda hacky.
l
I dont think me or James would recommend that. We need to find root cause. Let's see the procmon. But you will need a comparison between okay and not okay.
👍 1
n
Grabbed a ProcMon job (terminated it before the session actually ended because I figure that'd help not corrupt it).
l
It'll be okay by the way. It commits the writes to the file as it sees them (hence it being slow) so feel free to run until it stops.
j
Any form of changes in the environment re printers at all? New driver, new config? New app?
n
This is my new 1912 LTSR image, so 1912 is the big one, along with WEM 1912. My 7.15 image with WEM 1906 doesn't exhibit this behavior.
l
Okay so.... Any locally installed print drivers that windows may like to update?
I think James may be on to something.
n
Sorry, forgot to answer that. I only use the Citrix universal print driver, no native driver installs allowed.
Nice and clean
I don't see how it would matter, but since this is 1912, it's also got Adaptive Transport enabled by default.
l
Adaptive Transport wouldn't link to the print spooler but.... You may have something with UPS, so compare the procmon traces with and without print spooler enabled and then we may be able to raise a ticket.
n
Well, if anything ProcMon has shown me there's another issue. One of the App Layering batch files is running in the background constantly and it shouldn't be.
My eyes are bleeding reading these ProcMon logs, and nothing really jumps out at me.
And I'm back to logoffs being totally normal again, without me changing a damn thing. I just don't get it.
r
Man sounds rough bro.
w
IT's favorite word when troubleshooting issues: random.
👍 1
n
And that's truly what it is at this point. I logged in this morning to run through more testing, and now I can't replicate it. At the very least, while troubleshooting this I found an issue in App Layering 2001's kmssetup.cmd file (in my environment, at least), so there's that.
l
Not a total waste of your time then mate ;-)
n
No, but it drove me to working back to back 12's, so I've got a score to settle with my environment, haha.
l
Lol
n
It's too bad the end users don't get to experience what we go through to give them a nice environment to work in.
l
Bring them in for reviews once a month. Involve them in the direction and effort. They will ;-)
n
I work at a children's hospital, even I couldn't justify that use of their time. It's all good in the end.
2 Views
Open in Slack
PreviousNext
Powered by