Unable to protect a new server 2012 R2 machine

Hello carolyn while,

is perchance your SEC version too low? An attempt to Protect Win8.1/Win10/Win2012R2 endpoints fails with this message for SEC versions up to 5.2.0. Apart from upgrading SEC and Jak's suggestion there are additional options available.

Christian

Hi

My sec is 5.1.2 so would that be a problem?

I have sorted it by pulling from the server but I am just interested in why it is happening.

THanks

Hello Carolyn,

please see the article linked from my previous post. It's not a problem, but Protect of machines with the mentioned OSs is only possible with one of the workarounds, SEC 5.1.2 isn't "aware" of these OS versions and doesn't know how to handle them.

Christian

Ah yes sorry. Thank you for that. Is the upgrade to 5.3.1 fairly painless or are there risks attached?

Thanks

Hello Carolyn,

there's always a residual risk [:)].
Can't comment on specifically 5.1.2 - wait! has there ever been a 5.1.2? - to 5.3.1. I'm on 5.3.0 (don't need the functionality and SQL service pack support added in 5.3.1). On one machine initially 5.1, upgrade path 5.2, 5.2.1., no problems. The other initially 4.5. one minor issue with, IIRC; 4.7->5.0. 

Is this the first time you upgrade?

Christian 

Hello Carolyn,

there's always a residual risk [:)].
Can't comment on specifically 5.1.2 - wait! has there ever been a 5.1.2? - to 5.3.1. I'm on 5.3.0 (don't need the functionality and SQL service pack support added in 5.3.1). On one machine initially 5.1, upgrade path 5.2, 5.2.1., no problems. The other initially 4.5. one minor issue with, IIRC; 4.7->5.0. 

Is this the first time you upgrade?

Christian 

OK thanks.

I think I ave done it before but last time I was moving servers as well so I started from scratch.

I will backup the VM and give it a try :-)

Thanks