This message was deleted.
# microsoft-fslogix
s
This message was deleted.
r
Im 2 Verisons behind. Windows search service stops on my Verison. Control up starts it. Then they had 1909 which was a bad build. Now they have the hotfix for that. @Nick Panaccio he might be able to give his Verison stability. @Dennis as well.
@Leee Jeffries and @Tim Riegler and @Jarian Gibson these guys as well
j
I have mixed feelings on cloud cache. Need to test latest
s
yeah, good feedback i’ll look up the build i used on last deployment it was 3 releases before WVD, other than cloud cache it was pretty solid. @James Kindon what’s your thoughts you have been running and gunning for a while curious what’s your go to build
j
Sup mr @Shane Kleinert 🤘🤘I’ve just finished another build on latest release with no issues to report so far - I feel like a lot of the issues that turn up seem to be from upgrades, else I have had a lucky run as I’ve been on pretty much every latest release for years now and have not really been hurt - I don’t do a lot of upgrade work though and when I do I like to remove and reinstall from scratch.... cloud cache I’m still saddened by 🙈
s
nice!! cutting edge! yeah, the upgrades i have done were earlier releases, haven’t done one in a year or so, been all net new builds. I’ll give the latest a go, we’re in a test phase now so best time to kick the tires. We’re your resent ones Win10? if so which build? Yeah man, CC is a cool concept but unless you 100% need it not worth the hit in recent builds. Your article was spot on around HA options, read it over again the other day
j
I’m 2 versions behind as well for prod. I’m a little worried about latest versions with the issues reported. Can’t risk the update unless it’s solid.
n
Just upgraded one customer to the latest build, no issues so far and their environment is more stable than before. I stay clear of CC
d
We use the latest (hotfix) build for profiles and office containers and even with cloud cache. It’s stable and we have no errors. There are a few things to consider: 1. Always uninstall old versions first and reboot before installing a new version. Reboot after installation! 2. Configure the policies carefully (we discussed this here), e.g. disable settings that you don’t need and keep in mind that the policies for the profile container don’t get undone by switching them to ‚Not configured‘ 3. If you use MCS or PVS I would NOT apply the policies to your master to keep it clean 4. Disable Citrix UPM and the Office container feature but never disable UPM SERVICE itself because of Director monitoring 5. Windows search service has to run and set to automatic BEFORE installing MS Office to use the Outlook search. There are several optimizations that disable Windows search 6. If you want to exclude unnecessary Office data (like cache) from your profile don’t include Office data in your office container, otherwise the redirection.xml won’t work
👍 1
d
Hi @Dennis do u use CC in your environment?
n
Do you use CC with OneDrive on XenApp though? Think about the local cache disk here. With CC you don’t just need to worry about the storage implications on you’re File Server, but now locally too. Though you have made some good points above, especially the “tattooing” of the registry with Profile GPOs
l
2 versions behind and I don't use CC in production. It's too unpredictable IMO. I stick with standard vhd locations, clustered file server / SOFS with continuous availability. It works a d it's solid, easy to maintain. I had alot of grief with rules in the latest release.
⤴️ 2
j
@Shane Kleinert most of mine have been server OS, doing win10 at the moment with 1803 windows (I think) and have another one about to start with either 1809 or 1903 (up to customer) - I also agree with mr @Leee Jeffries around the file server HA stuff, it’s really critical that these things are available full time - gone are the days of “whoops” with minimal impact - now it’s flat out nasty
⤴️ 1
l
It's been a long time since any issue have been profile related for me. @James Kindon are you aware of any removal tools. I have also found that upgrades are problematic. Perhaps we can write a community script for removal and then the process is just a reinstall.
n
How’s about msiexec /x {ProductCode} /q 😉
l
Tried that, I still seem to have issues with the latest upgrades. As James seems to have a stable experience I'm leaning towards remnants, I should out more work in to confirm first though. You have a similar experience Nathan?
n
Last customer did an IPU themselves, they are very happy with the environment now. I generally do vanilla installs. You might be right about the remnants, if anything it will be driver/service cos ultimately that’s where the real “magic” happens - or not so magic in some cases
👍 1
d
Yes, we use CC and it works quite well. We started using OneDrive (per machine installer) and with ‘files on demand’ feature. No production environments yet, cause we have a problem with OneDrive. Some users don’t get the ‘files on demand’ option, although it’s forced with a machine GPO. Seems to be a known issue with Win 10 before, but we see this with Server 2019. Anyone else? Without ‘files on demand’ you can’t use OneDrive with XenApp in my opinion. We also set the policy ‘Set the maximum size of a user’s OneDrive that can download automatically’ and restricted it to 4 GB.
l
I've not seen this Dennis, that just means it's not been reported yet ;-)
d
Which version of fslogix do u use with cc feature on ?
j
@Leee Jeffries nope, just been removing, rebooting, installing, rebooting :)
l
I think that maybe in Oz the VMs are more relaxed or something ;-)
d
The latest version 2.9.7237.48865 and an old version 2.9.6964.52690
j
ahead of the curve bud - preparing the way for you lot
l
Ha ha, I'd expect no less.
🍺 1
d
We POC'd on 2.9.7117 (aka the first MS build/release), it is solid for us, no CC, dare not touch it until rollout is complete and can start looking at newer builds...
n
Going back to the original question, it’s probably split into three areas. 1 - which version is stable for new environments 2 - which version is stable for existing I.e existing containers 3 - which version is stable for CC (if any)
r
Love this community
Awesome information Dennis 👍
Good point Nathan. I vote that
c
I had random freezing with the last two builds, rolled back to UPM. Testing the latest build in a VERY isolated environment. RDSH has zero issues, all my issues were on Win10 1903. The latest version seems stable for now. Not using cloud cache.
t
Running 2.9.7117 on 2016, with CC (for profiles only), and standard VHDX location for Office containers. No problems with that part of it. Current problem is search service on 2016 stopping and being set to disabled by System at some random point during the day. Heard this was fixed in newer version, which also broke other things, and haven't tested the latest hotfix yet. We build our images with MDT, so always a new install, no upgrades.
👍 2
m
Speaking from experience James Kindon is right, upgrading from a FSLogix version to a MS FSLogix version. I am pretty sure that this resolved an upgrade issue where outlook wouldn't load after upgrading 2.9.6964.52690 to the first MS release. Removing, rebooting and installing the latest version resolved the issue. I have a server I'll be testing this week with the 2.9.7237.48865, so hopefully the removal approach fixes it. Especially as we've had a rare BSOD on this box.
t
We're getting ready to run the new version (with included HF01) in our new image build process this weekend, and should have it through QA and into Test next week. I'll update with our experience on it then.
d
I had the deadlock issues with version 2.9.7205.27375, latest version 2.9.7237.48865 runs stable for now WITH cloud cache.
r
Dennis what is ur login times if you dont mind me asking. With CC
d
Windows Server 2019 with CVAD 1909, WEM 1911.1 and Office 365. FSL Profile and Office Container with CloudCache. All user settings applied with WEM (many registry actions to avoid user GPO’s) except GPO’s for Google Chrome, Office and Citrix Files. Results with Logon duration script from @Trentent 😁: User name : user01 Logon Time : 184537.354 Logon Duration : 7,8 seconds Logon Phase Duration (s) Start Time End Time Interim Delay ----------- ------------ ---------- -------- ------------- Network Providers 1,2 184537.4 184538.6 0,1 FSLogix: LoadProfile 1,8 184538.9 184540.8 0,3 User Profile 0,1 184541.0 184541.2 0,3 Group Policy 2,0 184541.2 184543.2 0,0 Pre-Shell (Userinit) 1,5 184543.6 184545.1 0,5 Shell:AppX - Load Packages 21,2 184545.4 184606.6 0,2 Logon Sched. Task Duration (s) Action Name ----------------- ------------ ----------- \Microsoft\Windows\Plug and Play\Device Install Reboot Required 0.50 Device Installation Reboot Dialog Task \Microsoft\Windows\CertificateServicesClient\UserTask 1.01 Certificate Services Client Task Handler \Microsoft\Office\OfficeTelemetryAgentLogOn2016 1.48 C:\Program Files\Microsoft Office\root\Office16\msoia.exe \Microsoft\Office\OfficeBackgroundTaskHandlerLogon 0.70 C:\Program Files\Microsoft Office\root\Office16\officebackgroundtaskhandler.exe \Microsoft\Windows\TextServicesFramework\MsCtfMonitor 0.22 MsCtfMonitor task handler \GoogleUpdateTaskMachineCore 0.17 C:\Program Files (x86)\Google\Update\GoogleUpdate.exe
r
Oh wow.
Mines 15 or so
t
Very nice @Dennis !
r
Does shell say 21? Or is that a type O
t
AppX load packages. For server OS it runs asynchronous, but client OS its synchronous (and this blocks login)
d
I also wondered about the Shell.Appx value, but it’s no typo. Thanks for the explanation Trentent.
t
It does consume significant CPU when operating so its probably be worth seeing if you actually need them (and remove them if you don’t). We all need the Zune player on our server OS right?
d
That’s interesting, do you have an idea which of the AppX packages can be removed without an impact for the users? Maybe we should switch this conversation to _optimization channel 🤔?
r
Isnt the appx package the bloat in windows? Example ms mail ect.
d
Get-AppXPackage -AllUsers | fl name,PackageUserInformation
t
Yes, you'd need to investigate whether your users are using any of them. Odds are probably against it, but I can't make that determination 😞
r
I thought Citrix optimizer removes them.
Or most
d
No, Citrix optimizer doesn’t
Get-AppxPackage -AllUsers | Out-GridView -PassThru | Remove-AppxPackage
r
Remove built in apps in citrix optimizer must be different then
n
Citrix Optimizer removes some of the provisioned apps, but not everything.
What Dennis posted will nuke them all.
r
Ok cool. So some not all, need to update my optimization notes
d
You can select which one to remove from the grid view, but I really have no idea what the hell is behind all these packages
n
Bloat, that's what's behind them. 🙂
t
Looks like I only have ~14 on 2016. Thinking there might be 1 or 2 worth keeping...immersive control panel, AccountsControl? Wish these came with easy to understand descriptions as well!
d
Remember we talk about Windows Server 2019, Citrix Optimizer only removes Apps within the Windows 10 templates, a server template for removing AppX packages would be great? Anyone? 😁
n
@Martin Zugec would be the person to talk to about that.
...and he's not in this channel.
d
So, now it’s really time to switch the channel…
I told Martin about the topic in the optimization citrix-optimizer thread (sorry)
👍 1
n
....
n
Post it in one more channel so that we don't stop at an odd number...
l
Sound like you should add one Dennis. There's a community repo.
d
Yea I know, I was just checking if there is already one. Sounds like a good idea to build one.
l
I think the 2016 one would probably be a good start. I wanted to do one a while ago and never got round to it. It must go back on the to do list.
n
I've always thought about putting my W10 template up there, since I combined both W10 and App Layering into one, but it's probably so specialized that it's not worth it.
l
It's always worth it Nick.
n
Why not, I guess. I'll give it a go tomorrow.
👍 2
I managed to survive GitHub, as it looks like the template is now live in the Community Marketplace.
👍 1