PC Inventory Tool for Windows

Command Line PC Inventory Tool - ::Project Overview:: Hello - I need a command line pc inventory tool developed for me ASAP. The command line pc inventory tool needs to capture very detailed hardware and software data from the user's PC, authenticate with our server, and then send the results of the audit over the internet to my server via an HTTPS post (Must be able to post via HTTP also). Please read the entire project requirements and payment information for this project. DO NOT BID if you cannot follow through with this project, thoroughly debug and test the application, or communicate effectively over email. This should be an easy project if you have the experience. If we have a good experience with you, there is no reason why I won't give you precedence over other programmers for additional work. For a formatted Description please click here: [login to view URL] ::Project Details:: The PC Inventory Tool must run from the command line, as this may be deployed over a network login script, or ran off a floppy drive. When run, depending on the parameters used the program will first authenticate the user (see Authentication below) through our online system. If the authentication fails, the program will send the appropriate error message to a log file (See Error Logging below). Once the authentication is verified, the application must audit the machine using WMI methods first (See WMI Audit Method). If WMI is not installed or not working, the application then must use an alternative method to collect the information (See Alternative Audit Method). The collected data must then be sent via https to our online server (See Data Format). If the appropriate parameter (-x or -c) is used (see Export Functionality below), the application will not authenticate or send the collected information over the internet, but will instead store the data in a CSV or XML. ::Authentication:: The auditor (aka "PC Inventory Tool") authenticates via an HTTPS post to a specified URL. In order to authenticate a UserID is required, along with either a password or hash. By default, the UserID and Hash should consist of 35 pluses ("+") each, and they should be defined as global variables (this is so we can customize the binary automatically for different user accounts). When the auditor is run, if the UserID still only contains all the pluses, then it should require the ID and Password via the commandline. If they contain anything else, then it should run using those as the UserID and Hash. So in pseudocode: globalUserID = "+++++++++++++++++++++++++++++++++++" globalHash = "+++++++++++++++++++++++++++++++++++" if UserID and Password/Hash supplied via commandline parameters Get UserID and Password/Hash from commandline Authenticate with them else if globalUserID="+++++++++++++++++++++++++++++++++++" exit with error and display usage else authenticate with globalUserID and globalHash endif endif if authentication failed, exit with error message The auditor (also known as "PC Inventory Tool") should also automatically use Internet Explorer's default proxy settings if the computer is required to pass https/http data through a proxy server. ::Error Logging:: All Errors should automatically create/append to an [login to view URL] file in the directory that the command auditor is running from. This should include any communication errors, or failed audit information. ::Data Format:: Data that will be sent via https should be in the following format, to maintain compatibility with our system: 'login' => 'TESTUSER' 'password' => 'TESTPASS' 'id' => 'TESTPC' 'Software_OperatingSystem_0_Caption' => 'Microsoft Windows XP Professional' 'Software_OperatingSystem_0_BuildNumber' => '2600' 'Software_OperatingSystem_0_BuildType' => 'Uniprocessor Free' 'Software_OperatingSystem_0_ServicePack' => 'Service Pack 1' 'Software_OperatingSystem_0_SerialNumber' => '55174-640-4329327-21093' 'Software_OperatingSystem_0_RegisteredUser' => 'User' 'Software_OperatingSystem_0_LastBooted' => '20040121082647.500000-480' 'Software_OperatingSystem_0_WindowsDirectory' => 'C:\WINDOWS' 'Software_OperatingSystem_0_SystemDirectory' => 'C:\WINDOWS\System32' 'Software_OperatingSystem_0_InstallDate' => '20031021102037.000000-420' 'Software_OperatingSystem_0_Status' => 'OK' 'Software_InstalledSoftware_0_' => 'AddressBook' 'Software_InstalledSoftware_1_' => 'Adminpal Auditor 1.7.0.10' 'Software_InstalledSoftware_2_' => 'Adobe Photoshop 7.0' ...etc Please review the entire example data collection: [login to view URL] ::Export Functionality:: We need a command line argument to export the data to xml or csv. If either "-x" or "-c" is specified as a command line parameter, the auditor will not authenticate the user or communicate with our online server at all, but instead create the type of file specified. The command line argument "-x" will cause the application to save the collected data into an XML file, and the argument "-c" will save the file as a CSV (comma separated value). The files will be saved in the directory that the command line auditor is executed from. So if they are running on f:[login to view URL] -x, it will save the xml file as f:auditpcname.xml. If the auditor was executed within the UNC path, \servernameaudit the data should be stored in \servernameauditpcname.xml. ::WMI Audit Method:: You must be able to capture the following information using WMI which is similar to our current application. Please review our current collection example at: [login to view URL] ::Alternative Audit Method:: You may use any reliable method to obtain strong and accurate PC Inventory information that can be obtained from Windows 95,98,NT,ME,2000,XP, and 2003 machines. We will not accept 3rd party modules that will require additional licensing /development fees, such as "MiTec Components", unless agreed upon BEFORE the project begins. ::Command line Arguments:: -u USERID -h Hash -p Password -x (Export to XML) -c (Export to CSV) **Example Command Line Arguments Usages: C:[login to view URL] -u testuser -p password Auditapp -u testuser -h dd0ec3fa0376c96b0e54c164090c025b C:[login to view URL] F:[login to view URL] -x F:[login to view URL] -c -u testuser -h dd0ec3fa0376c96b0e54c164090c025b \[login to view URL] -x ::Requirements:: * MUST support Windows 95, 98, ME, 2000, NT, XP Pro, XP Home, 2003. * Must be a self contained exe file. * Must be developed with MS VC++. * Must collect the following information: o Installed Software o Network Settings o Installed Service Packs/Hot Fixes o NT Services o OS Version o Workstation ID o Registered User Name o Login Profile Name o Page File Size/Status o Motherboard/BIOS (May only be attainable with WMI) o System Processor o Memory o Hard Drive o Video Card o Sound Card o Video Monitor o Network Adapter o Hardware Failures (May only be attainable with WMI) ::Application Testing:: Programmer will be required to test the application thoroughly and verify that the application works on ALL platforms bug free. Programmer must also be willing to test the application with our live/beta system. We will not perform your testing for you. If you lack the resources to properly test your code, please do not bid on this project. ::Payment Terms:: 50% of payment will be escrowed up front at the start of project. After the project is 100% complete, 50% of the first escrow will be released. We will then escrow the remaining 50% of the funds, and release them after we obtain the source code. ::Terms and Conditions:: 1) Programmer must provide client with a fully functional program(s) in an executable form as well as complete source code of all work. 2) Deliverables must be in ready-to-use condition. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all Copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4) We reserve the right to cancel the project if we do not hear from the programmer within a reasonable timeframe. (We are running a business, 3-4 business days of non-responsive emails is un-acceptable) 5) We reserve the right to not release any of the escrowed fees if the programmer does not deliver the application. 6) Applications requiring additional licensing fees or separate modules/add-ons that will need to be purchased will not be accepted, unless agreed upon before the project begins. Payment shall be made through Scriptlance and an excellent comment will be provided upon successful completion of this project. Thanks for taking the time to read this Project Description.