Stress testing an RDS server / farm

You need to create a customization patch (.msp) file in order to upgrade to Office 2007 on a Windows Server 2003 Server running Terminal Services.

You also need to have an Office 2007 license key that will work on Terminal Server. Retail or OEM keys will not work. You need a volume licensing key.

The following Technet article describes how to create a .msp file using the Office Customization Tool.

http://support.microsoft.com/kb/311241

Customizing a 2007 Office installation or Office 2010 installation

To customize an Office installation, use the Office Customization Tool to create a customization patch (.MSP). When you install Office with this customization file, the Office features that are set to Not Available are not installed.

1. Start the Office Customization Tool (OCT). To do this, click Start, click Run, type Office installation CD \setup /admin, and then click OK.
2. Select Set Feature Installation States in the navigation bar on the left side of the screen, and then select the feature that you do not want to install in the tree on the right.
3. Set the installation state of the selected feature to Not Available, Hidden, or Locked. If more than one of these settings is needed, the menu must be accessed again to select the additional setting.
4. Repeat steps 2 through 3 for each feature that you do not want to install.
5. Set any additional options that you want in the OCT.
6. Select Save As on the File menu to create the MSP file. It should be saved in the \Updates folder unless another location is specified in the Config.xml file.
7. Install the 2007 Office suite with the .MSP file.

Note The Office Customization Tool requires that Windows Installer 3.1 be installed.

That would work since that data locations remain the same and are just surfaced in the Roaming profile.

It is quite common on VDI deployment to disable Outlook cached mode so it's running in "online" mode and not storing mail locally. The downside is this requires a constant connection to Exchange, and for Exchange Online could generate substantial traffic depending on users and usage patterns. You don't have to settle for "online" only, you can mitigate the download times by limiting the amount of data that Outlook Caches. In outlook 2016 you can set this to as little as 3 days. I believe 2013 is 1 week.