Category Archive

From the VMware blog:
“Workstation 6.0.1, ACE 2.0.1, and Player 2.0.1 have all been released. These updates address security issues, introduce new functionality, and broaden guest OS support, including experimental support for 32-bit and 64-bit Windows Server 2008 (code name Longhorn).In addition, Workstation 5.5.5, ACE 1.0.4, Player 1.0.5, and Server 1.0.4 have also been released. These updates address security and functionality issues.”

This is interesting because there are new versions of products to talk about, along with new features.

What really made US happy, was seeing that security is still a concern on older releases - specifically VMware Workstation 5.5 (now 5.5.5), which many developpers use to this day for many reasons.

Related Articles:

Since installing bbPress on the forum.blandname.com subdomain, I’ve become addicted to the rapid posting workflow: add topic, title, description and post! It’s 4 steps and is over so quick I’ve been thinking about making a bookmarklet that will automate the task for me. Here’s the latest smaller posts I sent there, but should some day expand upon here (I’ll use blandname for longer posts from now on):

• vTiger CRM Virtual Machine
• RDP Manager for your Windows System Tray
• HOWTO TrixBox - VoIP Virtual Machine
• Online Virtual Machine Builder
• Microsoft Distributes Demo Software via VHD
• FREE Terminal Server Monitoring Tool
• VMware Workstation 6 Feature List
• Multi monitor support for RDP 6
• Add Reflections to bbPress Images
• Google PageRank and Alexa in Your Firefox 2
• Display Digg in WordPress - Digg Dugg Plugin
• Google Analytics Plugn for bbPress

Related Articles:

In the coming weeks I will be working more on Microsoft’s Windows Vista as it ramps up to release to manufacture (RTM) status.

Although you can currently run Microsoft Virtual Server 2005 in 32 bit mode on a Windows Vista physical machine, I’ve learned that I was recently accepted into the Virtual PC 2007 beta tester program, and that Virtual PC 2007 can run on 64bit Vista.

If you are interested in joining the Virtual PC 2007 beta program, I highly suggest you sign up, then play some fantastic Rod Stewart albums until you are accepted.

By the way, this does in fact mean you can run Vista on Vista reliably now. VMWare Workstation and Server still don’t work at this point, but it’s on the way, just stay tuned.

Related Articles:

From the VMWare Converter 3 beta refresh release notes (found at virtualization.info):

VMware Converter provides an easy-to-use, scalable solution for migrations of machines, both physical to virtual and virtual to virtual. Optimized for mass migration, VMware Converter is equally effective for single-machine conversions. With its comprehensive and comprehensible wizards and task manager, VMware Converter imports virtual machines faster, with fewer manual steps required, and fewer source hardware limitations than other methods. Converter can, with its ability to hot clone, import with no downtime on the source physical machine.

VMware Converter combines and expands the functionality available in P2V Assistant and Virtual Machine Importer. It eases interoperability among VMware hosted products (Workstation, VMware Server, and VMware Player), VirtualCenter-managed ESX Server 3.x and 2.5.x, and unmanaged ESX Server 3.x.

Import from Physical Machines (Source)
VMware Converter can hot clone and reconfigure any local or remote physical machine running an operating system noted in Platforms VMware Converter Boot CD can be started from, and clone, local machines outfitted with storage controllers and network adapters that Microsoft lists as supported in Windows 2003

Import from Various Third-Party Formats and VMware Products (Source)

Microsoft Virtual PC (version 7 and higher) Microsoft Virtual Server (any version) Symantec Backup Exec System Recovery images1 VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x) VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x) VMware ESX Server 3.x VMware ESX Server 3.x (when managed by VirtualCenter 2.x) VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)

Export to a Virtual Machine for VMware Workstation and Datacenter Products (Destination)

VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)2 VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)3 VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x) VMware ESX Server 3.x (when managed by VirtualCenter 2.x) VMware ESX Server 3.x Not Supported: VMware ESX Server 2.5.x when managed by VirtualCenter 1.x VMware ESX Server 2.5.x unmanaged

1. The Symantec family of products includes the Backup Exec System Recovery (formerly LiveState Recovery) products and the Norton Ghost 9 (and higher) products. Only images from the Backup Exec System Recovery products are fully supported, but images from Norton Ghost 9 (and higher) are likely to work.

