Third Wall communicates your selected settings, policies and emergency action buttons through the Automate system.   To fully understand and set appropriate expectations of the time required to change remotes, it's important to first understand how Automate communicates with your endpoints.

The Automate System is built upon a hub-and-spoke model.  When you use the Control Center to make changes to endpoint settings, those commands are not sent directly to the endpoints.  Instead, it is sent to the Automate Server where it is held, waiting for the endpoints to report in and get them.  Once received, they are executed immediately and the response code (success or failure) is returned to the server.  This process is repeated the other way too; once the response code is communicated to the server, it is made visible to the Control Center.

We can see this in action.  Open a computer screen and send an 'Update Config' (Begin -> Commands -> Inventory -> Update Config) command to an endpoint.  Next, immediately open the 'Commands' view.  On the top of the screen, you'll see the freshly issued command with a 'Pending' state.  This tells us the command has been communicated and is queued on the server.  Now we're just waiting for the remote to report in.  As soon as it does, it will receive, then execute the command and update the 'Commands' view.  Press 'refresh' to see this real-time.  When this happens, you'll see the status update from 'Pending' to 'Executing' and finally show 'Success'.  This concludes the execution of the remote command 'Update Config'.

Third Wall commands occur in exactly the same way.  When a policy is enabled or undone, the very same sequence will be seen.  When making modifications to an entire location, this sequence is used for each and every computer that is a member of that location.

At this point, it is important to understand both the timing of remotes reporting in and the impact of of that variance.  Normally, your remotes will report in every 300 seconds (five minutes).  Master computers will report in every 30 seconds and a computer in FasTalk reports in every 5.  This variance means remote endpoints will receive the command from Third Wall somewhere between 1 and 300 seconds.  The result of this is one computer in a location may get its command immediately and its neighbor doesn't get it for another five minutes.

Third Wall uses a combination of Update Config (our 'gpedit /force' command) and monitors to apply and maintain your desired settings.  It uses Third Wall Commands to remove (undo) policies.  This means you should expect to see different commands when tracking Third Wall changes to your endpoints.  When applying policies, look for the 'Update Config' command to report a successful change.  When removing them, look for the 'Third Wall Command' command.  In either case, as soon as the command reports a successful completion, you can assume (with some exceptions) the change has been applied.