Endpoint Protection

Hello,

 

I recently performed an update from SEPM v12 to SEPM v14 on a Windows Server 2012 R2 server.  The update went smoothly.  I followed it with test installs of v14 clients to two machines on our network, both took place without issue.

The next day I attempted to deploy numerous clients at once to update other users to v14, I get to "Deploying Client Remotely" where it gives the progress and would normally be performing the install but nothing happens.  This doesn't matter if it's 1 machine, 10 machines, etc.  No changes were made to the server between point A (install to test clients) and point B.  All clients are on the same network and subnets and domain.

There's nothing in the event viewer that I can find related to any issues.  If I create a package and install it locally rather than pushing it, this is successful.  Any advice would be appreciated.  Thank you.

Is the remote registry service started? Is there a SEP_INST.Log file in the %temp% directory?

Did you remote push the two that were successful? 

Preparing Windows and Mac computers for remote deployment

check the firewall on win2012 if it allows file and printer sharing, does it work if you disable it for a while?

 

Hello Jeffrey,

What's so different between the Test machines and Production machines?

Were the Test machines from the Production group?

If yes, I personally suggest you to test deploying few more machines by taking 10 machines at a time.

Hope that works out.!!

Mithun,

There is nothing different between the test machines and the production machines.  I actually tried sending the newest version to the test machines and it stuck at the same point.  So there has to be something fundamentally wrong but nothing changed as far as I know and I'm the only person who would change settings on the server... I did try resending the newest client to myself and it was a no-go whereas before it worked.

 

Rafeeq,

 

As no settings were changed I don't think this is an issue but all internal firewalls are disabled.  We use a firebox (Watchguard) firewall that handles incoming packets so we disable firewalls by GPO.

 

Brian,

 

Let me check that log for you and be right back with that.

Mithun,

There is nothing different between the test machines and the production machines.  I actually tried sending the newest version to the test machines and it stuck at the same point.  So there has to be something fundamentally wrong but nothing changed as far as I know and I'm the only person who would change settings on the server... I did try resending the newest client to myself and it was a no-go whereas before it worked.

 

Rafeeq,

 

As no settings were changed I don't think this is an issue but all internal firewalls are disabled.  We use a firebox (Watchguard) firewall that handles incoming packets so we disable firewalls by GPO.

 

Brian,

 

Let me check that log for you and be right back with that.

ℬrίαη,

 

I confirmed that there is no sept_inst.log in any of the %temp% directories.  Not sure where else I could find it but I'll check the entire C: drive but thus far, no luck and i'm about 1000000% (Yes, I know that's not a real number) certain that the account that installed it doesn't hold this log.

This has been running since last night.  I have attempted the same process with a machine that I deployed v14 to already but updated the client version on the server but I receive the same results.  I honestly think something is wrong if after 16 hours a single client hasn't deployed whereas they were deploying after 2 minutes before.  (Note I didn't rename the computer/address here as they're local addresses and inaccessible remotely).  This problem exists on both Windows 7 and Windows 10.

 

So... the good news!  Looks like updates are going out automatically based on my Scheduled Install!  That's far better than nothing working as it was before!  (I made no changes to make this work, it just took time even though I set the days to 0).

 

The bad news is remote push still isn't working so I can't manually push the client to new machines I build out... I'm running the install locally for the time being but any suggestion is appreciated.

Hello Jeffrey,

in the tools and documents folder there is clientremote.exe,

use this tool to push the package remotely, if it fails it would throw an error and would be helpful to troubleshoot further

 

https://www.symantec.com/connect/articles/overview-push-deployment-wizard-symantec-endpoint-protection-121

Thank you Rafeeq.  Currently it has been putting clients out based on our scheduled time.  Remote Push is still failing.  As soon as I build out a new machine I'll test this and let you know the results.

Try the step suggested by vio in this thread: https://www.symantec.com/connect/forums/unable-push-sep-client-after-v14-mp2-upgrade