In a regular production environment I would tend to agree. This came out of the comments...

I had to do the work around...

What would probably be better is if you wrote an article or blogged about it. That would make it more accessible.

The interface has to be aware of the password change ability. So if you're using an older client (not SQL Server Native Client), they'll get the error that says they...

SQLPing can do blank password and...

I would use SQLPing.

Yes, on smaller systems. We may investigate on our larger servers, but that hasn't happened yet. Another resource you may engage is the PASS Virtualization Virtual Chapter[/url].

Or to use SQL Server based logins for that purpose that don't correspond to any real person.

The problem is you can't stop them. If you don't encrypt your stored procedures and the like, they can simply view the defintions of them. Even if you do, there...

You want to properly institute file system security. If you do that, only an administrator can override you. And if the person is an administrator, they can get access to...

Totall agree with Lynn here. You'll want to make sure the objects don't belong to an actual person. Probably need to institute that as a standard in your environment. That...

The 0x1B indicates that the server principal is valid for user-to-user only. The thing that stands out to me is the service name. I'm not sure why it's the same...

Yes, for ESX Server 3.5 Update 2 and above.

Here is the Microsoft support policy for non-Microsoft virtualization environments. Here is the support policy for SQL Server 2005/2008 in virtualized environments....

Are there any errors in the OS system event log indicating the server is having problems locating the domain or talking to the domain controller? That's the first place I'd...

You should always try to grant permissions to a role you've created and then put the appropriate users in that role. If you also want the role to have execute...