I’m officially lost now and begin to look at how rapidly I can deploy roaming profiles, but on a whim I try to mound one of the affected VHDXs and get …… “Sorry, there was a problem mounting the file”Īha! What’s this? A quick Google later -> Copy (not Move) a VHDX out of that folder and back again – and the existing profile started to work again!Īt this point everything is great yeah? Well no, I want to find out just WTF happened. Put the old one in its place and, BAM, temp profile. I rename an existing profile VHDX to VHDXBAK, login, a new VHDX is created and works fine, login after login. Double check the Session Collection config, all good, check each RD server can access the file server and share, all good. I Immediately start pulling apart permissions on the File share for the profile disks. I return to it today, and no profile disk will load – all users receive temporary profiles. I’d not touched it in a few weeks because the Client kept putting of the migration date. I have a pre production 3 server RDS Collection in place with about 50 users, using User profile disks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |