Here we cover how to turn on and enable remote desktop protocol (RDP).
If using an RDS VDI Deployment, these problems could manifest more quickly and with more severity, but you'd be setting up FSLogix at this point.By default in Windows Server 2016 remote desktop is disabled. You should be able to mitigate the performance losses with an REFS drive + Cached Exchange Mode + Latest version of Outlook (Office 365) Long and short, Outlook 2016 and newer does what FSLogix does for the Search index () The other Workaround to this is to use Outlook Online Mode. Online mode is not recommended with Office 365. Microsoft's recommendation for Office 365 hosted mailboxes being accessed from an RDS Server (Remember, proplus is now supported on 2019 now) is to use a Local Cached Exchange OST with Outlook 2016 or newer.
You *could* see some performance decreases if the indexer needs to go back to the local system cache, but in a Session Host environment, the chances of this happened are quite low. The Search limitation referred to in the first item is mitigated with Outlook 2016. Go to the Caching Settings of the profile disk share and select "No files or programs from the shared folder are available offline" It also has no negative effects since there is no need to cache the UPD files. It will go through your UPD share and compact any VHDX files that are not in use.ĭisabling share caching can prevent some rare situations where the UPD fails to dismount from the RDS server. The script below can be configured as a scheduled task on your file server. As a result, you may end up with a ton of blank used space.
The UPD automatically expands any time the user adds data to it, but it never compacts once data is removed. UPDs are dynamic VHDX files that can expand up to 20GB by default. This will make sure that none of the power settings lead to disconnections. Make sure that all your servers are set to a High Performance power plan. This will be evident when creating UPDs(first login) and when they need to expand. Using ReFS as the file system of the drive that will host the UPDs will improve VHDX performance. This might not always be possible based on your configuration, but it is ideal since it keeps all the network traffic within VMware. In order to reduce latency and the likelihood of a UPD disconnect the server hosting the UPD share should be on the same VMware host as the RDS servers. The next time the user signs into the server their index will load instantly. What they have done is create their own "UPD" that stores all the user's Outlook and index data. The solution is to configure FSLogix Office 365 containers. You could disable the index back off, but it will lead to performance issues and it won't actually fix the issue. This will become a major issue when you have 5+ users on a server and the index throttles itself. The result is that the next time the user logs into the RDS and opens Outlook their search index will need to rebuild. This means that when a UPD is disconnected the user's index data is deleted. On Server 20 (Server 2019 does not have this issue, but it doesn't support Office) the Windows Search index is machine wide. I'll keep this updated any time I find new improvements.īefore you even consider deploying UPDs you need to be aware of this limitation. The goal of this article will be to configure the RDS and file servers in a way that maximizes performance and reduces the likelihood of UPD disconnects. User Profile Disks (UPDs) are great for load balanced RDS farms since it allows users to seamlessly roam from server to server. Some of the items below apply to FSL Profile Containers. After months of testing I recommend deploying FSLogix Profile Containers instead of User Profile Disks.