2. For ESX Server 2.5.x the .vmdk files must be imported using the vmkfstools utility.

3. Only Workstation 5.5 can power on linked imports of .sv2i images.

For more info please visit VMWare’s Converter 3 Beta Refresh page.

Related Articles:

SSH is one powerful tool. You can do just about everything under the sun using an SSH login to a remote computer. SSH works very well in low-bandwidth situations like dialup, or satlinks.

But wakeup, we’re no longer in the 80s - people want GUIs, let’s give them fancy-pants graphics, bouncing cursors and silly linux wizards. Remotely.

Enter Xming, what I would name as top of my favorite applications. Xming is just like X over SSH, for dummies (or people who would rather spend more time working).

Xming allows you to connect to remote or local Linux workstations and servers and run full graphical applications on those remote machines on your local Windows computer.

Here’s how it works: all of the applications are run remotely, but when it comes to the graphics, the information that would invoke the graphics is sent to your local computer, not a bitmap or a sequence of bitmaps like VNC. Xming uses a local X server on your Windows computer in order to display your remote applications. This local X server is 2D accelerated, and it’s sometimes difficult to even notice that you are working remotely.

Since Xming can run in windowed or full-screen modes, you can establish thin client connections in this fashion, or you can publish applications Citrix-style.

Xming is completely free to install and setup. It is a great way to manage virtual machines, and in fact is often faster than Microsoft’s Virtual Server ActiveX control (surprised?), VMWare’s Virtual Machine view (even with VMWare tools!), and even Parallels speedy virtual machine view.

To set the whole thing up, you’ll need a computer running Microsoft Windows, one Linux box, a network connection between the two, but you won’t need much effort.

First install the Windows Xming server on your Windows computer. We’ll use Windows XP SP2 in this example, but it could easily be other varieties. Xming can be found on Sourceforge quite easily, download it, run the install (use defaults), and start XLauncher.

On the Linux computer this are slighlty more complicated, but not by much. For Gnome or KDE on Ubuntu Edgy, go to the System>Administration menu in your menu bar. In Administration, we’ll select login preferences as we’ll be setting up a new logon method (we’re using XDMCP). Select the Remote tab, and enable remote logon (same as local) to your Edgy Eft machine.

Now on your Windows machine, set up XLaunch to logon to your Linux machine using it’s IP address. Save the setting if you want, and connect. You will be presented with a logon screen to your Linux desktop!

Related Articles:

This is a list of my favorite Windows applications that I honestly couldn’t live without that also work on Microsoft Windows Vista RC as well, much to my surprise. All of the software is free to download and use, and in fact most of them are open source.

ConTEXT - ConTEXT is a free and lightweight editor for programming or can be used as a notepad replacement. ConTEXT supports find and replace in multiple files at once so changing one method in loads of files is no longer an issue. Works in Vista with no problems whatsoever.

Synergy - Synergy is like a software KVM, but only shares keyboard and mouse capabilities. Synergy is multiplatform, and I currently use it to have my keyboard and mouse work in Ubuntu, Vista, and my Mac Mini running Leopard with no problem at all! This way I get to use my favorite keyboard and mouse and get to free up some space on my desk at the same time.

VLC - VLC has been my favorite media player for years now. VLC comes with most of the codecs you will need to watch videos on your PC already. VLC is very lightweight, and JUST WORKS, something that can’t be said about many media players. The only issue with VLC in Vista is that it turns Aero Glass off while it is playing.

FileZilla - I use FileZilla to interface with clients that still haven’t moved to SCP. FileZilla is an open source FTP client that gets the job done, supporting drag and drop, SSL, and NAT to NAT connections. The only thing it is missing is FXP support, but that’s not really a big deal in my case. Works fine in Vista with no problems at all.

IMGBurn - I love IMGBurn. This is hands-down the easiest way to burn .IMG, .ISO and BIN/CUE disk images to backup CDs or DVDs. Free, open source, and awesome. Works a treat in Microsoft Vista Beta 2 as well.

WinSnap - I use WinSnap to make many of the screen shots you see on blandname. WinSnap supports full screen and windowed screen shots, and also allows for rotation and drop shadows if you feel the need.

