Register-SCVMMManagedComputer
Register-SCVMMManagedComputer
Reassociates a managed computer on which VMM agent software is installed with a different VMM management server.
Syntax
Parameter Set: Default
Register-SCVMMManagedComputer [-VMMManagedComputer] <VMMManagedComputer> -Credential <VMMCredential> [-JobVariable <String> ] [-PROTipID <Guid> ] [-RunAsynchronously] [ <CommonParameters>]
Detailed Description
The Register-SCVMMManagedComputer cmdlet reassociates a managed computer on which Virtual Machine Manager (VMM) agent software is installed with a different VMM management server.
When you initially add a host or library server to VMM, the host or library server is "associated" with the VMM management server that provides the VMM database that you added the host or library server to. The VMM database might be installed in a Microsoft SQL Server database on the VMM management server itself or on a remote computer running SQL Server.
After a host or library server is added to (and therefore associated with) a VMM management server, it cannot communicate with any other VMM management server. However, you can reassociate it with a different VMM management server, as described in the following scenarios.
SCENARIO 1: DISASTER RECOVERY
-----------------------------
In this scenario, VMMServerA fails, or the VMM service running on VMMServerA fails. You might already have VMMServerB available as a backup VMM management server. If not, you can install the VMM service on VMMServerB. At this point, the VMM database might be on VMMServerB, or, if you keep the database on a separate SQL Server, you can now point VMMServerB to the VMM database on that SQL Server.
However, although you now have a functioning VMM management server (VMMServerB) and database, hosts and library servers that were managed by VMMServerA are still configured to communicate with VMMServerA. VMMServerB recognizes these managed computers, but they are in an "Access Denied" state. At this point, you can use Reassociate-SCVMMManagedComputer to reassociate computers that were managed by VMMServerA with VMMServerB.
SCENARIO 2: RE-ORGANIZING SERVER GROUPINGS
------------------------------------------
In this scenario, VMMServerA and VMMServerB are two existing VMM management servers that manage different sets of hosts and library servers. If, for example, VMHost01 is currently managed by VMMServerA, you can add VMHost01 to VMMServerB by using the Add-SCVMHost cmdlet with the Reassociate parameter. If you do this, the state of VMHost01 on VMMServerA is now "Access Denied" and its state on VMMServerB is "Responding." VMHost01 is now managed by VMMServerB, so you can remove it from VMMServerA.
You can also use Reassociate-SCVMMManagedComputer to reassociate Host01 with VMMServerA.
Parameters
-Credential<VMMCredential>
Specifies a credential object or, for some cmdlets, a Run As account object that contains the user name and password of an account that has permission to perform this action. Or, in the case of Restart-SCJob, has permission to complete a restarted task.
For more information about the PSCredential object, type: "Get-Help Get-Credential".
For more information about Run As accounts, type: "Get-Help New-SCRunAsAccount".
Aliases |
none |
Required? |
true |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByValue) |
Accept Wildcard Characters? |
false |
-JobVariable<String>
Specifies that job progress is tracked and stored in the variable named by this parameter.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-PROTipID<Guid>
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-RunAsynchronously
Indicates that the job runs asynchronously so that control returns to the command shell immediately.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-VMMManagedComputer<VMMManagedComputer>
Specifies a computer object that is managed by VMM.
Aliases |
none |
Required? |
true |
Position? |
1 |
Default Value |
none |
Accept Pipeline Input? |
True (ByValue) |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
- VMMManagedComputer
Examples
1: Reassociate all unassociated managed computers with a specific VMM server.
The first command connects to VMMServer01 in the Contoso.com domain.
The second command uses Get-Credential to prompt you to supply a user name and password and stores your credentials in the $Credential variable. The required credentials for this operation are a domain account with administrator rights on the host server that you want to reassociate with a specific VMM server and the password for that account.
The last command gets all managed computers from VMMServer01 and selects only those objects that are in the Not Responding state. Then, it passes these objects to the Register-SCVMMManagedComputer cmdlet which changes the association of the objects to VMMerver01. As this command is processed, $Credential provides your credentials to Register-SCVMMManagedComputer.
PS C:\> Get-VMMServer -ComputerName "VMMServer01.Contoso.com"
PS C:\> $Credential = Get-Credential
PS C:\> Get-VMMManagedComputer | where {$_.State -eq "NotResponding"} | Register-SCVMMManagedComputer -Credential $Credential