Import the Certificates into the Keystore
I think from another post I read that when you upgrade the SSMC version this will over-write the certificate change and you will have to do this again, i have not tested this theory yet.
If you left the install path as default the below will work for you, yes you could get funky and put in path variables into windows but hey most people get lost in there too so I did this without it.
You have read through the most thorough of user guides supplied by HPE on how to do this but have got lost at a few parts, well i did maybe i am just thick…Īll the tools you need to complete this task are pretty well already on the server where you installed the SSMC software.
Once you save the permission in the policy, you may go into Services and start the HP 3PAR StoreServ Management Console Server service successfully.So you have installed the HPE 3PAR SSMC web management software onto a server and you now want to secure this with a signed SSL certificate. In the Local Security Policy, navigate to Security Settings > Local Policies > User Rights Assignments.ĭouble click Allow log on locally and add the. Choose the Local Security Policy item in the menu. To allow this, go to Start and then to Administrative Tools. This account needs to have “Allow log on locally” in the Local Security Policy on the server. The service attempts to use a local Windows account called hp3parssmcuser that is created during the installation. But if you want to keep a more locked-down policy in place, there is a workaround. A fresh build of Windows 2012 has the following settings in the Allow log on locally policy and with these settings it would work. Since we may not be the only company to make this change, I have included it. This is because we removed the Users group from the Allow log on locally policy in the computer’s Locally Security Policy as part of our standard server build. On my system, the service failed to start and gave an error after the installation completed. Once you login, you should see the Dashboard and from there, its time to start exploring SSMC. It would be the same account you used to login to the 3PAR Inform Management Console (IMC) - the old client. To login to the SSMC, you will use either a local account on the 3PAR arrays or using an LDAP account if your 3PAR arrays are configured and connected to LDAP. Uncheck the box for Administrator Console and you will get the normal SSMC login page. Once the arrays are connected, you may logout of the Administrator console and you will go back to the login page. Once the arrays are added, the SSMC begins the process of connecting the arrays to manage them. To connect your 3PARs, you use the Actions button to add the arrays. Once you login, you are presented with a Storage Systems view with no systems connected. The next step is to login to the Administrator console and connect the SSMC to your 3PAR arrays.
You click Set Credential button and save a password for the administrator account. On the SSMC server, you may browse to (if you chose the default TCP port during installation) and you will be presented a message saying that the Administrator credential is not set. If you have altered the Local Security Policy on your Windows system and removed the Users group from the Allow log on locally, you will get an error.
Once you finish the installation, the installer tries to start the service.