Electric Sheep - I often refer to Electric Sheep as “the best screensaver ever”, but truth be told, it’s really a collection of computer-generated screensavers that allow users to vote on them using a Digg-like system. On Windows, Electric Sheep uses bit torrent to transfer the sheep data. Again, working just fine in Vista!

Xming - Xming is my prefered interface to remote Linux boxes. Xming is for Linux what RDP is for Windows - you get a local X server and acceleration that displays data from remote applications running on Linux machines. Tested more than a few times to a remote Ubuntu computer, and one Gentoo box with no caveats.

WinSCP3 - SCP is now my preferred file transfer method. Luckily my favorite client also works on Vista, or I may not have used it at all. Much like FileZilla, WinSCP3 has a very simple, streamlined interface that is feature-rich and gets the job done, even on Vista.

So there you have it: 9 free applications I couldn’t live without that work just fine on Vista, and make it easy for me to do my day-to-day tasks. Hopefully someday this list will include F-Spot and Amarok, but I’m happy with this as a start considering neither of them work on Windows XP SP2 either!

Related Articles:

Parallels announced today the updated features of the newest iteration of Parallels Workstation.

Big new all around for Windows, Mac and Linux users.

Here’s the breakdown (from the newsletter):

Parallels Desktop for Mac is the first solution for running Windows and OS X at the same time – without rebooting!

The Desktop for Mac Official Update includes a number of powerful new features, such as:

• Works on ANY Intel-Mac with ANY memory configuration with no system modification. This includes Mac Pro towers with up to 16GB of RAM, and the full line of Core 2 Duo iMacs
• Support for Windows Vista as a guest OS
• Support for Mac OS X 10.5 “Leopard” as a Primary OS
• Better USB support, including support for isochronous devices and Windows Mobile 5 devices

Parallels Workstation 2.2 for Windows & Linux is a powerful, cost effective virtualization solution which boosts productivity and lowers IT costs by letting users run multiple OSes simultaneously - without rebooting - on any Windows or Linux PC.

The new version includes a variety of new features and improvements:

• Full support for AMD Secure Virtual Machine Technology, and stronger support for Intel Virtualization Technology
• Support for Windows Vista as a Guest OS
• A new shared folder utility lets users share files and folders between OSes
• Better networking
• Better USB support, including support for webcams and Windows Mobile 5 devices

Related Articles:

If you’re like me, you have many computers that you connect to remotely when away from work, or home, using RDP.

The easiest way to connect to all of these computers (aside from setting up a VPN) is to change the default port on which Windows will accept RDP connections.

Since things have changed a bit in Microsoft Windows Vista, here is how to change that port:
Click on the Start button, and navigate to accessories. From there, clik on the Run icon. Once the Run applet has started, we’ll enter the good ole regedit command. It still works like a charm!

Within the registry editor, navigate to:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\
Terminal Server\WinStations\EH-Tcp

We want to change the registry key PortNumber in order to modify the default port. The default port is 3390, and I normally use ports in the 338x range, so double click on the key, check the decimal setting, the set the “Value data” to 3389.

Click OK, then close Regedit, and connect from a remote PC.

Note: you may want to create a firewall rule for port 3389 in order to allow connections.

Related Articles:

Here are screenshots from the upcoming Micorosoft RDP 6 client for Windows (Vista and XP), and explanations for each feature so that you can get started with your testing now and stay ahead of the game.

The options screen to the new RDP 6 client is very similar to that in version 5, but as you can see, it does not have input regions for login name and password. This is now done when you connect, and yes it can still be stored. Also note that just like in previous versions, if you would like to save the settings you will need to return to this tab as Microsoft still seems to think that saving options should not be done from all tabs for some reason. If you would like to make the options that you changed or reconfigured global, you would save the file as default.rdp in your “My Documents” folder. In Vista this is simply called “Documents” to make things easier. Yes, they have gotten rid of the “My” prefix now.

We have all of three options here: Remote Desktop Size, Colors and the Option to diplay the connection bar when in full screen mode. Remote desktop size: whether you want to display your remote desktop connection in full screen mode or not. This does work fer very large monitors, including those widescreen suckers. It will scale down to many other sizes depending on what you maximum resolution is. The amount of colors has now increased to 32bit in the newest version of the Remote Desktop Connection 6 client (RDP 6). This means getting accurate color from applications such as Adobe Photoshop is much easier now, though you will still need to do proper calibration.

