6 Replies Latest reply on Jun 21, 2011 1:29 AM by georgec

    Disable Access if Not Synchronized Within XX Days

    cdobol

      As far as I can tell this is not an option with EEPC 6.1.  We really liked this feature.  Any alternative way to do a similar thing?  Anyone know if they plan to put this back in at some point? 

        • 1. Re: Disable Access if Not Synchronized Within XX Days

          no, it's not been a feature of the v6 product, but if you have a particular use case I'd encourage you to discuss it with your account manager, and get it listed as a possible future feature request!

          • 2. Re: Disable Access if Not Synchronized Within XX Days

            Luckily, we have ePO now so there's a world of possibilities in terms of workarounds. For example, you could

             

            1. Write a query that lists all machines who have not reported any EEPC events for the last X days
            2. Use a server task to run this query, and then take the action to put the machine in a new group in the system tree. The task could then take another action to do an agent wakeup to push the policy change down to the client.
            3. That new group would have to have no users assigned to it, thus locking out the end user. You could assign some admins to the group if you want your admins to login if they find the machine.
            • 3. Re: Disable Access if Not Synchronized Within XX Days
              cdobol

              Although the integration with EPO does allow for expanded user management, we were looking to disable the machine without having to communicate back to EPO server to remove the users.  We are going to submit a FMR for this.  Thanks for both of your responses.

              • 4. Re: Disable Access if Not Synchronized Within XX Days

                Out of curiousity, how many minutes/days/weeks/months would you set the timeout value to?

                • 5. Re: Disable Access if Not Synchronized Within XX Days
                  cdobol

                  We have it set to 30, 45, and 90 days depending on the business unit.

                  • 6. Re: Disable Access if Not Synchronized Within XX Days
                    georgec

                    "Luckily, we have ePO now so there's a world of possibilities in terms of workarounds. For example, you could

                     

                    1. Write a query that lists all machines who have not reported any EEPC events for the last X days
                    2. Use a server task to run this query, and then take the action to put the machine in a new group in the system tree. The task could then take another action to do an agent wakeup to push the policy change down to the client.
                    3. That new group would have to have no users assigned to it, thus locking out the end user. You could assign some admins to the group if you want your admins to login if they find the machine."

                     

                    That doesn't make any sense. He needs to lock out the user while the machine is offline so he can enforce a policy where the users need to connect to the network periodicaly. And you're asking him to do a wake-up (which requires connectivity) to enforce a new policy for machines without network connectivity?!