升級到 Windows Server 2016 使用 WID 資料庫中 AD FSUpgrading to AD FS in Windows Server 2016 using a WID database

適用於:Windows Server 2016Applies To: Windows Server 2016

Windows Server 2012 R2 AD FS 發電廠從移到 Windows Server 2016 AD FS 陣列Moving from a Windows Server 2012 R2 AD FS farm to a Windows Server 2016 AD FS farm

下列文件可描述您 AD FS Windows Server 2012 R2 發電廠升級到 Windows Server 2016 中的 AD FS,當您使用 WID 資料庫的方式。The following document will describe how to upgrade your AD FS Windows Server 2012 R2 farm to AD FS in Windows Server 2016 when you are using a WID database.

AD FS 升級到 Windows Server 2016 FBLUpgrading AD FS to Windows Server 2016 FBL

新在適用於 Windows Server 2016 AD FS 是發電廠行為層級功能 (FBL)。New in AD FS for Windows Server 2016 is the farm behavior level feature (FBL). 此功能發電廠寬並判斷 AD FS 發電廠可以使用的功能。This features is farm wide and determines the features that the AD FS farm can use. 根據預設,Windows Server 2012 R2 FBL 是在 Windows Server 2012 R2 AD FS 發電廠 FBL。By default, the FBL in a Windows Server 2012 R2 AD FS farm is at the Windows Server 2012 R2 FBL.

Windows Server 2016 AD FS 伺服器新增到 Windows Server 2012 R2 陣列,它會維持 FBL 相同與 Windows Server 2012 R2。A Windows Server 2016 AD FS server can be added to a Windows Server 2012 R2 farm and it will operate at the same FBL as a Windows Server 2012 R2. 當您有 Windows Server 2016 AD FS 伺服器以這種方式運作時,您發電廠即稱為 「 混合 」。When you have a Windows Server 2016 AD FS server operating in this fashion, your farm is said to be "mixed". 不過,您將無法善加利用 Windows Server 2016 的新功能,直到 FBL 以 Windows Server 2016 提出。However, you will not be able to take advantage of the new Windows Server 2016 features until the FBL is raised to Windows Server 2016. 使用混合發電廠:With a mixed farm:

  • 系統管理員可以新增新的 Windows Server 2016 聯盟現有的 Windows Server 2012 R2 發電廠伺服器。Administrators can add new, Windows Server 2016 federation servers to an existing Windows Server 2012 R2 farm. 如此一來,發電廠 「 混合模式 」 是與 Windows Server 2012 R2 發電廠行為層級的運作方式。As a result, the farm is in "mixed mode" and operates the Windows Server 2012 R2 farm behavior level. 若要確保發電廠一致的行為,Windows Server 2016 的新功能無法設定或使用此模式。To ensure consistent behavior across the farm, new Windows Server 2016 features cannot be configured or used in this mode.

  • 之後,已從農場混合模式下,移除所有的 Windows Server 2012 R2 聯盟伺服器,在 WID 陣列,其中一個新的 Windows Server 2016 聯盟伺服器已升級至主要節點的角色,系統管理員可以再提高 FBL Windows Server 2012 R2 的 Windows Server 2016。Once all Windows Server 2012 R2 federation servers have been removed from the mixed mode farm, and in the case of a WID farm, one of the new Windows Server 2016 federation servers has been promoted to the role of primary node, the administrator can then raise the FBL from Windows Server 2012 R2 to Windows Server 2016. 如此一來,任何新 AD FS Windows Server 2016 功能可以再設定及使用。As a result, any new AD FS Windows Server 2016 features can then be configured and used.

  • 如此一來的混合的發電廠功能,AD FS Windows Server 2012 R2 組織想要升級到 Windows Server 2016 不會部署全新發電廠,匯出與匯入設定資料。As a result of the mixed farm feature, AD FS Windows Server 2012 R2 organizations looking to upgrade to Windows Server 2016 will not have to deploy an entirely new farm, export and import configuration data. 他們可以 online 時 Windows Server 2016 節點加入現有發電廠而只會造成參與 FBL 提高相當簡短中斷。Instead, they can add Windows Server 2016 nodes to an existing farm while it is online and only incur the relatively brief downtime involved in the FBL raise.

請注意,在混合的發電廠模式時,AD FS 發電廠不支援的新功能或 AD FS 在 Windows Server 2016 中加入的功能。Be aware that while in mixed farm mode, the AD FS farm is not capable of any new features or functionality introduced in AD FS in Windows Server 2016. 這表示公司想要試用的新功能無法執行此動作 FBL 引發直到。This means organizations that want to try out new features cannot do this until the FBL is raised. 如果您的組織期待測試新功能 rasing FBL 之前,您需要部署不同發電廠,若要這樣做。So if your organization is looking to test the new features prior to rasing the FBL, you will need to deploy a separate farm to do this.

