Ahem. The term active\active is soooooooo last year. What you have there is a multi instance cluster.

it is possible but why do you want to do this? sounds risky.

yes

the process you are describing is for moving the master database not msdb.

msdb can be moved with the alter database modify file command and restarting SQL in the normal way....

The 10 per instance is not a hard and fast rule, its a 'recommendation' only and MS were being conservative.

for me the limit was hit on 24 databases, others have...

to bounce - to stop and restart a service, therefore the service goes...

In this situation I have been able to resume mirroring by bouncing SQL on the mirror.

How many databases are you mirroring? You may have reached the limit for your infrastructure....

In the security properties of the server (right click\properties) change the auditing level to 'failed logins only'

by the way, post SP3 you should apply security hotfix ms09-062 as well

http://www.microsoft.com/technet/security/bulletin/ms09-062.mspx

download SP3 and install

SKYBVI (9/10/2010)

We have a log shipping server. It just contains all the log shipped databases in standby/read only mode.

We want to upgrade it from 9.00.1399 RTM enterprise...

bit of a shot in the dark but has anyone changed the locale of the server?

you should see two keys listed, you only want to delete one of them, the key from the source,2005 database

SQL 2008 and 2008R2 are different versions and therefore on different release paths. Each will have their own service packs. there is not one out for R2 yet

if this is a DR server are you using database mirroring? that could cause this if you are mirroring a large number of databases and there is catching up to...