From
the Service Home
page - the Connected icon will show 
if muted
From the Asset dashboard - in the information for the asset
From the Configuration application, Asset wizard
When an asset is muted, all communications between the Platform and that asset are blocked. Any messages the Platform may have to send to that asset are neither sent nor retained by the Platform. Likewise, any messages the asset may send are blocked and not retained. Assets can be muted and unmuted from the Axeda Applications, Asset dashboard.
The ability to mute assets can be useful to a variety of business cases. Some Platforms may have deployed agents that don't communicate often and, when they do come on line, may send inaccurate or unnecessary messages. Also, the ability to mute an asset can be the key to troubleshooting issues with that asset or agent. If you question the amount of data an agent is sending or the frequency with which it is communicating with (and sending data to) the Platform, you can mute that asset. Immediately the messages to and from the asset will stop, giving you or your Platform administrators time to troubleshoot the current communications, data volume, and data rate settings. While an asset is muted, neither the Platform nor the related agent will retain any messages that were intended for communications. When ready, you can unmute the asset: this will reinstate communications immediately. To the Applications user it will appear as if there had been no interruption in communications.
To mute an asset, a user must have access and privileges to modify the asset (Service - Asset Muting). From the Asset dashboard you can mute or unmute the asset as needed.
You can determine if an asset is muted in the following ways:
From
the Service Home
page - the Connected icon will show if muted
From the Asset dashboard - in the information for the asset
From the Configuration application, Asset wizard
Administrators will be able to scan the Audit log to determine if and when an asset is muted or unmuted. (Muting activity is defined in the Audit log - System Configuration category.) When a Managing Gateway is muted, all managed assets are muted as well and an audit entry is created for each mute/unmute operation for a managed asset.
If an asset is configured to be managed by a Gateway then that individual asset cannot be muted. For this asset, the mute and unmute operations in the Asset Dashboard are disabled. To mute a managed asset you must mute the managing Gateway (from the Asset dashboard for that managing Gateway).
When an asset is muted, you cannot perform the following functionality for that asset:
Deploy or redeploy packages to that asset
Start remote sessions for that asset
Upload files to that asset (exceptions exist for assets managed by redundant gateways)
Download files to that asset (exceptions exist for assets managed by redundant gateways)
Run or register scripts on that asset
Run tasks on that asset, with the exception: Edit this Asset, Add this asset to watch list, and E-mail asset
For the most part, these commands and the links to view them (via the View All links in the related modules in the Asset dashboard ) will be disabled when an asset is muted. Also, functionality for these operations available in the related application (such as Configuration or Software) is also disabled. See the help for those operations for more information.