Terminal Services Easy Print Printer/Drive Mapping Issues

A recent application implementation through Terminal Services I was involved in had a large amount of problems with local printers and local drives not mapping correctly.

The solution to the problem? Microsoft’s Easy Print driver wasn’t actually being used because .NET framework 3.0 and 3.0 SP1 weren’t installed.

Evidently requirements mean requirements… who knew?