search : lockdown installer

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

Lockdown Installer should find port from server.xml
Lockdown Installer Download is not HTTPS
NumberFormatException when running Linux Lockdown Installer
Lockdown Installer does not report fatal errors as fatal
Linux Lockdown Installer should not require OS account passwords
Lockdown Installer Should default Domain to Computer Name
Lockdown Installer does not use inheritance for file permissions
Rollback of Lockdown Installer caused 500 server error
Lockdown Installer Rolls back if Apache is Stopped
Comment on Lockdown Installer Rolls back if Apache is Stopped by Kailash B.
Comment on Lockdown Installer should find port from server.xml by Kailash B.
Comment on Lockdown Installer does not use inheritance for file permissions by Aaron N.
Comment on Lockdown Installer Rolls back if Apache is Stopped by Manas M.
Comment on Lockdown Installer does not use inheritance for file permissions by Kailash B.
Comment on Lockdown Installer Failed to Restart Apache on RHEL 7.5 on SELinux by Peter F.
Comment on Lockdown Installer Rolls back if Apache is Stopped by Peter F.
Comment on Lockdown Installer Rolls back if Apache is Stopped by Manas M.
Comment on Lockdown Installer Failed to Restart Apache on RHEL 7.5 on SELinux by Peter F.
Comment on Lockdown Installer does not use inheritance for file permissions by Peter F.
Comment on Lockdown Installer does not use inheritance for file permissions by Kailash B.
Comment on Lockdown Installer Failed to Restart Apache on RHEL 7.5 on SELinux by Kailash B.
Lockdown Installer Failed to Restart Apache on RHEL 7.5 on SELinux
Typo in Lockdown Installer: intall
4476634 CF-4202932 Security : LockdownGuide Installer rolls back if wsconfig is left open Problem Description: If you accidentally leave wsconfig running while running the lockdown installer it fails half way through and has to roll back its changes. Ideally it could be checked at installer
[ANeff] Bug for: Auto-Lockdown installer missing
Tracker Issue Installer Errored
4214896 CF-4202005 Installation/Config : Lockdown Installer Installer Errored Problem Description: I got an error running the lockdown installer - see attached log file. Steps to Reproduce: Started with a fresh Windows 2016 server on EC2. Installed IIS. Deleted the Default Web Site, created two
Lockdown Installer: The BACKUP object with identifier LockDownBackup already exists.
Lockdown installer 1 NonFatalErrors on Win 2016
Carl Meyer Hello, Where do I download CF2018 Server Auto-Lockdown installer to be able to run that? Thanks in advance, Carl.
Comment on [ANeff] Bug for: Auto-Lockdown installer missing by Immanuel N.
4214883 CF-4202002 Peter F. FYI The passwords were also written to C:\ColdFusion2018\lockdown\cfusion\Logs\Adobe_ColdFusion_2018_Automated_Lockdown_Installer_Install_04_17_2018_20_23_37.log
Linux Installer points to cf11 lockdown guide
4214883 CF-4202002 Installation/Config : Lockdown Installer Passwords are written to lockdown_logs.txt Problem Description: When asked for the OS Administrator password it says "The password is not stored" but it ended up in the lockdown_logs.txt file. It also writes the CF Admin passwords
Peter Freitag ColdFusion 2018 Lockdown Guide Looking for the ColdFusion 2018 Lockdown guide? The post ColdFusion 2018 Lockdown Guide appeared first on ColdFusion. Blog,CF2018 Updates,ColdFusion 2018,2018,blog,cf2018 updates,coldfusion 2018,installation,security
4480653 CF-4202953 Security : LockdownGuide [Lockdown] CF Scripts URI Should be Random Problem Description: The lockdown installer remaps the /cf_scripts URI to /cfscripts_2018 - there is no benefit in changing it from one known default to another known default - if it is going to change it
Comment on Lockdown Installer: The BACKUP object with identifier LockDownBackup already exists. by Kailash B.
4214811 CF-4201999 Installation/Config : Installer [ANeff] Bug for: CF2018 Lockdown Guide URLs Issue: CF2018 Installer's "Select ColdFusion Server Profile" screen mentions these outdated URLs: 1) http://www.adobe.com/go/cf2016_secureprofile 2) http://www.adobe.com/go/cf2016-lockdown
4213060 CF-4201996 Installation/Config : Installer [ANeff] Bug for: CF2018 Lockdown Guide URLs Issue: CF2018 Installer's "Select ColdFusion Server Profile" screen mentions these outdated URLs: 1) http://www.adobe.com/go/cf2016_secureprofile 2) http://www.adobe.com/go/cf2016-lockdown
4213745 CF-4201995 Installation/Config : Installer [ANeff] Bug for: CF2018 Lockdown Guide URLs Issue: CF2018 Installer's "Select ColdFusion Server Profile" screen mentions these outdated URLs: 1) http://www.adobe.com/go/cf2016_secureprofile 2) http://www.adobe.com/go/cf2016-lockdown
Comment on Link to lockdown guide in installer returns a 404 by Piyush K.
CF2018 Auto lockdown not able to complete, if Add-on, ODBC and .NET service services are not installed in Windows environment.
Comment on Linux Installer points to cf11 lockdown guide by CFwatson U.
Vamseekrishna Nanneboina Regarding #2, the primary reason for refreshing the installers was to bundle Java 11, so the scope was kind of limited to Java 11 and Update 2 bug fixes. We've also added support for the Lockdown installer for Mac OS X.  We will see if anything can be done to fix #1 outside
Miguel Fernandez SauravGhosh – when you guys add security features like this in an update are you also updating the Server Auto-Lockdown installer to include them? (I realize this only applies to ColdFusion 2018)
Link to lockdown guide in installer returns a 404
Server Auto-Lockdown
Comment on Link to lockdown guide in installer returns a 404 by Piyush K.
Aaron Neff Hi All, These CF2018 Public Beta installers have been re-refreshed about 14 hours ago: - ColdFusion Windows installer - Performance Monitoring Toolset Windows installer - Automated Lockdown Windows installer CF build# changed from 2018.0.0.310409 to 2018.0.0.310608. The refreshed PMT
the following: Auto-discovery of nodes in Performance Monitoring Toolset Updated text in Server Lockdown installer screens More than 120 bug fixes For more information, see the blog, Adobe ColdFusion (2018 Release) Public Beta. The post ColdFusion (2018 release) Public Beta Refreshed Installers appeared first
philg15796544 Hi Miguel, I am experiencing the same issue. The lockdown is bailing out after it finds that I did not install the optional services. My log is identical to yours. Very frustrating!
4467319 CF-4202894 Aaron N. Hi Hari, Thanks very much, but what sense does it make to require manual wsconfig or Auto-Lockdown when installing CF as developer edition? That's a turn off. Making a simple thing complicated. Do you see what I mean? Installing Developer edition and configuring a site
Comment on [ANeff] Bug for: CF2018 Lockdown Guide URLs by Aaron N.
2608467 CF-4088018 Hot Fix Installer : Installer ext-user In the lockdown guide environment, after uninstalling the CF11 HF7 a manual restart of server is required. Problem: In the lockdown guide environment, after uninstalling the CF11 HF7 a manual restart of server is required
RAHUL UPADHYAY ColdFusion 2018 Add-on installers ColdFusion 2018 Add-on installers are available on https://www.adobe.com/support/coldfusion/downloads.html It includes installers for: COLDFUSION (2018 RELEASE) PERFORMANCE MONITORING TOOLSET COLDFUSION (2018 RELEASE) SERVER AUTO-LOCKDOWN COLDFUSION
scalable, high-performing web applications in CFML. Now in ColdFusion, we’ve added an all-new Performance Monitoring Toolset, a standalone server with low overhead to control and optimize applications and a new auto lockdown installer to help increase security in the Production Server. In addition, web
Charlie Arehart

