Download: White Paper - Intel PROSet for Windows* Device Manager WMI User‟s Guide

Intel PROSet For Windows* Device Manager WMI Provider User‟s Guide Wh ite Paper Revi sion 1.8 Contents Introduction ... 3 Technology Overview ... 4 Web-based Enterprise Management ... 4 Windows Management Instrumentation ... 4 Installed Files ... 6 Namespaces ... 7 Locales and Localization ... 7 WBEM Context ... 8 Error Reporting ... 9 Classes ... 10 Class List ... 10 Appendix ... 38 Related Documents... 38 Terminology... 38 Working Examples ... 38 Updating the Configuration ... 40 Changing Settings ... 41 Working with Teams ... 42 Working with VLANs ... 43 Running Diagnostics ... 44 iSCSI Set...

Downloads: 950 Views: 2387 Author: Walton Shared: 7/30/19

Author: Walton Shared: 7/30/19

Downloads: 950 Views: 2387

Content

Intel PROSet For Windows* Device Manager WMI Provider User‟s Guide

Wh ite Paper

Associations

Inherits an association with IANet_LogicalEthernetAdapter through IANet_TeamToTeamSettingAssoc.

Instances

An instance of this class exists for each setting that will be displayed as a slider. Users can neither create nor remove instances.

Properties

In addition to the properties supported by IANet_Setting, this class supports: Name Type Description FirstLabel string The label that should be displayed on the left side of the slider. LastLabel string The label that should be displayed on the right side of the slider. PossibleValues [ ] sint64 The initial value of the parameter. Unsupported properties: refer to IANet_Setting Modifiable properties : CurrentValue PossibleValues[]

Methods

There are no supported methods.

Associations

Inherits an association with IANet_VLAN through IANet_VLANToVLANSettingAssoc.

IANet_VLANSettingMultiSelection

Instances

An instance of this class exists for each setting that should be displayed as a list of options.

Properties

In addition to the properties supported by IANet_Setting, this class supports: Name Type Description FirstLabel string The label that should be displayed on the left side of the slider. LastLabel string The label that should be displayed on the right side of the slider. PossibleValues [ ] sint64 The initial value of the parameter. Unsupported properties: refer to IANet_Setting Modifiable properties : CurrentValue,

Methods

There are no supported methods.

Associations

Inherits an association with IANet_VLAN through IANet_VLANToVLANSettingAssoc.

IANet_VLANSettingString

This class models a setting whereby the user can enter a free-form string value. For IANet_VLANSettingString, it is expected that the GUI will display an edit box.

Instances

An instance of this class exists for each setting that should be displayed as a string.

Properties

In addition to the properties supported by IANet_Setting, this class supports: Name Type Description MaxLength uint32 The maximum length of the string

Methods

There are no supported methods.

Associations

Inherits an association with IANet_VLAN through IANet_VLANToVLANSettingAssoc.

IANet_VLANtoVLANSettingAssoc

This is an association class between an instance of a VLAN and a setting on the VLAN.

Instances

There will be one instance of this class for every setting on a VLAN

Properties

Name Type Description Element ref Reference to IANet_VLAN Setting ref Reference to IANet_VLANSetting,

Appendix

This section contains specific information to help users working with the NCS2 architecture.

Terminology

Term Explanation ANS Advanced Networking Services (ANS) teaming is a feature of the Intel® Advanced Networking Services component that lets you group multiple adapters in a system into a team. API An Application Programming Interface exposed by a library or system for service requests. CIM Common Information Model; a standard for describing computers and services. CIMOM CIM Object Manager; part of Windows Management. COM Component Object Model; a Microsoft platform for inter-process communication and object creation. DMiX Acronym for Intel® PROSet for Windows* Device Manager DMTF Distributed Management Task Force; a standards organization for the IT industry. GUI Graphical User Interface; refers to the user interface layer of Intel® PROSet for Windows* Device Manager MOF Managed Object Format; a file extension of a special file format used in Windows management. NCS2 Network Configuration Services 2.0 - the architecture used in Intel® PROSet for Windows* Device Manager VLAN Virtual LAN; a method for creating logical networks within a physical network. WBEM Web Based Enterprise Management; technologies to unify distributed computing environments. WMI Windows Management Instrumentation; Microsoft‟s implementation of the CIM standard for Windows.

