This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Control Center 4.0 and Endpoint Security and Control 10.2 Tamper Control

Under Authenticate User in Tamper control on the ESC on the server also running Control Center. No one ever turned on Tamper Control but it is on. So we have no way of knowing the password to change settings on any clients or the server.

How do we learn our password or disable tamper control?

:39179


This thread was automatically locked due to age.
Parents
  • Hello Vandal,

    we cannot change the Primary location

    that's also the case in an SEC environment - it's possible to work around but it can't be centrally enabled (it doesn't make sense anyway in a manged environment). You should be able though to configure the other policies if Use central configuration is deselected fot the policy.

    push updates - every time I see this I have to point out that updates are not pushed to the clients (they are of course written - deployed as it is called - to the CID). It's the client making a connection (UNC or HTTP) to the CID and downloading them - if the clients fails to do so there is no way to push them.

    Christian

    :39237
Reply
  • Hello Vandal,

    we cannot change the Primary location

    that's also the case in an SEC environment - it's possible to work around but it can't be centrally enabled (it doesn't make sense anyway in a manged environment). You should be able though to configure the other policies if Use central configuration is deselected fot the policy.

    push updates - every time I see this I have to point out that updates are not pushed to the clients (they are of course written - deployed as it is called - to the CID). It's the client making a connection (UNC or HTTP) to the CID and downloading them - if the clients fails to do so there is no way to push them.

    Christian

    :39237
Children
No Data