So the issue has been identified. EMC support spent a day troubleshooting with me, I called in and had it re-qued this morning and Nicholas Owens knew exactly what to do. Implementing a shorter install path worked right away.  Thank you EMC support Owen, Nicholas From the latest logs, it appears the issue is caused by the Windows short names not translating correctly after 7 characters - this only occurs on non-default install directories.  Here is the log evidence, we can see that it is not recognizing anything after the 7th character in 'Program Files':  2017-04-21 12:46:04,322 INFO  [com.emc.em.deployer.ServerManagerService] (EJB default - 1) ServerManagerService.getLine(): 'F:\Program' is not recognized as an internal or external command, 2017-04-21 12:46:04,322 INFO  [com.emc.em.deployer.ServerManagerService] (EJB default - 1) ServerManagerService.getLine(): operable program or batch file.  You will need to uninstall the current instance of Unisphere for VMAX, and install it to a new directory (under 7 characters) - example: F:\EMC\
UNIVMAX_V8.3.0.6_WINDOWS_X86_64   Error message Received during install:   CST Configuration Error. Installation will be aborted   log4j:WARN No appenders could be found for logger (org.hibernate.cfg.annotations.Version).   log4j:WARN Please initialize the log4j system properly.   java.lang.Exception: CST initialization failed: Opening the Lockbox failed because of inconsistent policy settings between the Lockbox library and the Lockbox file.   at com.emc.em.common.security.cst.AMSCallback.initCST(AMSCallback.java:338)   at com.emcem.common.security.cstAMSCallbackBase.mainlmpl(AMSCallbackBase.java:480)   at com.emc.em.common.security.cst.AMSCallback.main(AMSCallback.java:85)   at com.emc.em.common.security.cst.AMSCallbackMain.main(AMSCallbackMain.java:10)   Does anyone have any insight on what to do here. I have a good idea, I am just looking for confirmation before applying any changes to my server.
Unisphere for VMAX installation issues