規劃 Configuration Manager 中的移轉作業策略Plan a migration job strategy in Configuration Manager

適用於: Configuration Manager (最新分支)Applies to: Configuration Manager (current branch)

使用移轉作業設定您要移轉至 Configuration Manager 最新分支環境中的特定資料。Use migration jobs to configure the specific data that you want to migrate to your Configuration Manager current branch environment. 移轉作業可識別您要移轉的物件,而且會在目的地階層中的頂層站台執行。Migration jobs identify the objects that you plan to migrate, and they run at the top-level site in your destination hierarchy. 您可以在每個來源站台上設定一項或多項移轉作業。You can set up one or more migration jobs per source site. 這可讓您一次移轉所有物件,或是在每項作業中移轉有限的資料子集。This lets you migrate all objects at one time or limited subsets of data with each job.

在 Configuration Manager 從來源階層的一或多個站台成功收集資料後,即可建立移轉作業。You can create migration jobs after Configuration Manager has successfully gathered data from one or more sites from the source hierarchy. 您可以依照任意順序從收集資料的來源站台移轉資料。You can migrate data in any sequence from the source sites that have gathered data. 若是 Configuration Manager 2007 來源站台,您只能從建立物件所在的站台移轉資料。With a Configuration Manager 2007 source site, you can migrate data only from the site where an object was created. 若是執行 System Center 2012 Configuration Manager 或更新版本的來源站台,則可移轉的所有資料都在來源階層的頂層站台上。With source sites that run System Center 2012 Configuration Manager or later, all data that you can migrate is available at the top-level site of the source hierarchy.

您在各階層之間移轉用戶端之前,請先確定用戶端使用的物件已移轉,且這些物件都在目的地階層中。Before you migrate clients between hierarchies, ensure that the objects that clients use have migrated and that these objects are available in the destination hierarchy. 例如,當您從 Configuration Manager 2007 SP2 來源階層移轉時,可能有部署至包含用戶端之自訂集合的內容公告。For example, when you migrate from a Configuration Manager 2007 SP2 source hierarchy, you might have an advertisement for content that is deployed to a custom collection that has a client. 在此案例中,建議您在移轉用戶端之前移轉集合、公告和相關聯內容。In this scenario, we recommend that you migrate the collection, the advertisement, and the associated content before you migrate the client. 如果內容、集合和公告未在用戶端移轉之前移轉,此資料就無法與目的地階層中的用戶端建立關聯。This data cannot be associated with the client in the destination hierarchy if the content, collection, and advertisement are not migrated before the client migrates. 如果用戶端未與之前執行的公告和內容相關的資料產生關聯,用戶端就可能收到要在目的地階層中安裝的內容,但該內容並非必要。If a client is not associated with the data related to a previously run advertisement and content, the client can be offered the content for installation in the destination hierarchy, which might be unnecessary. 若用戶端在資料移轉之後移轉,用戶端就會與此資料和公告產生關聯,而除非公告為週期性,否則就不會再收到已移轉公告的此內容。When the client migrates after the data has migrated, the client is associated with this content and advertisement, and unless the advertisement is recurring, is not offered this content for the migrated advertisement again.

某些物件不僅需要從來源階層移轉資料至目的地階層。Some objects require more than the migration of data from the source hierarchy to the destination hierarchy. 例如,若要將用戶端的軟體更新成功移轉至目的地階層,您必須在目的地階層中部署主動式軟體更新點、設定產品的類別目錄,以及同步處理軟體更新點與 Windows Server Update Services (WSUS)。For example, to successfully migrate software updates for your clients to your destination hierarchy, you must deploy an active software update point, configure the catalog of products, and synchronize the software update point with Windows Server Update Services (WSUS) in the destination hierarchy.

移轉作業類型Types of migration jobs

Configuration Manager 支援下列移轉作業類型。Configuration Manager supports the following types of migration jobs. 每一種作業類型的設計都是幫助您定義可包含在該作業內的物件。Each job type is designed to help define the objects that you can include in that job.

集合移轉 (僅在從 Configuration Manager 2007 SP2 移轉時才支援):移轉與您所選擇集合相關的物件。Collection migration (only supported when migrating from Configuration Manager 2007 SP2): Migrate objects that are related to collections you select. 根據預設,集合移轉包括與集合成員相關聯的所有物件。By default, collection migration includes all objects that are associated with members of the collection. 當您使用集合移轉作業時,可以排除特定物件執行個體。You can exclude specific object instances when you use a collection migration job.

物件移轉:移轉您選取的個別物件。Object migration: Migrate individual objects that you select. 您只選取要移轉的特定資料。You select only the specific data that you want to migrate.

移轉之前已移轉的物件:移轉您之前已移轉的物件 (當這些物件自上一次移轉後,在來源階層中有所更新時移轉)。Previously migrated object migration: Migrate objects that you previously migrated when they have updated in the source hierarchy after they were last migrated.

可移轉的物件Objects that you can migrate

特定移轉作業類型不一定能夠移轉每一個物件。Not every object can migrate by a specific type of migration job. 下列清單識別每一種移轉作業類型可移轉的物件類型。The following list identifies the type of objects that you can migrate with each type of migration job.

注意

集合移轉作業只有在您從 Configuration Manager 2007 SP2 來源階層移轉物件時才可使用。Collection migration jobs are available only when you migrate objects from a Configuration Manager 2007 SP2 source hierarchy.

您可以用來移轉每個物件的作業類型Job types you can use to migrate each object

  • 公告 (可從支援的 Configuration Manager 2007 來源站台移轉)Advertisements (available to migrate from supported Configuration Manager 2007 source sites)

    • 集合移轉Collection migration
  • Asset Intelligence 類別目錄Asset Intelligence catalog

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • Asset Intelligence 硬體需求Asset Intelligence hardware requirements

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • Asset Intelligence 軟體清單Asset Intelligence software list

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 界限Boundaries

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 設定基準Configuration baselines

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 設定項目Configuration items

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 維護期間Maintenance windows

    • 集合移轉Collection migration
  • 作業系統部署開機映像Operating system deployment boot images

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 作業系統部署驅動程式套件Operating system deployment driver packages

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 作業系統部署驅動程式Operating system deployment drivers

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 作業系統部署映像Operating system deployment images

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 作業系統部署套件Operating system deployment packages

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 軟體發佈套件Software distribution packages

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 軟體計量規則Software metering rules

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 軟體更新部署套件Software update deployment packages

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 軟體更新部署範本Software update deployment templates

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 軟體更新部署Software update deployments

    • 集合移轉Collection migration
  • 軟體更新清單Software update lists

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 工作順序Task sequences

    • 集合移轉Collection migration

    • 物件移轉Object migration

    • 移轉之前已移轉的物件Previously migrated object migration

  • 虛擬應用程式套件Virtual application packages

    • 集合移轉Collection migration

    • 物件移轉Object migration

    重要

    雖然您可以使用物件移轉來移轉虛擬應用程式套件,但是無法使用 [移轉之前已移轉物件] 移轉作業類型進行移轉。Although you can migrate a virtual application package by using object migration, the packages cannot be migrated by using the migration job type of Previously Migrated Object Migration. 您必須從目的地站台刪除已移轉的虛擬應用程式套件,然後建立新的移轉作業來移轉虛擬應用程式。Instead, you must delete the migrated virtual application package from the destination site and then create a new migration job to migrate the virtual application.

所有移轉作業的一般規劃General planning for all migration jobs

使用 [建立移轉作業精靈] 建立移轉作業將物件移轉至您的目的地階層。Use the Create Migration Job wizard to create a migration job to migrate objects to your destination hierarchy. 您建立的移轉作業類型會決定可移轉的物件。The type of the migration job that you create determines which objects are available to migrate. 您可以建立並使用多項移轉作業從相同的來源站台或多個來源站台移轉資料。You can create and use multiple migration jobs to migrate data from the same source site or from multiple source sites. 使用某一種類型的移轉作業並不會阻止您使用另一種類型的移轉作業。The use of one type of migration job does not block the use of a different type of migration job.

