This is basically the same as a regular install, with the addition of step 3. The extra libraries are for vmware-config.pl, and xinetd is required anyways.
Step 1: Download VMWare Server
wget VMware-server-1.0.3-44356.i386.rpm
Step 2: Install vmware server
rpm -ivh VMware-server-1.0.3-44356.i386.rpm
Step 3: Install required files / libraries
yum install libXtst-devel libXrender-devel xinetd
Step #4: Configure VMWARE server
vmware-config.pl
A quick registry fix revealed here shows how to increase the POP3 email retrieval speed on Small Business Server 2003. Yes, having SMTP mail delivered directly to the server is better, but first things first!
1. Locate and then click the following registry subkey:
“HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/SmallBusinessServer/Network/POP3 Connector”2. On the “Edit” menu, point to “New”, and then click “DWORD Value”.
3. Type “ScheduleAccelerator” as the entry name, and then press ENTER.
5. On the “Edit” menu, click “Modify”.
6. In the “Value data” box, type the value that you want, and then click “OK”. To determine the polling interval, the value that is configured on the “Scheduling” tab in the GUI is divided by the value that you type for the ScheduleAccelerator entry. For example, if a 15 minute interval is specified in the GUI and you set the value of the ScheduleAccelerator entry to 3, the connector will poll every five minutes.
7. Quit Registry Editor and restart the “Microsoft Connector for POP3 Mailboxes” service.
Note: I’m not entirely convinced that the “[GUI Interval]/[ScheduleAccelerator]=[Minutes]” theory is correct. With the server set at 15/5, I should get polling every 3 minutes, but it seems to be more like 45 seconds. With it set at 15/3, I am getting mixed results between 30 seconds and 5 minutes. I guess that’s good enough for government work; YMMV.
Thanks to Scott Forsyth, I found a way to disconnect remote desktop sessions when you are unable to connect to the server via RDP… Apparently qwinsta and rwinsta are built-in to Windows (XP Pro at least).
Scott said:
qwinsta /server:12.12.12.12
Where 12.12.12.12 is the IP address or name of the non-accessible machine.
This will display something like this:
> qwinsta /server:12.12.12.12
SESSIONNAME USERNAME ID STATE TYPE DEVICE
console 0 Conn wdcon
rdp-tcp 65536 Listen rdpwd
rdp-tcp#470 Bob 1 Active rdpwd
rdp-tcp#471 Jane 3 Active rdpwdNow I know that Bob and Jane are the two that are logged in. Since Jane left the office 20 minutes ago I know that she forgot to log off. I don’t know where Bob is but I only need one session so I’ll ignore him for now.
To disconnect Jane’s session I would type this:
rwinsta /server:12.12.12.12 3
Notice the 3 which is the session ID I found from using qwinsta above.
Step 1: Purchase Buffalo Airstation WHR-G54S.
Step 2: Flash with dd-wrt.v24_std_generic.bin dated July 16 2007 using TFTP.
Step 3: Perform SD/MMC Card Modification to add some flash storage. Completely ignore section where you determine where the solder points are, and just get soldering. Also ignore the section about SD card adapters and solder your wires directly to the card. All you need is about 30k of storage space for the AutoAP script, so any crappy old card will do.
Step 4: SCP autoap_test_2007-07-16beta.sh to the new /mmc directory on your router, rename autoap_test_2007-07-16beta.sh to autoap.sh, and chmod 755 autoap.sh.
Step 5: Add “/mmc/autoap.sh &” to the startup section in the DD-WRT administration pages.
Step 6: Drive around and see if it works. Look at http://X.Y.Z.1/user/autoap.htm to see what the script is doing.
Here are some scans of my completed board so you can see the solder points a bit better…
The issue in webmail where your Identities and personal settings are not being saved has been fixed. (On my server, anyways.)
Thanks once again to HowToForge and the people there with way too much free time.