My “Connectivity Tests” always failed, but the Agent always worked fine for me when I was using my FQDN.
Some people have weird issues with connectivity using hostname/FQDN, which in those cases does usually work with IP address, something to try [Bug #65919]:
Not sure about not saving settings. I haven’t experienced that, but have you looked in the registry to see what’s going on?
On my 64-bit system, it’s saved here, for reference:
- [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Spiceworks\Agent]
My laptop hasn’t been on in a week or two to really check into it more, but it has Win7 SP1 on it with 10.0.1 of Agent that was installed that I could probably fire up when I get some time.
For XP, that’s a bummer for the new Agent 10.x, but the new Agent requires .NET 4.5:
Bill C (Spiceworks) Feb 18, 2016 at 7:48 AM
Only new requirement is .Net 4.5, but most modern Windows systems already have that
And XP doesn’t support upgrading or installing .NET 4.5:- .NET Framework system requirements - .NET Framework | Microsoft Learn
Operating system | Supported editions | Preinstalled with the OS | Installable separately
Windows XP | 32-bit and 64-bit | -- | .NET Framework 4
If you were feeling adventuresome, you could possibly try Mono, which doesn’t support everything that .NET 4.5 can do but might be “good enough” for what Spiceworks Agent needs:
Or the other long, weird, involved suggestion here may help in some way, if you can decipher it: