Understanding client synchronization with the AdminByRequest portal is essential for maintaining optimal system performance and ensuring timely policy updates. This guide covers synchronization timing, manual sync procedures, and application pre-approval processes.
By default, endpoint clients synchronize with the portal approximately every four hours. This automated process ensures that endpoints receive regular updates without requiring manual intervention.
| Sync Parameter | Default Setting | Business Impact |
|---|
| Sync Frequency | Every 4 hours | Balance between real-time updates and system performance |
| Sync Content | Policies, settings, and configuration data | Ensures endpoints have latest security controls |
| Network Impact | Minimal bandwidth usage | Efficient communication without disrupting user activities |
| Step | Action | Result |
|---|
| 1. Policy Check | Client queries portal for updated policies | Identifies any configuration changes |
| 2. Settings Update | Downloads new settings and configurations | Applies latest security policies |
| 3. Status Reporting | Uploads endpoint status and inventory data | Provides real-time visibility to administrators |
| 4. Acknowledgment | Confirms successful synchronization | Ensures reliable communication |
If an immediate sync is needed on a particular client, you can achieve this through the client interface:
| Platform | Access Method | Steps |
|---|
| Windows | Tray tool | Open Admin By Request from tray tool → Select About Admin By Request |
| macOS | Menu bar | Open Admin By Request from menu bar → Select About Admin By Request |
| Linux | System tray | Open Admin By Request from tray tool → Select About Admin By Request |
When performing manual synchronization, it’s important to verify connectivity:
| Check | Method | Expected Result |
|---|
| Connectivity Status | Click the Connectivity button | OK status indicates successful portal connection |
| Network Access | Verify internet connection | Uninterrupted access to AdminByRequest services |
| Firewall Settings | Confirm required ports are open | Successful communication with portal |
Note: Refer to Synchronizing Clients with the Portal for more information, or if you are having problems with synchronization.
Admin By Request allows for quick pre-approval of trusted applications from the Auditlog. Pre-Approval is based on the application vendor or checksum, visible when the Application Control screen is displayed.
Important Note: At the time of writing, this functionality is not available for Linux clients.
Once an application has been installed on an endpoint with Admin By Request:
| Step | Action | Location |
|---|
| 1. Locate Application Entry | Navigate to the application’s corresponding entry in the portal Auditlog | Auditlog section of Admin Portal |
| 2. Expand Entry Details | Click on the application entry to view detailed information | Expanded audit entry view |
| 3. Initiate Pre-Approval | Select “Pre-approve this file” under Actions | Actions menu in audit entry |
| 4. Configure Settings | Modify any settings as required on the Application Control screen | Application Control interface |
| 5. Save Configuration | Click Save to confirm the app has been added to pre-approved list | Save button on Application Control screen |
| Setting Category | Configuration Options | Business Value |
|---|
| Approval Scope | All users, specific groups, or individual users | Granular control over application access |
| Time Restrictions | Always available, business hours only, or custom schedule | Security control based on time parameters |
| Elevation Method | Automatic approval, admin approval required, or denied | Flexible security policies |
| Audit Level | Detailed logging, summary logging, or minimal logging | Compliance and monitoring requirements |
| Issue | Possible Cause | Resolution |
|---|
| Delayed Sync | Network connectivity issues | Verify internet connection and firewall settings |
| Failed Policy Update | Portal communication error | Check connectivity status and retry manual sync |
| Missing Inventory Data | Client not properly enrolled | Verify client installation and registration |
| Configuration Not Applied | Policy conflict or error | Review policy settings and resolve conflicts |
| Step | Action | Expected Outcome |
|---|
| 1. Check Connectivity | Use Connectivity button in client interface | OK status displayed |
| 2. Review Auditlog | Check for sync-related entries in portal | Recent synchronization entries visible |
| 3. Verify Client Status | Confirm client appears in portal inventory | Client listed with current status |
| 4. Test Manual Sync | Perform manual synchronization | Successful sync completion confirmed |
| Practice | Implementation | Benefit |
|---|
| Regular Connectivity Checks | Periodically verify client connectivity | Proactive issue identification |
| Policy Update Scheduling | Plan policy changes during low-usage periods | Minimize disruption to users |
| Audit Log Monitoring | Regular review of synchronization entries | Early detection of issues |
| Network Performance Monitoring | Ensure adequate bandwidth for sync operations | Reliable and timely updates |
| Security Aspect | Recommendation | Rationale |
|---|
| Connectivity Verification | Always verify connectivity before critical operations | Ensures reliable policy application |
| Pre-Approval Validation | Thoroughly vet applications before pre-approval | Prevents unauthorized software execution |
| Audit Trail Maintenance | Maintain complete synchronization logs | Supports compliance and forensic analysis |
| Access Control | Limit who can modify synchronization settings | Prevents unauthorized configuration changes |
| Configuration Option | Default Setting | Customization Impact |
|---|
| Sync Interval | 4 hours | More frequent updates vs. network resource usage |
| Retry Logic | Automatic retry on failure | Improved reliability vs. system resource consumption |
| Bandwidth Throttling | Optimized for minimal impact | Fine-tuned performance vs. user experience |
| Priority Settings | Balanced priority | Critical updates vs. routine synchronization |
| Integration Type | Supported Platforms | Benefits |
|---|
| Group Policy | Windows environments | Centralized synchronization management |
| MDM Integration | Mobile device management platforms | Coordinated policy deployment |
| Scripting Interface | All platforms | Automated synchronization control |
| API Access | Custom integrations | Programmatic sync management |
Key Takeaway: Client synchronization with the AdminByRequest portal is designed to be automated and efficient, with manual options available for immediate updates, ensuring that endpoints maintain current security policies while minimizing system overhead.
Client synchronization with the AdminByRequest portal operates on a reliable four-hour automatic cycle, ensuring that endpoints receive timely policy updates while maintaining optimal system performance. The ability to force manual synchronization provides flexibility for urgent updates, while the auditlog-based pre-approval system streamlines application management.
By understanding these synchronization mechanisms and following best practices for connectivity verification and application pre-approval, administrators can ensure that their AdminByRequest deployment maintains optimal security posture and operational efficiency. Regular monitoring of synchronization status and proactive troubleshooting help prevent issues before they impact user productivity or security compliance.