成功執行移轉作業後,其狀態會列出為 [已完成] 且無法再次執行。After a migration job runs successfully, its status is listed as Completed and it cannot be run again. 不過,您可以建立新的移轉作業來移轉原始作業所移轉的任何物件,而且新的移轉作業也可包含其他物件。However, you can create a new migration job to migrate any of the objects that were migrated by the original job, and the new migration job can include additional objects as well. 當您建立其他移轉作業時,之前已移轉物件的狀態會顯示為 [已移轉] 。When you create additional migration jobs, the objects that have been previously migrated show the state of Migrated. 您可以選取這些物件並再次移轉,但除非物件已在來源階層中更新,否則不需要再次移轉這些物件。You can select these objects to migrate them again, but unless the object has been updated in the source hierarchy, migrating these objects again is not necessary. 如果物件最初移轉後已在來源階層中更新,當您使用移轉作業類型 [移轉後修改的物件] 時可以識別該物件。If the object has been updated in the source hierarchy after it was originally migrated, you can identify that object when you use the migration job type of Objects modified after migration.

您可以在移轉作業執行之前將它刪除。You can delete a migration job before it runs. 不過,移轉作業完成後,仍會在 Configuration Manager 主控台中顯示且無法刪除。However, after a migration job finishes, it remains visible in the Configuration Manager console and cannot be deleted. 每一項已完成或尚未執行的移轉作業,都會繼續在 Configuration Manager 主控台中顯示,直到您完成移轉程序並清理移轉資料。Each migration job that has finished or has not yet run remains visible in the Configuration Manager console until you finish the migration process and clean up migration data.

注意

在您使用 [清理移轉資料] 動作完成移轉後,可以重新設定相同的階層作為目前的來源階層,以便再次顯示您之前移轉的物件。After you have finished migration by using the Clean Up Migration Data action, you can reconfigure the same hierarchy as the current source hierarchy to restore visibility to the objects you previously migrated.

在 Configuration Manager 主控台中選取移轉作業,然後選擇 [作業中的物件] 索引標籤,即可檢視任何移轉作業中包含的物件。You can view the objects contained in any migration job in the Configuration Manager console by selecting the migration job and then choosing the Objects in Job tab.

使用以下各節中的資訊可幫助您規劃所有移轉作業。Use the information in the following sections to help you plan for all migration jobs.

選取資料Data selection

當您建立集合移轉作業時,必須選取一個或多個集合。When you create a collection migration job, you must select one or more collections. 選取集合後,[建立移轉作業精靈] 就會顯示與集合相關聯的物件。After you select the collections, the Create Migration Job wizard shows the objects that are associated with the collections. 根據預設,與所選取集合相關聯的所有物件都會移轉,但是您可以取消核取不想要隨該作業移轉的物件。By default, all objects associated with the selected collections are migrated, but you can uncheck the objects that you do not want to migrate with that job. 如果您取消核取的物件有相依物件,這些相依物件也會一併取消核取。When you uncheck an object that has dependent objects, those dependent objects are also unchecked. 所有取消核取的物件都會新增至排除清單中。All unchecked objects are added to an exclusion list. 排除清單上的物件會從未來移轉作業的自動選取範圍內移除。Objects on an exclusion list are removed from automatic selection for future migration jobs. 您必須手動編輯排除清單,才能將您要在未來建立的移轉作業中自動選取進行移轉的物件移除。You must manually edit the exclusion list to remove objects that you want to have automatically selected for migration in migration jobs you create in the future.

已移轉內容的站台擁有權Site ownership for migrated content

當您移轉部署的內容時,必須將內容物件指派至目的地階層中的站台。When you migrate content for deployments, you must assign the content object to a site in the destination hierarchy. 此站台就會變成目的地階層中該內容的擁有者。This site then becomes the owner for that content in the destination hierarchy. 雖然目的地階層的頂層站台是實際移轉內容中繼資料的站台,但它會是跨網路存取內容之原始來源檔案的指派站台。Although the top-level site of your destination hierarchy is the site that actually migrates the metadata for content, it is the assigned site that accesses the original source files for the content across the network.

若要盡可能減少移轉期間使用的網路頻寬,請考慮將內容的擁有權傳送至最近的可用站台。To minimize the network bandwidth that is used during migration, consider transferring ownership of content to the closest available site. 由於與內容相關的資訊會在 Configuration Manager 中全域共用,因此每個站台都可以使用。Because information about the content is shared globally in Configuration Manager, it will be available at every site.

使用資料庫複寫,即可在目的地階層的所有站台上共用內容相關資訊。Information about content is shared to all sites in the destination hierarchy by using database replication. 不過,您指派至主要站台,然後部署到其他主要站台發佈點的內容仍會使用以檔案為基礎的複寫來傳輸。However, any content that you assign to a primary site and then deploy to distribution points at other primary sites transfers by using file-based replication. 這項傳輸是透過管理中心網站路由傳送至其他各主要站台。This transfer is routed through the central administration site and then to each additional primary site. 在您將站台指派為內容擁有者時,藉由移轉前或移轉期間,將您規劃發佈至多個主要站台的套件集中化,就能降低資料傳輸量,使用較低的網路頻寬。By centralizing packages that you plan to distribute to multiple primary sites before or during migration when you assign a site as the content owner, you can reduce data transfers across low-bandwidth networks.

已移轉資料的以角色為基礎的系統管理安全性範圍Role-based administration security scopes for migrated data

您將資料移轉至目的地階層時,必須將一個或多個以角色為基礎的系統管理安全性範圍指派至其資料已移轉的物件。When you migrate data to a destination hierarchy, you must assign one or more role-based administration security scopes to the objects whose data is migrated. 這樣可確保只有適當的系統管理使用者可在移轉後存取此資料。This ensures that only the appropriate administrative users have access to this data after it is migrated. 您指定的安全性範圍是由移轉作業定義,並且會套用至該作業所移轉的每個物件。The security scopes that you specify are defined by the migration job and are applied to each object that is migrated by that job. 如果您需要將不同的安全性範圍套用至不同的物件集合,而且想要在移轉期間指派這些範圍,則必須使用不同的移轉作業移轉不同的物件集合。If you require different security scopes to be applied to different sets of objects and you want to assign those scopes during migration, you must migrate the different sets of objects by using different migration jobs.

在您設定移轉作業之前,請先檢閱以角色為基礎的系統管理如何在 Configuration Manager 中運作。Before you set up a migration job, review how role-based administration works in Configuration Manager. 必要時,為您移轉的資料設定一或多個安全性範圍,以控制哪些人員可存取目的地階層中的已移轉物件。If necessary, set up one or more security scopes for the data that you migrate to control who will have access to the migrated objects in the destination hierarchy.

如需安全性範圍與以角色為基礎之系統管理的詳細資訊,請參閱 Configuration Manager 以角色為基礎之系統管理的基礎For more about security scopes and role-based administration, see Fundamentals of role-based administration for Configuration Manager.

檢閱移轉動作Review migration actions

當您設定移轉作業時,[建立移轉作業精靈] 會顯示確保移轉成功所需採取之動作的清單,以及 Configuration Manager 在移轉所選取資料期間所採取動作的清單。When you set up a migration job, the Create Migration Job wizard shows a list of actions that you must take to ensure a successful migration and a list of actions that Configuration Manager takes during the migration of the selected data. 請詳細檢閱這項資訊,以確保獲得預期的結果。Review this information carefully to check the expected outcome.

排定移轉作業Schedule migration jobs

根據預設,移轉作業會在建立之後立即執行。By default, a migration job runs immediately after it is created. 不過,您可以在建立作業時或藉由編輯作業的內容,指定何時執行移轉作業。However, you can specify when the migration job runs when you create the job or by editing the properties of the job. 您可以如下排定執行移轉作業:You can schedule the migration job to run as follows:

  • 立即執行作業Run the job now

  • 於特定開始時間執行作業Run the job at a specific start time

  • 不執行作業Not run the job

指定移轉之資料的衝突解決方式Specify conflict resolution for migrated data

