Endpoint Protection

Hello,

I created two hyper-v vm's for test.  Both are in the private vm switch so they can not talk to any other external network. 

One Server # 1 - I set the IP & Subnet for 192.168.0.1 with no DNS / Gateway.  I installed SQL on this server and restored a copy of production SQL SEPM database.

One Server # 2 - I set the IP & subnet for 192.168.0.2 with no DNS / Gateway.  I Installed SEPM 12.1.5 on this server and configured it use Server # 1 as the backen database.

On an additional 3rd VM - I have a SEP client on Windows Seven that is talking to Server # 2.  IP here is 192.168.0.3 with no DNS / Gateway.

Now I log in to Server #2 SEPM, and I see that almost all (30k) clients are noted in SEPM as online mirroring the produciton DB, I would expect all machines (sep clients) to go offline as the server is unable to talk to those client.  This is not happening though and all client show online after 3 days of this setup.  Our heartbeat is set to 2 hours.

Why are the clients not showing as offline?  The only client online should be the 3rd VM.  Any ideas?

I think I got what you're saying. You restored a snapshot so how you see it in your test is exactly how it looked in prod. I have a feeling those clients aren't actually connecting but what you're looking at is the point in time data. Especially if you configure your routes the way you did they shouldn't be able to get into that environment any way.

exactly, so in the test environment, how do I get the clients to show offline?

I would run management server config wizard once to check the issue. SEPM hasn't changed the last state it was in, when you backed it up. 

Did you run the management server config wizard after doing this?

I ran the management configuration wizard when i first created the test SEPM server.  I can do it again and choose reconfigure?

just did the reconfiguration through the config wizard, same thing. when I log into SEPM, I see almost alla active clients.

Since this is test, do you even need those clients? What if you just delete them?

I agree.

The whole reason we are performing this test is so that we are going to be doing the same thing in production pretty soon.  However, when we do this in production, we do not want these clients to be in the hung health status state as it is in now.  That is why we are trying to figure out what is happening here so we can avoid in production.

One of the other things I am trying is rebuilding indexes.  One thing I noticed is that Rebuildingof Indexes is happenting in PST so two hours behind.  Both SEPM & SQL server operating system time is set to CST.  Can this have an effect?

Rebuilding just does a defrag to ensure better searching performance. Ideally, when you move the DB, those clients are all going to point to that DB again at some point. In this case you restored prod onto a dev / empty environment. There is no way to tell those clients to go offline. You'd probably have to run some sort of SQL query to manually update the DB to change the status to offline.