Iconics Genesis 32 Keygen Music
APP:EXCHANGE:EMSMDB32-DOS, APP: Microsoft Exchange EMSMDB32 Denial of Service. Denial of Service. FTP:DOS:GEN-GLOB-DOS, FTP: Globbing Denial of Service. Integer Overflow. HTTP:STC:ACTIVEX:ICONICS-WEBHM1, HTTP: ICONICS IcoSetServer Unsafe ActiveX Control1.
I am working with a vendor who is supplying a server-based application which requires licensing for activation. There are two options, software-based licensing and hardware (USB-dongle) based activation. What are the pros and cons to using hardware or software license keys in an environment where the application software is running on a VMware based server? The USB hardware license key will be plugged into one of these: There are two applications which are being licensed: Vendor: Iconics Software:GENESIS32 SCADA platform Vendor: Rockwell Automation Software: FactoryTalk (RSLinx) This is the reasoning the vendor gave for their preference for hardware keys: We have found that hardware keys are more stable than software keys, especially in a VM environment. Software keys are usually attached to the hard drive or NIC id of a computer. Any time this number changes (hard drive failure, VM reconfiguration, etc) the license is lost and needs to be reloaded with the help of the manufacturer. Today’s licensing is done over the internet, and most servers do not have internet access, so dealing with licensing issues has become a major headache.
Hardware keys work well for the VMs because they don’t reside on the VM. If you have an image failure or other server failure, you can copy in a new image, point to the license key, and you are up and running. The hardware keys add an extra point of failure.
I've seen them break. When they do break, you can't log into your card swipe system and give new people access to the building.
Sigh Always go software key if you have the choice. FlexLM (one of the more common license servers) for example is a real pain in the ass, but once it's up and running, you don't have to worry about it. With a hardware key, you have to worry about the key failing, the USBAnywhere failing, the USBAnywhere software failing, etc. Real Football 2012 Multiplayer 320x240 there. I've used those USBAnywhere devices and they've been pretty solid, but I'd still prefer software keys 10 out of 10 times.
Software keys are usually attached to the hard drive or NIC id of a computer. Any time this number changes (hard drive failure, VM reconfiguration, etc) the license is lost and needs to be reloaded with the help of the manufacturer. The NIC id of a computer (Also known as the MAC address) should not change in a VM environment. In addition, you can often assign the MAC address to match the MAC address within the license file. The MAC address can usually be fudged in the Operating system (I do it on Linux).
A license server which relies on a the hardcoded ID of a harddrive is asking for trouble-- Drive failures are inevitable, RAID arrays are common, and it's normal to replace drives time to time. It would seem that a USB dongle would be more prone to failure then just about anything else. We manage about 20 license servers, and all of them rely on the MAC address or a simpler mechanism. I realize your question is in a VMware environment but I think the general question is relevant to other virtualization platforms including Hyper-V. I recently virtualized an aging server that ran a service dependent upon hardware USB-based licensing keys and found that they do not work natively in a Hyper-V environment.
The Hyper-V Deployment Guide has this to say: No access to a physical COM port is available from a virtual machine. You can connect your virtual machine's COM port to named pipes but apparently not to actual serial ports.
Apparently this is primarily a debugging feature. You can provide access for a virtual machine to a serial port using a COM port re-director such as KernelPro's USB over Ethernet. Additionally the software and drivers for the licensing key need to support being installed on Window Server and in our case on Server Core if you want the licensing key to be installed on the host server. I ended up installing the licensing key and software on a workstation and then using it as that site's 'licensing server'.
This adds about ten different things that can now break this software. A software-based licensing key would of saved me much trouble and I suspect be a more reliable solution.
What is GENESIS32? GENESIS32™ is the industry’s first and only fully scalable suite of OPC, SNMP, BACnet and Web-enabled HMI and SCADA applications. The GENESIS32 Automation Suite is designed from the ground up to take advantage of the entire range of Microsoft Windows® operating systems, including Windows 7, providing reliable integration with the most popular communication infrastructures.
It delivers unparalleled ease-of-use, performance and cost savings due to its open standards-based design. The products listed below are components of the GENESIS32 Automation Suite: and - Multimedia OPC Alarm Management Software - OPC Data Aggregation, Bridging, Redundancy and Tunneling - Dazzling Animated Graphics for your HMI - Creation and Management of Visual Basic for Applications (VBA) 6.0 scripts - User and Group-level Security - Calendar-based Scheduling Tool - Enterprise-wide data collection, logging, charting, reporting and analysis system - Historical Plant and Business Data Replay - Web-based Real-time Automation Software. Features & Benefits One Development Tool for Multiple Targets Single-development tool for operator stations, servers, Web appliances, panels or over the Internet to wireless devices and Web browsers. Easy Configuration with Robust Workbench Application Service management is easy and reliable. Remotely start and stop any GENESIS64 Service.
Monitor Service health and get statistics for any service. Project Management Provides a centralized Web-based environment for GENESIS32 configuration and monitoring with Pack and Go capabilities for rapid deployment. Web-Based HMI/SCADA Visualization Connects to real-time and historical data through firewalls and integrates with standard Internet browser technology. Modular Suite of Data Tools Family of modular products for visualization, HMI and SCADA.
Multimedia OPC Alarming and Alert Notification Schedule and deliver alarms using voice-over IP, phones, E-mail, pagers, fax, text-to-speech, voice systems, Skype, Add-ons and marquees. OPC, SNMP, BACnet and Database Connectivity You are a click away from your data. Integrate with standards like OPC DA, OPC AE, OPC HDA, OPC Unified Architecture, SNMP and BACnet. One Development Tool for Multiple Targets The GENESIS32 development studio is certified for Microsoft Windows 7, Windows Server 2008 and Windows Vista operating systems.
Web-enabled applications run on Web browsers and Terminal Servers as well as dedicated wireless devices, Windows CE and Embedded devices. Easy Configuration with Robust Workbench Application WorkBench32™ provides a centralized Web-based environment for GENESIS32 system configuration and monitoring, enabling configuration via one workspace of GENESIS32 servers including: AlarmWorX32 Server, AlarmWorX32 Logger, TrendWorX32 Logger, Unified Data Manager, ScheduleWorX32, DataWorX32, Global Aliasing, Language Aliasing and the ICONICS Modbus (Serial) OPC Server. Additional server support will be added in future releases.