Our security policy requires that no user account have access to both dev/test and live instances. Anyone who has any business looking at both has separate accounts. This also applies to our service accounts - service accounts for live are not allowed access to test, and vice versa.

Rather than going through a very lengthy process with our security people (and auditors), it would make our lives much easier if we could either specify a different Windows account to use for a given SQL Server instance, or alternatively if one Dashboard front-end could display change data gathered from multiple monitoring services (running as different users, possibly in different locations).