You open the Outlook Rules Wizard, create a new rule, and see the message “On this computer only” next to certain conditions or actions. This label appears because some rule components rely on local hardware, software, or data that cannot be processed by the Exchange server. Understanding why this limitation shows helps you decide whether to use the rule as-is or find an alternative approach that works across all your devices.
The “On this computer only” indicator is not an error. It is Outlook’s way of telling you that the rule will run only on the machine where you created it. If you use Outlook on another computer or mobile device, the rule will not execute there. This article explains the technical reasons behind this limitation, lists the specific conditions and actions that trigger it, and provides practical steps to manage or work around these rules.
You will learn how to identify which parts of your rule are local-only, how to test whether the rule still functions as intended, and what to do if you need the same behavior on multiple devices.
Key Takeaways: Understanding and Managing Local-Only Outlook Rules
- Rules Wizard > Conditions or Actions marked “On this computer only”: Identifies rule components that depend on local resources like printers, folders, or software that the Exchange server cannot access.
- File > Info > Manage Rules & Alerts > Rule Properties: Check the rule’s status to see which conditions or actions are marked as local-only and whether the rule is enabled for all devices.
- File > Options > Mail > Rules and Alerts > Run Rules Now: Manually trigger a local-only rule to test its behavior without waiting for incoming mail.
Why Outlook Shows “On This Computer Only” for Certain Rule Components
Outlook rules can run either on the Exchange server or on your local computer. Server-side rules process messages before they reach your inbox, which means they work regardless of which device you use to access your mailbox. Client-side rules, on the other hand, execute only on the computer where Outlook is installed because they rely on local resources that the server cannot see or control.
The “On this computer only” label appears when you select a condition or action that requires access to something stored or running on your local machine. Common examples include moving messages to a local PST file, printing a message, running a script, or showing a desktop alert. The Exchange server cannot perform these actions because it has no access to your local file system, printer, or application runtime.
This behavior is by design. Microsoft separates rule components into two categories: server-side and client-side. Server-side components are available in all Outlook clients connected to the same Exchange account. Client-side components run only on the computer where the rule was created. The Rules Wizard displays the warning to prevent confusion when the rule does not fire on another device.
Server-Side vs Client-Side Rule Components
Server-side conditions include common triggers such as “from a specific person,” “sent directly to me,” or “with specific words in the subject.” Server-side actions include “move to a folder in your mailbox,” “delete it,” or “forward it to a distribution list.” These components process on the Exchange server and work across all your Outlook clients.
Client-side conditions include “with specific words in the message header” and “with specific words in the recipient address.” Client-side actions include “print it,” “play a sound,” “move it to a folder in a personal folders file PST,” “run a script,” “display a specific message in a new window,” and “show a desktop alert.” Any rule that mixes server-side and client-side components runs entirely on the client side. This means even the server-side parts of a mixed rule will not execute until Outlook is running on the computer where the rule was created.
Steps to Identify and Manage Local-Only Rules
Follow these steps to see which rules are local-only and to verify how they behave.
- Open the Rules and Alerts dialog
In Outlook, go to File > Info > Manage Rules & Alerts. This opens the Rules and Alerts window where all your rules are listed. - Review the rule list for the local-only icon
Each rule has an icon next to its name. A rule with a small computer icon and the text “(this computer only)” is a client-side rule. Rules without this icon are server-side and run on the Exchange server. - Double-click a rule to inspect its components
Select a rule and click Change Rule or double-click the rule name. The Rules Wizard opens and shows each condition and action. Any step marked with “(on this computer only)” is a client-side component. - Test the rule manually
Go to File > Options > Mail > Rules and Alerts > Run Rules Now. Select the rule you want to test, choose the folder to apply it to, and click Run Now. This lets you verify the rule behaves correctly on your current computer. - Check rule behavior on another device
Log into Outlook on a different computer or the Outlook mobile app. Send a test message that should trigger the rule. If the rule does not fire, it is a client-side rule that only runs on the original computer.
How to Convert a Local-Only Rule to a Server-Side Rule
If you need a rule to work on all your devices, replace the client-side condition or action with a server-side equivalent. For example, instead of using “move to a folder in a personal folders file PST,” create a folder in your Exchange mailbox and use the “move it to a specified folder” action. Instead of “display a specific message in a new window,” use “forward it to a distribution list” or “have it replied to using a specific template.” If the action has no server-side equivalent, you must accept that the rule will run only on the original computer.
If Outlook Still Shows the Limitation After Removing Local Components
Sometimes the “On this computer only” label persists even after you remove all client-side conditions and actions. This happens when the rule was originally created as a client-side rule or when the rule contains a hidden client-side component.
“I removed the local action but the rule is still marked as client-only”
Outlook caches the rule type when you first create it. If you add a client-side component and then remove it, Outlook may still treat the rule as client-side. To force a reset, delete the rule entirely and recreate it using only server-side components. Do not add any client-side condition or action during the creation process.
“The rule works on one computer but not on another”
This confirms the rule is client-side. Go back to the Rules and Alerts dialog and check the rule icon. If it shows the local-only icon, the rule will never run on another device. Create a duplicate rule on the second computer using the same server-side conditions and actions. Each computer needs its own copy of the rule if you want the same behavior everywhere.
Server-Side vs Client-Side Rules: Key Differences
| Item | Server-Side Rule | Client-Side Rule |
|---|---|---|
| Execution location | Exchange server | Local computer where Outlook runs |
| Works on other devices | Yes | No |
| Requires Outlook to be open | No | Yes |
| Can use local resources | No | Yes |
| Example actions | Move to mailbox folder, delete, forward, reply with template | Print, play sound, show alert, run script, move to PST |
You can now identify which rules in Outlook are client-side and understand why the “On this computer only” limitation appears. Use the Run Rules Now feature to test local rules on your primary computer. If you need the same rule on multiple devices, recreate it with server-side components only. For actions that have no server-side equivalent, such as printing or running a script, keep the rule on the original computer and accept its single-device limitation.