The Agent is a hangover from the early days of Spiceworks and completely unsupported although there are some of us using it for machines which are either not available on the network or for some security reason not available to Spiceworks to look at. Spiceworks generally prides itself on being an Agentless system for gathering networks and systems information. The Flash updater removes the old entries automatically, you can't have multiple instances of AX or FF. In addition, Adobe Flash Player has just two entries in the registry (1 each for ActiveX and Firefox) but Spiceworks shows four entries (2 each for AX & FF, for 10r42 and 10r45). On the machine (XP Pro) which shows Firefox 3.5.7 and 3.6 in SW, "Add/Remove Programs" only shows a single entry, and examining the registry remotely (so I know my admin login and password work) I only see a single entry for Mozilla Firefox.
YAML file, I can probably even set it up as a batch file, but I want to resolve this double-entry situation first. I can get the laptops to run the standalone Agent and email me the. In addition, I have a large number of mostly-out-of-the-office laptops. In addition, they have one XP-Home computer, and XP Home doesn't support WMI at all, so I have to use the Agent method on that machine. This office is using XP Pro in Workgroup mode and WMI has been problematic all along.
I've already gone through rebuilding WMI on that particular workstation several times using all the various troubleshooting WMI techniques from the SW community without success. Then there is this help topic too which has some useful info:īut for me the most interesting thing is you have just used the Agent method, that we use quite often and have been told by a number of sources no longer works in 4.6 but have not found another case of it having been used sucessfully and you are now my independant confirmation it still works. Resolving Spiceworks Unknowns Script to make changes to the PCs with ease:
One of the things this Howto covers is fixing WMI problems (along with resolving a number of other possible issues): The other thing that would probably be a good thing to do is fix WMI on the PC. Spiceworks gets the software information from the HKLM\Software hive of the client registry, visit the PC in question and search the registry on that hive for a reference to the 3.5.7 version as it is described in the software listing on Spiceworks. In the live configs the solution is often to clean up the registry entries left behind on the client. There have been quite a few people complainin about overhanging version info from Firefox in live configs too.
0 kommentar(er)
