Ggtcf

When launching processes on remote machines, where said processes are required to run under a specific Windows domain account, I use code similar to this:

new ManagementClass(
 new ManagementScope(
 String.Format("\\0\root\cimv2","machine_name"),
 new ConnectionOptions
 Username="username",
 Password="password",
 Impersonation=ImpersonationLevel.Delegate,
 Authentication= AuthenticationLevel.Default,
 EnablePrivileges=false
 
 ),
 new ManagementPath("Win32_Process"),
 null
).InvokeMethod("Create",new String[]"process_name.exe");

This works fine but throws an exception when attempting to launch a process on the local machine, that is, the same machine on which the launch code is running. The error message is quite clear regarding the nature of the problem: System.Management.ManagementException: User credentials cannot be used for local connections

Sure enough, nulling out the username and password fields allows the call to succeed.

Thus far, this limitation hasn't really been a problem because, as it turns out, when I need to launch a process on the local machine, I don't mind it running under the same account as my launcher code. So the logic of the program detects whether or not we're targeting the local machine, and if so, simply nulls out the username and password.

As you may have guessed by now, I'm currently in a situation where I need to launch a process on the local machine using a different windows account with a known username/password. But I'm not sure how to overcome this odd limitation of being unable to use a ManagementScope of the local machine alongside a username/password.

I can pull this off with Process.Start(), of course, but it's been made clear to me that using the ManagementClass is the preferred course of action on this project.

Back on 2011, this guy was having a similar problem in a very different context, but as you can see in the comments, suggested actions aren't helping.

Are there any workarounds?