ITAutomated is a Windows administration application that brings Citrix, Active Directory, Remote Desktop Services licensing, diagnostics, reporting and controlled engineering workflows into one consistent interface.

It is designed to reduce the need to move between disconnected consoles and scripts while preserving the permissions and controls already present in your environment.

ITAutomated is intended for authorised Citrix, EUC, VDI, Active Directory, infrastructure and support engineers, as well as managed service providers responsible for enterprise Windows environments.

It is not intended for general end users or for administrators who have not been delegated the permissions required by the selected module.

No. ITAutomated complements the supported Citrix and Microsoft administration platforms. It provides a unified workflow layer for common operational tasks, diagnostics and reporting, but your organisation should retain the native consoles for platform configuration, vendor support and specialist operations.

ITAutomated is currently a 64-bit Windows desktop application. It runs from an approved administrator workstation or management server and connects to the services that the signed-in administrator is authorised to use.

Yes. Beginning in read-only mode is recommended. Searches, environment summaries, diagnostics, reporting and preview workflows can be used before live administration is enabled or approved.

Actions that can change a platform should be limited to delegated administrators and should always be reviewed through the available confirmation or preview controls.

Current modules are designed for Windows-based enterprise environments and include support paths for Citrix DaaS, supported on-premises Citrix Virtual Apps and Desktops deployments, Microsoft Active Directory, DNS, RDS licensing and Windows administration services.

Individual capabilities depend on the SDKs, RSAT components, network access and permissions available on the computer running ITAutomated.

A new installation starts with a seven-day Pro trial. During the trial, the Pro administration modules are available so that the product can be evaluated against your own authorised environment.

The trial begins on first use and is associated with the local installation state.

When the Pro trial expires, the administration modules require a Starter or active Pro licence. The Free experience remains available for the product overview and licence status.

Your local configuration is not deliberately erased when the trial ends. Activating a valid edition restores the capabilities included with that edition.

The final commercial feature matrix displayed on the pricing page and purchase agreement takes precedence if editions change in a future release.

Purchased licence keys are issued for the computer ID displayed by ITAutomated. This prevents one licence from being copied across multiple unlicensed computers.

Use the computer ID shown in the product licence panel when purchasing or requesting a replacement licence.

1. Deactivate the licence on the old computer where possible.
2. Install the complete ITAutomated package on the new computer.
3. Copy the new computer ID from the licence panel.
4. Request a reissued licence for that computer ID.
5. Activate the replacement key on the new computer.

Do not expect a key issued for the old computer to activate on a different computer.

Current builds validate the signed licence key locally and confirm that it was issued for the displayed computer ID. The purchase or licence-delivery process may still require internet access, but entering a valid supplied key does not rely on storing your environment credentials.

An active Pro subscription includes software updates, fixes and new releases. Starter provides perpetual access to the purchased version but does not include ongoing updates or support unless a separate entitlement is stated in the purchase agreement.

ITAutomated protects trial and subscription status against significant backwards changes to the Windows clock. Correct the date, time and time-zone configuration, synchronise the computer with an approved time source, and then restart the application.

Do not attempt to bypass clock validation. Contact support when the system time is correct but the warning remains.

The complete Windows x64 package contains the full application and is required for a new installation or recovery.

The smaller incremental update package contains only the files required to update a compatible existing installation. It must not be used as a new installation.

No separate .NET Desktop Runtime is normally required for the published self-contained Windows x64 build. The required runtime components are included with the complete package.

Citrix SDKs and Microsoft RSAT components remain separate prerequisites because they provide access to the platforms being administered.

Use a stable local folder that the administrator can read and update, for example:

C:\Program Files\ITAutomated

For an early test or where change control prevents use of Program Files, an approved local applications folder may be used. Do not run the production application directly from Downloads, a temporary folder or inside the ZIP file.

Local administrator rights may be required to place files under Program Files, install SDKs or RSAT, and configure machine-level prerequisites. Normal day-to-day application use should follow your organisation’s least-privilege policy.

Platform administration permissions are separate from local Windows administrator rights.

First confirm that the package came from the official ITAutomated download location and verify the supplied file hash where available. Your security team may need to approve the package or allow the signed publisher.

Do not disable SmartScreen, antivirus or endpoint protection across the computer merely to run the application.

1. Confirm that the current licence includes updates.
2. Download the incremental update ZIP for a newer compatible version.
3. Open the update function in ITAutomated and select the ZIP.
4. Allow the package manifest and file hashes to be validated.
5. Close the dashboard when prompted so the updater can replace the files.
6. Confirm the new build number after ITAutomated restarts.

The update workflow creates a local backup of the files it replaces. If the update cannot complete, the updater attempts to restore the previous files and relaunch the earlier version.

Keep the complete recovery package available for the installed release and do not delete update backups until the new version has been validated.

Close the application, remove the approved application folder or use the installer removal option when one is provided, and then remove local settings only when a clean reset is required.

Before deleting local data, retain any logs, exported reports and licence information required for audit or support.

Yes. ITAutomated can use the Citrix DaaS Remote PowerShell SDK installed on the administration computer. The signed-in administrator must have an authorised Citrix Cloud profile and suitable delegated permissions.

Supported on-premises CVAD environments can be accessed through the installed Citrix PowerShell SDK or snap-ins. Availability depends on the CVAD version, installed management components, network access and permissions.

Test the connection in a non-production or read-only workflow before enabling live operations.

Install the Citrix DaaS Remote PowerShell SDK for Citrix Cloud environments or the supported Citrix management PowerShell components for an on-premises site.

ITAutomated detects the available SDK mode. It does not replace missing Citrix management modules.

Use Sign in to Citrix from the Overview page when a Citrix DaaS authentication profile is not already available. Complete the authorised Citrix authentication flow, then select Test Citrix connection.

The connection test should display the detected SDK mode, site or environment and read-only resource counts.

Permissions depend on the selected operation. Read-only dashboards require visibility of the relevant Broker objects. Session actions, publishing and configuration workflows require the corresponding delegated Citrix administrator rights.

ITAutomated does not grant additional Citrix permissions. The platform still enforces the identity and role used by the administrator.

No, Director is not required for the core Broker SDK inventory, machine, delivery group, application and session workflows.

Some advanced historical or performance telemetry may depend on separate monitoring data, API access or platform availability. When that data source is unavailable, ITAutomated should clearly identify the limitation rather than invent a value.

Common causes include delegated scope, an empty object type, a different customer or site context, an unavailable optional API, or a module that needs additional permissions.

Confirm the site name, compare the result with the native Citrix console using the same account, review the local logs and test a broad read-only page such as Overview or Delivery Groups.

• Confirm the correct Citrix SDK is installed and discoverable in Windows PowerShell 5.1.
• Complete the Citrix sign-in flow again.
• Verify internet, proxy and TLS access for Citrix DaaS.
• Confirm the account has access to the intended customer and site.
• Check whether endpoint security blocked PowerShell or the Citrix modules.
• Open the local logs and record the exact error.

Install only the RSAT features required by the modules you will use. Active Directory workflows typically require the Active Directory PowerShell module. DNS workflows require the DNS Server tools, and some remote diagnostics require CIM, WMI, WinRM or Remote Registry access.

A domain-joined administration computer is the recommended configuration because it simplifies integrated authentication, DNS discovery and access to trusted management services.

Some cross-domain or workgroup scenarios may be possible with explicit infrastructure and credentials, but they require separate validation and are not the default support path.

Read-only searches require directory read access. User, group, computer or DNS changes require the exact delegated rights for the target objects and zones.

Destructive operations remain subject to Active Directory protection, permissions and ITAutomated confirmation controls. Always preview the proposed action first.

Potentially, provided name resolution, trust, firewall rules, RSAT and delegated access are correctly configured. Specify the target domain or server where the workflow provides that option.

Validate cross-domain operations with read-only searches before attempting a live change.

Open Settings, locate the RDS licensing configuration and add each authorised licence server by name or FQDN. Test access and then open the Licences page to load the available licence packs and utilisation.

Only supported Windows Server licence generations are included in the product summaries.

• Confirm the server name resolves from the administration computer.
• Verify the Remote Desktop Licensing service is running.
• Check firewall, DCOM, WMI/CIM and RPC requirements.
• Confirm the administrator has permission to query the server.
• Compare the result with Remote Desktop Licensing Manager.

Those checks query the target Windows computer rather than only the directory or Citrix broker. The target must permit the required CIM, WMI, WinRM, event log, service or file-system access.

A blocked remote check should be reported as unavailable or unverified; it does not necessarily mean that the server itself is unhealthy.

ITAutomated is designed to use the current Windows security context and supported platform authentication profiles wherever possible. It should not place passwords, tokens or complete request payloads into operational logs.

Never paste credentials into a general notes, search or support field.

The local licence state is protected for the current Windows user and the purchased key is validated using a digital signature and the computer ID.

Copying the protected local state to another user or computer does not create a valid licence for that computer.

Core administration queries run from the local application against the configured services. Environment data is not automatically published as public data.

Exports, diagnostic attachments or support submissions leave the computer only when an authorised administrator deliberately saves or sends them.

Internet access is required for services that are themselves online, such as Citrix DaaS authentication, approved update checks, downloads or online support. Local Active Directory, DNS, RDS and on-premises Citrix operations can remain within the organisation’s network when their dependencies are internal.

ITAutomated provides local operational logging and structured results intended to record success, warning and failure information without exposing secrets. Your organisation should combine these logs with native Citrix, Active Directory, Windows and security audit records.

High-impact workflows should use preview or dry-run output, explicit confirmation, restricted controls and a final result. The underlying platform permissions and protections continue to apply.

A preview is not a substitute for backups, change approval or testing.

Yes. PowerShell execution, remote administration modules, temporary scripts, WMI/CIM and application updates may be inspected or blocked by endpoint security.

Use documented, narrowly scoped exclusions only after review by your security team. Do not disable protection globally.

1. Confirm that the complete package was fully extracted.
2. Run the executable from a stable local folder.
3. Check Windows SmartScreen, antivirus and endpoint-security events.
4. Confirm the operating system is supported and 64-bit.
5. Re-download the package and verify its hash.
6. Review Windows Application event logs for the exact failure.

Wait for the current operation to finish, then use the page refresh or cancellation control. A slow platform query, missing SDK, restricted permission or unreachable server may delay only that module.

Open the logs, capture the page name and timestamp, and confirm whether another read-only page still works.

The component may not be installed for Windows PowerShell 5.1, may be installed only for another architecture, or may not be discoverable in the current module path.

Open Windows PowerShell 5.1 as the same user, import the required module and confirm that its supported read command works before retesting ITAutomated.

The signed-in identity reached the service but does not have permission for the requested object or operation. Confirm the account, delegated scope, target server and whether the action needs elevation.

Do not solve a narrowly scoped permission issue by granting broad domain or full Citrix administrator access without review.

Use the Open logs button from the application where available. Also record the ITAutomated build number, current Windows user, affected module, target environment, time of failure and the complete visible error.

• ITAutomated version and licence edition
• Windows version and whether it is a workstation or server
• Affected module and exact action
• Expected result and actual result
• Exact error text and timestamp
• Relevant screenshots with secrets removed
• Sanitised logs or exported diagnostics
• Business impact and whether a workaround exists

Free and Starter customers use the published self-service documentation unless a separate support agreement applies. An active Pro subscription includes basic product support during the entitlement period.

Platform incidents, architecture consulting and emergency response may require a separate service agreement.

Use the Support page and describe the operational problem, who experiences it, the current manual process, desired outcome, security considerations and expected business value.

A requested feature is not committed until it appears in an approved roadmap or release note.

Review the System Requirements, Installation Guide and Getting Started page, then collect the support information listed above.

Open the ITAutomated Support Centre to choose the appropriate documentation or support-request path.