Virtual Usb Hasp Dongle 11
Jemima Torguson
So, the big question would be... how on Earth can we link these hardware keys to our virtual machine?
And im not asking about configurations, I can easily figure out how to assign a USB port/ device to a VM..
With this sort of solution you can maintain the separation of the VM from the physical host and you can scale it out as big as you need. You can even test that this works before you virtualise by testing this on a server that you are currently using.
I think that you'll need a 1 x USB anywhere for each virtual server and I think that the minimum size USB anywhere has 4 ports... Obviousy you can have as many USB anwhere boxes as you need... just that each will need an IP address. For the flexibility that you getting they are reasonably priced.
We use Hyper-V on Server 2012 here. To connect all of our USB dongles(4 HASP License keys) to the virtual machines, I use a USB Hub and this software http:/ Opens a new window/www.usb-over-ethernet.com . I have tried other USB of Ethernet software and I like the one I mentioned the best.
Just be aware that this entire dongle thing will limit your DR functions. What do you do when recovering from a collapsed ceiling that buries your USB over IP equipment? You can recover the workload but if it doesn't see the dongle any more...
I don't see the big deal with tying the USB dongle to the physical machine, because of exactly what John just said, all you've done is moved the point of failure to another device. Further now you also have added the network as an additional layer of possible failure. Obviously it can be done either way I think they both have their merits though.
BMoore, did you buy the AnywhereUSB server?
If you did, can you please confirm if it works with Sentinel HASP HL dongle?
I bought a Lindy USB server, and so far have had no luck. I can see the USB device, and install the drivers, but the software does not see it.
-firewire-c4/usb-over-ip-c1509/4-port-usb-2-0-over-gigabit-ip-server-p1454
Opens a new window
The gist of it is to simply plug the dongle into a host, add a USB controller to the VM and then add a USB device. Since my security dongle was the only USB device in the farm it was the only option when adding the USB device. The software in question is not mission critical and is of no concern to DR plans.
Hello, I have a piece of software requiring a HASP USB license dongle connected to the virtual machine where it's running. I have a cluster with two ESXi 5.5 hosts, one dongle per host. Customer wants both USB dongles to be connected to the same vm, if one host fails, the second license dongle is available. so far so good, the USB device of the first host is connected to the vm with vmotion support. when I'm connecting the second one, I get the error "already connecting this device to virtual machine". dongles are identical but on different hosts, I don't get why the vm thinks it's the same one. if anyone has a suggestion would be very appreciated.
We are looking to provide hasp dongle licensing to multiple client customers offsite. We've done this in the past successfully via one Hyper-V guest and anywhere usb.. but they are all on the same dongle..
with hasp/sentinel.. if you do :1947 Opens a new window on the remote client which connects to the virtual server remotely.. it would be able to see all the hasp keys (take for instance if you had 5 hasp keys pointing at that vm on a single ip).. as a result this is a security issue.
Virtual USB dongles can be accessed on other remote PCs (client computers) as long as they are logged into the same Donglify account as the computer with a physically attached security key (server computer). In addition, you also need to install Donglify on the PC that your USB key is physically connected to and the machine from which you want to access it remotely.
I installed the Trial Version of Fusion three days ago - 1.1.1. Build 72241 on my MacBook Pro in Tiger. Installed Windows XP disc as the guest. Installed a Hasp Key Driver from Alladin and dongle into my USP port and program for Color Matters/Fashion Toolbox CAD, also VM Tools------no problem. Everything worked fine (after a year trying to make it work w/ Parallels). The next time I turned on Windows and launched Color Matters, I got "Illegal Hasp Key, Color Matters will shut down now" message. The same message I always got from Parallels.
I have the same program installed in a Windows Partition, that was set up when I first bought my Mac Book Pro. The same Color Matters/ Fashion Toolbox software and Hasp Key works fine in that OS. The Device Drivers are recognized and when I remove the dongle from the USB port, a little noise is made and an alert that a device has been removed. When I do the same thing is Windows using Fusion, it doesn't seem to recognize the dongle at all, although it is illuminated. I hate going back and forth between operating systems when I need to use my Windows OS only CAD program. From everything I have been reading, seems like I shouldn't have a problem using VMware but I do.
I've read this thread and some of the others regarding Aladdin Knowledge HASP problems. I installed VM Fusion 2.0.1 on an Intel Xeon Quad Mac in trial mode and it works great except that it won't recognize the Aladdin dongle (HASP 2.17) for a piece of software I use often. The dongle appears in the list of unconnected USB devices in the VM (Windows XP SP3) , but when I choose to connect it to the VM either in the Settings dialog or from the Windows Task Bar, the dongle LED blinks but doesn't connect.
I have a dongle which is read by another application on the Mac side. Using the Aladdin HL key software, I uninstalled the software on the Mac side. Once this was done, Leopard no longer recognizes the HASP dongle so that it can be captured by the virtual machine. Unfortunately, it means I can't use the Mac app and the Windows app simultaneously. I plan to keep looking for a "cleaner" method than constant installs and uninstalls.
After converting this VM machine on VM Infrastrukture ESX3i, the dongle is no longer seen by software. How should I configure VM machine settings to get access to USB port installed physically in server?
I have a USB ADC/DAC and a HASP protected proprietary data acquisition system for it, both of which do not work in linux. I am trying to make it work in Windows virtual machine using qemu.Here are the devices:
The problem is, both devices are showing in guest, but do not work. ADC/DAC should identify as a USB block drive, and is showing as one in device list, but doesn't work. I've installed HASP drivers for my dongle on the guest system, but the DAS software doesn't recognize it. What am I doing wrong?
Any proper virtual machine engine just asks you if you want the newly connected USB device should be assigned to the VM or to the Host.
Why make it so difficult to work? Same goes to adding a shared folder. next to impossible.
Too bad.
In addition on my host machine I have two USB license key plugged in. The problem is I'd like to be able to easily tell which of the virtual machines can have access to the USB license key. However my problem is that the first one that grabs it has the exclusive use of it.Since they are special USB key that are, as far as I'm aware, not mounted but rather just there I'm wondering how I could tell the virtual machine that currently has it to drop it.
Generic USB redirection feature allows redirection of arbitrary USB devices from client machines to XenDesktop virtual desktops. With this feature, the end users have the ability to interact with a wide selection of generic USB devices in their XenDesktop session as if it had been physical plugged into it.
Generic USB redirection works at a low level and redirect USB request and response message between client machines and XenDesktop virtual desktop. It avoids the requirement for compatible device drivers on the client machine and the driver is expected to be supported on the virtual desktop only.
When the user tries to redirect USB device to Virtual Desktop, it is checked against each USB policy rules in turn until a match is found. The first match for any devices is considered final. If the first match is an Allow rule, the matched device is allowed to be redirected to the virtual desktop. If the first match is a Deny rule, the matched device is only available in the local desktop.
Besides generic USB redirection, XenDesktop provides optimized redirection methods for some specific USB devices. Some advanced functions such as, data compression is provided by these dedicated virtual channels:
I have downloaded the drivers from the Thales website and the dongles light up but they are still not being recognized by Chief Architect after I put the CD key info in. I get the usual prompt to run the trouble shooter etc.
I would hope that someone here might be able to tell me, by going into the device manager and clicking on the dongles and then tell me what driver is being used by the system to get Chief Architect version 10 or 9.5 to run on Windows 7 or higher ?
e2b47a7662