Jump to content

Recommended Posts

Posted

Hi @julianhave and @bsylvain!

I’d understand this if you had at least one machine with KES10 installed, or if you had an active policy for that product.. but for this I have no explanation 🙄

 

Anyway, we have to take it as it is and be grateful that there is a way out 🤡

 

Take care, guys!
Milan

Posted

Hi @julianhave and @bsylvain!

I’d understand this if you had at least one machine with KES10 installed, or if you had an active policy for that product.. but for this I have no explanation 🙄

 

Anyway, we have to take it as it is and be grateful that there is a way out 🤡

 

Take care, guys!
Milan

I have no machine with KES10, no policies and no tasks. I always cleanup all this after upgrading to any version.

KSC just detect some of my KES11 machines as needing a KES10 patch. I have no idea why.

Still it’s a quite old KSC, upgraded from KSC10 to KSC11 to KSC12, might have some old registries or else.

Posted

Hi @julianhave and @bsylvain!

I’d understand this if you had at least one machine with KES10 installed, or if you had an active policy for that product.. but for this I have no explanation 🙄

 

Anyway, we have to take it as it is and be grateful that there is a way out 🤡

 

Take care, guys!
Milan

 

Hi @MilanBortel 

Hi @bsylvain 

This is weirder because I have never installed KSC10 or KES 10 or any policy for KES10 on that server or network.

I started in that network with KSC 11 and KES 11.

 

Thank you for your support.

 

Julian

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...