The local resources tab controls the way your remote computer or terminal connects to your Longhorn or Windows 2003 R2 Terminal Server. For sound, you have the option to play sound locally, to leave the sound on the remote computer (host) or to ignore sound completely. I have noticed that the sound quality seems tobe much better in the new RDP client, but that it depends on the connection you are using. For example when using a Wifi-B connection, the sound quality appeared to be roughly the same as the previous client iteration. When I then connected the laptop to a wired (LAN) connection, the difference was apparent when switching back and forth between RDP 5 and RDP 6. I should probably be more precise here - what I mean by sound quality appears to affect times when multiple sounds play at once, as well as when sound are triggered by alerts or login notifications, the sounds appear to play faster, having less latency than in the RDP 5 client.

The keyboard menu here allows you to specify whether actions such as alt-tab will always be recognized by the remote computer even when in windowed mode, or if the host should accept them - the host being your computer in this case. I think the default is fine for most people - meaning keep it set to only accept these commands when in full-screen mode.

Local Devices and Resources: RDC 6 supports using local devices will logged into a remote computer provided that the proper driver exists on the remote host. Microsoft will be writing generic drivers for many devices, and currently things like smart cards, serial ports and hard drives are already supported, but the list will be growing.

The programs tab allows you to specify applications to run on connection to a remote host. You can specify the path of the application to run, as well as input information regarding the folder to start the program in.

The experience tab allows you to tweak the connection settings in order to get a less latent (slow updating) connection to your remote host. When people complain about this to me it typically involves things like typing speed not being fast enough in RDP sessions, and screen refreshes being very slow. If you are using a connection to a remote computer in a local network that runs at 100mbit or up, I have found that you can safely have all of the experience options turned on. On a wireless B connection (11mbps), you may want to turn all of the settings off. If you are connecting remotely, I would highly recommend turning all of them off.

There is also an option on the screen that has always looked out of place to me - and I think it should be on the general page as it seems to be a general option. At any rate, you can also specify whether or not to reconnection after your connection is dropped by checking this checkbox. I typically have this checked.

Lastly, we have the advanced tab, which allows you to set so-called “advanced” options. Basically this involves two things.

The first is server authentication. This allows you to confirm if you are connecting to the proper remote computer. In practice, I have found that this simply does not work in Windows XP, and now have it set to not warn me if the authentication fails, because it will always fail, without a doubt. If you use Vista or Windows Server Codename Longhorn, this does in fact work, so you can leave it set to default (”Warn me if authentication fails”).

The second option dubbed “Connect from anywhere” only works with gateway servers, like the new Terminal Services in Longhorn. At this point, you are unable to use the function on Windows XP. You are able to turn it on in Windows Vista, and can play with the settings provided you have a Terminal Services Gateway Server in your network.

Related Articles:

Here is my collection of all of the Windows XP commands that you can start from the Start -> Run dialog box in order to manage a Windows XP (SP2) workstation.

