1

Hello,

I’ve been trying to search for an answer to this with no success. I’m sure someone will have some links that put my search skills to shame… :stuck_out_tongue:

I have a Central Server Spiceworks installation as well as a Remote Site installation. The two networks these were on have been merged, now all devices are on the same subnet as the Central Server. The Remote Site server is online in this network with a new IP address, and Spiceworks has been reconfigured to scan the same subnet. All inventory seems to have been updated with the correct information via scans from the remote site server, but I would like to transfer all inventory to the central server while keeping all ticket associations (which is the main thing that’s keeping me from just deleting the inventory and allowing the central server to scan it from scratch).

Is this possible?

Thanks!

1 Spice up
2

https://community.spiceworks.com/how_to/295-move-your-spiceworks-installation

if you want to move the central server, if you want to migrate the remote database, I thought this was in the central one just gathered by the remote one. I could be wrong though

Lets see if we can get some confirmation for you, V_S may know, otherwise we can ask support.

@v-s

2 Spice ups
3

The Remote Collector is forwarded to the Central Install and stored in the Central Install database.

I have to run out for Physical Therapy right now so can’t read more on the association with current tickets, but skimming what you ready, there shouldn’t be migration in that way needing to be done with the devices from the Remote Collector.

You did say they are currently already being scanned already with the Remote Collector on the same network as the Central Install of Spiceworks, so the information on the devices should be updated in the Central Install.

I would try shutting down the Remote Collector, then maybe restart your main Central Installation of Spiceworks and see how the device associations in tickets come up.

Any issues with that post back and maybe the community can figure out what’s up or Support can jump in.

1 Spice up
4

Thanks to the both of you. I’ll try these suggestions out and report back.

1 Spice up
5

All devices were in the central database, but they were still associated with the remote site. When looking at the ‘Settings’ → ‘Remote Sites & Agents’ page, the site was listed in the “Manage Your Remote Sites” section and had over 100 devices associated with it. Each one of these devices also listed the name of this remote site on its page in the Inventory view, so I was concerned that deleting the remote site would delete all of these devices or somehow prevent them from being included in future scans from the Central Server with the Remote Collector out of the picture.

I did try shutting down the Remote Collector but the devices were still associated with that site.

I ended up manually updating the database to re-associate all devices that were associated with this remote site with the central server (making sure to do this as carefully as I could – I took backups, disabled all remote sites and agents, disabled all Spiceworks services on all servers to keep the database from changing as I was modifying the copy I made of it, etc…). After spinning everything back up, the remote site had 0 devices and the central server had all of the correct ones. I forced a full inventory scan and everything seems to be good now.

I’m sure this was unnecessary (when I finally did delete the remote site, I did get a warning that all devices scanned by this site would still be in inventory), but I didn’t want to risk losing the devices or putting them in a sort of “limbo” of being associated with a remote site that no longer exists and excluded from future scans. If it happens that this was the correct thing to do and the correct way to do it, I’d be happy to provide the steps I took for future reference.

Thanks again for your help.

1 Spice up
6

Manually editing the database can invalidate any help from Spiceworks Support in the future. In all honesty, I would wait for confirmation from Spiceworks on this instead of going the manual database edit route.

The only other thread I have for reference is the exact opposite of what you’re doing, where they said delete the items.

I have deleted and re-added items before and it seemed (if I remember correctly) to re-add the device association indicators for tickets, but I didn’t specifically check anything.

When you delete a Remote Collector in Spiceworks, you did say Spiceworks prompted that it wouldn’t delete the devices. I would think a safer test would be backup everything in the current state, restore to before the database edit, delete the Remote Collector in Spiceworks, re-scan, see if the Central Install re-tags them, if not then delete them, re-scan and see if all of the device ticket associations are still intact.

If yes, you’re good to go

If not, you can always reload your manual edit that you backed up before starting this.

Since I’ve never dealt with your scenario, Spiceworks would have the best information on this and ensure that you don’t void future support options with continuing with your install using the manual database edits.