Install-RmsMfgSupport

Adds Microsoft Federation Gateway support to an AD RMS server.

Syntax

Install-RmsMfgSupport
       [-Force]
       [-FederationUrl <String>]
       [-WhatIf]
       [-Confirm]
       [<CommonParameters>]

Description

The Install-RmsMfgSupport cmdlet adds Microsoft Federation Gateway support to an AD RMS server.

Examples

-------------- EXAMPLE 1 --------------

PS C:\>Install-RmsMfgSupport

Adds Microsoft Federation Gateway support to an AD RMS server.

Parameters

-Confirm

Prompts you for confirmation before running the cmdlet.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:False
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-FederationUrl

Specifies the uniform resource locator (URL) that the AD RMS server is to use when connecting to the Microsoft Federation Gateway. If this parameter is not supplied, AD RMS will connect to the Microsoft Federation Gateway using default

Type:String
Position:Named
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False

-Force

Forces the installation process to be completed, even if there are issues.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:False
Required:False
Accept pipeline input:False
Accept wildcard characters:False

Inputs

None

Outputs

None

Notes

  • Before adding Microsoft Federation Gateway Support, it is very important that you back up the AD RMS configuration database.

    Do not run this command if the AD RMS snap-in is open in the Microsoft Management Console (MMC). If you do, the command will not respond until you close the AD RMS MMC snap-in.

    Before uninstalling Service Pack 1 for nextref_windows_7, you must remove Microsoft Federation Gateway Support from the AD RMS cluster by running the Uninstall-RmsMfgSupport cmdlet. Failure to do this may cause an inconsistent configuration of your AD RMS cluster.