Onboarding
Verifying Your First Successful Scan
What a working cloud connection or server agent looks like, and when to start troubleshooting.
A connection is working when it appears in SeqOps and data starts populating within 6–24 hours. If nothing appears after 24 hours, something needs troubleshooting.
A Working Cloud Connection
- •The cloud environment appears in SeqOps.
- •Its connection status shows as active or valid.
- •Resource inventory starts to populate.
- •Within 6–24 hours, findings and configuration results appear.
A Working Server Agent
- •The server is visible in Server List.
- •The provisioning helper completed without errors.
- •The agent services are running: Seqops Server Agent and Seqops Updater Service on Windows, or
serveragentandedr-updateron Linux. - •Within 6–24 hours, data for the server appears in SeqOps.
What Needs Troubleshooting
| What you see | What to check |
|---|---|
| The cloud connection test fails | The permissions for that provider. For GCP, confirm both required APIs are enabled. See Minimum Permissions Required for Cloud Connect. |
| A cloud environment that worked has stopped | Whether its credentials have expired or been rotated, such as an Azure client secret past its expiry date. |
| The provisioning helper fails | The server URL, Server ID, Tenant ID, and Registration Token. A credential set that has expired or has already been used can't register an agent. |
| The server is registered but no data appears after 24 hours | See Agent Shows Offline: Step-by-Step Diagnosis. |
Need Help?
If data doesn't appear after 24 hours, contact support@seqops.io or use the Contact Us page. Include the provider or server name, the host operating system, and the exact error message.
verificationfirst scanonboardingtroubleshootingtiming