There's also no real need to enable it... normally!
To get auth'd to the SQL server for dev purposes, without using SQL auth:
1) Create a local user account on the CCX server, with the same user name as you have in your normal domain or local PC (i.e. aaron.harrison for me)
2) Make sure you set your same, current password on the account (yes, it needs updating whenever you change yours)
3) Go into SQL Ent Manager, and grant the new local account DBO permissions on db_cra
You can now authenticate using windows auth to the DB.
CCX 5+ seems more picky about how you auth to the DB and what method you use to connect (i.e. 'ADO for ODBC drivers' using TCP/IP) so I try not to meddle at all so as to ensure compatibility with customer setups.
SQL Auth is considered weaker, and therefore bad.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.