I've been trying to enroll a metricbeat on a Windows Server 2016 box through the Central Managaement feature and I've had no luck getting it to register. Here are the troubleshooting steps that I've gone through so far.

Sorry for my delay but I appreciate your response awhile back. I just got back around to troubleshooting this as some other projects took precedence over this one for the time being. I was able to work around this issue by pointing the autogenerated token link to a specific server within our Kibana cluster and remvoing the kiban.gov part. Our setup like many has a VIP that directs data to one of the three Kibana servers in the pool. So we have kibana-test.gov with abc.gov, def.gov and ghi.gov servers and once I took out the kibana-test.gov from the link and put in abc.gov with the username and password it worked. For this example, metricbeat on Windows Server 2016 pointing to RPM Linux Kibana, the below command worked.

Saving a copy of current settings to metricbeat.yml.bak
Enrolled and ready to retrieve settings from Kibana

One of the other issues that popped up was that due to the fact that our Kibana servers sit behind the VIP I had to remove the https part and change it to http. The error message that I got with https was:

Overall removal of the link that Kibana generated and inputting a specific server within our DNS pool worked. Thanks for the help and hopefully this helps some others out as well. Enjoy the rest of your day.