After reading the docs, installing the RSD module on the ePO server, installing a Sensor on one test client....and then reading everything I could find on this forum on RSD, I'm no further along in figuring out what's happening than I was before!
So, I'm looking for some practical "here's how you do this" info.
Here's what I have: Covered Subnets: 0% Covered: 0 Contain Rogues: 0 Uncovered: 72
No Sensors Available Active: 0 Passive: 0 Missing: 0
So: How do I "turn on" the Sensor I've installed? How do I make it Active or Passive? How do I cover the subnets in our domain? I know with only one test Sensor, only it's subnet is going to be covered...correct?
How do I "turn on" the Sensor I've installed? The sensor will turn on automatically once it is installed
How do I make it Active or Passive? They switch between active and passive automatically, if you have more than one RSD sensor installed they take it in turns to work/rest
How do I cover the subnets in our domain? I know with only one test Sensor, only it's subnet is going to be covered...correct? You can either install a couple of sensors per subnet or you could put sensors on your DHCP servers instead, as the majority of your IP based clients will be coming here.
I thought the Sensor would turn on automatically...but the Rogue System Sensor Status screen still shows "No Sensors Available". I've rebooted the client with the Sensor on it, but that didn't make a difference.
I also thought the single subnet that the Sensor belongs to would show up in the Subnet Status screen...but it doesn't.
Obviously, something is wrong, but I don't have a clue what it would be. I didn't get any error messages when I installed the RSD module. All the other ePO functions are working correctly.
jmaxwell, If "RSS" means "rogue system sensor", then nope, not going thru any firewalls.
rwhitehill, Yes, I have the policy enabled.
But late yesterday, I thought the problem was with the Sensor installation (I had installed using a Client Task), so I checked the tags and the System Details for the client I had installed the Sensor on, and nothing shows that this client is a Sensor....so the install had not worked.
I then tried the install using the "More Actions" button for that client, and got this: "Rogue Sensor Install deployment task create failed (Unable to add Rogue Sensor install deployment task to node "My Organization\ADM\Computers\WSUS computers\RIC" because "My Organization\ADM\Computers\WSUS computers\RIC" already contains an Rogue Sensor install deployment task) 7:05 " So, I moved that client to another group, tried again, and got the same error message.
I then did an "uninstall the Sensor" from the "More Actions" button. That seemed to work, but none of this shows up in the server logs, so I'm not sure.
I'm going to try installing a sensor to a different client later today.
Both, no firewall appliances and no firewall settings on the clients.
But here's a question about the setup: I'm still trying to see if the Sensor installation is working...is there a way to confirm that from the Sensor machine itself? A process running...an indicator on the Task Bar...anything?
I see NO confirmation on the ePO server; it still says "No Sensors Available", "Covered Subnets 0%", and no Tags or RSD properties on the clients I've "installed" the Sensor on.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.