RDS 2019 Setup and RDS License Role
-
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
Archiving is simpler for users that leave the org. Archive the .VHDX file.
Profile choke fix: Rename the .VHDX file to .OLD, log the user on, migrate their data. Done.Is this specific to Hyper-V or is that even related to the way this works?
The User Profile Disk is a dynamic .VHDX file that gets created in the designated storage location.
It can be set up with a storage limit. 5GB, 10GB, or more. Whatever maximum user GB size may be needed.
^^^ This is another reason to use UPDs/FSLogix. Storage sprall.UPD TIP: Once the RDS setup is complete and the TEMPLATE.VHDX is created in the designated location, mount the TEMPLATE.VHDX file, and shrink the partition down to a "starter size" GB, and dismount it.
Example: We have a setup where we deployed 30GB maximum UPDs.
We edit the template to shrink the partition to 10GB. That's all a new user gets when they log on the first time. If they hit a warning for low storage down the road, we can do one of two things:
1: Clean-up your mess
2: Log them off, mount the .VHDX, expand the partition by 5GB or more, dismount the .VHDX, and have the user log on. They get instant storage increases. -
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
Archiving is simpler for users that leave the org. Archive the .VHDX file.
Profile choke fix: Rename the .VHDX file to .OLD, log the user on, migrate their data. Done.Is this specific to Hyper-V or is that even related to the way this works?
The User Profile Disk is a dynamic .VHDX file that gets created in the designated storage location.
It can be set up with a storage limit. 5GB, 10GB, or more. Whatever maximum user GB size may be needed.
^^^ This is another reason to use UPDs/FSLogix. Storage sprall.UPD TIP: Once the RDS setup is complete and the TEMPLATE.VHDX is created in the designated location, mount the TEMPLATE.VHDX file, and shrink the partition down to a "starter size" GB, and dismount it.
Example: We have a setup where we deployed 30GB maximum UPDs.
We edit the template to shrink the partition to 10GB. That's all a new user gets when they log on the first time. If they hit a warning for low storage down the road, we can do one of two things:
1: Clean-up your mess
2: Log them off, mount the .VHDX, expand the partition by 5GB or more, dismount the .VHDX, and have the user log on. They get instant storage increases.Good info. You gave me much to think about.
Are UPD's still worth it if I expect a user to use <200MB? Everything our users need on the RDSH server is in the LOB app?
-
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
Archiving is simpler for users that leave the org. Archive the .VHDX file.
Profile choke fix: Rename the .VHDX file to .OLD, log the user on, migrate their data. Done.Is this specific to Hyper-V or is that even related to the way this works?
The User Profile Disk is a dynamic .VHDX file that gets created in the designated storage location.
It can be set up with a storage limit. 5GB, 10GB, or more. Whatever maximum user GB size may be needed.
^^^ This is another reason to use UPDs/FSLogix. Storage sprall.UPD TIP: Once the RDS setup is complete and the TEMPLATE.VHDX is created in the designated location, mount the TEMPLATE.VHDX file, and shrink the partition down to a "starter size" GB, and dismount it.
Example: We have a setup where we deployed 30GB maximum UPDs.
We edit the template to shrink the partition to 10GB. That's all a new user gets when they log on the first time. If they hit a warning for low storage down the road, we can do one of two things:
1: Clean-up your mess
2: Log them off, mount the .VHDX, expand the partition by 5GB or more, dismount the .VHDX, and have the user log on. They get instant storage increases.10 GB in a profile? what are they saving in there? I can see giving them maybe 2, but even a 2 GB profile seems HUGE.
-
Profiles can be 1-2 GB easy even without the user intentionally adding things to it. Every program out there seems to want to pack info into the profile these days and not in small quantities.
-
@NDC said in RDS 2019 Setup and RDS License Role:
Profiles can be 1-2 GB easy even without the user intentionally adding things to it. Every program out there seems to want to pack info into the profile these days and not in small quantities.
Sure, fine (though I generally don't see them much over a 1 GB) but 10 GB or the ridiculous 30GB they start at as stated above? I suppose I have an ISO directory on my desktop right now that's 10 GB itself.. so that's in my profile... but if I'm on a TS, I'm likely not doing that.
-
@pmoncho said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
Archiving is simpler for users that leave the org. Archive the .VHDX file.
Profile choke fix: Rename the .VHDX file to .OLD, log the user on, migrate their data. Done.Is this specific to Hyper-V or is that even related to the way this works?
The User Profile Disk is a dynamic .VHDX file that gets created in the designated storage location.
It can be set up with a storage limit. 5GB, 10GB, or more. Whatever maximum user GB size may be needed.
^^^ This is another reason to use UPDs/FSLogix. Storage sprall.UPD TIP: Once the RDS setup is complete and the TEMPLATE.VHDX is created in the designated location, mount the TEMPLATE.VHDX file, and shrink the partition down to a "starter size" GB, and dismount it.
Example: We have a setup where we deployed 30GB maximum UPDs.
We edit the template to shrink the partition to 10GB. That's all a new user gets when they log on the first time. If they hit a warning for low storage down the road, we can do one of two things:
1: Clean-up your mess
2: Log them off, mount the .VHDX, expand the partition by 5GB or more, dismount the .VHDX, and have the user log on. They get instant storage increases.Good info. You gave me much to think about.
Are UPD's still worth it if I expect a user to use <200MB? Everything our users need on the RDSH server is in the LOB app?
I think so. After working with them for a while, it becomes fairly clear as to the "why".
-
@Dashrender said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
Archiving is simpler for users that leave the org. Archive the .VHDX file.
Profile choke fix: Rename the .VHDX file to .OLD, log the user on, migrate their data. Done.Is this specific to Hyper-V or is that even related to the way this works?
The User Profile Disk is a dynamic .VHDX file that gets created in the designated storage location.
It can be set up with a storage limit. 5GB, 10GB, or more. Whatever maximum user GB size may be needed.
^^^ This is another reason to use UPDs/FSLogix. Storage sprall.UPD TIP: Once the RDS setup is complete and the TEMPLATE.VHDX is created in the designated location, mount the TEMPLATE.VHDX file, and shrink the partition down to a "starter size" GB, and dismount it.
Example: We have a setup where we deployed 30GB maximum UPDs.
We edit the template to shrink the partition to 10GB. That's all a new user gets when they log on the first time. If they hit a warning for low storage down the road, we can do one of two things:
1: Clean-up your mess
2: Log them off, mount the .VHDX, expand the partition by 5GB or more, dismount the .VHDX, and have the user log on. They get instant storage increases.10 GB in a profile? what are they saving in there? I can see giving them maybe 2, but even a 2 GB profile seems HUGE.
Remember, these are dynamic VHDX files. They start out at something like 4096 KB in size. If there's nothing much to go into the profile, then edit the template down to 500MB with a 1GB default size. They only use physical storage as they grow.
NOTE: If you need to enlarge the profile beyond the default maximum sized set when the farm was set up then it is a two step process with the user logged off:
1: Expand the .VHDX by needed GB
2: Mount and expand the partition then dismountThe user can then log on and they now have more space.
-
@Dashrender said in RDS 2019 Setup and RDS License Role:
@NDC said in RDS 2019 Setup and RDS License Role:
Profiles can be 1-2 GB easy even without the user intentionally adding things to it. Every program out there seems to want to pack info into the profile these days and not in small quantities.
Sure, fine (though I generally don't see them much over a 1 GB) but 10 GB or the ridiculous 30GB they start at as stated above? I suppose I have an ISO directory on my desktop right now that's 10 GB itself.. so that's in my profile... but if I'm on a TS, I'm likely not doing that.
There are plenty of user types that can have 20GB or more in their profile. It is what it is.
-
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@Dashrender said in RDS 2019 Setup and RDS License Role:
@NDC said in RDS 2019 Setup and RDS License Role:
Profiles can be 1-2 GB easy even without the user intentionally adding things to it. Every program out there seems to want to pack info into the profile these days and not in small quantities.
Sure, fine (though I generally don't see them much over a 1 GB) but 10 GB or the ridiculous 30GB they start at as stated above? I suppose I have an ISO directory on my desktop right now that's 10 GB itself.. so that's in my profile... but if I'm on a TS, I'm likely not doing that.
There are plenty of user types that can have 20GB or more in their profile. It is what it is.
Yes I have mini users with 5 to 15 GB of data in their documents and such
-
When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\DesktopEdit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.
-
@wrx7m said in RDS 2019 Setup and RDS License Role:
When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\DesktopEdit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.
The path is there in the form of a symbolic link. So, no. It's one way to limit exposure to ransomware.
If there is a need, the user can be logged off and one can mount the .VHDX file to gain access to whatever is needed.
-
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\DesktopEdit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.
The path is there in the form of a symbolic link. So, no. It's one way to limit exposure to ransomware.
If there is a need, the user can be logged off and one can mount the .VHDX file to gain access to whatever is needed.
Yeah, I fairly often have to copy files into a user profile here and there. I did notice that the disk is only mounted for the duration of their session and obviously would prevent interaction with it if the user is logged out. But, mounting the VHDX isn't that bad... if I had to do it when they were logged out. I would have to revisit a tool I just saw somewhere that allows you to quickly match the VHDX file with the user, since it only uses the SID in the file name.
-
@wrx7m said in RDS 2019 Setup and RDS License Role:
@PhlipElder said in RDS 2019 Setup and RDS License Role:
@wrx7m said in RDS 2019 Setup and RDS License Role:
When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\DesktopEdit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.
The path is there in the form of a symbolic link. So, no. It's one way to limit exposure to ransomware.
If there is a need, the user can be logged off and one can mount the .VHDX file to gain access to whatever is needed.
Yeah, I fairly often have to copy files into a user profile here and there. I did notice that the disk is only mounted for the duration of their session and obviously would prevent interaction with it if the user is logged out. But, mounting the VHDX isn't that bad... if I had to do it when they were logged out. I would have to revisit a tool I just saw somewhere that allows you to quickly match the VHDX file with the user, since it only uses the SID in the file name.
-
@wrx7m said in RDS 2019 Setup and RDS License Role:
When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\DesktopEdit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.
That is what I HATE about roaming folders... they simply do not act the same as local folders!
I typically download things to the desktop and execute from there. But when on a system that has a desktop redirected to the server - that fails 99% of the time, I have to move the executable to something actually local, then execute it.