Working Examples Getting Current Configuration

The client does not need to get a client handle to read the current configuration. Clients can use a NULL context, however, any error messages will be returned in the default language for the managed machine. In the following tables, items enclosed in { } are object paths. These paths are assumed to have been obtained from previous WQL queries. The client should never need to construct an object path without doing a query. The _PATH attribute of every object contains the object path for that object. In all the following use cases, the methods IWbemServices::ExecQuery or IWbemServices::ExecQueryAsync are used to execute WQL queries.

Physical Adapters

The main class for adapters is IANet_PhysicalEthernetAdapter. This class is used for both physical and virtual adapters, and the client needs to know how to distinguish between them. Task WQL Query Result Class Comment Enumerate SELECT * FROM IANet_EthernetAdapter Returns all IANet_EthernetAdapter instances. all adapters IANet_EthernetAdapter This is equivalent to IWbemServices::CreateInstanceEnumAsync. Determine if ASSOCIATORS OF {adapter path} IANet_TeamOfAdapters If the query results in no classes then the adapter is WHERE AssocClass = adapter is a real adapter., virtual IANet_NetworkVirtualAdapter

Team Configuration

The main classes in the teaming schema are IANet_LogicalEthernetAdapter, IANet_TeamOfAdapters, IANet_NetworkVirtualAdapter and IANet_TeamedMemberAdapter in the root\IntelNCS2 namespace. The association class IANet_NetworkVirtualAdapter contains no useful data – clients are really only interested in the endpoints of this association. IANet_TeamedMemberAdapter does contain useful data about how the member adapter is used within the team. Task WQL Queries Result Class Comments Enumerate all SELECT * FROM IANet_TeamOfAdapters There is one instance of teams IANet_TeamOfAdapters IANet_TeamOfAdapters for each team. Get the ASSOCIATORS OF IANet_LogicalEthernetAdapter Returns only the adapter object for the virtual {IANet_TeamOfAdapters Path} virtual adapter in the team. Apply must adapter for a WHERE AssocClass = be called before this instance will exist. team IANet_NetworkVirtualAdapter Enumerate ASSOCIATORS OF IANet_PhysicalEthernetAdapter Returns the adapters which are in the the team‟s {IANet_TeamOfAdapters path} team, but does not describe what role member WHERE AssocClass = the adapter plays. adapters IANet_TeamedMemberAdapter Determine an REFERENCES OF IANet_TeamedMemberAdapter The class contains information about adapter‟s role {IANet_PhysicalEthernetAdapter how the member adapter relates to the in a team path} WHERE ResultClass = team and its current status within the IANet_TeamedMemberAdapter team.

VLAN Configuration

Any adapter or team supporting VLANs has an IANet_802dot1QVLANService associated with it, using the association class IANet_Device802do1QVVLANServiceImplementation. If an adapter or team does not have an instance of this class associated with it, then it does not support VLANs. Each VLAN is represented by an instance of IANet_VLAN in the root\IntelNCS2 namespace. IANet_VLAN does not have a direct association – it is associated with the corresponding IANet_802dot1QVLANService for the adapter or team. The association class IANet_VLANFor is used to associate each VLAN instance with the correct ANet_802dot1QVLANService. Task WQL Queries Result Class Comments Get the 802.1q VLAN ASSOCIATORS OF IANet_802dot1QVLANService Returns one or no service object associated {IANet_EthernetAdapter path} object(s). with an adapter WHERE ResultClass = IANet_802dot1QVLANService Get the VLANs on an ASSOCIATORS OF IANet_VLAN This can return no objects adapter {IANet_802dot1QVLANService path} if there are no VLANs WHERE ResultClass = IANet_VLAN installed.

