VMware WSX 1.0.1, and the new Community Page

Last month, we released WSX 1.0. Those following along with the beta knew what to expect, as it was largely our latest Tech Preview release with some more fixes thrown in.

Unfortunately, we also threw in a regression that we’ve since been working to fix. The console would, at times, stop displaying anything, just appearing black. Clicking the little Refresh button would fix it, but it was annoying and, to me personally, quite embarrassing.

Today I’m happy to announce that we’ve released WSX 1.0.1, which has fixes for the black screen issue, and also support for Windows domains in usernames (indicated by “MYDOMAIN\username”) when logging in.

Along with the release, we’ve also introduced the new WSX Community Page, where you’ll be able to find the latest releases, documentation, and discussions on WSX. I’ll be on there, as will some of our QA, to answer questions.

13 thoughts on “VMware WSX 1.0.1, and the new Community Page”

  1. Pingback: vNews September 2012 – Stu McHugh & Steve Bruck | Stu McHugh's Virtualisation Blog

  2. Man, i am just stumped. I have a port forwarded on my router to my server with the correct port. I cant access my VMs from the “localhost:8888”, in fact it works marvelously.

    But when i try to connect from another computer on the network,, the connection is refused everytime.

    I also can remote desktop into the VM’s from outside my home or inside my home No problems.


  3. Hi.
    It seems that VMware WSX can’t recognize multi-byte characters.
    I can boot shared VMs via WSX Web interface, but nothing is displayed.
    Please solve this problem.
    Thanks. 🙂

    1. Can you post in the community forums and go into more detail on this problem? Multi-byte characters where? What browser/device? All the information you can provide would greatly help.

      1. Thank you for your reply.

        >Multi-byte characters where?
        file path or machine-name of shared VMs
        (e.g. C:\Shared VMs\[Multi-byte Char]\Example.vmx)

        >What browser/device?
        Firefox 16.0 on Windows 7 x64 Pro
        (and also checked in Chrome 22, IE10)

        >Can you post in the community forums and go into more detail on this problem?
        OK, I’m going to report in community this problem later. (I forgot my VMware’s account… ;-(

  4. Why would anyone run WSX now with the Vsphere web client out? Is there a difference? What are the pros/cons? We are looking at having custom code interact with our Vcenter server/API and are trying to find the best solution.

    1. There’s a difference. The vSphere web client requires VC and is intended for managing infrastructure. It won’t work with Workstation Shared VMs, or free ESXi servers without VC.

      WSX is more like Workstation/Player, in that it’s an end user client for working with individual VMs and not server infrastructure. It’s suited more for individual users or those with simpler setups.

      1. But WSX is supposed to work with free ESXi, right? That’s the impression I get from other sites, but it doesn’t appear to be the case.

        I recently built a new ESXi server (version 5.1.0-799733) and applied the license. I built a Ubuntu VM, and installed the WSX bundle.

        I could not get a console in any VM, just the progress indicator.

        I disabled the license, and reverted to evaluation mode. I can now get a console in any of my VMs.

        1. Yeah, there’s some bugs we’re trying to figure out. We haven’t managed to reproduce this issue, but we see it coming up a lot in real world testing.

          WSX right now is a very small thing with limited resources. We’ll get there.

  5. After upgrading from WS 9.0 & WSX 1.0 (on x64 “Windows 7”) to WS 9.0.1 & WSX 1.0.1, rebooting and testing, WSX failed to connect remotely (via LAN or WAN). Port 8888 was still defined in the (Windows) Firewall rules. Temporarily disabling the Firewall made everything OK. I concluded that this WAS a Firewall issue.

    This is the same situation described by “neil shelton” above.

    The SOLUTION (for me) was to uninstall WSX, delete the (Windows) Firewall entries, reboot, reinstall WSX, reboot and re-define the Firewall rules.

    I hope this helps someone.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top