Folks finding this post in mid-2019 and beyond should note that in the technotes for CF2018 update 4 (from June 2019) there is indication that the Lockdown tool installer was “refreshed” (a new one was made available). See 

Comment on Linux Installer points to cf11 lockdown guide by CFwatson U.
Dan OKeefe Giancarlo Gomez  Hi JC. Charlie, I searching to see if there are any know issues with Windows 2016 and came across your post here. On a fresh AWS ec2 instance, Windows 2016, CF 2018 Update 3 applied, CF 2018 Lockdown
2610074 CF-3732913 External U. This has been requested for many years and Adobe's continued response is "there isn't enough time". Well, when will there be time? How many times does this security flaw have to bite Adobe before they find the time? One of the first things I do when when installing a
4467319 CF-4202894 Aaron N. Wish I could edit. Please ignore the "Maybe in next updater?" as that doesn't even make sense. Issue should be fixed in next refresh of the installers. The Developer Edition installer flow should not have been changed in CF2018. One doesn't typically lockdown one's Dev
2612295 CF-3529336 Installation/Config David Epler Default user in Windows The installer for Windows should allow for specifying the user that ColdFusion should run as and not rely on the administrator to come back and change it by following the lockdown guide. The Linux and Solaris installers have
quick hit on the update log revealed permission issues. Steps to Reproduce: Install CF2016 and follow the Lockdown guide completely (especially the part about the CFUser) Actual Result: The hotfix wasn't applied. Looks like it can't access/delete certain files. Expected Result: Hotfix
2609506 CF-3840648 External U. I am getting the exact same error. I have CF11 installed with no updates applied so far. I am also using the-built in web server and have not applied any lockdown steps or enabled secure mode.
Comment on "Download and Install" fails when installing on Update 1 by External U.
RAHUL UPADHYAY How to install ColdFusion updates manually Sometimes, CF administrator UI update installation could fail due to permissions, lockdown guide, network restrictions etc. You can follow below instructions to apply updates manually. Navigate to https
Comment on [Lockdown] CF Scripts URI Should be Random by Miguel F.
Comment on Block Download and Install / Install Buttons in Server Update Page on Windows by External U.
="nofollow">https://www.adobe.com/support/coldfusion/downloads.html As far as I can tell, the following installers were refreshed: Add-on Services Installers for ColdFusion (2018 release) ColdFusion (2018 release) .NET Integration Service Installer ColdFusion (2018 release) Performance Monitoring Toolset ColdFusion (2018 release) Server Auto-Lockdown
Comment on Server Auto-Lockdown by Miguel Fernandez
structure on my development computers and per the Lockdown Guide on my Windows production server). The only way I've been able to get the updates to install properly from the CF Administrator is as follows: 1. Change the ColdFusion service account to run as the local Administrator account. 2. Stop
to the lockdown guide: Download and Install Windows tool named SubInACL.exe from http://www.microsoft.com/en-us/download/confirmation.aspx?id=23510 Then, run the following to give stop/start permissions to the new secure user: "C:\Program Files (x86)\Windows Resource Kits\Tools\subinacl.exe" /service "\\\Cold
Vincent Krist I am unable to install Update 8 on our CF 2016 server. The server is running CF 2016 Update 7 on Windows Server 2008 R2. Coldfusion 2016 was originally installed using Pete Freitag's lockdown guide and we have never had any problems installing the previous updates. The Coldfusion
for this seems to have first started. In the old lockdown guides for CF10 and CF 11, the reference for editing server.xml was limited to Linux installations (apparently CF Admin took care of this under the hood in Windows in that case). As it is I'm heavily inclined to leave my workaround in place
Comment on CF11 update 8 doesn't install properly by External U.
5369952 CF-4204032 connector unable to stat uriworkermap.properties error logged in mod_jk.log Problem Description: As soon as ColdFusion 2018 update 2 was installed and the Apache connector was rebuilt, we are seeing this following error in mod_jk.log, repeatedly. [Thu Feb 14 12:42:06 2019
\hf-updates\updates.xml. This file is nothing more than an XML file that contains a list of applied updates. Adobe issues a Lockdown Guide that HIGHLY recommends that ColdFusion be run under a local user account with limited permissions. This prevents ColdFusion Updates from being installed even when the above file or even
Comment on "Download and Install" fails when installing on Update 1 by External U.
Comment on "Download and Install" fails when installing on Update 1 by S P.
Full Control) prior to running CF's installer. According to Nimit, it is not related to the lock-down steps. Just mentioning it FWIW. Related thread: http://prerelease.adobe.com/r/?8b745481c2d34200a84f12e3a5cb8bcb ----------------------------- Additional Watson Details
Comment on ColdFusion 11 Updates do NOT install when ColdFusion is running as local user account by External U.
Comment on ColdFusion 11 Updates do NOT install when ColdFusion is running as local user account by S P.
-database-drivers-leaking-memory Steps to Reproduce: Install ColdFusion 10 or 11 x64 on Microsoft Windows 2008 R2 x64. Follow ColdFusion-lockdown guides. Setup multiple websites and multiple datasources, all on Microsoft SQL Server. Let websites run over time with 4096MB heap size. Actual Result: Over time, java
Team for help with this on CFsup@adobe.com I hope this post helps though. Installing ColdFusion 2016 in Distributed Mode under Windows/IIS:
  1. Install IIS (and URL Rewrite) on the Distributed Web Server
  2. Install Visual C++ 2012 x64