Boot Agent Information

Each adapter that can support a boot agent in flash ROM will have an IANet_BootAgent instance associated with it using the IANet_DeviceBootServiceImplementation association class. Task WQL Queries Result Class Comments Get the Boot Agent associated with an ASSOCIATORS OF {path of IANet_BootAgent The following read only adapter IANet_EthernetAdapter} WHERE properties provide information ResultClass = IANet_BootAgent on the boot ROM image for this adapter: InvalidImageSignature, Version, UpdateAvailable, FlashImageType,

Updating the Configuration Client Locks

A client lock ID is used to authenticate the source of changes and to make sure two sources are not trying to make changes at the same time. When submitting configuration requests, a sequence of smaller changes is recommended rather than submitting all changes within a single session. For example, creating a team and then adding VLANs to the team should be accomplished in two separate lock and apply sequences. Obtain Lock •Enumerate the single instance of IANet_NetService •Call the BeginApply( ) method, obtaining the unique client lock ID Commit Changes • Configuration change requests are accompanied by the client lock ID • Any number of changes can be made (fewer is recommended) Release Lock • Obtain the instance of IANet_NetService • Call the Apply( ) method, passing the unique client lock ID

Obtain Lock

In most cases, to update the configuration, the client application will need to get a client handle from the IANet_NetService class and store this handle in a WbemContext context object. The handle is simply an integer and is retrieved from the IANet_NetService BeginApply ( ) function. Changes to the configuration will finalized when the “Apply” method on the IANet_NetService is called. WbemContext is a user created object which has to be customized for use with the NCS2 provider. Discussion of the WbemContext objects is located at WBEM Context. The following code sample shows how this might be accomplished: VBScript Set colNetServiceObjects = mWbemServices.ExecQuery("Select * from IANet_NetService", , 16) For Each NetServiceObject In colNetServiceObjects Set objReturn = NetServiceObject.ExecMethod_("BeginApply") If objReturn.ReturnValue = 0 Then iClientID = CInt(objReturn.ClientSetHandle) End If Next

Commit Changes

The client ID lock cannot be simply passed into functions as an integer argument. It has to be contained within a context qualifier. Context qualifiers are optional additional information which can be passed to WMI providers; use of this qualifier is mandatory with the NCS2 provider. The SwbemNamedValueSet interface is used to create named value pairs; the client lock ID is paired with the string “ClientSetId”. The following code demonstrates: VBScript Set oValueSet = CreateObject("WbemScripting.SWbemNamedValueSet") oValueSet.Add "ClientSetId", iClientID, This named value set is then passed into functions which require a client ID lock. In this example, it is being used with a request to create a team: VBScript Set OutParameterObj = IANet_TeamOfAdapters_Def.ExecMethod_ ("CreateTeam", InParameterObj, 0, oValueSet)

Release Lock

Once configuration change requests are submitted, they need to be applied. The changes are not complete until the IANet_NetService function ApplyDone ( ) has been called. This function also requires users pass in the client lock ID but it uses it differently than the previous example. In this case, the ClientSetHandle parameter of the Apply IN parameters is assigned the number which was obtained from the earlier call to BeginApply ( ). VBScript Set objInParams = NetServiceObject.Methods_. Item("Apply").InParameters.SpawnInstance_() objInParams.ClientSetHandle = iClientID NetServiceObject.ExecMethod_("Apply", objInParams)

Troubleshooting Disabled Drivers

Some device drivers may become disabled until the IANet_NetService.Apply( ) function is called. This is expected; Apply( ) will re-enable the drivers. Typically, this is only seen during teaming changes.

Restarting the Provider

