Hello,
We had a serious issue with UPDs in our environment and I'm really just testing the water to see if we were extremely unlucky, or there is inherent problems with UPDs.
The scenario is as follows:
We have a single RDS server. The Collection on this server is configured to use UPDs which are stored on a separate server. One morning, we had a full BSOD on the RDS server due, we think, the a lack of available RAM. In any case, after the RDS server rebooted from the BSOD, we discovered that all users who were connected to the server when it fell over were being logged on with a temporary profile. On closer inspection, we observed that there was a c:\users\%username% folder for all of these users, but when they logged in, they were actually being dumped into a c:\users\%username%TEMP folder instead.
We consulted the Event Viewer where we observed a ntuser.dat error for every single user. Of course the ntuser.dat resides on the UPDs and it soon became evident that every single user who was connected to the RDS server when it fell over ended up with a corrupt ntuser.dat hive.
Any thoughts? Has anyone seen anything similar to this? It was a very time consuming restoring all the UPDs from the previous night's backup and I am worried that the UPD concept is perhaps not as resilient as I would have thought.
Thanks in advance.