I am having issues trying to get spiceworks to recognise my vcenter server. I am running the VMware vCenter Server Appliance (the virtual vcenter virtual appliance) and it keeps telling me ports are not open. I can ssh into it and the scanning machine is on the same subnet not going through any firewalls.

With 5.0 one of the supported configurations (in fact suggested by some) is to run the vcenter as an pre-canned vmware made appliance in the cluster itself. The vCenter appliance provided by VMWARE runs on a custom configured linux variant.

I don't think this is a VMware problem. I have just installed the 5.5 vCenter appliance and have a similar problem. Everything is working as it should, but Spiceworks cannot inventory the device. I can SSH into it using Putty no problems. Spiceworks tells me ports 443, 80 and 22 are open. If I tell Spiceworks it's an ESXi device it say it's not, (Error. This is not an ESX/vSphere server). If I say it's a Unix device, it fails to connect. Same if I tell it to connect via SSH or HTTP. I'm wondering if it's something silly like the SSL certificate is not valid, or that it is locked to UTC time zone, (10 hours different from my domain).

There are options for SNMP in the vCenter server, but only for sending data to an SNMP management server, it doesn't let the software to come in and pick up the SNMP info itself, I think that's the problem here, seeing as Spiceworks can only pick up data, not receive it.

I'm in the same boat. Spiceworks 7.2.00223 (current). Today I just got all my esxi hosts to scan correctly (my settings.yaml was missing the https: 443 line, probably due to my upgrades since 5.x) but I can't get my vcenter 5.5 appliance (VCSA) to scan. Ports 22, 80, 443 show as open

I'm already working with support so I'll return here with my findings as soon as we track down the issue

what update would you expect ? as I said vcenter can only send data to SNMP receivers, spiceworks is not a receiver, it can only pick up data, vcenter doesn't let apps to pick up snmp data from it. it's not a bug, it simply won't work together like this.