It may be necessary to restart the NCS2 provider if a mistake is made in locking and unlocking the software stack. Normally, the provider will time out in a few minutes, allowing users to resume troubleshooting of scripts and programs. To avoid this timeout, the NCS2 provider can be directly restarted by ending the NCS2Prov.exe process then restarting the WMI Service in the operating system. Use of this option should always be a last resort and unexpected consequences in the software may occur if the provider is shut down during an operation.

Changing Settings

To change an adapter, VLAN or team setting, the client must first get the object path of the setting that it will change. This is best done by enumerating the settings on the object and storing the _PATH attribute of the setting. How to change a setting: Get an instance of the setting to be modified Obtain a client software ID lock by calling IANet_NetService.BeginApply( ). Create a context qualifier and set the client ID lock value. See the section above on Client Locks. Modify the „CurrentValue‟ parameter of the setting object to the new value for the setting. Call IWbemServices::PutInstance() to pass the modified instance back to the NCS2 WMI provider. PutInstance must be called with the flag WBEM_FLAG_UPDATE_ONLY. The context qualifier must be passed in as well. The NCS2 provider will validate CurrentValue and return 0 if the operation succeeded. An instance of IANet_ExtendedStatus will be available if there were any errors. Release the client software ID lock by calling IANet_NetService. Apply( ),

Troubleshooting Setting Changes

Failed setting changes can occur for several reasons. There are certain rules about what values a setting can have, often enforced by other parameters in the class. A few of the reasons for typical failures are: The integer setting value was less than the minimum allowed The integer setting value was greater than the maximum allowed The integer setting value is not one of the allowable steps The length of the string setting is bigger than the maximum allowed The length of the string is smaller than the minimum allowed The setting value is not one of the allowable values A string requires special formatting, such as that seen in IP addresses (“x.x.x.x”) A string may contain invalid characters An IP address is invalid

Working with Teams

Adapter teams can be created by utilizing classes and methods in the root\IntelNCS2 namespace: Teams can be created through the IANet_TeamOfAdapters.CreateTeam( ) function. Like all configuration changes, team creation requires a client ID lock to be in place. Steps to create a team Create an instance of the IN parameters for the CreateTeam( ) function. This can be accomplished by obtaining a definition of the IANet_TeamOfAdapters class and calling using IWbemServices::SpawnInstance(). The IN parameters object will contain 4 fields which need to be filled out: Set .Adapters to an array of IANet_PhysicalEthernetAdapter paths; these are the adapters which will be teamed. Set .TeamingMode to an integer corresponding to the type of team which will be created. Set .TeamName to the name of the team Set .MFOEnable to false. MFO is manageability failover and only needs to be set true with manageability adapters and environments supporting this feature. Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) Create a context qualifier and set the client ID lock value. See the section above on Client Locks. Invoke the CreateTeam( ) method of the IANet_TeamOfAdapters class, passing in the context qualifier. The NCS2 Provider will validate the candidate adapters and team mode. It will return 0 if the operation succeeded. An instance of IANet_ExtendedStatus will be available if there were any errors. Release the client software ID lock by calling IANet_NetService. Apply( )

Troubleshooting Team Creation

Teams have certain rules around team types and membership which are enforced by all team creation requests. Documentation for Intel® PROSet for Windows* Device Manager contains these restrictions. The adapter may already be part of another team Teaming membership rules have not been followed,

Modifying Teams

Teams and their membership can be modified through the WMI interface of the NCS2 provider. There isn‟t a method available for performing these actions; the user can directly manipulate instances to effect configuration changes. The required steps are outlined below. Adding an adapter to a team Create an instance of IANet_TeamedMemberAdapter (i.e., use IWbemServices::GetObject() to get a class object for IANet_TeamedMemberAdapter, and then use IWbemServices::SpawnInstance() to create an instance of this object). The following properties in the object must be set: GroupComponent must be set to be the full object path of the IANet_TeamOfAdapter which the adapter is to be added PartComponent must be set to be the full object path of the IANet_EthernetAdapter that is to be added to the team. Set priority of the adapter in the team (optional) Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) Create a context qualifier and set the client ID lock value. See the section above on Client Locks. Finally, call IWbemServices::PutInstance() to add the adapter to the team, passing the flag WBEM_FLAG_CREATE_ONLY. If this action fails, check IANet_ExtendedStatus for the error code. Release the client software ID lock by calling IANet_NetService. Apply( ) Removing an adapter from a team (abbreviated steps) Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) Delete the IANet_TeamedMemberAdapter instance that associates the adapter to the team using IWbemServices::DeleteInstance(). If this action fails, check IANet_ExtendedStatus for the error code. Release the client software ID lock by calling IANet_NetService. Apply( ) Deleting a team (abbreviated steps) Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) To delete a team, delete the IANet_TeamOfAdapters instance using IWbemServices::DeleteInstance(). If this action fails, check IANet_ExtendedStatus to get the error code. Release the client software ID lock by calling IANet_NetService. Apply( ) Changing team type (abbreviated steps) Manipulate the IANet_TeamOfAdapters.TeamMode parameter. This will require obtaining and releasing a client software ID lock. Changing adapter priority (abbreviated steps) Manipulate the IANet_TeamedMemberAdapter.AdapterFunction parameter. This will require obtaining and releasing a client software ID lock.

Working with VLANs

VLANs can be added, removed, and modified through the NCS2 provider. The steps for performing these actions are detailed below. VLANs can be added and removed from teams and adapters. Steps to create a VLAN Create an instance of the IN parameters for the CreateVLAN ( ) function. This can be accomplished by obtaining a definition of the IANet_802dot1QVLANService class and calling using IWbemServices::SpawnInstance(). For this step, it is easier to work with the instance of IANet_802dot1QVLANService that associates to the device to receive the VLAN., The IN parameters object will contain two fields which need to be filled out: Set .VLANNumber to number of the VLAN. (Range 1- 4094) Untagged VLANs use the number 0. Set .Name to user defined name to identify the VLAN. Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) Create a context qualifier and set the client ID lock value. See the section above on Client Locks. Call the CreateVLAN method on the IANet_802dot1QVLANService for the device (adapter or team) to which the VLAN is to be added. The function will return the object path of the newly created VLAN in the out parameter. If this action fails, check IANet_ExtendedStatus for the error code. Release the client software ID lock by calling IANet_NetService. Apply( ) Steps to delete a VLAN (abbreviated steps) Obtain a client software ID lock by calling IANet_NetService.BeginApply( ) Call IWbemServices::DeleteInstance passing the object path of the VLAN to delete. Release the client software ID lock by calling IANet_NetService. Apply( )

Troubleshooting VLANs

VLANs also have certain rules around how they are created and where they can exist. Fortunately, they are very simple: The VLAN ID must be in the range of 1-4094 When creating an untagged VLAN (ID 0), a tagged VLAN must first exist. An untagged VLAN cannot exist without a tagged VLAN on a device. Removing the last tagged VLAN will also remove the untagged VLAN.

Running Diagnostics

Diagnostics can be executed through the NCS2 provider and the results retrieved after execution. The class IANet_DiagTest is used for this purpose and its method, RunTest ( ) facilitates diagnostic requests. Client software ID locks are not required for diagnostic execution – these steps have intentionally been left out of the following instructions. Steps to run a diagnostic Identify an instance of IANet_DiagTest which represents both the diagnostic to be executed and the adapter on which it is to run. Create an instance of the IN parameters for the RunTest( ) function. The IN parameters must be populated with the following: The .Setting receives a reference to an instance of IANet_DiagSetting whose .Setting ID represents the desired @ test. The .SystemElement receives a reference to an instance of IANet_PhysicalEthernetAdapter which corresponds to the particular diagnostic under test. Assign the object‟s path to this parameter. Execute the RunTest( ) method. Examine instances of IANet_DiagResult to find results.

