I understand that this is not supported and purely unofficial, but since I know how hard it is sometimes for to get new laptops in some countries, here's a bit of advice for MSP 3.3.1 that worked for me: * Create a WS2003 VM with 2 GB RAM (I run WS2003R2) * Install MSP 3.3.1 * Shrink VM RAM size to 512M, enjoy It still works, running IIS ASP, IIS FTP (2 relay servers), SQL 2008 with SASS (to work with MSP Data Collection) on the same VM on my HP8440p (Core i5). However, I tested it with up to 12 devices only. This may be fine for training and customer demo, but DEFINITELY not even for pilot. Hope it helps to those having older laptops. The VM distribution is tricky because of MS licensing requirements. When MSP officially was supported on XP it was easier, since Motorola has VLK license for XP. For newer versions of MSP you have to purchase linceses: * Windows Server 2003/2008 * SQL Server Standard if you need control I found that MSDN license (that can be purchased through TIGERS) works best as it gives you freedom to experiment with different software setups and costs less then retail SQL license (and you get all the other goodies too).

Thanks! Unfortunately I cannot test it, all I have is an old VMWare image for 3.2.1 in my PC... which cannot be upgraded to 3.3.1 since it only has 512 MB of RAM which cannot be increased without violating MS' 2003 server licencing. Does anyone know if there is a new VMWare image for 3.3.1 ?  thanks!

I don't think there is a prepared MSP 3.3.1 image that we have made available, but even if there was, it wouldn't run in 512MB of RAM.  So, if you can't update your current VM to MSP 3.3.1, then you can't run a VM we would prepare either.  You really need a better laptop if you plan to run MSP on it since MSP 4.0 will require even more, if you want to be able to do everything.  Plan on a minimum laptop that is 32 bit, dual core, with at least 3GB of RAM.  Even better would be 64 bit, dual core, and 4GB or better.  We do plan on providing a way for folks to run MSP 4.0 in a VM on their laptops, although we are still working out the logistics of licensing to make sure we are legal.  But we are targetting to make this available only to folks with a laptop that meets the above guidelines.  So, now is the time to start planning a laptop upgrade if this is something you will need to do.

JAM, IP Management can be turned off in Fusion options. In that case the IP address will be assinged by the OS. By default the OS configures the WLAN NIC to use DHCP but you could change that to static IP. All the information is stored in the registry in key HKLM\Comm\\Parms\Tcpip. Than you could use Staging Batches to assign Ip, Subnet, Gw by using SetRegistry object, etc. Be aware that you have at least MSP Agent/RdClient 7.02.38 or higher running on the device. Thomas

Dynamic Staging in MSP was made just for that. Use one Network Settings object, but make the Static IP field dynamic. We do a lab in MSP training just on that :) Basically, create a CSV file (look in MSP Docs for Staging Batch format description) with IP addresses and (optionall) device identity attributes (UUID/ESN/MAC/etc) if you want to assign specific IP addresses to specific devices. Then upload the staging batch and use dynamic staging with ths batch (barcodes/cradle). The whole thing takes about 10 min to set up once you are accustomed to it. See attached ZIP file with an example of what you need to do (courtesy Mike Hennel). Dynamic Deployment must be enabled (via MSP Admin program on MSP Server: View -> Configure -> Features -> Dynamic Content).