Spiceworks On- Prem Inventory Agent: Documentation“Wait,” you say, “I thought Spiceworks has an agent- free scanner… Why an agent?” That’s true, Spiceworks can be used without any. Just set up your scan ranges and admin accounts and maybe do a little firewall tweaking and you’ll be set. But, maybe you’d. That also works. Or you can do a combo of the. You’ll also find agents to be useful for devices that are off- network a lot. The agent will handle the scanning, then update. Spiceworks once it’s reconnected to the network. Download the agent. You can find the agent under Settings → Inventory → Remote Sites & Agents → Manage Your Devices with Remote Agents. Or you can just download it here (as long as you aren’t installing it on Windows XP… if you. Why are there 2 versions of the agent? In order to support TLS 1. On-Premises Inventory Agent. You can find the agent under Settings → Inventory → Remote Sites & Agents → Manage Your. Server 2012; Windows XP SP2+ Windows. Part 7: Create Delivery Group; Citrix XenApp 7.6 Install. of the Remote Desktop limit on client operating. do not support Windows 2012 R2. ![]() Net version used by the agent (now. NET 4. 5). Windows XP does not support . NET 4. 5, so this new secure agent will not work on that operating system. So. Spiceworks includes both versions now. Unfortunately, the old agent cannot automatically update to the new, secure agent, so you will. XP device agents to this new version. You’ll only need to do this once though. Once they’ve been. In fact, it will be more efficient in that you don’t even need to be running the. Spiceworks versions from now on will automatically pull the latest. You’ll also see a colored dot next to your agents under Settings → Inventory → Remote Sites & Agents → Manage Your. Devices with Remote Agents to help you determine their status. Yellow: This agent is out- of- date and needs to be updated. Most likely, you’ll need to manually install the agent on the device to. XP agent. Gray: This agent is the final version of the XP agent. If this is not an XP device, you should update to the new secure agent. Green: This device has the newest version of the secure agent. Rejoice. System requirements. The following requirements are for the machine where the agent will be installed. The agent will only work on Windows machines. Server 2. 00. 3 SP2+Server 2. Server 2. 01. 2Windows XP SP2+Windows Vista. Windows 7. Windows 8 (and 8. Net has client and full versions. The agent will only work on the full version of . Net. You can check which version you have. Windows Program Manager (Programs and Features). Multiple versions can coexist on the same machine. If you only. need . NET installed for the agent, we recommend simplifying by installing . NET 4. 5 or the latest version supported by your OS. Installation instructions. If you are just installing a couple of agents, it may be easiest to just do this manually. To install the agent you need to log in as. Access and log in to your Spiceworks installation. Navigate to Settings → Inventory → Remote Sites & Agents → Manage Your Devices with Remote Agents. Click the button to Download Agent for . NET 4. 5 and up (unless you are installing on XP devices). This will save the agent. Spiceworks installation to the desktop of the device. On your central installation, you’ll need to set up an authorization key and set your scan interval under Remote Agent Settings. On the device where the agent is to be installed, run the installer. After agreeing the terms of use, you will be presented a. You need to enter the Spiceworks central server FQDN or IP address and HTTPS port number, as well as the. You have the option to add a client port, but it is not a required field. You can. also indicate whether you want the tray icon installed or not, and where the tray url should point to. You can find the HTTPS port number that you need to enter by right- clicking on the Spiceworks tray icon of your Spiceworks. Preferences. Deploying the agent. Installing the agent using PDQ or similar. You can use PDQ Deploy to install, update, uninstall and reinstall the Spiceworks agent. Note that when creating an admin agent. At this time, the only way to get the encrypted value. GUI method (using the plain text authorization code), then navigate to the registry to lookup. If you choose to deploy the agent in this manner, make sure you configure the agent settings from within. Spiceworks first; you’ll need your authorization code when deploying. MSI Command Options: SPICEWORKS_SERVER: You’ll need to enter the fully qualified domain name of your Spiceworks server here. SPICEWORKS_PORT: This is the port your Spiceworks installation is running on (generally 4. SPICEWORKS_AUTH_KEY: This is the value you set in your Spiceworks installation. SPICEWORKS_SITE_LABEL: This is used to name your remote site installation if the agent is reporting to it. ADDLOCAL: You would use this to run the agent as a service and install the tray icon. TRAY_CLICK_LABEL: This is the name displayed on the tray icon for your end users. TRAY_CLICK_URL: When your users click the tray icon to go to your help desk, this is where they will be taken. You will also. need to follow up this command with a semicolon after the quotation mark (see the example MSI command below). So your MSI would look like this: msiexec. Spiceworks Agent. SPICEWORKS_SERVER="server- name. SPICEWORKS_PORT="4. SPICEWORKS_AUTH_KEY="encrypted- auth- code" ADDLOCAL="Feature. Service,Feature. Tray" TRAY_CLICK_LABEL="Help Desk" TRAY_CLICK_URL="https: //spiceworks- server. Other resources. Configuring the agent (from Spiceworks)After agents are installed, you have a few configurable options from your Spiceworks installation. You can access these settings. Settings → Inventory; → Remote Sites & Agents → Remote Agent Settings: Authorization Code: Here you’ll need to set up the key that your agents use to authenticate with your Spiceworks installation. If you’ve already set up agents, though, you won’t ever need to mess with this. Scan Interval: Set how often you want the agents to scan and report back to your central installation. The default value is. Connectivity Check Interval: This configures how often the agent will check to see if it can connect to the Spiceworks sever. NOTE: If you are using a large amount of agents on your network, having a low connectivity check interval can cause performance. Try raising this to a higher number. Custom Icon: The agent will place a tray app on the remote computer. If you want to use your own icon rather than the. Spiceworks logo, you can upload it here. Note that the icon can take up to 5 minutes to update. Configuring the agent (from the agent)If you are signed in, as an admin, to the computer containing the agent, you can make configuration changes directly from there. Right- click the tray icon to bring up the following options: About: See what version of the Spiceworks agent you are running. Open Help Desk: This will connect to your Spiceworks installation’s user portal (this is always available from the tray icon. Administration: These options will only be available to admin- level Windows profiles: Config: This will bring up the configuration options you had when initially setting up the agent, including Central Server. You can also gain access to the logs from here. Service: Here you have the option to stop, start, and restart the Spiceworks agent service. Scan now: Immediately start a scan of the device. Exit: Click the exit link to exit the tray app. Note that this will not stop the agent, only close the tray app. How do I update the agent? You don’t even need to. How awesome is that? When the agent heartbeats to the Spiceworks Community servers, it will automatically. If there is, it will automatically update. Using the agent with remote site installations. If you’re using the Spiceworks Agent in conjunction with remote site installations, please. When installing the agent, just connect the agent to the remote site installation’s FQDN or IP address. Please note these important points: The authentication code still needs to be configured on the central installation under. Settings → Inventory → Remote Sites & Agents. You don’t need to set up the authentication code on the remote sites. Download the agent installer from your central installation and follow the same installation instructions as above. The connectivity interval, scan interval,and tray icon also needs to be set up on the Central Installation rather than the Remote. Site. I’m having connectivity issues. When you’re setting up the agent, the device the agent is installed on is going to need to be able to connect to the device where. Spiceworks installation is installed. You can test this connectivity by just opening a browser and attempting to navigate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |