整合 SharePoint Server 2013 中的單一 Yammer 網路Integrate a single Yammer network into SharePoint Server 2013

摘要:了解如何將單一、 作用中的 Yammer 網路與 SharePoint Server 2013 環境進行整合。Summary: Learn how to integrate a single, active Yammer network together with your SharePoint Server 2013 environment.

此案例中說明的必要與建議整合單一、 作用中的 Yammer 網路與 SharePoint Server 2013 環境的步驟。This scenario describes the prerequisites and recommended steps to integrate a single, active Yammer network together with your SharePoint Server 2013 environment.

部署案例的先決條件Scenario prerequisites

針對此案例,我們假設的:For this scenario, we assume that:

  • 您具有 SharePoint Server 2013 SP1 或更新版本安裝。You have SharePoint Server 2013 SP1 or later installed.

  • 您不使用 SharePoint Server 2013 新聞摘要社交功能。You don't use the SharePoint Server 2013 Newsfeed social feature.

  • 您可以使用 Active Directory 網域服務 (AD DS) 身分識別提供者與 Active Directory Federation Services (AD FS) 2.0 的識別身分同盟。You use Active Directory Domain Services (AD DS) as your identity provider and Active Directory Federation Services (AD FS) 2.0 for identity federation.

  • 您有單一、 建立基本 Yammer 或企業網路具有作用中的使用者。You have one single, established Yammer Basic or Enterprise network that has active users.

    如需如何 Yammer Enterprise 中管理使用者資訊,請參閱 <管理 Yammer 整個生命週期從 Office 365 的使用者For information about how users are managed in Yammer Enterprise, see Manage Yammer users across their life cycle from Office 365.

案例挑戰Scenario challenges

在此案例中前幾名問題的其中一個是使用者和登入認證 Yammer 中的使用者設定檔儲存區與 SharePoint Server 2013 之間的不一致處。下圖顯示可能的認證 AD DS 使用者儲存機制還是 Yammer 網路使用者儲存機制不符情況。One of the top issues in this scenario is the inconsistency of users and their logon credentials between the user profile stores in Yammer and SharePoint Server 2013. The following diagram shows the possible credentials mismatch situations between your AD DS user repository and the Yammer network user repository.

Yammer 使用者認證不符情況Yammer user credential mismatch cases

認證和不相符項目的 Yammer 圖表

表格: 案例 2 挑戰: SharePoint Server 2013 和單一 active Yammer 網路Table: Scenario 2 challenges: SharePoint Server 2013 and a single active Yammer network

挑戰Challenge 描述Description
在 AD DS 與 Yammer 相同的使用者與電子郵件地址Same user and email address in AD DS and Yammer
在這兩個 AD DS 中存在相同的使用者與 Yammer 與相同的使用者名稱和電子郵件地址。此使用者的使用者名稱中的變更後設定目錄同步作業及 Yammer Enterprise。The same user exists in both AD DS and Yammer with the same user name and email address. For this user, there is no change in the user name after you set up directory synchronization and Yammer Enterprise.
不同的使用者帳戶Different user account
當他們已註冊 Yammer 使用者 B 會使用不同的電子郵件地址。此使用者的變更後沒有設定 Yammer Enterprise。針對此案例,您應讓受影響的使用者登入認證來了解所做的變更。不同的登入認證的原因可能是因為使用者加入基本網路使用的別名不其主要電子郵件地址。它也可以發生因為使用者變更其名稱。您可以管理並使用 [大量更新使用者] 頁面上進行這些電子郵件地址變更。User B used a different email address when they signed up for Yammer. For this user, there is a change after you set up Yammer Enterprise. For this scenario, you should let the affected users know about the changes to their logon credentials. The reason for the different logon credentials might be because the user joined the Basic network by using an alias, not their primary email address. It can also occur because the user changed their name. You can manage and make these email address changes by using the Bulk Update Users page.
不同的網域Different domain
在此案例中有多個 Yammer 網路的位置,您已中斷連線的使用者。在此例中,我們建議您合併 Yammer 網路。中的網路,在組織中的每個人都可以使用單一 Yammer 網路。整合到 SharePoint Server 2013 的多個 Yammer 網路中的更詳細地討論此案例。In a scenario where you have multiple Yammer networks, you have disconnected users. In this case, we recommend that you merge Yammer networks. By merging networks, everyone in your organization can use a single Yammer network. This scenario is covered in more detail in Integrate multiple Yammer networks into SharePoint Server 2013.
非因使用者Non-existent users
當使用者已移除或停用在 Office 365 中,如果您已設定好 Yammer Yammer 使用者強制執行 Office 365身分識別時,使用者已從 Yammer Enterprise。When a user is removed or disabled in Office 365, if you have set up Yammer to Enforce Office 365 identity for Yammer users, the user is removed from Yammer Enterprise.

步驟 1: 設定目錄同步作業Step 1: Set up directory synchronization

Office 365 使用的身分識別管理 Azure Active Directory 與 Yammer 企業可以被設定為 Yammer 使用者強制執行 Office 365身分識別。如果您使用的內部部署目錄,以管理集中一處的使用者,您需要使用 Azure [Active Directory 連線同步處理您的內部部署目錄與 Azure Active Directory。Office 365 uses Azure Active Directory for identity management, and Yammer Enterprise can be set up to Enforce Office 365 identity for Yammer users. If you're using an on-premises directory, in order to manage users in one place, you need to sync your on-premises directory with Azure Active Directory by using Azure Active Directory Connect.

如需詳細資訊,請參閱規劃 Office 365 的目錄同步作業利用 Azure Active Directory 的整合您內部部署目錄For more information, see Plan for directory synchronization for Office 365 and Integrate your on-premises directories with Azure Active Directory.

步驟 2: 停用預設 SharePoint Server 2013 社交功能Step 2: Disable default SharePoint Server 2013 social features

之後您設定目錄同步作業,停用預設的 SharePoint Server 2013 社交功能After you set up directory synchronization, disable the default SharePoint Server 2013 social features.

步驟 3: 使用 Yammer 內嵌Step 3: Use Yammer Embed

停用預設的 SharePoint Server 2013 社交功能後,您應該使用 Yammer 內嵌 widget包含 SharePoint 頁面上的 Yammer 摘要。After you disable the default SharePoint Server 2013 social features, you should use the Yammer embed widget to include Yammer feeds on SharePoint pages.

另請參閱See also

概念Concepts

整合 Yammer 與內部部署 SharePoint 2013 環境Integrate Yammer with on-premises SharePoint 2013 environments

Yammer 與 SharePoint Server 2013 的社交案例Social scenarios with Yammer and SharePoint Server 2013

其他資源Other Resources

不同 Office 365 的生命週期管理 Yammer 使用者Manage Yammer users across their life cycle from Office 365