Hi all! Hoping someone might be able to shed some light on this: We recently updated our stand-alone Adobe CF servers from 2018 to 2021 and noticed that a site on the new server, the CF code is looking for the built-in javascript packages for the CF-based UI elements in

/cfscripts_2021_870314/

instead of

/cf_scripts/

or

/cfscripts/

. Re-running the connector doesn't seem to resolve the issue (e.g. doesn't create the expected vitual directory (IIS). We can of course create an alias manually to match the expected pattern, but would be extremely wary that the next update would break this approach if the cfscripts mapping is now version-tagged. Has anyone encountered this and knows what the action item should be here?

there's a setting in the admin for the script path, i assume it's where that version path is coming from?

@s1deburn - Thanks for that! A member of our team actually tracked down the root cause - the CF lockdown tool actually will set that setting to a randomized value (from the default

/cf_scripts/scripts

in order to deflect/reduce attack surface area. That's what had happened in our case. Issue resolved - appreciate the engagement!