其餘部分是文件會提供適用於 Windows Server 2016 聯盟伺服器新增到 Windows Server 2012 R2 環境,然後引發 FBL Windows Server 2016 的步驟。The remainder of the is document provides the steps for adding a Windows Server 2016 federation server to a Windows Server 2012 R2 environment and then raising the FBL to Windows Server 2016. 架構如下圖所要求的測試環境中執行這些步驟。These steps were performed in a test environment outlined by the architectural diagram below.

注意

您可以移至在 Windows Server 2016 FBL AD FS 之前,您必須移除所有的 Windows 2012 R2 節點。Before you can move to AD FS in Windows Server 2016 FBL, you must remove all of the Windows 2012 R2 nodes. 您只是無法升級到 Windows Server 2016 的是 Windows Server 2012 R2 的作業系統,並讓它變得 2016年節點。You cannot just upgrade a Windows Server 2012 R2 OS to Windows Server 2016 and have it become a 2016 node. 您必須將它移除,並更換新 2016年節點。You will need to remove it and replace it with a new 2016 node.

AD FS 發電廠您升級到 Windows Server 2016 發電廠行為層級To upgrade your AD FS farm to Windows Server 2016 Farm Behavior Level
  1. Windows Server 2016 上使用伺服器管理員安裝 Active Directory 同盟服務的角色Using Server Manager install the Active Directory Federation Services Role on the Windows Server 2016

  2. 請使用 AD FS 設定精靈,加入現有的 AD FS 發電廠新的 Windows Server 2016 伺服器。Using the AD FS Configuration wizard, join the new Windows Server 2016 server to the existing AD FS farm.

    升級

  3. Windows Server 2016 聯盟伺服器上開放 AD FS 管理。On the Windows Server 2016 federation server, open AD FS management. 請注意,不顯示在此聯盟伺服器不主要伺服器。Note that nothing is showing up as this federation server is not the primary server.

    升級

  4. 加入完成之後,在 Windows Server 2016 伺服器上,請打開 PowerShell,並執行下列 cmdlt: AdfsSyncProperties 設定-角色 PrimaryComputerOnce the join is complete, on the Windows Server 2016 server, open PowerShell and run the following cmdlt: Set-AdfsSyncProperties -Role PrimaryComputer

    升級

  5. 伺服器原始 AD FS Windows Server 2012 R2 上開放 PowerShell 並執行下列 cmdlt: AdfsSyncProperties 設定-角色 SecondaryComputer PrimaryComputerName {FQDN}On the original AD FS Windows Server 2012 R2 server, open PowerShell and run the following cmdlt: Set-AdfsSyncProperties -Role SecondaryComputer -PrimaryComputerName {FQDN}

    升級

  6. 在您的 Web 應用程式 Proxy 開放 PowerShell 並執行 followoing cmdlt: 安裝-WebApplicationProxy CertificateThumbprint {SSLCert}-fsname fsname-TrustCred $trustcredOn your Web Application Proxy open PowerShell and run the followoing cmdlt: Install-WebApplicationProxy -CertificateThumbprint {SSLCert} -fsname fsname -TrustCred $trustcred

  7. 現在在 Windows Server 2016 聯盟伺服器開放 AD FS 管理。Now on the Windows Server 2016 federation server open AD FS Management. 請注意,現在所有節點會因為此伺服器的主要職務已經傳輸。Note that now all of the nodes appear because the primary role has been transferred to this server.

    升級

  8. 與 Windows Server 2016 的安裝媒體,開放命令提示字元中,瀏覽至 support\adprep directory。With the Windows Server 2016 installation media, open a command prompt and navigate to support\adprep directory. 執行下列命令: adprep /forestprep。Run the following: adprep /forestprep.

    升級

  9. 一旦您已完成準備網域執行的 adprep 日Once that completes run adprep/domainprep

    升級

  10. 現在在 Windows Server 2016 伺服器開放 PowerShell 並執行下列 cmdlt: 叫用 AdfsFarmBehaviorLevelRaiseNow on the Windows Server 2016 Server open PowerShell and run the following cmdlt: Invoke-AdfsFarmBehaviorLevelRaise

    升級

  11. 出現提示時,Y 的輸入。這將會開始提高層級。When prompted, type Y. This will begin raising the level. 一旦完成後您已成功地提高 FBL。Once this completes you have successfully raised the FBL.

    升級

  12. 現在,如果您移至 [AD FS 管理,您將會看到 AD fs Windows Server 2016 中已加入新節點Now, if you go to AD FS Management, you will see the new nodes that have been added for AD FS in Windows Server 2016

    升級

  13. 同樣地,您可以使用 PowerShell cmdlt: 取得-AdfsFarmInformation 來顯示您目前 FBL。Likewise, you can use the PowerShell cmdlt: Get-AdfsFarmInformation to show you the current FBL.

    升級