SCCM 2007-2012 migration job

Hi,
We have an empty SCCM 2012 R2 environment (only testmachines in it).
Now I would like to migrate some first Windows 7 machines by pushing a SCCM 2012 client to it. Therefore first the collections and packages of SCCM 2007 should be migrated.
So I started an SCCM 2012 Collection migration job from SCCM 2007 to 2012:
1.Selected only the Windows 7 collections (only those should be migrated, not the XP ones)
2.selected software assigned to it (it comes from a DFS-share \\ourcompany\share
3.all with default values, except "Enable programs for deployment"
My questions:
1.It took only 10 minutes to complete (share is 100 GB) but I see now software is not distributed to distribution point.
=> Is that normal? Should I run distribute to distribution point for all packages are rerun migration job with differen values?
2.After step 1, I can now migrate a Windows 7 computer fro SCCM 2007 to 2012, right?
Everything looks fine to me. There is also the object migration but don't think I need it.Just want to doublecheck.
Please advise.
J.
Jan Hoedt

#1: that's default behavior. Packages are migrated, but not distributed to DPs automatically. That's up to you right now.
#2: yes, but that's independent from step #1. You can install the CM12 client to the clients anytime.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

SCCM 2007 & 2012

Hi everyone, I need a urgent support. In my organization we have sccm 2007 & 2012 environment. Both are not interconnected few clients connected to 2012 and rest in 2007. Person who handled this technology earlier has designed, i don't know the exact
reason. Now i am in a position to handle. My knowledge in sccm is basic. My organization is asked to check the status complete sccm servers & clients and give the complete report and progressive plan. Please guide me how to take the current severs &
client health status.
2007 used for - hardware inventory, Software meetering, deployments, wsus. - how are each roles are working condition no idea.
2012 used for - hardware inventory.
Please advice with step by step guide instruction for merging and henceforth to success SCCM in my organization.
Regards
Kumar

And do please start reading the guides at windows-noob here http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

2007 - 2012 migration resources?

hey all,
i'm planning the migration of our SCCM 2007 SP2 server to 2012 R2, and was hoping to get some direction in terms of articles, documentation etc. that anyone could recommend for such a project (hardware/resource/configuration requirements for 2012 installation,
SQL database setup considerations, central/primary site planning, configuring client and distribution/management point setup, etc).
i get the sense that this is going to be a challenge, and want to make sure i'm following the proper steps to get 2012 up and running smoothly.
has anyone tackled this migration before? i'd appreciate any feedback others could give on the topic.
thanks!

This should help you
Official documentation
https://technet.microsoft.com/en-us/library/gg682006.aspx
SCCM 2012 general
http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide.html
SCCM 2007 to 2012 migration specific
http://www.gerryhampsoncm.blogspot.ie/2013/07/configmgr-2012-sccm-2012-sp1-step-by.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2007 to 2012 R2 Migration Data Gathering Error: RPC

