Requested of VMware to use VMware Server for Linux development. VMware serial number: 98W4H-YAV47-28097-41NKW. Download performed on 6 August 2008. This key is not being used.
On server schizo exist a number of domains for development testing (rather than use the Test Team’s a.vas, etc. To get there, go to schizo in the browser and download the VMware console. Then, click on the icon of one of these domains to get, variously, control of the management console or a VMware-console by which you can gain control in a separate window. After down-loading a console corresponding to the desired domain, launch it (from /usr/bin) via vmware-console. (It was necessary to run /usr/bin/vmware-config-console.pl to do almost nothing before this would work.)
# vmware-config-console.pl # vmware-console # the one downloaded from the schizo page
Download this console from VMware-console-2.5.2-16390.i386.rpm for use on SuSE 10. Right-click on this link, choose, Save link as..., etc. To install it, you use rpm, then a Perl script distributed with it (you can usually invoke it right from /tmp without going looking for it (it lives in /usr/bin/vmware-config-console.pl). Take the default when prompted.
# su Password: # cd /tmp # rpm -e VMware-console-2.5.2-16390.i386.rpm # vmware-config-console.pl # exit
The password for every domain and user associated with schizo is Test1234, however, launch vmware-console (above) with server name schizo and user/password russellb. See Seth for the nitty-gritty details (getting the VMware Console, which domains are available for use, etc.).
The steps are (this is not complete).
If you install AD to test with in a VMware server running on, say, Linux and it has its own domain, etc., to reach it, it will be necessary to modify /etc/resolv.conf, which leads potentially to failing to find services (web sites in Firefox, e-mail, other hosts, etc.) once this file has been touched. Also, you bump up against the time-out problem in that your host is frantically looking (in the wrong places) for things it cannot find.
The solution is “forwarding.” In your Windows 2003 Server, in the DNS management, you right-click on the domain container (root node) and choose Properties, then Forwarders and fill in your nameserver addresses. (Right click here and choose View Image to see the whole illustration.)