根據預設,除非您設定移轉作業略過或覆寫之前已移轉至目的地資料庫資料,否則移轉作業不會覆寫目的地資料庫中的資料。By default, migration jobs do not overwrite data in the destination database unless you configure the migration job to skip or overwrite data that has previously been migrated to the destination database.

規劃集合移轉作業Plan for collection migration jobs

集合移轉作業僅適用於從來源階層 (執行支援的 Configuration Manager 2007 版本) 移轉資料。Collection migration jobs are available only when you migrate data from a source hierarchy that runs a supported version of Configuration Manager 2007. 依集合進行移轉時,請指定一個或多個要進行移轉的集合。You must specify one or more collections to migrate when you migrate by collection. 對於您指定的每個集合,移轉作業會自動選取所有相關的物件以進行移轉。For each collection that you specify, the migration job automatically selects all related objects for migration. 例如,若您選取特定的使用者集合,將識別其集合成員以供您移轉與該集合相關聯的部署。For example, if you select a specific collection of users, the collection members are then identified, and you can migrate the deployments associated with that collection. 或者,您也可以選取其他與該成員相關聯的部署物件來進行移轉。Optionally, you can select other deployment objects to migrate that are associated with those members. 此處選取的所有項目都會新增到可移轉的物件清單中。All these selected items are added to the list of objects that can be migrated.

當您移轉集合時,Configuration Manager 會同時移轉集合設定,包括維護期間和集合變數,但無法移轉用於 AMT 用戶端佈建的集合設定。When you migrate a collection, Configuration Manager also migrates collection settings, including maintenance windows and collection variables, but it cannot migrate collection settings for AMT client provisioning.

使用以下各節的資訊來瞭解其他設定,以套用至以集合為基礎的移轉作業。Use the information in the following sections to learn about additional configurations that can apply to collection-based migration jobs.

從集合移轉作業排除物件Exclude objects from collection migration jobs

您可以從集合移轉作業中排除特定物件。You can exclude specific objects from a collection migration job. 當您從集合移轉作業中排除特定物件時,該物件會新增至全域排除清單,清單包含從目前來源階層內任何來源站台所建立移轉作業中排除的所有物件。When you exclude a specific object from a collection migration job, that object is added to a global exclusion list that has all the objects that you have excluded from migration jobs created for any source site in the current source hierarchy. 排除清單中的物件仍可在未來作業中進行移轉,不過當您建立以集合為基礎的新移轉作業時,這些物件不會自動包含在其中。Objects on the exclusion list are still available for migration in future jobs but are not automatically included when you create a new collection-based migration job.

您可以編輯排除清單以移除之前排除的物件。You can edit the exclusion list to remove objects that you have previously excluded. 由排除清單移除物件之後,若您在新移轉作業建立期間選取與該物件相關聯的集合,該物件也會自動選取。After you remove an object from the exclusion list, it is then automatically selected when an associated collection is specified during the creation of a new migration job.

不支援的集合Unsupported collections

Configuration Manager 可從 Configuration Manager 2007 來源階層移轉任何預設使用者集合、裝置集合與多數自訂集合。Configuration Manager can migrate any of the default user collections, device collections, and most custom collections from a Configuration Manager 2007 source hierarchy. 不過,若集合中同時包含使用者和裝置,Configuration Manager 無法移轉該集合。However, Configuration Manager cannot migrate collections that contain users and devices in the same collection.

無法移轉下列集合︰The following collections cannot be migrated:

  • 包含使用者和裝置的集合。A collection that has users and devices.

  • 包含不同資源類型集合參照的集合。A collection that has a reference to a collection of a different resource type. 例如某個以裝置為基礎的集合,集合中包含以使用者為主的集合之子集合或連結。For example, a device-based collection that has either a subcollection or a link to a user-based collection. 在此範例中,僅會移轉頂層集合。In this example, only the top-level collection migrates.

  • 會依規則加入未知電腦的集合。A collection that has a rule to include unknown computers. 該集合會進行移轉,但將未知電腦加入的規則將無法進行移轉。The collection migrates, but the rule to include unknown computers does not migrate.

空集合Empty collections

