Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

0 Neutral

My Information

  • Location
    United States
  • Agent Count
    500 - 750 Agents

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am struggling with the new GEN2 probe and it's identification of VMware virtual machines. The probe locates the VM, but it classifies it as: Manufacturer = "Vmware, INC." Type - "Network Device" It appears to stop there and is never identified as a windows machine so the probe never pushes out the agent to the endpoint. The Agent Readiness shows either Not Applicable (can't recognize if it is a computer) or Not Ready (no valid credentials found) even though every possible location where client credentials are needed is populated with the correct credentials (I verified this because non-VM's get the agent installed just fine from the same probe.) The legacy deployment manager can push the agent to the endpoint, and the new CWA agent deploy utility can also push the agent out to these endpoints without issue. I just want to figure out why the probe isn't detecting it as a windows endpoint and pushing the agent out automatically. I need some help on this one as Automate support never figured it out and it is slowing down our deployment having to open each device and install the client manually or use one of the tool or utilities to manually push the agent out. Note: I am aware of GPO based deployment but I can't wait forever to get an endpoint to reboot to install the agent. Most of these are servers and getting clients to allow server reboots (even when everyone is asleep is next to impossible.)
  • Create New...