This message was deleted.

The load log time seems to be in this section of the log

[19:48:19.735][tid:000009f8.00000974][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\CleanOutNotifications.  Using default: 1
[19:48:19.735][tid:000009f8.00000974][INFO]             Prep1
[19:49:52.201][tid:000009f8.00000974][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\RegisterAppNotifications.  Using default: 1
[19:49:52.201][tid:000009f8.00000974][INFO]             Prep2

in this example, 93 seconds of time between those two log entries

What about the creation of a new fslogix profile? Log in and creat it. Log out, allow it to unmount and meeger the rw into the parent vhdx. Then log back in. Compare that time. I understand you want to keep the users data. But it would be good to see that of a non convergetion from one peofile type to another. I went from upm to fslogix. Wasn't a good experience.

The same profile loads fast on other collections, which the same fslogix version. The only difference on this collection is the application set. Will get feed back over the weekend. Works fine once logged in, just there is a extra 90 delay in logon.

Maybe explain collections and applications sets?

Sorry Ray, RDS Collections. it is almost like a Delivery Group

RDS Collections are plastic , Delivery Groups are playdo lol sounds like an odd issue here. Same storage being used?

Good analogy. I remember rds collections.

Faster storage actually. The other collections on the FSLogix profile are using the same storage, 1.3 seconds spend in the logon phase for FSLogix