remoteapp. How to mount profile disks?

Question

RDP

There are 2 servers: 1 - domain controller (WS2008R2); 2 - terminal (WS2008R2) (on it RemoteApp).
Profile disks are configured in remoteapp. When a user opens a remote application for the first time, a vhdx disk is created, and a link to this disk is created in the C:/Users/ directory.
It is necessary to make authorization in the domain and, so that this disk is mounted to the user when entering the domain.
Through group policies on the domain controller, I set up "mapping drives" and everything is mounted, but:
1. In order for the disk to be created and mounted, the user must first open the application from remoteapp and only then enter the domain. How can I make the remoteapp profile disk be created when I log in to the domain, and not when the application is first launched?
2. Disks are mounted via links (which are in C:/Users/) and when the server is rebooted/the client is disconnected, these links are deleted (until the next user opens the application). How to leave these links or how to mount disks so that they do not fall off (I tried to mount not through links, but immediately vhdx [\\example.com\Users\UVHD-%LogOnUserSid%.vhdx], but nothing happened)?
I don’t understand what the advantages of remoteapp disks are, can it be easier and better to create disks yourself (something like this: www.padisetty.com/2013/11/creating-data-vhd-using-... )?

Answer 1

"It is necessary to make authorization in the domain and, so that this disk is mounted to the user when entering the domain."
What's the point? You will block vhdx in this way - when you log on to the terminal server, you will receive a temp profile.
"The simpler way is user profile disks. User profile disks store user and application data on a single virtual disk that is dedicated to one user's profile. One of the key challenges to pooled virtual desktop deployments is easily maintaining the user settings and data; this is because this information is discarded at logoff when a pooled virtual desktop image is rolled back to its initial state.
blogs.msdn.com/b/rds/archive/2012/11/13/easier-use...