OCS Inventory Data Collection

[Ric_]

I've been having a play with OCS Inventory NG over the past couple of days. I was just wondering if any experienced users could enlighten me on the way that the data is collected and ways to debug this.

I realise that it can take a while for the data to be reported back to the server (I have manually installed the agent on a couple of servers and this seems to have worked - it took several hours to report mind!). What is the default amount of time that I should expect to be waiting?

I have also used WIWW to package the installer and deployed it via GPO but none of these clients have reported yet. This may be due to delays in installing the client or the eon that it seems to take to report (or a combination).

So any advice?

Incidentally... the integration with GLPI seems pretty cool!

[Ric_]

Found the answer at http://forums.ocsinventory-ng.org/viewtopic.php?id=147 - 10 hours!

[_Bat_]

I want to implement OCS Inventory (simply to audit the network) soon so could I ask some questions too?

1. By agent, I assume you mean the software installed onto the client machines to report back to the server?

2. If so, can this be installed via user login script? I'm sure this was the case when I played about with this a long time ago. All it seemed to require was a line or two in the login script and that was all that was needed for the client computers.

3. Why is there such a long delay as stated above? Can this be changed? Or is that not recommended?

Are there any other issues that I should know about? At the moment my plan of action is to install ubuntu on an old server and installed OCS Inventory on that. I'll reserve an IP address on our DHCP server for it and place the server in the necessary location. Then add in additions to login script? Is that correct?

Thanks.

[Geoff]

1. yes
2. A start-up script would work better.
3. The minimum you can set it to is an hour I think.

Your plan should work fine.

[wesleyw]

Yeah I'm doing this with a WAMP server should be interesting. Before Geoff suffers apoplexy from this I have a netbsd box which is one package away from an OCS install but seeing as I was installing little binaries for three - four hours last night I thought I'd try windows and see how quickly I could get it working lol.

Wes

[Ric_]

I found it very easy to install on my Debian Etch box that I use for general admin bits and bats.

The recommendation is to install the service so that you can take advantage of all the functionality. It was very easy to create a MSI for this using WIWW (Windows Installer Wrapper Wizard).

The 10 hour thing seems to be a default following the first install, after that you can change the frequency through the admin interface.