Advertisement
This is a how-to explaining the settings associated with the Windows Spiceworks Agent (MSI). With this information, you should be able to deploy the agent in a number of scenarios, including SCCM, PDQ Deploy, PSExec, batch files, etc.<\/p>\n
See the references at the bottom for deploying the agent via GPO. Yes, it involves using Orca, an MSI editor, but it’s not terribly hard…!<\/p>\n
NOTE: This documentation was written some years ago, so the location from where you would download the MSI might change by the time you read this.<\/p>\n
Pre-requisites:<\/p>\n
The Windows client must have Dot Net 3.5 SP1 installed prior to deploying the agent.<\/p>\n
Since the SW Agent is an MSI, the installer itself has a number of parameters available to you.<\/p>\n
To find out what those are, run ‘msiexec.exe /?’ and take a look at the command-switches available. Alternatively, review the following Microsoft website: Command-Line Options - Win32 apps | Microsoft Learn<\/a><\/p>\n However, remember that the agent requires various parameters specific to itself in order to install properly. If you try and use, say, the “passive” switch with msiexec, the agent will fail since it requires some options like the Spiceworks server address, port, authentication key, etc. to install properly.<\/p>\n<\/div>\n *THE LOCATION OF THE MSI MAY CHANGE OVER TIME, so be aware<\/p>\n To find the MSI, open up your Spiceworks instance, hover over either the ‘Inventory,’ ‘Help Desk,’ or ‘Purchasing’ menu items > ‘Settings’ (this tends to change from version to version) - or look for ‘Remote Settings.’<\/p>\n Below ‘Additional,’ click the ‘Remote Sites & Agents’ link.<\/p>\n Look for the section called “Manage Your Devices With Remote Agents,” the link for the MSI should be below, entitled “Download the remote agent for this installation.”<\/p>\n Save this MSI somewhere handy for your computers/users to install.<\/p>\n<\/div>\n Here we go:<\/p>\n This install scenario would assume the following:<\/p>\n These are the parameters you need to configure:<\/p>\n SPICEWORKS_SERVER=“spiceworks.yourdomain.com<\/a>” So, how does this work while installing via MSI?<\/p>\n Run the install like this (should be all on one line):<\/p>\n msiexec.exe /i “Spiceworks Agent.msi” SPICEWORKS_SERVER=“spiceworks.yourdomain.com<\/a>” SPICEWORKS_AUTH_KEY=“supersecretspiceysauce” SPICEWORKS_PORT=443 SPICEWORKS_SITE_LABEL=“Remote” TRAY_CLICK_LABEL=“Company Helpdesk” TRAY_CLICK_URL=“https://spiceworks.yourdomain.com/portal<\/a>” ADDLOCAL=FeatureService,FeatureTray /q /norestart /log c:\\spicey_install.log<\/p>\n<\/div>\n This is the ip address or hostname of your Spiceworks server.<\/p>\n In order for the agent to work, it needs to be able to communicate with the server address.<\/p>\n Enclose your address in quotes. Note that you do NOT put http or https here, just the hostname or IP address.<\/p>\n Example:<\/p>\n SPICEWORKS_SERVER=“spiceworks.yourdomain.com<\/a>”<\/p>\n<\/div>\n\n<\/a>Step 2: Where the heck IS the Spiceworks Agent MSI?<\/h3>\n
\n<\/a>Step 3: Deploying the MSI<\/h3>\n
\n
\nSPICEWORKS_AUTH_KEY=“supersecretspiceysauce”
\nSPICEWORKS_PORT=443
\nSPICEWORKS_SITE_LABEL=“Remote”
\nTRAY_CLICK_LABEL=“Company Helpdesk”
\nTRAY_CLICK_URL=“https://spiceworks.yourdomain.com/portal<\/a>”
\nADDLOCAL=FeatureService,FeatureTray<\/p>\n\n<\/a>Step 4: SPICEWORKS_SERVER<\/h3>\n
![\"3c2bab47c07d568c3f30074a3ce6088f5ec0a559585682cf4af48a2838c28160_spiceworks__authentication_code.jpg\"](\"https://us1.discourse-cdn.com/spiceworks/optimized/4X/7/2/a/72a688ce82ac62d26eca0f69f2f7c7789402209c_2_690x135.jpeg\")