Export (0) Print
Expand All

Manually Deploying Resource Types

Once you have created a resource DLL and a Cluster Administrator extension DLL, the next step is to deploy the new resource types. Typically, you deploy manually when designing and testing the resource type and create a cluster-aware setup application to deploy the finished product. No matter how you accomplish the deployment, the following list describes the end result:

  • Each cluster node has a local installation of the application, service, or device to be managed as a highly available resource. This includes the application binaries, COM and ActiveX components, registry and crypto keys, and other files necessary to run the application.
  • Each cluster node has a local copy of your resource DLL under the same path and filename.
  • Each cluster node and each remote non-clustered system that will be used to administer the cluster must have local copies of your extension DLL under the same path and filename.
  • Your resource DLL and extension DLL are registered with the cluster.
  • Your extension DLL is registered with COM on every system containing a copy of the DLL.

The following procedure describes how to deploy resource types manually. For information on deploying resource types through setup applications, see Creating Cluster-Aware Setup Applications.

Aa369350.wedge(en-us,VS.85).gifTo deploy resource types manually

  1. Install the application files on each node. For more information on this process see Installing Files.
  2. Copy your resource DLL to each cluster node, using the same path and filename on each node.
  3. Copy the extension DLL to each cluster node and to each remote system that will be using Cluster Administrator to administer the cluster. Use the same path and filename on each system.
  4. From any cluster node, enter the following PowerShell cmdlet code once for each resource type supported by your resource DLL:

    Add-ClusterResourceType -Name MyResourceTypeName -Dll path\dllname

    Specify the path to the location of your DLL (see step 2.). If no path is specified, it defaults to %SystemRoot%\Cluster.

    Windows Server 2008 and Windows Server 2003:  

    The Add-ClusterResourceType PowerShell cmdlet is unavailable. Use the following Cluster.exe command instead:

    cluster restype MyResourceTypeName /create /dll: path\dllname

  5. From any cluster node, call RegSvr32 using the following syntax:

    RegSvr32 drive:\path\MyExtensionDLLName

 

 

Show:
© 2015 Microsoft