Has anyone seen any issues with disabling File System Object (FSO) in CM 9.3?
Good day CM Experts,
I have searched Forum and Quixy as well as general Web-searches but have not seen an answer to this yet. As part of hardening my customer's servers I would like to disable the Scripting Runtime Library (for FSO) (regsvr32 scrrunrun.dll /u) but I want to make sure that it won't interfere with Content Manager's ability to work 'behind the scenes'.
Does anyone know if CM uses any calls to FSO for document storage or manipulation that disabling this will affect? I know that MIcro Focus HPOA installation vbscript file depends on it but we usually just re-enable the FSO then disable it once we are finished installation.