Troubleshooting Diagnostics

Getting the correct object paths for each diagnostic can be complicated. They key piece of information that ties them all together is the {GUID}, a long number that uniquely identifies each device. When working with diagnostics, this number is very important to getting the correct object instances. The following table provides some hints on how this number can be used across classes., Hint Value Use IANet_DiagTest.Name 1@{1F770A4C-B9DB-4174-9FD3- Use the .RunTest( ) of this instance 0BF520C3CB73} IANet_PhysicalEthernetAdapter.DeviceID {1F770A4C-B9DB-4174- 9FD3- Assign the .Path of this object to the RunTest( ) 0BF520C3CB73} IN parameter .SystemElement. IANet_DiagSetting.SettingID 1@{1F770A4C-B9DB-4174-9FD3- Assign the .Path of this object to the RunTest( ) 0BF520C3CB73} IN parameter .Setting The association classes for IANet_DiagTest can also help locate the correct instances of the classes above. IANet_DiagTestForMSE associates to an instance of IANet_PhysicalEthernetAdapter and IANet_DiagSettingForTest associates to an instance of IANet_DiagSetting. Using this association can take a lot of the guesswork out of obtaining the correct references.

Getting Diagnostic Results

Diagnostic results can be enumerated any time a diagnostic test has been executed. Since the NCS2 provider does not store results permanently, the results are only available as long as the provider is running. If it has become idle for too long, it will unload and erase any existing results.

Diagnostic Names

The name of a diagnostic result will be contained in the .DiagnosticName parameter for a class instance of IANet_DiagResult. It is a concatenation of the diagnostic ID, the “@” symbol, and the unique identifier of the adapter for which it was executed. The IANet_DiagResultForMSE association class can also be used to find all results for a particular adapter. For most instances, the results of the test will be contained in the .Result parameter.

Packages

The results of some diagnostic tests may be contained in a package. This is a logical grouping of a parent test result and any additional result instances which apply to it. Thus it is possible to have one main result for a test and a one or more results which provide additional results. Packages can be recognized in a few ways: Results in a package will have a sub-index in the diagnostics ID for the DiagnosticName parameter of the class instance. The parent result will have its IsPackage parameter set to “Yes” and will have a IANet_DiagResultInPackage association to any packaged results. Type DiagnosticName IsPackage Parent Result 37@{66DFCDDC-A535-4265-99CB-21B03561497A} Yes Packaged Result 37.1@{66DFCDDC-A535-4265-99CB-21B03561497A} Packaged Result 37.2@{66DFCDDC-A535-4265-99CB-21B03561497A} Packaged Result 37.3@{66DFCDDC-A535-4265-99CB-21B03561497A} Packaged Result 37.4@{66DFCDDC-A535-4265-99CB-21B03561497A} Packaged Result 37.5@{66DFCDDC-A535-4265-99CB-21B03561497A} iSCSI Settings The iSCSI settings of an Intel network card can be manipulated through the WMI interface. Only operating systems which support iSCSI will have these settings available. Working with iSCSI configurations requires additional information which is not readily available in the class descriptions.

Getting iSCSI Status

To retrieve the iSCSI status of a network card, enumerate instances of the IANet_BootAgent_iSCSI_Adapters class. In this class, look at the iSCSI_Status parameter. This will indicate the current state of an iSCSI enabled adapter.

Setting iSCSI Status

, The iSCSI state of the adapter is manipulated through the SetiSCSI_Status method of the IANet_BootAgent_iSCSI_Adapters class. This only controls whether the adapter can be set to a Primary, Secondary or Disabled state.

Manipulating iSCSI Parameters

