in reply to Microsoft Windows Configuration/Assett Management Using Perl

It's not Perl, but hardware and software inventory are among the features of Microsoft's Systems Management Server. While SMS has some annoying things about it, it's pretty robust and should be able to determine all of your information for you.

Having said that, a fair number of those items could be determined through a Perl script, but I'm not sure that all of them could. Dave Roth's Win32 Perl Pages would be a good place to start.

  • Comment on Re: Microsoft Windows Configuration/Assett Management Using Perl

Replies are listed 'Best First'.
Re: Re: Microsoft Windows Configuration/Assett Management Using Perl
by Keef (Sexton) on Mar 31, 2001 at 05:48 UTC
    Well I know you're not going to like this answer either, but I would serisously reccomend against using perl for this. Windows machines, by deafult, do not come with a perl complier installed. If you're using them as workstations, I doubt you've installed perl on every one. (if you are installing perl on them, I hope you understand the security implications) But for this sort of thing to work thru perl, you'd have to install perl on each machine then run the script (quite possibly run it manually from each machine). Just making sure you understood this ;-)
[reply]
      That's not true, you only need to have Perl installed on one machine - the machine that checks all the others. I have written scripts that read remote windows registries and check sytem config on other windows machines that do not have Perl installed.

      Even if this were the case, it is possible to run perl scripts using the perl interpretter on a network share.

      $ perldoc perldoc
[reply]
        It is possible to run perl scripts using the perl interpretter on a network share.

        You can also run Perl off of a CD. It's a great way to work around a "thou shalt not install Perl" edict when you have complicated installation and configuration tasks.

[reply]

In Section Seekers of Perl Wisdom