After a new installation of SAS® 9.3 is installed on a machine, the shared-files directory is no longer created. (A "new" installation of SAS means that no previous SAS versions had been installed on the machine.) Instead, each product is installed in a directory of its own under the SASHOME directory. Here is an example:
C:\Program Files\SASHome\ReportFontsforClients\9.3
However, the JMP stand-alone installer, which is performed outside of the SAS® Deployment Wizard, creates an empty SharedFiles folder:
C:\Program Files\SAS\SharedFiles
This behavior occurs under both 32-bit and x64 operating systems.
After using the JMP stand-alone installer, do not be concerned that a shared-files subdirectory was created and that it is empty. You would not see a populated subdirectory unless a previous version of SAS was installed on the operating system.
See SAS Note 32578 for more details about the shared-files directory locations for SAS® 8.2, SAS® 9.1, SAS® 9.2, and SAS® 9.3.
Note: The JMP stand-alone installer uses older InstallShield technology that creates the shared-file directories. The SAS Deployment Wizard uses newer Java technology and does not create the shared-files directory.
[Previously JMP Note 44170]