Based on the discussion in #107 there is interest in adding support for the "Update Hardware" MIP SDK method on Hardware object types.
The Management Client has two similar features: Update Hardware, and Replace Hardware. The Update Hardware feature does not allow you to change which driver is used, or change the hardware address. The Replace Hardware feature effectively allows you to perform the Update Hardware action, and also you can change the hardware driver, address, or credentials.
MilestonePSTools has the Set-VmsHardwareDriver command which performs the "Replace Hardware" functionality added to MIP SDK in version 2023 R1.
The MIP SDK has an UpdateHardware method on hardware objects, but the server only allows you to call this on Interconnect devices today. Doing so enables you to add/remove/rename devices on the parent server to match the "interconnected" site.
As far as command names go, it probably makes sense to use Update-VmsHardware. There might be some confusion given there is already a Set-VmsHardware, but I think anyone familiar with XProtect will understand the difference. An alternative might be Invoke-VmsUpdateHardware or Invoke-VmsHardwareUpdate. I don't have strong feelings about the command name, other than I tend to favor shorter names.
Based on the discussion in #107 there is interest in adding support for the "Update Hardware" MIP SDK method on
Hardwareobject types.The Management Client has two similar features: Update Hardware, and Replace Hardware. The Update Hardware feature does not allow you to change which driver is used, or change the hardware address. The Replace Hardware feature effectively allows you to perform the Update Hardware action, and also you can change the hardware driver, address, or credentials.
MilestonePSTools has the
Set-VmsHardwareDrivercommand which performs the "Replace Hardware" functionality added to MIP SDK in version 2023 R1.The MIP SDK has an
UpdateHardwaremethod on hardware objects, but the server only allows you to call this on Interconnect devices today. Doing so enables you to add/remove/rename devices on the parent server to match the "interconnected" site.As far as command names go, it probably makes sense to use
Update-VmsHardware. There might be some confusion given there is already aSet-VmsHardware, but I think anyone familiar with XProtect will understand the difference. An alternative might beInvoke-VmsUpdateHardwareorInvoke-VmsHardwareUpdate. I don't have strong feelings about the command name, other than I tend to favor shorter names.