OPERATIONAL DEFECT DATABASE
...
...
HPE SimpliVity RapidDR Software installations may fail with an error message about failed license initialization or a missing PowerCLI component failure. When installing the HPE SimpliVity RapidDR Software on a system running Windows 8 (or later) or a system running Windows Server 2012 (or later), the license initialization may fail. When the initialization fails, a pop-up window will appear with the message, "License initialization is not done. Skipping operation." This issue occurs due to the User Access Control (UAC) permission settings in the Windows OS. The state of these settings changed starting with Windows 8, Windows Server 2012 (and later versions). The HPE SimpliVity RapidDR Software may also fail installation with the error message, "Please install PowerCLI 10.0 to install Rapid DR." This can occur even when the VMware PowerCLI version 10.0 is installed on the system if the environmental variable for the PowerShell path is missing.
Any HPE SimpliVity RapidDR Software.
License Initialization Failure The HPE SimpliVity RapidDR software can be installed by right-clicking the RapidDR icon and selecting Run as administrator. As an alternative, change the registry key, "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA", from 1 to 0 to enable the RapidDR software installation as an administrator without using the drop-down menu. Changing the registry requires a restart of the Windows system before the change takes effect. VMware PowerCLI 10.0 Missing If the VMware PowerCLI version 10.0 is not installed on the system hosting the SimpliVity RapidDR Software, install it. VMware PowerCLI downloads can be found at https://code.vmware.com/web/dp/tool/vmware-powercli/10.0.0 . If the system has VMware PowerCLI version 10.0 installed, verify that the PSModulePath environmental variable includes the path to the latest PowerShell module. 1. Right-click the Computer icon and select Properties. Alternately, open the Control Panel, click System and Security. On the next page, click System. 2. In the left navigation bar, click on Advanced system settings. 3. A System Properties window will pop-up. Click the Environmental Variables button near the bottom. 4. In the Environment Variables window, look for the PSModulePath variable under System variables. Verify that the value of this variable includes the path to the latest PowerShell modules. If the PSModulePath variable does not exist, click on New to create the variable with the path to the PowerShell modules. If the variable exists, but does not include the path to the latest PowerShell modules on the system, click Edit to add the path. Note : One or more of the links above will take you outside the Hewlett Packard Enterprise web site. HPE does not control and is not responsible for information outside of the HPE web site. NOTE: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form. NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document .
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