Hi Guys,
I am doing Migration from SCCM 2007 to 2012 R2. Facing a RPC connection Error.
Following is the details from Migmcctrl.log
[MigMCtrl]: Migration Manager has received a new job request
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: Start two step scheduling for MIG_SiteMapping
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[Worker]: Start processing status
changed event for MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
5024 (0x13A0)
[Worker]:
Set the schedule item 16777236 start time SMS_MIGRATION_MANAGER
19-03-2014 02:21:57 5024 (0x13A0)
[Worker]:
Set the schedule item 16777236 status to Running
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
5024 (0x13A0)
[Worker]: End processing status changed
event for MIG_SiteMapping.ID=16777236 SMS_MIGRATION_MANAGER
19-03-2014 02:21:57 5024 (0x13A0)
[Worker]: ==================== Sync
Agent Job 16777236 Started ====================
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
5024 (0x13A0)
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: No item found. Sleep until the next event.
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: End two step scheduling for MIG_SiteMapping
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: Start two step scheduling for MIG_Job
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: No item found. Sleep until the next event.
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigrationManager]: End two step scheduling for MIG_Job
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[MigMCtrl]: the workitem queue is full! SMS_MIGRATION_MANAGER
19-03-2014 02:21:57 4648 (0x1228)
[MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s).
SMS_MIGRATION_MANAGER 19-03-2014 02:21:57
4648 (0x1228)
[Worker]:
========== Start prerequisite checking ==========
SMS_MIGRATION_MANAGER 19-03-2014 02:22:05
5024 (0x13A0)
[Worker]:
Validating source site for central site ...
SMS_MIGRATION_MANAGER 19-03-2014 02:22:05
5024 (0x13A0)
[Worker]:
========== End prerequisite checking ==========
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]: ==================== Sync
Agent Job 16777236 Ended ====================
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
ERROR: [Worker]: System.Runtime.InteropServices.COMException
(0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Adapters.WmiObjectManager.GetObjects(ObjectSearchCriteria criteria) at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Adapters.WmiObjectManager.TryGetInstance(ObjectKey
objKey) at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.ObjectManager.GetInstance(ObjectKey objKey, LibraryContext context) at Microsoft.ConfigurationManagement.SoftwareLibrary.ObjectSerialization.Library.Get[T](Expression`1
key) at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<get_ExecutionPlan>d__7.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.Job`1.ExecuteNext()
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]: Start processing status
changed event for MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]:
Set the schedule item 16777236 end time SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
[Worker]:
Set the schedule item 16777236 status to Failed
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]: End processing status changed
event for MIG_SiteMapping.ID=16777236 SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
[Worker]: Disposing Job 16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]: Removing Job 16777236 from
job manager. SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
[Worker]: Removing the Job with Id
16777236. SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
[Worker]: Disposing worker
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
5024 (0x13A0)
[Worker]: Disposing current site
connection SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = The remote procedure call failed., 800706be
SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = The remote procedure call failed., 800706be
SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 5024 (0x13A0)
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Start two step scheduling for MIG_SiteMapping
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: The item MIG_SiteMapping 16777236 is scheduled to run at 03/19/2014 13:21:36 UTC, 03/19/2014 18:51:36 Local Time, sleep for 03:46:40.4440000.
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: End two step scheduling for MIG_SiteMapping
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Start two step scheduling for MIG_Job
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: No item found. Sleep until the next event.
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: End two step scheduling for MIG_Job
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigMCtrl]: the workitem queue is full! SMS_MIGRATION_MANAGER
19-03-2014 02:34:55 4648 (0x1228)
[MigMCtrl]: NOTIFY job manager ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777236.SYN ).
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Start processing schedule changed event for MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:55
4648 (0x1228)
[MigrationManager]: Update the DateNextRun of the schedule item MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigrationManager]: Calculating the next run time ...
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigrationManager]: This is a recurring schedule token.
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigrationManager]: This item already run at 03/19/2014 09:21:57 UTC, 03/19/2014 14:51:57 Local Time, the next run time is 03/19/2014 13:21:57 UTC, 03/19/2014 18:51:57 Local Time.
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigrationManager]: Check requested operation for schedule item MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigrationManager]: End processing schedule changed event for MIG_SiteMapping.ID=16777236
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigMCtrl]: EVENT raised ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777236.SYN ).
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
[MigMCtrl]: 1 instruction file processed. SMS_MIGRATION_MANAGER
19-03-2014 02:34:56 4648 (0x1228)
[MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s).
SMS_MIGRATION_MANAGER 19-03-2014 02:34:56
4648 (0x1228)
help me out please.
Thanks

Hi Guys ,I figured out the issue.
It was the boundary in SCCM 2007.Actually my SCCM 2007 and SCCM 2012 server were accessing the same Active Directory Site-(Default First Site Name).
I deleted the boundary and every thing went well.
So thing is SCCM 2007 and SCCM 2012 should not fall under same active directory Site.
Cheers

SCCM 2007 to 2012 R2 Migration Data Gathering Error