空集合意指沒有任何相關聯資源的集合。An empty collection is a collection that has no resources associated with it. Configuration Manager 移轉空集合時,會將該集合轉換成組織資料夾,但資料中不包含任何使用者或裝置。When Configuration Manager migrates an empty collection, it converts the collection to an organizational folder that has no users or devices. 這個資料夾將建立於 Configuration Manager 主控台之 [資產與相容性] 工作區的 [使用者集合] 或 [裝置集合] 節點下,並以該空集合的名稱來建立。This folder is created with the name of the empty collection under the User Collections or Device Collections node in the Assets and Compliance workspace in the Configuration Manager console.

連結的集合與子集合Linked collections and subcollections

當您移轉已連結至其他集合或擁有子集合的集合時,除了連結的集合與子集合以外,Configuration Manager 會同時在 [使用者集合] 或 [裝置集合] 節點下建立一個資料夾。When you migrate collections that are linked to other collections or that have subcollections, Configuration Manager creates a folder under the User Collections or Device Collections node in addition to the linked collections and subcollections.

集合相依性與包含物件Collection dependencies and include objects

當您在 [建立移轉作業精靈] 中指定要移轉的集合時,系統將自動選取任何相依的集合以包含到移轉作業中。When you specify a collection to migrate in the Create Migration Job wizard, any dependent collections are automatically selected to be included with the job. 此行為可確保在移轉之後所有必要的資源仍可使用。This behavior ensures that all necessary resources are available after migration.

例如:您為執行 Windows 10 的裝置選取集合,該集合命名為 Win_10For example: You select a collection for devices that run Windows 10 and is named Win_10. 此集合僅限於包含您所有用戶端作業系統的集合,且該集合命名為 All_ClientsThis collection is limited to a collection that has all your client operating systems and is named All_Clients. 將自動選取集合 All_Clients 以用於移轉作業。The collection All_Clients will be automatically selected for migration.

集合限制Collection limiting

使用 Configuration Manager 最新分支時,集合會是全域資料,且會在階層中的每個站台進行評估。With Configuration Manager current branch, collections are global data and are evaluated at each site in the hierarchy. 因此,請規劃在移轉之後,要如何限制集合範圍。Therefore, plan how to limit the scope of a collection after it is migrated. 您可於移轉期間先從目的地階層找出集合來使用,以限制該集合的移轉後範圍,避免移轉後的集合包含非預期的成員。During migration, you can identify a collection from the destination hierarchy to use to limit the scope of the collection that you are migrating so that the migrated collection does not include unanticipated members.

例如,在 Configuration Manager 2007 中,將於建立集合的所在站台與子站台上為集合進行評估。For example, in Configuration Manager 2007, collections are evaluated at the site that creates them and at child sites. 公告可能僅會部署至子站台,如此便可將該公告的範圍限制於該子站台。An advertisement might be deployed to only a child site, and this would limit the scope for that advertisement to that child site. 相較之下,Configuration Manager 最新分支集合則會在每個站台進行評估,之後才會為每個站台評估相關聯的公告。In comparison, with Configuration Manager current branch, collections are evaluated at each site and associated advertisements are then evaluated for each site. 集合限制可供您依據另一個集合來縮小集合成員,以避免加入非預期的集合成員。Collection limiting lets you refine the collection members based on another collection to avoid the addition of unexpected collection members.

站台碼取代Site code replacement

若您要移轉的集合包含可識別 Configuration Manager 2007 站台的準則,則必須在目的地階層中指定特定的站台。When you migrate a collection that has criteria that identifies a Configuration Manager 2007 site, you must specify a specific site in the destination hierarchy. 如此可確保移轉後的集合在目的地階層中仍可運作,且其範圍不會變大。This ensures that the migrated collection remains functional in your destination hierarchy and does not increase in scope.

指定移轉後公告的行為Specify behavior for migrated advertisements

