Prepare your environment
Choose an agent host and a permitted target. Confirm network access, the target listener and the operating-system account permissions.
CUVENA / RESOURCES
A clearer path from setup to execution.
Understand the architecture, prepare your environment and verify your first run.
YOUR FIRST VERIFIED EXECUTION
Start with one agent.
One target. One clear result.
Pair and configure the agent
Install the appropriate agent, pair it with your workspace and assign its pool. Add the exact permitted target address in execution settings.
Choose the account roles
Assign the connection account to the agent. Select the agent account or a separately authorized task account for execution.
Publish a simple verification script
Use a script that writes a known file or returns a clear result. Desktop windows are not a reliable verification method for background execution.
Test the connection, then run
Inspect each connection-test stage. Run the task once the checks succeed, then verify the output and intended change on the target.
A FEW IMPORTANT DETAILS
Questions,
answered.
Can agents update without a desktop prompt?
After a one-time v44 administrator or root installation, signed updates can be requested for selected agents. Platform admins control customer offers; customer owners and administrators can update their own agents. The updater waits for work to finish, verifies the new heartbeat and attempts rollback on failure. Operating-system policies still apply.
Where do scripts execute?
On the selected target servers through your execution agents. Cuvena provides central management, dispatch and visibility.
Do I need the same account for the agent and the task?
No. You can use the agent connection account or assign a separate task account, provided the account is authorized and the target permits the requested execution.
Can I use credentials stored on the agent?
Yes. Agent managed account details appear in the platform, while the password remains in the protected local vault. Centrally managed accounts are managed in Cuvena.
Will a script open a window on my desktop?
Background execution does not display application windows in the signed-in user’s desktop session. Verify returned output or the intended file or system change.
What happens if the connection is lost?
An execution can require outcome verification when completion cannot be confirmed. Review the result before retrying uncertain work to avoid running a script twice.
SUPPORT WITH ACCOUNTABILITY
Troubleshoot together.
Keep responsibility clear.
Cuvena support workspaces let authorised platform staff investigate an organisation without asking for a customer's password or replacing their login.
Standard access requires customer approval by default and starts read-only. Platform owners and separately authorised privileged support staff can investigate without an individual customer approval. Platform owners are not required to use an authenticator for support access. Both modes identify the staff member and record activity in the organisation and platform audit logs.
Read how support access worksACCOUNT ACCESS
Precise permissions. Practical recovery.
Platform owners can assign detailed Admin roles to administrators and support staff. Optional authenticator setup includes a scannable QR code and single-use recovery codes. Enabled authenticator protection is enforced at sign-in.
Read the access and recovery guideCUVENA SCRIPT MANAGER