A scenario may be encountered when trying to install the CA Single Sign-On (SiteMinder) AdminUI on a non-default drive, (for exmaple E:\) the service fails to install and the AdminUI fails to start when manually run via batch script.
CA Single Sign-On (SiteMinder) r12.52
Windows Server 2012 R2
In this scenario, the user had enabled the 8dot3 name format on Microsoft Windows but noticed the problem persisting even after uninstalling and then reinstalling the CA Single Sign On (SSO) AdminUI.
Install problems can be encountered if the name conventions and file locations are not correct. For exmaple; if a "Program Files" folder had been created on the non-default drive before the 8dot3 name format was enabled, and the user was trying to use an install path using "Program Files (x86)".
1. Completely remove AdminUI (folders and registry);
2. Reboot the machine;
3. Run the following command from a Windows Command Prompt:
fsutil file setshortname <PathName> <shortname>
fsutil file setshortname "E:\Program Files" PROGRA~1
4. Test to ensure the short name is working as expected. For exmaple:
a. Open a Windows Command Prompt;
c. cd PROGRA~1
Note: You should now be in folder E:\Program Files
5) Install AdminUI again, pointing to drive E.
Executing fsutil -? at the command prompt will provide a full list of the supported commands.