Hi guys ,
I am working on SCCM 2007 to 2012 migration and stucked at data gathering process. Following
error i am getting while gartering data process.I have made the erroe details bold to easily find.
Migmcctrl.log is showing this error:
[Worker]: Start syncing #MIG_Entity.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.957+420><thread=5024 (0x13A0)>
[Worker]:
Query against Legacy Site , @rowversion=00-00-00-00-00-0A-4C-E2, @collectionrowversion=00-00-A2-DD-00-20-26-14, @SourceSiteCode=ABC:
SELECT (CASE WHEN ISNULL(ext_cilp.DisplayName, ext_ci.CI_ID) IS NULL THEN NULL
ELSE dbo.fnSCCMMultiByteToWideChar(
CASE WHEN (SELECT LocaleID FROM SMSData) IS NULL THEN (SELECT d.LocaleID FROM SMSData d)
WHEN (SELECT LocaleID FROM SMSData) IN (-1, 0, 65535, 1024, 2048) THEN (SELECT d.LocaleID FROM SMSData d)
ELSE (SELECT LocaleID FROM SMSData) END,
CONVERT(VARBINARY(MAX), ISNULL(ext_cilp.DisplayName, ext_ci.CI_ID))) END) as EntityName, CONVERT(NVARCHAR(256), ext_ci.CI_ID) as ObjectKey,
ext_ci.CIType_ID as ObjectTypeID, ext_ci.rowversion AS rowversion, ext_ci.ChangeAction as ChangeAction,
ext_ci.CI_UniqueID as UniqueID FROM SCCM_Ext.vex_ConfigurationItems as ext_ci LEFT JOIN v_LocalizedCIProperties_SiteLoc
as ext_cilp ON ext_ci.CI_ID=ext_cilp.CI_ID WHERE (1 = 1 OR ISNULL(ext_ci.SourceSite, @SourceSiteCode) = @SourceSiteCode) AND ext_ci.rowversion > @rowversion AND
ISNULL(ext_ci.CIType_ID, 0)<>1 AND ISNULL(ext_ci.CIType_ID, 0)<>8 AND ISNULL(ext_ci.CIType_ID,
0)<>9~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.962+420><thread=5024 (0x13A0)>
[Worker]:
End syncing object tables.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.964+420><thread=5024 (0x13A0)>
[Worker]:
========== End syncing objects metadata ==========~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.965+420><thread=5024 (0x13A0)>
ERROR: [Worker]:
System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed. at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method) at System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
method, SqlCommand command) at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.ConfigurationManagement.MigrationManager.LegacyRepository.GetDataReader(String sqlQuery, Dictionary`2 parameters, Boolean ignoreLocalSite)
at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<SyncObjectsInformation>d__25.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext()
at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext()~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.966+420><thread=5024 (0x13A0)>
STATMSG: ID=8617 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS=SCCM2012R2.RAT.Com SITE=ASL PID=2804 TID=5024 GMTDATE=Wed Mar 19 09:11:07.966 2014 ISTR0="SCCM2012R2.RAT.Com (ASL)" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.966+420><thread=5024 (0x13A0)>
[Worker]: ==================== Sync
Agent Job 16777235 Ended ====================~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.967+420><thread=5024 (0x13A0)>
ERROR: [Worker]: System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed. at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
at System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String method, SqlCommand command) at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.ConfigurationManagement.MigrationManager.LegacyRepository.GetDataReader(String
sqlQuery, Dictionary`2 parameters, Boolean ignoreLocalSite) at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<SyncObjectsInformation>d__25.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext()
at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<get_ExecutionPlan>d__7.MoveNext()
at Microsoft.ConfigurationManagement.MigrationManager.Job`1.ExecuteNext()~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.968+420><thread=5024 (0x13A0)>
[Worker]: Start processing status
changed event for MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.975+420><thread=5024 (0x13A0)>
[Worker]:
Set the schedule item 16777235 end time~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.976+420><thread=5024 (0x13A0)>
[Worker]: Set the schedule item 16777235 status to Failed~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.976+420><thread=5024 (0x13A0)>
[Worker]: End processing status changed
event for MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.982+420><thread=5024 (0x13A0)>
[Worker]: Disposing Job 16777235~~
$$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.984+420><thread=5024 (0x13A0)>
[Worker]: Removing Job 16777235 from
job manager.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.984+420><thread=5024 (0x13A0)>
[Worker]: Removing the Job with Id
16777235.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.985+420><thread=5024 (0x13A0)>
[Worker]: Disposing worker~~ $$<SMS_MIGRATION_MANAGER><03-19-2014
02:11:07.985+420><thread=5024 (0x13A0)>
[Worker]: Disposing current site
connection~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.985+420><thread=5024 (0x13A0)>
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131509, 80131509~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.985+420><thread=5024 (0x13A0)>
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131509, 80131509~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.986+420><thread=5024 (0x13A0)>
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.996+420><thread=4648
(0x1228)>
[MigrationManager]: Start two step scheduling for MIG_SiteMapping~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.997+420><thread=4648 (0x1228)>
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:07.997+420><thread=4648 (0x1228)>
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.022+420><thread=4648 (0x1228)>
[MigrationManager]: The item MIG_SiteMapping 16777235 is scheduled to run at 03/19/2014 13:10:06 UTC, 03/19/2014 18:40:06 Local Time, sleep for 03:58:58.2280000.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014
02:11:08.039+420><thread=4648 (0x1228)>
[MigrationManager]: End two step scheduling for MIG_SiteMapping~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.039+420><thread=4648 (0x1228)>
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.040+420><thread=4648
(0x1228)>
[MigrationManager]: Start two step scheduling for MIG_Job~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.040+420><thread=4648 (0x1228)>
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.041+420><thread=4648 (0x1228)>
[MigrationManager]: Step 2. Query the first item in order of DateNextRun ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.064+420><thread=4648 (0x1228)>
[MigrationManager]: No item found. Sleep until the next event.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.084+420><thread=4648 (0x1228)>
[MigrationManager]: End two step scheduling for MIG_Job~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.084+420><thread=4648 (0x1228)>
[MigMCtrl]: the workitem queue is full!~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.084+420><thread=4648 (0x1228)>
[MigMCtrl]: NOTIFY job manager ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777235.SYN ).~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.085+420><thread=4648 (0x1228)>
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.086+420><thread=4648
(0x1228)>
[MigrationManager]: Start processing schedule changed event for MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.086+420><thread=4648 (0x1228)>
[MigrationManager]: Update the DateNextRun of the schedule item MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.118+420><thread=4648 (0x1228)>
[MigrationManager]: Calculating the next run time ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.118+420><thread=4648 (0x1228)>
[MigrationManager]: This is a recurring schedule token.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.118+420><thread=4648 (0x1228)>
[MigrationManager]: This item already run at 03/19/2014 09:10:27 UTC, 03/19/2014 14:40:27 Local Time, the next run time is 03/19/2014 13:10:27 UTC, 03/19/2014 18:40:27 Local Time.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014
02:11:08.119+420><thread=4648 (0x1228)>
[MigrationManager]: Check requested operation for schedule item MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.132+420><thread=4648 (0x1228)>
[MigrationManager]: End processing schedule changed event for MIG_SiteMapping.ID=16777235~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.132+420><thread=4648 (0x1228)>
[MigMCtrl]: EVENT raised ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777235.SYN ).~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.133+420><thread=4648 (0x1228)>
[MigMCtrl]: 1 instruction file processed.~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.133+420><thread=4648 (0x1228)>
[MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s).~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:11:08.133+420><thread=4648 (0x1228)>
[MigMCtrl]: NOTIFY job manager ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777236.SYN ).~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.315+420><thread=4648 (0x1228)>
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.316+420><thread=4648
(0x1228)>
[MigrationManager]: Start processing schedule changed event for MIG_SiteMapping.ID=16777236~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.331+420><thread=4648 (0x1228)>
[MigrationManager]: Update the DateNextRun of the schedule item MIG_SiteMapping.ID=16777236~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.350+420><thread=4648 (0x1228)>
[MigrationManager]: Calculating the next run time ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.350+420><thread=4648 (0x1228)>
[MigrationManager]: This is a recurring schedule token.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.350+420><thread=4648 (0x1228)>
[MigrationManager]: This item hasn't run yet, we will run it immediately.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.351+420><thread=4648 (0x1228)>
[MigrationManager]: Check requested operation for schedule item MIG_SiteMapping.ID=16777236~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.359+420><thread=4648 (0x1228)>
[MigrationManager]: Start operation requested, the scheduled item 16777236 will be started once computing resource is allocated.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.359+420><thread=4648 (0x1228)>
[MigrationManager]: End processing schedule changed event for MIG_SiteMapping.ID=16777236~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.360+420><thread=4648 (0x1228)>
[MigMCtrl]: EVENT raised ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777236.SYN ).~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.360+420><thread=4648 (0x1228)>
[MigMCtrl]: 1 instruction file processed.~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.361+420><thread=4648 (0x1228)>
Connection string = Data Source=(local);Initial Catalog=CM_ASL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.362+420><thread=4648
(0x1228)>
[MigrationManager]: Start two step scheduling for MIG_SiteMapping~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.363+420><thread=4648 (0x1228)>
[MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.363+420><thread=4648 (0x1228)>
[MigrationManager]: Clear the requested operation.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.386+420><thread=4648 (0x1228)>
[MigrationManager]: Calculating the next run time ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.387+420><thread=4648 (0x1228)>
[MigrationManager]: This is a recurring schedule token.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.387+420><thread=4648 (0x1228)>
[MigrationManager]: This item already run at 03/19/2014 09:21:36 UTC, 03/19/2014 14:51:36 Local Time, the next run time is 03/19/2014 13:21:36 UTC, 03/19/2014 18:51:36 Local
Time.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.387+420><thread=4648 (0x1228)>
[MigrationManager]: Set the next run time to 03/19/2014 13:21:36 UTC, 03/19/2014 18:51:36 LocalTime.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.388+420><thread=4648 (0x1228)>
[MigrationManager]: Got an scheduled item 16777236. Set the sleep time to 0.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.411+420><thread=4648 (0x1228)>
[MigrationManager]: End two step scheduling for MIG_SiteMapping~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:36.412+420><thread=4648 (0x1228)>
[MigrationManager]: Impersonation is about to start ...~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:49.554+420><thread=4648 (0x1228)>
[MigrationManager]: Impersonation succeed, current user identity is: rat\cmmig~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:49.555+420><thread=4648 (0x1228)>
Connection string = Data Source=SCCM;Initial Catalog=SMS_ABC;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=True;Application Name="Migration Manager".~~ $$<SMS_MIGRATION_MANAGER><03-19-2014
02:21:49.555+420><thread=4648 (0x1228)>
[MigrationManager]: Impersonation is reverted.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:49.683+420><thread=4648 (0x1228)>
[MigrationManager]: Detected source collation SQL_Latin1_General_CP1_CI_AS~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:57.841+420><thread=4648 (0x1228)>
[MigrationManager]: Detected destination collation SQL_Latin1_General_CP1_CI_AS~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:57.842+420><thread=4648 (0x1228)>
STATMSG: ID=8600 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS=SCCM2012R2.RAT.Com SITE=ASL PID=2804 TID=4648 GMTDATE=Wed Mar 19 09:21:57.843 2014 ISTR0="SCCM2012R2.RAT.Com (ASL)" ISTR1="SCCM.RAT.COM"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:57.853+420><thread=4648 (0x1228)>
[MigrationManager]: Job 16777236 added.~~ $$<SMS_MIGRATION_MANAGER><03-19-2014 02:21:57.854+420><thread=4648 (0x1228)>
I am not getting any solution of this please help.

ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131509
I previously had a similar issue. See blog post here
http://gerryhampsoncm.blogspot.ie/2013/07/configmgr-sccm-2012-migration-sharing.html
In my case one of the boundaries in the 2007 site had an empty Display column and this, it seems, is not allowed.
Have you checked the box to "Enable DP sharing" while you create the Source Hierarchy? If so, try the process with the box unchecked.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to migrate the computers from SCCM 2007 to SCCM 2012

Hello,
Could anyone tell me how to mirgrate the computers present in SCCM 2007 to SCCM 2012.
Does the "collection migration" job migrate the computers or devices present in the collection? I tried this but computers were not migrated.
Should we again discover the computers in SCCM 2012?
Thanks,
SreehariG

There is no migration job in CM12 that will migrate CM07 clients. You need to install CM12 agent on your CM07 client in order to migrate them. During the installation the existing CM07 client will be uninstalled. You can use any supported
client deployment methods to migrate to your new CM12 environment. More information here:
http://social.technet.microsoft.com/Forums/en-US/configmanagermigration/thread/71175a47-22fe-4284-871c-834c0c999075

Help needed -- Considerations to be taken while migrating 2 different SCCM 2007 hierarchies into a single SCCM 2012 Hierarchy.

Hi, I need your help on consolidating two different SCCM 2007 infrastructures into a single SCCM 2012.
We have two different SCCM 2007 Hierarchies, Lets say 123 and ABC
About 123 SCCM 2007 -- On 123 Hierarchy, we have already started migrating clients from SCCM 2007 to SCCM 2012.
About ABC SCCM 2007 -- On ABC Hierarchy, This is still running on SCCM 2007 (This hierarchy only be started migrating once we
are completed migration on 123)
Out of which, we have few co located offices across the globe for both 123 and ABC. Now we are decided to replace the hardware on all these locations by removing the existing two servers (one for 123 and other for ABC,with two different Forest and domains),
and consolidate them into a single server.how can we plan/design to ensure that we covering both hierarchies SCCM clients for the operations.
===================Below are some possibilities we are discussing on================================
1.Is there any way on "System management" in AD to enable access either in 123's domain or ABC's domain.
2.Since we are planning to replace the hardware with Server 2012 R2 with Hyper-V, Create two instances and migrate 123 hierarchy to SCCM 2012 and other instance will serve ABC until we start the migration on this.
========================================================================================
correct me, If i am in wrong direction. Please suggest me the best of doing it. Thanks in advance.
srkr

1) In CM 2012 you can publish data to System Management in other forest but you have to configure the permissions manually and create the forest object in the ConfigMgr console.
2) CM07 and CM2012 instances can co-exist as long as you don't create boundary groups in CM12 for site assignment (that will cause overlapping boundaries if you still have boundaries in Cm07)
Kent Agerlund | My blogs: blog.coretech.dk and
SCUG.DK | Twitter: @Agerlund | Linkedin:
Kent Agerlund

Software Distribution & Patching Design Issues - Migration of Packages SCCM 2007 to Application or Conventional Packages in SCCM 2012

Hi All
I am starting in discussion to deep root on Software Distribution & Patching model in large environments from SCCM 2007 migrating to SCCM 2012.
Below are certain assertions i am putting forward for your expert views or you may in a similar situation
1- I have migrated the packages from SCCM 2007 to SCCM 2012 as conventional methods, now i am deploying them [ not migrated the advertisements and collections ], so while deploying i am facing a peculiar situation that the deployment when created is of the
name "<<Package name>>(program)". I am not able to rename the deployment for the conventional packages. is there a way out to that??
2- Will the collection queries work the same in SCCM 2012 as was in SCCM 2007??
3- In SCCM 2012 Primary site there is default role called Site System role in that there is tab for proxy settings. I have observed that if do not check the proxy tab there and punch in proxy IP and port then after some time in the WSUS server the update
source and proxy server tab the proxy option gets unchecked and hence the sync in software update point status appears failed. Is that anyone else also has observed !!!!!
Regards Sushain KApoor

This is a duplicate of
https://social.technet.microsoft.com/Forums/en-US/2ddb8170-529b-4652-830e-fd0ade384b98/software-distribution-patching?forum=configmanagermigration
Please do not double post.
Jason | http://blog.configmgrftw.com | @jasonsandys

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2007 Migration to SCCM 2012

Hello,
I read http://social.technet.microsoft.com/Forums/en-US/58ba35e5-d84e-4741-8089-624f5269a2ca/sccm-2012-design-consideration-advice?forum=configmanagergeneral&prof=required with the following notes:
Secondary vs. DP is a subjective call based on two factors: client count and available bandwidth. More clients and/or less bandwidths means secondary site, less clients and/or more bandwidth means DP. Both use a server OS so there's really no cost difference, just some added complexity for a secondary site. Without knowing the bandwidth, no way for me to be able to say one way or the other.
As for IBCM, correct, it's no a primary site server, it's simply a site system that typically hosts an MP, DP, and SUP. The App Catalog Website Point is also applicable.
Are you planning on managing legacy mobile devices or Mac OSX? If not, the Enrollment Proxy Point is not needed -- it's not applicable to IBCM anyway to my knowledge.
Also, the FSP must be on a separate site system so that clients can communicate with it via HTTP.
I have for now two sites:
- 25,000 Desktops on one site
- 1,500 Servers on the second site
in SCCM 2007 I had three sites: One Parent doing the reporting and two child sites handling the inventory, distribution, etc... (No SUP do far)
I have on each child sites 1 DP.
What should be changed for SCCM 2012?
What is "More Clients" or "Less Clients" ?
"More Bandwidth" or "Less Bandwidth"?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello Dom,
If you have Two Primary servers you may need to plan for a CAS (Central administration site), in SCCM 2012 when you have more than one primary server you need a CAS to connect them. But remember the CAS does not
process any client data, DPs nor MPs (hardware nor software inventory), and bear in mind that a primary stand-alone can support up to 100,000 clients, and in SCCM 2012 the big idea is to simplify the hierarchy. So if you have a primary site you can manage
a lot of clients, and you can separate them in your case in boundaries, boundaries in 2012 do two things: Site assignment and content lookup, but they only work with boundary groups, in which you set the limits in the boundary, and latter associate it with
a boundary group.
You can then just have a primary server and remote DPs, and decide how the clients will look for content in the DPs with the boundaries and boundary groups. The bandwidth needs to be really important about sending
packages between sites, or if the boundaries are not configured properly the clients can end up looking for content where it should not. Also don’t forget about fallback packages and content, because DPs and packages can be set as fallback, so if clients
cannot find in a local DP they will search those packages.
Below a few references that may help you with your migration.
Any more questions, please let me know.
References
==========
Planning for Configuration Manager Sites and Hierarchy
http://technet.microsoft.com/en-us/library/gg682075.aspx
Planning for Sites and Hierarchies in Configuration Manager
http://technet.microsoft.com/en-us/library/gg712681.aspx
Migrating Hierarchies in System Center 2012 Configuration Manager
http://technet.microsoft.com/en-us/library/gg682006.aspx
VIDEOS
========
Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007
http://technet.microsoft.com/en-us/video/configuration-manager-2012-plan-deploy-and-migrate-from-configuration-manager-2007.aspx
Microsoft System Center Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012
http://channel9.msdn.com/Events/TechEd/Europe/2012/MGT313
Cheers,
Renato S. Pacheco

How to force site code discovery on all the clients, Migration SCCM 2007 to SCCM 2012

HI,
I migrated SCCM 2007 to SCCM 2012 SP1, but the clients does not update the New Site Code Automatically, if I click on Discovery option the client find the new site, but I need do this automatically because are too many clients.
This registry key does not exist on client computers.
HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min)
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour)
Any Help?
Thanks.

Hello ICH-CR,
Thanks for writing to the SysCtr ConfigMgr forums.
I think there are multiple solutions to this issue and you can choose whatever fits best to your scenario.
1. While upgrading the clients from SCCM 2007 to 2012 you can assign the clients to your ConfigMgr 2012 site.
http://technet.microsoft.com/en-us/library/gg682060.aspx#BKMK_AutomaticAssignment
You just need to ensure that you have a boundary group and boundaries. More details on
http://technet.microsoft.com/en-us/library/13694ac5-8f3b-42a9-8040-b23f21c79637#BMBK_CreateBoundaryGrp
I would suggest the first method because if you create another child site, you shouldn't have to reassign the clients back again. If that is unlikely then use the following script which is method no 2
2.
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327
This is a VBSCRIPT and can be ran from a network location using the PSEXC
3. Here is a smaller script
'Replace with your Site Code sSiteCode = "EnterNewSiteCode"
sMachine
= "."
set oCCMNamespace
= GetObject("winmgmts://"
& sMachine & "/root/ccm")
Set oInstance
= oCCMNamespace.Get("SMS_Client")
set oParams
= oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode
= sSiteCode
oCCMNamespace.ExecMethod
"SMS_Client",
"SetAssignedSite",
oParams
You can use this script as a logon script .
Anurag
Microsoft Certified Professional| Microsoft Certified Technology Specialist (ConfigMgr)
This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights.
My Blog
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Types of SCCM 2007 to SCCM 2012 Migration

Hi all,
Can i know what are the different types of migration we can do from sccm 2007 to sccm 2012 ?
Thanks

Hi,
There are now in-place upgrade so the only option you have is side-by-side migration. Install the new Configuration Manager 2012 infrastructure and migrate you objects, client e.t.c to all the new CM 2012 site server.
Here is a link that will get you started:
http://technet.microsoft.com/en-us/library/gg699364.aspx
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2007 migrated clients (SCCM 2012) are still visible

Hi,
We migrated some SCCM 2007 Windows 7 clients to SCCM 2012 (upgraded the clients via push).
This worked fine for most of the clients but not all so I cannot just delete clients from SCCM 2007.
How can we clean the succesfully migrated? I cannot see which ones are succesfully migrated in SCCM 2007, the all show active (even the succesfully migrated ones).
Pls advise.
J.
Jan Hoedt

The client will become inactive if it's not requesting client policies, sending heartbeats, sending inventories, or sending status messages any more in a period of by default 7 days (but it all depends on the configured intervals). Also, if you
delete clients that are still active, they will come back with the next heartbeat if they are still active.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 to SCCM 2012 client migration via Powershell

Hi
I'm looking for a controlled way to migrate a SCCM 2007 server client to SCCM 2012. A push of SCCM Console is no option.
I 'll do all the testing but hoped to gain some time by having these questions answered:
*can an install of SCCM 2012 client be remotely triggered in one go (no uninstall of 2007 needed)?
*if uninstall is needed (of sccm 2007 client), does it need a reboot?
What command to use (preferrably powershell):
\\ourserver\Client\ccmsetup.exe" -argumentlist "SMSSITECODE=sitecode","SMSMP=oursccmserver","SMSCACHESIZE=8000","FSP=oursccmserver","CCMLOGMAXSIZE=104857600"
OR (guess that's the command SCCM is using)
Install-CMClient-DeviceName$ComputerName-IncludeDomainController$False-SiteCodePRD-ForceReinstall$True-AlwaysInstallClient$True-Verbose
J.
Jan Hoedt

do I need to import the machine in SCCM 2012 also or launching the SCCM 2012 install from a SCCM 2007
will do this?
How will you do that? This does not work at all when using client push obviously. You can only use packages/programs to update clients to CM12 in that case and that's something you did not want to do.
Torsten Meringer | http://www.mssccmfaq.de

MOF file migration from SCCM 2007 to SCCM 2012

Hi,
I have an issue while migrating SCCM 2007 MOF (Configuration.mof) to SCCM 2012,Problem is...
In our infrastructure, We have integrated our custom inventory classes with the logon script.Now we are migrating to SCCM 2012.When i migrate the same Custom inventory classes to SCCM 2012,I can able to compile/migrate, However SCCM 2012 views are not in
sync with SCCM 2007.
Example: If i use SCCM 2007 collection/Query in SCCM 2012 that uses these custom inventory classes, its thrown an error saying that objects in this query are not valid, because of this none of the collections/Queries that uses old inventory classes are not
working.
I dont want to change anything in the logon script...
Can someone please help me on this.Thanks in advance..
srkr

Hi Garth,
Thanks for the reply.
As per my understand,there's nothing to do with SMS_DEF.mof and only Configuration.mof can be editable.
When you say Importing sms_def.mof in SCCM 2012,I guess there's is something i missed out.
Below is the both SMS_DEF.mof and Configuration.mof from SCCM 2007, Also please let me know how to import SMS_DEF.mof in SCCM 2012
************SMS_DEF.MOF*********************
//-- SCCM Report: XXX_AD_Info
[SMS_Report(TRUE),
SMS_Group_Name("XXX AD Info"),
ResID(6200),
ResDLL("SMS_RXPL.dll"),
SMS_Class_ID("XXX|EDADInfo|5.0")]
class XXX_AD_Info
[SMS_Report(TRUE), key]
string KeyName;
[SMS_Report(TRUE)]
string Distinguished_Name;
[SMS_Report(TRUE)]
string AD_Site;
[SMS_Report(TRUE)]
string DCName;
[SMS_Report(TRUE)]
string MachineDomain;
*********Configuration.mof*******************
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
class XXX_AD_Info
[key]
string KeyName;
string Distinguished_Name;
string AD_Site;
string DCName;
string MachineDomain;
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
instance of XXX_AD_Info
KeyName = "XXX AD Info";
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Distinguished-Name"), Dynamic, Provider("RegPropProv")]
Distinguished_Name;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Site-Name"), Dynamic, Provider("RegPropProv")]
AD_Site;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|DCName"), Dynamic, Provider("RegPropProv")]
DCName;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|MachineDomain"), Dynamic, Provider("RegPropProv")]
MachineDomain;
srkr

SCCM 2007-2012 migration job

Similar Messages

Maybe you are looking for