free for apple download Lansweeper 10.5.2.1

In the resulting pop-up, select the State field, choose your preferred asset state for the assets you selected and select Change Field(s).

Go to the Assets section of the web console, tick the checkboxes in front of the assets of your choice and select Mass Edit Assets under Asset Actions.Select an asset state from the dropdown and select Save asset. Browse to an asset's detailed page and select Edit asset under Asset options.Try one of the following options to change an asset's state, depending on whether you want to update a single asset or multiple assets at once: The state is now included in any state dropdowns within the web console. Enter a state name into the State Name field of the pop-up window.Select Add Asset state in the Asset States section of the page.

Browse to the Configuration > Asset Pages section of the web console.Assets with a state other than 'active' can be found through the search bar as well and in the list in the Assets section of the web console. This article explains how you can create your own asset states, change an asset's state manually or change an asset's state through automated cleanup options. Reports found in the Reports tab of the web console can also be modified to list machines with other states. Setting a machine to another state is therefore a good way to ignore the asset and remove it from overviews, without fully deleting the machine from your database. Most built-in reports and pages only list machines whose state is set to 'active'. There are built-in states, but you can create your own as well. However, this state can be changed, either manually or by enabling automated cleanup options. By default, a machine's state is set to 'active'.

States are a Lansweeper feature that allow you to keep track of which machines are active in your network, which have been decommissioned, which are in stock etc. Every scanned or manually created computer and device in Lansweeper has an asset state.

Free for apple download Lansweeper 10.5.2.1