Blancco related license issues might not always be related the software (Blancco 5, Blancco Drive Eraser, Blancco Mobile Device Eraser, Blancco LUN Eraser, Management Console, etc.). The HASP USB dongle can also be the source of the problem. Before contacting the Blancco Technical Support team, do the following:
virtual usb hasp dongle 11
A virtual dongle refers to a software program intended to virtualize the security dongle key. The virtual version of a dongle permits access to programs that use dongles, eliminating the need for a physical hardware key for the required program.
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.
Didn't see any hacks in that link. I've checked quite a few forums & threads all with the same problem but no one seems to have a solution. I'll try those other virtual PC programs.Besides my PCIe parallel port, I also have a parallel to USB adapter. My next idea is to learn how to maybe try and forward/assign/link the LPT1 port in XP Mode to the USB adapter. Seem doable and if so, any references anyone can point me to would be appreciated.
For CimLM NLO to serve licenses on a virtual server, keyed licensing (i.e., with a USB hardware dongle) is required. If you have questions or problems regarding hardware keys themselves, see "How do I resolve an issue with a hardware key?" above or "What kind of hardware key do I have?" above.
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.
Protected application is running on a virtual machine, but one or more Features are not enabled for virtual machines.ORThe user attempted to rehost a protection key from a physical machine to a virtual machine. However, none of the Features contained in the protection key are enabled for virtual machines.
One of the significant disadvantages of Hyper-V over other hypervisors (for example, VMWare ESXi or Proxmox) is the lack of a feature of redirecting USB devices from the host to virtual machines. Since version Hyper-V 2012 R2, there have been a number of changes regarding USB Passthrough options, but this functionality is still inferior to those of competitors. In this article, we will discuss the specifics of USB redirection in Hyper-V. (adsbygoogle = window.adsbygoogle []).push();
To safely remove the USB drive, you can open the Hyper-V Manager console and go to the virtual machine settings window. In the SCSI Controller section, select the hard drive you want to remove and click Remove. Save your changes. After that, you can physically remove the hard drive from the USB port of the Hyper-V host.
In the version of Hyper-V introduced in Windows Server 2012 R2/8.1, any USB device can be forwarded to a virtual machine from a client computer using Enhanced Session Mode (ESM). The Hyper-V Manager tool vmconnect.exe is used to connect. It allows you to connect to the virtual machine console and select the USB devices you want to redirect.
In order to redirect the USB device through Enhanced Session Mode, you need to open the Hyper-V console, select the virtual machine, and click the Connect button. Or you can run the vmconnect.exe tool (Virtual Machine Connection), specify the Hyper-V server and the virtual machine name. The vmconnect tool supports some command line options, so you can give a customized bat file with the options you want to users.
If you are redirecting USB devices over the network (USB over IP or over an RDP session), you can still access the USB key even after migrating the virtual machine to another host (Hyper-V Live Migration / vMotion).
VirtualBox USB passthrough can be implemented but only partially solves the problem. This technique only enables VirtualBox users to connect to security dongles attached to the host computer. We will now discuss two different methods of enabling VirtualBox USB device capture to access a security key: on the fly or with a filter.
A common misconception is that USB devices are easily used in virtual environments. Getting the host and guest operating systems to play together nicely requires navigating multiple software layers to eventually communicate with the drivers controlling the hardware resources.
Using a USB filter is the second method of capturing a USB device in VirtualBox. Capturing with a filter is considered to usually be more effective and reliable than the on-the-fly technique. Using a filter, a VM that is up and running can immediately capture a dongle connected to the host OS. Filters work best if each device has an individual filter.
When using virtual machines, the principle of hardware virtualization is used and hypervisor software emulates devices used by VMs on the software level. Virtual controllers, disks, DVD-ROM, video card, network cards, input devices, and other devices are usually created in a virtual machine. Sometimes you may need to connect a physical device to a virtual machine directly. This device can be a printer, scanner, USB flash drive, USB hard disk drive, USB smart card reader, security dongles, USB license keys, etc. If your external physical device has the USB interface, you can attach this device to a virtual machine running on VMware Workstation and ESXi server. VMware allows you to connect USB devices to virtual machines by using the USB passthrough feature (passing the device through). This blog post explains how to use this feature on ESXi hosts in VMware vSphere.
VMware USB device passthrough is a feature that allows you to connect a physical USB device attached to a USB port of a physical ESXi server to a virtual machine as if the USB device was connected to a virtual machine directly. VMware passthrough is a feature available starting with ESXi 4.1.
The arbitrator is a dedicated service on an ESXi server. The arbitrator scans physical USB devices attached to the physical server and is responsible for USB device traffic routing between a physical host and a virtual machine. Only one VM can access the USB device at a time. Access to the USB device connected to one VM is blocked for other VMs. The USB arbitrator supports up to 15 USB controllers (vSphere 7.0). The Arbitrator service is enabled on ESXi by default.
A virtual USB controller is an emulated device created especially for a virtual machine running on a hypervisor. A virtual USB controller interacts with a physical USB controller when you passthrough a physical USB device from a physical ESXi server to a guest OS on the VM. Presence of a virtual USB controller in VM configuration is required to use the USB passthrough feature on the VM. A maximum of eight virtual USB controllers can be connected to a VM on an ESXi host. If you need to remove a virtual USB controller from a VM configuration, you have to remove all USB devices connected to that controller first. VMware USB driver is installed in a guest OS after adding a virtual USB controller to VM configuration.
As for creating a VMware virtual USB drive or virtual flash drive for attaching to a virtual machine running on ESXi or VMware Workstation, just like you would mount a virtual floppy disk or CD/DVD disc, currently this option is not possible.
The VM is residing on the ESXi host that is managed by vCenter Server in my example. Windows is installed as a guest OS on my VM. Open VMware vSphere Client, go to Hosts and Clusters. In the Navigator pane select a virtual machine to which you want to connect the USB device by using the passthrough feature. The VM should be in the powered-off state. You should install VMware Tools in the guest OS. 2ff7e9595c
Comments