The server and clients are not showing up in the console
Published: September 28, 2016 - 5:55 PM
Hello,
I installed WAPT on a virtual machine running Windows Server 2012 R2.
The inventory table is empty, whereas I expected the virtual machine on which I installed WAPT to be inventoried.
I proceeded with the deployment of the WAPT agent on the client machines. The agent was deployed via GPO without any issues, but these client machines (the web interface at http://127.0.0.1:8088 shows that the agent is deployed) are not appearing in the WAPT console on the server.
I've tried a multitude of things:
installing and reinstalling => no results;
deleting and recreating the virtual machine => nothing.
I've verified that the DNS configurations are working. nslookup on the machine name works correctly (name-to-IP and IP-to-name resolution is correct).
've added the WAPT CNAME alias, which points to the FQDN of my WAPT server.
Do you have any idea what's preventing my WAPT server from working?
I'd like to reiterate that in my test on a different machine (a single domain controller), everything works fine, but when I switch to a production environment with two domain controllers, one with a primary zone and the other with a secondary zone, the WAPT server isn't reporting the inventories in its console. DNS functionality has been checked (nslookup resolves the names).
Can anyone help me, please?
I installed WAPT on a virtual machine running Windows Server 2012 R2.
The inventory table is empty, whereas I expected the virtual machine on which I installed WAPT to be inventoried.
I proceeded with the deployment of the WAPT agent on the client machines. The agent was deployed via GPO without any issues, but these client machines (the web interface at http://127.0.0.1:8088 shows that the agent is deployed) are not appearing in the WAPT console on the server.
I've tried a multitude of things:
installing and reinstalling => no results;
deleting and recreating the virtual machine => nothing.
I've verified that the DNS configurations are working. nslookup on the machine name works correctly (name-to-IP and IP-to-name resolution is correct).
've added the WAPT CNAME alias, which points to the FQDN of my WAPT server.
Do you have any idea what's preventing my WAPT server from working?
I'd like to reiterate that in my test on a different machine (a single domain controller), everything works fine, but when I switch to a production environment with two domain controllers, one with a primary zone and the other with a secondary zone, the WAPT server isn't reporting the inventories in its console. DNS functionality has been checked (nslookup resolves the names).
Can anyone help me, please?