So we ran the CF 2021 auto-lockdown tool, and the ...
# adobe
b
So we ran the CF 2021 auto-lockdown tool, and the status bar says it’s at 100% but it doesn’t seem to be actually done. There’s no success message or fatal error message on the screen or in the logs and I can’t close the window. Has anyone else seen this?
d
Watching... We haven't used it yet, but plan to on a new server we're setting up. Let us know how that resolves.
👍🏻 1
b
yeah it’s just sitting there, no idea what’s going on. The permissions for our web root are all wrong now, so I assume it is not actually done. Nothing in the logs for 30 minutes now.
rebooted and trying to run the lockdown tool again
Yeah, same thing kinda. Just sits there at 100% but it’s clearly not done because permissions on our web root are all screwed up.
c
I ran into that myself when I went to upgrade our production system from CF 2018. Had no problems with our staging system, so it was unexpected. I retried a couple of times with the same result. Since I had run the lockdown tool on CF2018, the file system part it was working on adjusting permissions for was already set properly - so I just ran the Web Connector tool manually and everything seems to be ok.
b
That’s good to know, we are doing the same thing (upgrading from 2018).
The tool never ended up working. Ended up manually fixing permissions, removing the CF 2018 ISAPI tomcat module from IIS, running the connector, manually updating related virtual directories.
I don’t know if I even want to try running it on prod, lol
Follow-up: tried it on prod and had the same issue. Had to rebuild permissions and do stuff manually. Weird.
d
And, I have to say, unwelcome.
@bendur @cfvonner Did either of you run this by Adobe? If so, any response?
b
I did not, probably should have I suppose.
Was kind of hoping they would read this thread.
d
Mmmm. @Mark Takata (Adobe) Any ideas?
m
Please email cfsup@adobe.com with the issue, the lockdown tool should work...