“Good morning, Dave.”
Well, my last post detailed a pre-production RDS Session Collection using User Profile Disks (UPDs) and some issue to had when mixing with Dedupe and DFSR.
This time it’s not a post about a pre-production RDS Session Collection using User Profile Disks. It is a post about the now production RDS Session Collection using User Profile Disks.
The Clients Migration went live on Monday, and besides the normal few minor issues, has been going pretty well.
“This mission is too important for me to allow you to jeopardize it.”
UPDs bit me on the ass today though – I’ll admit this my first production use of UPDs, but I’ve been labbing them long enough to feel fairly confident. Labbing =/= real world, as I found out today.
All Users were assigned a 1GB profile disk, with stuff like Documents and Downloads redirected to their main file share. That’s plenty right? However just 3 days in users began hitting space issues on their UPDs. I couldn’t understand it. The VHD was only 620MB on the Server, the Space taken inside the VHD was 400MB, when getting file properties, but the User could not write to the vhd due to lack of space. Disk properties show the mounted Drive at 900MB in use?
None of this makes sense, I can’t account for the bloat that isn’t actually there. Although…..I’m going to look suspiciously in the direction of Shadow copies, I can’t prove anything though. Just a gut feeling.
“Just what do you think you’re doing, Dave?”
So, I’ve spent about 2 1/2 hours, manually Extending the VHDs, and then extending the volumes in Disk manager to 3 GB. It’s laborious, but as with any task like this you fall in to a rhythm.
Next, to the Session Collection properties, I’ll just edit that so new users….wait…..why is that greyed out? I see no Solution after a quick goggle, so……… ¬.¬ …….. make sure nobody’s looking… I disable UPDs altogether and ¬.¬ re-enable them with the correct value of 3gb.
After Few missing heartbeats, I login to an existing user and the profile is fine.
Given the 2 people who read this blog are me, and me in work, I’m not expecting anybody to come along and say “Hey you idiot, it works this way…….” But if you do have an answer as to these oddities I’d appreciate it.
“My God, it’s full of stars.”
PS. Don’t use the “Replace” Action when mapping a Drive with GPOs, it will remove and recreate the Mapping every time the GPO is refreshed with Server 2012, bad news if somebody is using databases on the file share. Use “Update” instead.