1

Totally new to Spiceworks so apologies for stupid questions … I am a managed IT service provider so we have our office and support a number of customers. I am using a Windows Server in our office as the central Spiceworks server which I have Network Monitor and Inventory installed and working. I then followed guides to install on a customer s site in that a Remote Site is setup and sends data back to central server.

I have connectivity setup, but don;t appear to have Windows devices detected from remote site. I have just added the IP range but am unsure about the credentials for these remote sites as that are AD domains, so the credentials would be domain\username. Can I just use username instead if the username and password is the same or do I need domain\username for each customer? And if so do I nominate the credentials per site/IP range?

Once the devices are inventories/scanned, will there be something that can deploy the agent or is this a separate manual process for me?

2 Spice ups
2

Welcome to the community! You mention you have Network Monitor and Invetory working, but Network Monitor is a separate application from the Spiceworks desktop application. I assume you mean you just have the central server at your office setup to scan your main office network and inventory devices.

3

Remember that all scanning for remote sites is handled by the remote collector and then transferred to the central server via the HTTPS port used for the central server and remote collector. You will need to get into the settings of the remote collector ( HTTPS://remotecollector:spiceworkshttpsport ) and enter the up ranges and credentials that are to be used to scan devices on your customers’ networks. On the Settings → Network Scan page of the remote collector you add your up ranges or DNS names for the remote network you want to scan, but you will also see near the bottom of that page you can add all of the Windows, Linux, SNMP, SSH, VSphere credentials needed to scan devices on that network. Even if you need to scan the 100 devices, putting in credentials for 1 Windows user with the proper permissions to scan each machine will allow Spiceworks to try to scan the machines in the up range you specify.

4

Remember also firewall rules need to be in place on the workstations at each customer site to allow Spiceworks to scan the machines. If this is not the case, that could be a reason why you would not see devices in inventory, but you can check the Spiceworks logs inside C:\Program Files (x86)\Spiceworks\Log (I think) and see what is happening during scans of the remote network to troubleshoot a bit further.

You already mentioned you have the remote collector authorized with the central server, so hopefully the remote site shows inside Settings → Remote Sites and Agents from the central server.

1 Spice up
5

My office I have installed Network Monitor and Inventory with the purpose of then installing Remote Collectors on all our client sites so we can monitor their networks - not so concerned with my home office as it is only me and another employee working from here.

Client’s office I have installed both Network Monitor and Inventory and configured as a Remote Collector.

Currently I have port forwarded HTTP and HTTPS ports for both apps at client site and home office.

Should I close the HTTP ports and stick to HTTPS?
When you say https://remotecollector:spiceworkshttpsport , is this referring to Inventory or Network Monitor?

6

I think I have this one resolved now … reinstalled and just opened HTTPS ports and now have a static IP (which I previously did not).

Am dealing with login errors strangely even though devices are also inventoried using domain admin credentials. I think I will leave overnight in case there is some cleanup that occurs of login errors and post separate question if necessary.

1 Spice up