"Steve Jain [MVP]" wrote:
> On Sun, 13 Sep 2009 17:25:01 -0700, dmyers2k
> <> wrote:
>
> >Host: Windows 7 64bit RTM
> >Guest: Windows 7 32bit RTM
> >
> >Why is the Start/Shutdown button modified in the Guest OS?
> >
> >The VM can only be shutdown using the Action drop-down menu
> >
> >Why is it this way by design?
> >
> >VMware and VirtualBox both retain the normal Guest Start/Shutdown button
> >function
> >
> >Why has Microsoft chosen this alternate path?
>
> Are you referring to Windows Virtual PC VMs? If so, it’s because
> your’e connecting via Terminal Services which doesn’t allow you to
> remotely shutdown the session on a client OS. If you disable the
> Integration components you can do this.
> Also, you can simply type "shutdown -s -t 00" from the cmd prompt, or
> a create a short-cut to launch this cmd as a .bat or .cmd file.
>
> —
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>
Thank you so much for that answer.
For me, it is always good when I can get a logical explaination for these
things.
I am playing around with virtualization on my Dell XPS M1730 laptop.
My interest in virtualization was prompted when I worked doing tech support
for different OSes. I always thought it would be good to have a vm for each
OS.
Now, I am going to delve into App-V since it is irritating to me when
software applications can’t coexist without problems.
It will be nice when virtualization technology reaches beyond the
Server/Client role.
Again, Thanks