There are several settings applicable to iSCSI which can be manipulated through WMI. To locate these parameters, use the table below to find the name of the class, the type of parameter, and guidelines for setting them. Each iSCSI enabled adapter will have its own settings. Setting Caption Class Notes Authentication IANet_BootAgentSettingEnum 0 (Disable CHAP) or 1 (Enable CHAP) BootLUN IANet_BootAgentSettingInt The iSCSI Boot LUN ChapPassword IANet_BootAgentSettingString A string value no longer than 16 characters ChapUserName IANet_BootAgentSettingString A string value no longer than 16 characters CrashDump IANet_BootAgentSettingEnum 0 (Disable) or 1 (Enable) InitiatorDHCP IANet_BootAgentSettingEnum This requires an string formatted as an IP address InitiatorGateway IANet_BootAgentSettingString This requires an string formatted as an IP address InitiatorIPAddress IANet_BootAgentSettingString This requires an string formatted as an IP address InitiatorName IANet_BootAgentSettingString A string value no longer than 255 characters InitiatorSubnetMask IANet_BootAgentSettingString This requires an string formatted as an IP address TargetDHCP IANet_BootAgentSettingEnum This requires an string formatted as an IP address TargetIPAddress IANet_BootAgentSettingString This requires an string formatted as an IP address TargetName IANet_BootAgentSettingString A string value no longer than 255 characters TargetPort IANet_BootAgentSettingInt An integer between 0 and 65535 TargetSecret IANet_BootAgentSettingString A string between 12 – 255 characters. Some parameters which contain security information will be intentionally obscured upon reading their value. Examples are passwords where the user will only see “*” characters for values.,

Errata

The following is information which may be relevant to viewing or changing a configuration in Intel® PROSet for Windows* Device Manager. It is supplied as a supplement and, in some cases, troubleshooting guide.

Phantom Adapters

When enumerating instances of IANet_PhysicalEthernetAdapter, all installed adapters will be returned whether or not the hardware is actually present. This only occurs when an adapter is installed and then physically removed or replaced by another adapter without first removing its driver. Queries of IANet_PhysicalEthernetAdapter can be modified to filter out these „phantom‟ instances. Amended query: Select * from IANet_PhysicalEthernetAdapter WHERE StatusInfo = '3'

Permissions

Interaction with the NCS2 provider requires Administrator rights on the operating system. This applies to local and remote access. Windows* Vista may require elevated Administrator rights. These can be obtained by logging in as the Administrator and elevating permissions. Failure to work in an elevated environment may result in failure to obtain and apply client software locks. Intel® PROSet for Windows* Device Manager automatically elevates permissions when it runs in user interface mode.

Diagnostic Results Timeout

The NCS2 provider will automatically terminate within a few minutes of not being used. When this event occurs, all diagnostic results will be lost.

Remote Desktop Limitations

When connecting to a computer remotely with Remote Desktop Protocol and no Administrator locally logged in, use the “/console” option. The other workaround is to make sure a local Administrator account is logged in when initiating remote desktop access. This makes sure the WMI layer can authenticate with the local permissions.

Win32_Product

The Uninstall () method of the Win32_Product class cannot be used to uninstall Intel® PROSet for Windows* Device Manager. Attempting this operation will result in a corrupted installation and, possibly, the need for manual software removal.

Function Return Values

Functions exposed in classes supported by the NCS2 provider will return the value 0 to indicate success. If the function call failed, nothing will be returned. A return value of 0 will only indicate the function was successfully called. It does not validate the final configuration requested by the user. In most cases, a successful function call can be trusted to perform the expected changes. However, it may be necessary to verify those changes before performing further operations.

Passing Client ID Locks in C#

When using client ID locks in C#, the lock number must be cast to type int before it is used. This is due to a mismatch between how numbers are treated as data types between WMI, C#, and the NCS2 provider. Attempting to pass the ID without casting it first will result in a failed change request. C# outParams = netService.InvokeMethod("BeginApply", null, null); result = (uint)outParams["ReturnValue"]; clientHandle = (uint)outParams["ClientSetHandle"]; g_SValueSet.Add("ClientSetId", (int)clientHandle);]