根據預設,依集合進行的移轉作業會停用移轉至目的地階層的公告。By default, collection-based migration jobs disable advertisements that migrate to the destination hierarchy. 其包含與公告相關聯的任何程式。This includes any programs that are associated with the advertisement. 若您建立以集合為基礎且其中包含公告的移轉作業,則可在 [建立移轉作業精靈] 的 [設定] 頁面上,看到 [Enable programs for deployment in Configuration Manager after an advertisement is migrated (在公告移轉後啟用 Configuration Manager 部署程式)] 選項。When you create a collection-based migration job that has advertisements, you see the Enable programs for deployment in Configuration Manager after an advertisement is migrated option on the Settings page of the Create Migration Job wizard. 若您選取此選項,將在移轉後啟用與公告相關聯的程式。If you select this option, programs that are associated with the advertisements are enabled after they have migrated. 最佳作法是不要選取此選項。As a best practice, do not select this option. 而是在完成移轉後驗證要接收這些程式的用戶端,再啟用這些程式。Instead, enable the programs after they have migrated when you can verify the clients that will receive them.

注意

只有在您建立以集合為基礎的移轉作業且其中包含公告時,才會看到 [Enable programs for deployment in Configuration Manager after an advertisement is migrated](在公告移轉後啟用 Configuration Manager 部署程式) 選項。You see the Enable programs for deployment in Configuration Manager after an advertisement is migrated option only when you are creating a collection-based migration job and the migration job contains advertisements.

若要在移轉後啟用程式,請在程式內容的 [進階] 索引標籤上清除 [Disable this program on computers where it is advertised](在程式公告所在電腦上停用該程式) 。To enable a program after migration, clear Disable this program on computers where it is advertised on the Advanced tab of the program properties.

規劃物件移轉作業Plan for object migration jobs

有別於集合移轉,您必須選取要移轉的每個物件和物件執行個體。Unlike collection migration, you must select each object and object instance that you want to migrate. 您可以選取個別物件 (例如從 Configuration Manager 2007 階層選取公告,或從 System Center 2012 Configuration Manager 或 Configuration Manager 最新分支階層選取發行),以新增至特定移轉作業的移轉物件清單。You can select the individual objects (like advertisements from a Configuration Manager 2007 hierarchy or a publication from a System Center 2012 Configuration Manager or Configuration Manager current branch hierarchy) to add to the list of objects to migrate for a specific migration job. 物件移轉作業不會將任何未新增到移轉清單的物件移轉到目的地站台。Any objects that you do not add to the migration list are not migrated to the destination site by the object migration job.

除了適用於所有移轉作業的設定之外,以物件為基礎的移轉作業沒有其他任何要規劃的設定。Object-based migration jobs do not have any additional configurations to plan for beyond those applicable to all migration jobs.

規劃先前移轉的物件移轉作業Plan for previously migrated object migration jobs

若已移轉至目的地階層的物件在來源階層中有更新,您可使用 [移轉後已修改的物件] 作業類型再次移轉該物件。When an object that you have already migrated to the destination hierarchy is updated in the source hierarchy, you can migrate that object again by using the Objects modified after migration job type. 例如,若您在來源階層針對套件來源檔案進行重新命名或更新,該套件在來源階層中的版本會遞增。For example, when you rename or update the source files for a package in the source hierarchy, the package version increments in the source hierarchy. 套件版本遞增後,該套件便可依此作業類型識別以進行移轉。After the package version increments, the package can be identified for migration by this job type.

此作業類型與物件移轉類型相似,除了前者在選取要移轉的物件時,可選取的物件僅限於在先前移轉作業移轉後有更新的物件。This job type is similar to the object migration type except that when you select objects to migrate, you can only select from objects that have been updated after they were migrated by a previous migration job.

當您選取此作業類型時,[建立移轉作業精靈] 之 [設定] 頁面上的衝突解決行為,會設定為覆寫先前移轉的物件。When you select this job type, the conflict resolution behavior on the Settings page of the Create Migration Job wizard is configured to overwrite previously migrated objects. 您無法變更這項設定。This setting cannot be changed.

注意

此移轉作業可識別由來源階層自動更新的物件以及由系統管理使用者更新的物件。This migration job can identify objects that are automatically updated by the source hierarchy and objects that an administrative user updates.