What's up with IVMGuestOS::ExecuteCommand?

re: What's up with IVMGuestOS::ExecuteCommand?

Desmond Lee — Mon, 04 Dec 2006 20:58:36 GMT

Ben,

I noticed this ExecuteCommand() fact when I was researching for my Virtual Server 2005 scripting article*, as well as talking to IT Pro peers interested in this area. There is no direct means to call even native FindWindow() Windows API in the gust OS from the Virtual Server COM API, which would certainly be very useful to automate and control guest OS (without having to resort to WMI for simple operations for instance).

Will this behavior change or learning WMI will be the only way forward, especially when Windows Virtualization core will have no COM API interface (but WMI support only)?

* Part I is at http://go.microsoft.com/?linkid=5461095 or http://mcpmag.com/features/article.asp?editorialsid=623 and Part II should be on its way soon.

re: What's up with IVMGuestOS::ExecuteCommand?

Norman Diamond — Mon, 04 Dec 2006 05:12:13 GMT

Betas are betas. In all of the arguments I've seen about whether backwards compatibility is important or not, I've never seen anyone say that backwards compatibility to a beta is important.

re: What's up with IVMGuestOS::ExecuteCommand?

Dan — Sat, 02 Dec 2006 19:35:28 GMT

Adam: He means the user who executed the script.

re: What's up with IVMGuestOS::ExecuteCommand?

Adam — Fri, 01 Dec 2006 12:25:14 GMT

What do you mean "whichever user was logged on"? What if no users were logged on? What if multiple users were logged on?

Bizarre!

re: What's up with IVMGuestOS::ExecuteCommand?

Niels — Fri, 01 Dec 2006 10:57:25 GMT

Hi Ben,

What about the future of the command? Is it likely to return with security additions making it safe to use, or will it be killed completely?

TIA

Niels