Hi Matt,
Yep, I saw that.
In addition to overriding HOMEDRIVE / HOMEPATH in the current cmd.exe environment, you can set your own cookie via environment variables, bypassing the file entirely. Log in using the same administrative account you used to install RabbitMQ , and create the %AppData%\RabbitMQ\rabbitmq-env-conf.bat file with the following contents:
set SERVER_ADDITIONAL_ERL_ARGS=-setcookie TEST12345678
set CTL_ERL_ARGS=-setcookie TEST12345678
Then, open the "RabbitMQ Command Prompt (sbin dir)" start menu item and run these commands:
.\rabbitmq-service.bat stop
.\rabbitmq-service.bat remove
.\rabbitmq-service.bat install
.\rabbitmq-service.bat start
If you check the arguments to erl.exe via task manager, you should see -setcookie TEST12345678 among them. If you change the values in rabbitmq-env-conf.bat you must remove and re-install the RabbitMQ windows service using the steps above.
If you log in using the same account to run rabbitmqctl.bat, it will also "source" the rabbitmq-env-conf.bat file and pick up those environment variables, and will connect without using the .erlang.cookie file. You can test it by running .\rabbitmqctl.bat status
I realize this is all a bit convoluted. We have begun a project to simplify the startup scripts for RabbitMQ on Unix and Windows, which may lead to simplification of how you configure RabbitMQ.
Thanks,
Luke