1. Accessibility Controls - access.cpl
2. Accessibility Wizard - accwiz
3. Add Hardware Wizard - hdwwiz.cpl
4. Add/Remove Programs - appwiz.cpl
5. Administrative Tools - control admintools
6. Automatic Updates - wuaucpl.cpl
7. Bluetooth Transfer Wizard - fsquirt
8. Certificate Manager - certmgr.msc
9. Character Map - charmap
10. Check Disk Utility - chkdsk
11. Clipboard Viewer - clipbrd
12. Command Prompt - cmd
13. Component Services - dcomcnfg
14. Computer Management - compmgmt.msc
15. Control Panel - control
16. Date and Time Properties - timedate.cpl
17. DDE Shares - ddeshare
18. Device Manager - devmgmt.msc
19. Direct X Troubleshooter - dxdiag
20. Disk Cleanup Utility - cleanmgr
21. Disk Defragment - dfrg.msc
22. Disk Management - diskmgmt.msc
23. Disk Partition Manager - diskpart
24. Display Properties - desk.cpl
25. Dr. Watson System Troubleshooting Utility - drwtsn32
26. Driver Verifier Utility - verifier
27. Event Viewer - eventvwr.msc
28. Files and Settings Transfer Tool - migwiz
29. File Signature Verification Tool - sigverif
30. Findfast - findfast.cpl
31. Folders Properties - control folders
32. Fonts - control fonts
33. Game Controllers - joy.cpl
34. Group Policy Editor - gpedit.msc
35. Help and Support - helpctr
36. HyperTerminal - hypertrm
37. Iexpress Wizard - iexpress
38. Indexing Service - ciadv.msc
39. Internet Connection Wizard - icwconn1
40. Internet Explorer - iexplore
41. Internet Properties - inetcpl.cpl
42. Keyboard Properties - control keyboard
43. Local Security Settings - secpol.msc
44. Local Users and Groups - lusrmgr.msc
45. Logoff Windows - logoff
46. Malicious Software Removal Tool - mrt
47. Microsoft Chat - winchat
48. Microsoft Syncronization Tool - mobsync
49. Mouse Properties - control mouse
50. Netmeeting - conf
51. Network Connections - control netconnections
52. Network Connections - ncpa.cpl
53. Network Setup Wizard - netsetup.cpl
54. Object Packager - packager
55. ODBC Data Source Administrator - odbccp32.cpl
56. On Screen Keyboard - osk
57. Outlook Express - msimn
58. Password Properties - password.cpl
59. Performance Monitor - perfmon
60. Phone and Modem Options - telephon.cpl
61. Power Configuration - powercfg.cpl
62. Printers and Faxes - control printers
63. Regional Settings - intl.cpl
64. Registry Editor - regedit32
65. Remote Access Phonebook - rasphone
66. Remote Desktop - mstsc
67. Removable Storage - ntmsmgr.msc
68. Removable Storage Operator Requests - ntmsoprq.msc
69. Resultant Set of Policy - rsop.msc
70. Scanners and Cameras - sticpl.cpl
71. Scheduled Tasks - control schedtasks
72. Security Center - wscui.cpl
73. Services - services.msc
74. Shared Folders - fsmgmt.msc
75. Shutdown Windows - shutdown
76. Sounds and Audio - mmsys.cpl
77. SQL Client Configuration - cliconfg
78. System Configuration Editor - sysedit
79. System Configuration Utility - msconfig
80. System Information - msinfo32
81. System Properties - sysdm.cpl
82. Task Manager - taskmgr
83. TCP Tester - tcptest
84. Telnet Client - telnet
85. User Account Management - nusrmgr.cpl
86. Utility Manager - utilman
87. Windows Address Book - wab
88. Windows Address Book Import Utility - wabmig
89. Windows Explorer - explorer
90. Windows Firewall - firewall.cpl
91. Windows Management Infrastructure - wmimgmt.msc
92. Windows System Security Tool - syskey
93. Windows Update - wupdmgr
94. Windows Version - winver

Also to note: any executables found in PATH folders, for example “Program Files” can also be run from the Start -> Run dialog as well. This means to start VMWare Sever, you can type in “vmware” and it will start for you!

Related Articles:

This hack will allow you to connect multiple time to your Microsoft Windows XP machine using an RDP client coming from a Mac, Linux, or another PC like a real Terminal Server, or a Windows Server running Citrix.

In detail, this hack patches many pieces of Windows XP in order to allow the same Terminal Services functionality that you find in Microsoft Windows Terminal Server, but without the licensing costs. The stability of the hack has not been verified, but the virtual machine used has been running for over a week now with 20 conenctions to it and has yet to fail once.

In order to perform the hack you will need one external file, some guts, and a backup. The backup is extremely important. I highly recommend that you test the procedure using virtualisation technoloy like Parallels, Virtual Server (free), or VMWare Server (also free). You have no excuse to procede without a backup - consider yourselves warned.

Let’s begin.

The file needed for the hack is actually a combination of some registry tweaks and DLL/EXE patches made by “antiwpa”. antiwpa is known for dealing with another Windows XP issue that we won’t get into here - I’m sure you can guess what it is easily.

No that you have the file, and backup, we’ll extract it and start the install process. It’s quite simple - you double-click on the application, it starts a command line window, you press a key and the patch commences. Eventually the command line portion will end and you will get a Windows warning regarding system files having been replaced - we’ll cancel the restore “feature”, and let Microsoft know that we are running untested code by pressing the “yes” button on the next window.

A second patcher launches with full GUI this time. We click on the “patch” button and we are finished. Easy huh?

