On Sun, Aug 15, 2010 at 3:11 PM, Nadav Cohen <[email protected]> wrote:
> Hi everyone,
>
> I'm trying to implement a VirtualBox host on top of Windows 2003 with a
> RHEL5 as a guest. When I log into the Win2k3 server with my user, I can use
> VBoxManage list vms and see my vm listed properly.
>
> When I try to perform the same VBoxManage command from a remote machine
> using psexec
> (http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx), the list
> vms command simply returns that there are no registered virtual machines.
>
> This is the command I'm using:
>
> psexec \\<ip> -u <domain>\<username> -p <password> VBoxManage list vms
>
> I also ran "list systemproperties" from the remote machine, and got this
> response:
>
> <...>
> Maximum Devices per Floppy Port: 2
> Default machine folder:          C:\Documents and Settings\Default
> User\.VirtualBox\Machines
> Default hard disk folder:        C:\Documents and Settings\Default
> User\.VirtualBox\HardDisks
> VRDP authentication library:     VRDPAuth
> Webservice auth. library:        VRDPAuth
>
> Which is different from the same command from the Win2k3 machine, which
> results in:
>
> <...>
> Maximum Devices per Floppy Port: 2
> Default machine folder:          C:\Documents and Settings\<my
> username>\.VirtualBox\Machines
> Default hard disk folder:        C:\Documents and Settings\<my
> username>\.VirtualBox\HardDisks
> VRDP authentication library:     VRDPAuth
> Webservice auth. library:        VRDPAuth
>
> Is there a way to specify the default machine folder for VBoxManage? Or some
> other trick to make it work?
>
> Thanks in advance!
>
> Nadav
>
>

Its clear from the error messages you posted that psexec is not
actually logging in to the remote system and creating a set of
environment variables.  Thats why psexec is running as the Default
user and not the specified user.  Your problem is not a virtualbox
problem per se as I'm convinced if you could get psexec to login to
the remote box correctly youd get the output you think you should.

There is a command line option for psexec allowing for interactive
use, "-i" but I don't know if that would fix the problem.

Sounds to me like a question for the psexec list.

Rance

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to