# Fleet enrollment is done but doesn't appear on Security \> Administration \> Endpoints

**URL:** <https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142>\
**Category:** Endpoint Security\
**Created:** [January 5, 2021, 1:29am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142 "2021-01-05T01:29:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![roh](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@roh](https://discuss.elastic.co/u/roh)\
**Post date:** [January 5, 2021, 1:29am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/1 "2021-01-05T01:29:24Z")

</div>

Hi all!  
I'm trying to enroll Elastic Agent on Fleet.  
Kibana and Elasticsearch are on Windows 10 WSL Ubuntu 16.04 and Elastic Agent is on Windows 10.  
I'm using self-signed certs so I imported certificates as root trusted certificate.  
I do see Agent on Fleet and data sets on data streams but no hosts appear on Endpoints.  
Is there any solution of this case?  
I'm gonna test again by installing KB and ES on Windows 10 by the way.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/7/f7ffc8e17997c9a3bf18e339b55d1b2134c35e8e.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/3/53d8b1a65cef62be4da0a5faab32b915c9e82bc5.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af8566081b781b4c7600872485360f0ac6c52ad5.png)

---

<div class="post-metadata">

**Author:** ![roh](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@roh](https://discuss.elastic.co/u/roh)\
**Post date:** [January 5, 2021, 3:54am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/2 "2021-01-05T03:54:27Z")

</div>

Tried on windows 10 but still doesn't appear on Security \> Administration \> Endpoints 🤔

---

<div class="post-metadata">

**Author:** ![ferullo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ferullo/32/74240_2.png) [@ferullo](https://discuss.elastic.co/u/ferullo)\
**Post date:** [January 5, 2021, 11:16pm UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/3 "2021-01-05T23:16:35Z")

</div>

Hi @roh

I'm sorry to hear you're having trouble. Can you follow the instructions here [Endpoints are enrolling stuck message](https://discuss.elastic.co/t/endpoints-are-enrolling-stuck-message/258599/7) to see if there might be an issue with how your root certificate was imported?

Our of curiosity, what Agent version are you using?

---

<div class="post-metadata">

**Author:** ![roh](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@roh](https://discuss.elastic.co/u/roh)\
**Post date:** [January 6, 2021, 1:31am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/4 "2021-01-06T01:31:43Z")

</div>

Used latest version, 7.10.1.

I'm curious I used correct self-signed CA.  
I used CA made from this command.

./bin/elasticsearch-certutil ca

I already followed instructions in [Endpoints are enrolling stuck message](https://discuss.elastic.co/t/endpoints-are-enrolling-stuck-message/258599/7), but still didn't work.

I'v succeeded before with not using HTTPS security... maybe I should try that once more.

---

<div class="post-metadata">

**Author:** ![Nick\_Berlin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick_berlin/32/74426_2.png) [@Nick\_Berlin](https://discuss.elastic.co/u/Nick_Berlin)\
**Post date:** [January 6, 2021, 6:26pm UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/5 "2021-01-06T18:26:08Z")

</div>

@roh, this is bummer, sorry for all the trouble.

Can you confirm that the self-signed CA was added as `Local Machine`?  
Others have had trouble by choosing the default, `Current User`.

Also, it's necessary for Endpoint Security to be restarted after adding a new CA to the system.

If you are sure about those two things we will need to see logs (or snippets of logs) to debug this beast.

Elastic Endpoint is installed in `c:\Program Files\Elastic\Endpoint` . Logs are written to `c:\Program Files\Elastic\Endpoint\state\log\endpoint-*.log` . Are they any errors in there? If so, please post them.

---

<div class="post-metadata">

**Author:** ![Ameer\_Mukadam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ameer_mukadam/32/47196_2.png) [@Ameer\_Mukadam](https://discuss.elastic.co/u/Ameer_Mukadam)\
**Post date:** [January 7, 2021, 9:00am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/6 "2021-01-07T09:00:57Z")

</div>

I too have this same issue logs are shipping and everything works but the administration page in Security still shows agents are enrolling. Although the enrollment completed successfully days ago. For now I just change the endpoint security settings by going and editing the Elastic Security policy and clicking show advance settings it then successfully takes me to Security settings page but I want to go via Elastic Security App it keeps saying enrollment in process.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 4, 2021, 9:01am UTC](https://discuss.elastic.co/t/fleet-enrollment-is-done-but-doesnt-appear-on-security-administration-endpoints/260142/7 "2021-02-04T09:01:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