Moving on… If you try to connect to the XP machine now, you will notice that the maximum number of connections has been reached. This is easy enough to fix, but it’s readily apparent where we need to go. Click on Start, then Run, and type in:

gpedit.msc

Once the Group Policy Editor has opened, navigate to “Computer Configuration”, “Administrative Templates”, then “Terminal Services”.

In the “Terminal Services” tree, you’ll see a policy named “Limit number of connections”. Double-click on this policy. Set the policy to enabled, and adjust the maximum connections to suit your need. I recommend trying “2″ to start off with.

Now reboot your machine, and attempt to connect the amount of times you have specified. If you need mre connections, navigate back to the policy editor and set the maximum amount higher.

Once you have completed your testing, back the machine up once more for good measure. If you don’t have disk imaging software, I’d recommend using the open source g4u - otherwise commercial applications such as Symantec Ghost will work.

Moving on, if you feel the need to manage the users (log them off, control sessions) like on a real Terminal Server, you can grab a copy of the “tsadmin.exe” file from a Windows Server 2003 machine’s “SYSTEM32″ folder and copy to the Windows XP machine’s SYSTEM32 folder. Running TSAdmin is as easy as clicking on Start, Run, then typing tsadmin, but you might also want to make a shortcut to the file for good measure.

Related Articles:

I’ve been using Parallels Workstation on my beefy Windows test host alongside VMWare Server and Windows Virtual Server. Parallels, though a relatively new piece of software, is remarkably good.

Recently I received an email about the new Apple Mac version which adds a lot of features that have me very excited. I have been debating a MacBook Pro purchase, and this announcement just may be the tipping point.

So let’s hear them out on this spam, and have a look at why I’m so excited.

Big features to mention:

• Support for new quad-processor Mac Pro towers outfitted with up to 3.5GB of RAM

• This addition means that Parallels Desktop for Mac is now compatible with all Intel-powered Apple computers, which in addition to the Mac Pro includes the MacBook, MacBook Pro, iMac, and Mac Mini!

• Compatibility with developer build of Mac OS X 10.5, code-named “Leopard”

• Experimental support for Windows Vista

Bugs Fixed:

• Solaris guest OS no longer hangs after suspend/resume

• An improved Parallels Tools package

• Full support for OpenBSD 3.8 as a guest operating system

• G4U hard disk cloning tool now works in virtual machines

The new Parallels release candidate adds many exciting features including (but not limited to):

• USB improvements — easily use multi interfaced and isochronous USB devices (including Windows Mobile 2005 and webcams)

• Mac OS X performance improvements — optimize Mac OS X or guest OS performance by switching off the Mac cache function

• Graphic performance improvements — enjoy faster, smoother video playback

• Keyboard support improvements — use all of the keys on your Mac keyboard, such as the eject CD button, right-left and Shift/Ctrl/Alt (option)/Windows keys, in any virtual machine

• Unicode path support improvements — name files and paths in national languages

• Shared folders performance improvements — open folders and files faster, and transfer data across OSes with almost zero lag

Related Articles:

I have recently purchased Parallels Compressor Server because I work with virtual machines on a daily basis and also because it is CHEAP. At $179 this is very affordable software, even for someone on a budget - like me. Why purchase the software? What Parallels Compressor Server does is pretty complicated, but it comes down to one thing: if you run a Windows XP SP2 or Server 2003 R2 virtual machine (VM), Parallels Compressor Server speeds it up insanely. It removes unwanted services, temp files, files you’ll never need in a VM, and the same goes for drivers. Parallels also tunes things like network drivers in order to take full advantage of the virtualization.

Installation is a snap. It’s pretty much next, next, next through the Windows client installation. You enter your key, and are allowed to make a CDROM image for later use with the VM. Use you have finished, you boot the VM using the CD image and start the process (which can take some time). Parallels Compressor Server does it’s magic, and you reboot. HUZZAH! Faster VM just like that.

Conclusion - you may run a free virtualization platform - but how fast is it? For $179, Parallels Compressor Server is a steal.

No disclaimers needed - I am in no way affiliated with the software, I’m just that impressed.

Related Articles:

Checkout the Media Player toolbar in this shot - is Microsoft hiring suspicious characters now?

Related Articles: