Skip to content

Configuration Profiles ​

Use configuration profiles to check and maintain desired endpoint settings. Create the profile in Library → Configuration Profiles, assign it to devices, and choose whether to report differences or correct them.

Profile types ​

Ordyn Agent Settings ​

Manage Remote Access, unattended access, and logging centrally. Leave fields Not managed when local choices should apply. Enforced values take precedence over local settings; audit-only checks report differences without changing them.

Logging applies to Windows and Linux; Remote Access settings apply to Windows. See Agent Configuration for local settings and Remote Access for consent.

Windows Update Policy ​

Configure the update source, installation schedule, deferral, restart behavior, and user access to Windows Update. Use Windows Updates to coordinate these settings with ring approvals.

Blocking Windows Update user access applies to interactive administrators too, while Ordyn jobs can still install updates. Notification settings affect visibility, not installation or reboot timing.

Quality-update deferral delays when Windows offers an update. Leave it unmanaged to preserve the endpoint's setting, use zero for no deferral, or choose up to 30 days. A scan during deferral can report no missing updates without proving that all published updates are installed.

Windows Delivery Optimization ​

Control peer sharing for Microsoft content independently from update approval. Choose direct HTTP downloads, local-network peers, or a private peer group. Private groups require the same group ID on participating endpoints.

Set cache and VPN sharing limits to suit the network. When GPO, MDM, or another tool controls Delivery Optimization, resolve that ownership before using Ordyn remediation.

Windows Firewall Policy ​

Enable or disable the Domain, Private, and Public firewall profiles that Ordyn should manage. Leave other profiles unmanaged. This controls firewall state, not individual rules.

Windows Firewall Rules ​

Audit or enforce each endpoint's active local rule policy. Import its rules first, then assign this profile. Editing rules in Ordyn takes effect on the device only when the profile runs.

See Windows Firewall Rules for unsupported rules and connectivity precautions.

Windows Security Policy ​

Manage Windows authentication, credential protection, UAC, and Remote Desktop safeguards. Select only settings Ordyn should own; other management tools can overwrite them and cause recurring drift. Microsoft Defender is inventory-only.

Test authentication and remote-access restrictions before broad deployment. UEFI-locked protections require local firmware changes to remove; Ordyn cannot remotely unlock them.

Some changes require a restart. Ordyn reports the requirement but does not restart the device automatically. Cached-logon policy is incompatible with domain controllers.

Windows SMB Hardening ​

Manage SMB client and server safeguards, including protocol compatibility, signing, encryption, and guest access. Test against the file servers and clients in use before enforcing stricter settings.

Modern dialect limits, client encryption enforcement, NTLM blocking, auditing, and authentication-delay settings require Windows 11 24H2 or Windows Server 2025 and the relevant Windows support. Profiles selecting unsupported settings cannot be applied to older devices.

Changing SMB1 client configuration requires a restart; plan that separately.

Windows Energy Policy ​

Set display, sleep, and hibernation timeouts for plugged-in and battery operation. Use Never when the transition should not occur.

Remediation activates an Ordyn power plan. Removing the assignment does not restore another plan; apply the desired plan explicitly. The profile does not enable sleep or hibernation when the device cannot perform that transition.

Firmware / BIOS Policy ​

Audit or enforce supported Dell firmware settings, such as Secure Boot, Wake on LAN, or virtualization. Supported devices need Dell's agentless BIOS interface; release year alone is not a compatibility guarantee.

For password-protected changes, set the endpoint's effective hardware.firmware.password secret. Audit-only checks do not require it. The profile does not change the BIOS password; use the BIOS password task for that.

Firmware changes can affect boot and recovery and may require a restart. Test representative devices before deployment and schedule any restart explicitly.

Intel AMT ​

Choose control mode, network configuration, consent, and power settings. Remediate can provision a ready unmanaged device; external configurations require adoption first.

Disabling the profile stops AMT management and certificate maintenance. Removing an assignment leaves firmware configured. Follow Intel AMT management for provisioning, adoption, recovery, and deprovisioning.

Custom Script ​

Use a check script and a remediation script when built-in types do not cover the desired state. Define the typed fields and desired values the scripts will use.

Both scripts must target endpoints on the same platform and must not declare parameters. Use a supported script interpreter. Test the check and remediation on representative endpoints before broad assignment.

Assignments ​

Assign profiles from a tenant, endpoint folder, group, or endpoint. Edit inherited assignments at their source scope. Choose Audit only to report drift or Remediate to correct it, then configure when the profile should run.

The effective assignment supplies behavior and automation. Windows Security Policy, SMB Hardening, Energy Policy, and Intel AMT each allow one effective profile of their type; more specific assignments take precedence. Review the effective profile on an endpoint when assignments overlap.

For Intel AMT, precedence is endpoint, group, nearest folder, then tenant; remediation takes precedence over audit at the same scope.

Behavior ​

Audit-only checks leave settings unchanged. Remediation checks first and applies the desired state when needed. Run a check before enabling broad remediation.

An assignment without automations is manual-only. Intel AMT uses its lifecycle schedule rather than the assignment automations below.

Disable a profile for an endpoint ​

Disable a profile when it should remain assigned but stop running on a particular device. Enable it when the exception ends. Disabling does not undo settings already applied.

For types that allow one effective profile, disabling applies to that type even if another assignment becomes effective. For other types, it applies to the selected profile.

Use profile state tasks when a maintenance job needs to suspend checks. Disabling Intel AMT also stops its communication and certificate maintenance without deprovisioning firmware.

Assignment automations ​

Run a profile when its assignment becomes effective, on recurring schedules, or after system boot or Windows logon/logoff. Use random delay to spread work across a fleet.

Recurring schedules ​

Choose a cron expression and timezone. Enable catch-up on reconnect for offline devices when needed; missed times produce one deferred run, not a backlog.

Device events ​

Logon/logoff means a Windows console or RDP session starts or ends. Locking, unlocking, and RDP reconnection do not count. Boot checks depend on a new boot reported by the Agent.

A script using the current active user context runs for the console user active when execution starts, which may differ from the person whose logon triggered it. Do not use that context when the job must act on the triggering RDP session.

Endpoint view ​

Review the effective assignment and result on the endpoint's Configuration Profiles tab. Inspect differences, errors, and restart requirements before remediation. A missing or failed check does not establish compliance.

Profile view ​

Use a profile's Endpoints view to review its affected devices and run a check across them before rollout.

Compliance states ​

Compliant means the last check matched the desired state. Drifted means it found differences. Error means the check could not establish compliance. Check the collection time and resolve errors before relying on a result.