Getting Started

Before you can write applications or compile and run the Samples contained in the tool kit, make sure that the basic components are in place. Components include the WMI SDK, the SMS libraries and header files, and language-specific service packs.

WMI SDK

The WMI SDK contains documentation, the WMI API methods, and sample applications that you can use when writing your application. The SMS setup program can install the WMI SDK for you. If you choose to install the WMI SDK yourself, run the Wbemsdk.exe executable file, which is found on the SMS SDK CD in the \wmi directory.

For more instructions, see the WMI SDK Readme.txt file.

SMS Libraries and Header Files

Libraries:

• Wbemuuid.lib contains the WMI Component Object Model (COM) interface definitions.

  The Wbemuuid.idl is shipped with WMI, but has been compiled by the SMS SDK for your convenience.

• Wbemdisp.tlb contains the WMI scripting components.

  This type library is shipped with WMI. Refer to the WMI SDK documents for details for adding the library to your Visual Basic project.

• Sms_nmgr.tlb contains the interfaces necessary to write extension snap-ins for the SMS Administrator Console.

  You must import (#import) the Sms_nmgr.tlb and the Wbemcli.tlb type libraries into your C/C++ file. The Wbemcli.tlb type library is compiled from the Wbemcli.idl file, which is shipped with WMI.

• SMSRsGen.lib contains the functions that you use to create data discovery records.

Header Files:

• Smsprov.h contains string constants for the class, properties and methods names. This enables C/C++ developers to add these constants to their programs rather than using literal strings.
• Ssperrcode.h contains the error codes and macros used to evaluate an error condition returned from the SMS Provider.
• SMSRsGen.h contains the function prototypes and property flags for the data discovery record functions found in the SMSRsGen.lib library.

WMI Managed Object Format (MOF) Files:

• SmsProv.mof contains all the static class definitions for the SMS Provider classes. The file is located in the \Bin\<platform> directory.
• Cimwin32.mof contains all the static class definitions for the Microsoft® Win32® Provider. The file is located in the %windir%\system32\wbem directory on an SMS client.

Languages and Service Packs

Currently, you can develop SMS applications with C++ or any of the Visual Basic languages (Visual Basic, Visual Basic Scripting Edition (VBScript), or Visual Basic for Applications). You can use Microsoft® Visual C++® version 5.0 SP3 or later to develop your applications. However, you are encouraged to use Visual C++ 6.0 when writing MMC snap-ins to extend the SMS Administrator Console.

Note that the C++ provider samples included with this SMS SDK use Visual C/C++ 5.0. However, the MMC snap-in samples use version 6.0.

If you use Visual Basic to write your applications you should use version 5.0 SP3 or later. If you do not have Service Pack 3, you can get a copy at http://msdn.microsoft.com/vbasic/. Also, you should have the Windows Script Host in order to run .vbs files. A copy is available at http://msdn.microsoft.com/scripting/.

Note that the Visual Basic samples included with this SMS SDK use Visual Basic 6.0.