How the conversation goes…

Interviewer: Makes sense. Can you talk a little bit about how you work with SCCM group policies and any of that in that direction to ensure endpoint– if I was an IT pro trying to use Agent and I’m really thinking, how can I use this? I know I have SCCM, I know I’m using group policies, maybe even Windows update services, etc, how can I make the most out of that tool to ensure security?

SCCM & Access Agent

Interviewee: Well, I think with SCCM it’s in competition with XAgent to some degree. If you had SCCM you wouldn’t need a full XAgent for you to know– you wouldn’t need a Windows service or an Agent running on the desktop all the time, but you could use fixengine by itself, or a notification service that runs on-demand which gets triggered by SCCM. That could be a way for the two products to work together.

But with SCCM it takes away some of the back-end management of your repository, executing your repository against targeted machines. It presents a new different way of interacting with XAgent I suppose.

Interviewer: How would you use–.

Interviewee: There isn’t a huge amount of integration to it. How to use it? The notification system is there to inform people of things or to let them know that there’s an issue ongoing for example please do not log a ticket that scenario will be there to save costs from tickets, but you could inform people that there’s a potential wannaCry exploit ongoing, please be wary of this, that, or the other. Or you could. No, because you can notify individuals, you can notify locations or different amounts of business. You could target people with instant messages through the notification system.

Interviewer: Okay. That’s a great use case. What was the other thing that you mentioned? Notifications and you had mentioned one other thing of the SCCM. You could use the other fix center, so that would be in the script?

Interviewee: Yes, you could equate your fix, then you could use SCCM to deploy and execute it, rather than use the inbuilt notification mechanism. Sorry, using the inbuilt XAgent mechanism to deploy.

Interviewer: Okay. Either you go for the SCCM route, or you go for the Agent route?

Interviewee: Yes.

Interviewer: You can buy fix center and notification separately?

Interviewee: Yes, so XAgent is modular enough that you could separate these out into their own subsystems. And a company could purchase them individually.

Leave a Reply

Your email address will not be published. Required fields are marked *

Post comment