This message was deleted.
# microsoft-fslogix
s
This message was deleted.
s
Hey Kasper, it's pretty much the same. first mount is RW, if you don't configure the profiletype option. If you do, than type '3' will be forced RW at mount will back to RO on subsequent mounts. type '2' forces RO mount. We use this approach together with CC in a DSK Role / App Silo Role scenario. so mounts on DSK role machines will always be RW (assuming you only use 1 desktop together with 1 specific profiledisk). and mounts on App Silo roles get a RO mounted profile disk, where app settings are handled trough UEM.
๐Ÿ‘ 1
k
Thx..I'll pass that on to my colleague
r
what are peoples thoughts on the latest version of cloud cache? i am behind on implementing this and need to get that done.
k
It turned out to be a configuration issue. We got it sorted out, so both the customer and my colleague are all good now ๐Ÿ™‚
a
Hi Kasper, i've seen your trade and i'd like to ask if you could give some specifics on FSLogix configuration in this case. I'm a bit in the same situation with two silos DSK/APP and FSLogix CCD configured. When i enable multi session support (type 3), first session works fine, but launching the second one (app) gets stacked on 'Please wait for the FSLogix Apps service' and eventually stops. Launching the application as a 1st session works fine though, but then same problem with desktop session. Thanx in advance.
k
@Asmir Hmm...it sounds like I am going to do some more testing on Cloud Cache. As far as I know you should be able to use multi-session with Cloud Cache
s
Make sure you are on the latest and youโ€™re not having both CCDLocations and VHDlocation enabled
๐Ÿ‘ 1
a
Hi and thank you both for your answers. @Kasper Johansen indeed i checked the documentation and couldn't find anything explicitly saying it doesn't work with CCD on the other hand nothing explicit that it works but i continue with my tests. @Siebrand Feenstra VHDLocations are not enabled just CCDLocations directly in the registry since PVS based images, v.2.9.7117.27413 is being used, I'm not aware of anything newer.