SCCM 2007 Secondary to SCCM 2012 Secondary Site

we are planning to upgrade SCCM 2007 secondary to SCCM 2012 Secondary Site, As per the TechNet document that I understand i can't do in place upgrade of Secondary site. I can do only upgrade
of 2007 DP to 2012 DP,
This is what I plan,
1. Install a SCCM 2012 Secondary site
2. Enable DP sharing in 2012 and share the DP of 2007
3. Upgrade the 2007 DP into 2012 DP on 2012 Secondary Site.
My question is,
1. How to copy the DP package to 2012 Secondary Server DP, it will happen during the upgrade or we need to use Export/extract Content feature in SCCM 2012
2. How the client migration will happen? Do we need to distribute the 2012 client prior to DP update or we can use client push to upgrade old client.
3. before share the DP, do i have to remove the MP, PXE role on the 2007 secondary?
Thanks for your support

I have already few packages available in that DP that I am going to migrate
The second shared DP that I want to migrate to 2012, but it is not working.
Do I need to specify any thing in reassign distribution point wizard, because I only select the site code where I want to migrate the 2007 DP, and all other option I leave default and client on next.
This is what I am trying to do.
I have build a SCCM 2012 Primary and Secondary Server and I am trying to move the DP from exiting SCCM 2007 Secondary Site DP to 2012 Secondary Site.
I set a source hierarchy for primary server with enable shared DP then I am trying to reassign a DP.

Similar Messages

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

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

Can I use SCCM 2007 to deploy SCCM 2012 Agent

I was reading the scenarios for deploying the SCCM 2012 agent here
http://technet.microsoft.com/en-us/library/gg682132.aspx
I have been planning to deploy the 2012 agent using an SCCM 2007 deployment package. I am not migrating any data/packages/collections/anything from SCCM 2007.
I am looking for a sane way to deploy 2000ish clients a day for 2 weeks and be done.
I figure they are all SCCM 2007 clients so lets deploy 2012 agent using SCCM 2007.
I read the following in the link above and it sounds like the way I want to go – use SCCM 2007 software distribution…
Upgrade installation by using application management
Upgrades clients to a newer version by using Configuration Manager application management. You can also use Configuration Manager 2007 software
distribution to upgrade clients to System Center 2012 Configuration Manager.
Then later in the same document there is this…
How to Upgrade Configuration Manager Clients by Using a Package and Program
You can use Configuration Manager to create and deploy a package and program that upgrades the client software for selected computers in your hierarchy. A package definition file
is supplied with Configuration Manager that populates the package properties with typically used values. You can customize the behavior of the client installation by specifying additional command line properties.
You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client.
What???!?? There is no Automatic client upgrade feature in 2007 – so how does that even make sense? In one section, it says I can deploy the 2012 Agent using SCCM 2007 software distribution, and then later in the same document, it
says I can't. I am probably misunderstanding somthing.
Is it possible to make a package/program in SCCM 2007 that will make targeted clients upgrade to Agent 2012 and join the new SCCM 2012 Site?

I tested this (deploying 2012 agent using existing 2007 SCCM infrastructure) with a few test systems at my desk and it seems to work pretty smoothly. I made a package to deploy SCCM 2012 SP1 and added it to my SCCM 2007 Site. Then I deployed
the 2012 agent from 2007 and it worked great. If it works this well in production, I will be able to migrate all of my clients in less than a weeks time.
I have not published the 2012 site information in AD - and I don't plan to. We would have some overlapping site boundaries - and in 2012 it seems its unnecessary in a single site hierarchy. I AM planning to use boundaries to assign
DPs, but thankfully site and DP boundaries have been separated. It works great to just specify the site in everything and not worry about auto discovery. My clients don't move among sites since I only have one large site.
Sorry that I somehow posted this same question twice, and thanks for cleaning that up.
In my installation, I just called ccmsetup.exe with the following command line...
/mp:myMP.mydomain.com CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=1000000 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=myMP.mydomain.com SMSSITECODE=CCM
I am not sure that I need to specify the MP twice, but it is working to do so. I'm also not sure whether the log and cache flags will be honored since there are existing settings from SCCM2007 agent. I think that the 2012 install will not change
these settings upon installation, but it does not appear to hurt the process to include them just in case it does work.

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

Unable to move SCCM 2007 database to SQL 2012 SP1

Hi ,
We want to Move
SCCM 2007 R3 database to SQL Server 2012 SP1.
SCCM server Version :
4.00.6487.2000
Build Number : 6487
But it says fatal error during the move wizard.
In ConfigMgrSetup.log it says :
***SqlError: [42000][102][Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '99901'. : SiteControl_ins_upd
***SqlError: [42000][102][Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '99901'. : SiteControl_ins_upd
I already installed following updates on SCCM server , but still it failed to move.
2676737
2676776

This would be manual process. The simplest way to fix them is to reinstall the reporting point.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

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

Can I go to SCCM 2007 after deploying SCCM 2012?

About a month ago I deployed SCCM 2012 in my Lab environment.
The testing I conduct supports a Security Engineering team.
I’m running 100 servers, 2003 & 2008 R2, and 40 XP and Win7 Clients (most Win7).
After a month of troubleshooting it still will not function correctly.
30% of the clients show failed Client Health status, I can’t get the system to auto install via GPO, and of the simple MS updates I’ve pushed, only about 20% clients work.
I’ve had a ticket with MS open for over a month now on the Client install piece but they have largely ignored me.
It’s been two weeks since I spoke with a MS tech, and that was after requesting the case be elevated.
After bouncing a few emails back and forth the Tier II Tech has never called me during my work Hrs.
8-5 EST.
Is it possible to install SCCM 2007 once you have expanded the Schema to install SCCM 2012?
Absent that I’ll be forced to scrap SCCM and go with WSUS for updates for the short run.
This issue is starting to really impact production issues and has to get either solved or bypassed.
Regards,
Bryan
Arlington VA

I'd recommend that you run the Schema Expansion tool that comes with Configuration Manager 2007.
The reason being is that 2012 has done away with the SLP, meaning that this may or may not be included in it's version of the schema extensions. However, Configuration Manager 2012 does not have anything 'new' in its schema expansion, so you can safely 'downgrade'
to 2007, but as I said, run the 2007 schema extension tool just in case the SLP attributes are not included in the 2012 schema expansion.
I am more curious as to the problems you're experiencing with 2012 though, if your having problems with 2012 I don't see how reverting to 2007 will resolve the problems?
Kriss Milne | MCSE
*Please click 'Vote As Helpful' or 'Mark as Answer' if a post has helped you or answered your question*

Migrating MBAM 2.0 Integration from SCCM 2007 R3 to SCCM 2012 R2

Hello--
We are preparing to migrate our client base from SCCM 2007 to SCCM 2012 R2. We have MBAM 2.0 integrated with SCCM 2007 and need to know what steps/process is needed to successfully move the integration over to SCCM 2012.
I know that the .mof files need to be modified, but what else do we need to do? Re-run the SCCM Integration Setup on the MBAM SQL Server and SCCM Server?
Any help would be much appreciated!
Thank you!
Matt

TPM ownership info is hit or miss. I personally have never had to use it, but I now that we have a few machines that get configured incorrectly and we have to manually initialize and take ownership of the TPM, so that information does not make into MBAM.
How would we go about moving the DB? I agree that building the new implementation sounds desirable.
Thanks!
Matt

OSD: upgrade sccm 2007 (XP) client to 2012, then deploy TS

Hi,
We have some Windows XP machines in our SCCM 2007. They are discovered via AD in SCCM 2012.
Now we would like to upgrade their client to SCCM 2012 then deploy (available) a task sequence to it (Windows 7 install). This way users can choose whenever to upgrade to Windows 7.
My questions:
*When I right click an XP/SCCM 2007 client and choose upgrade, nothing happens. How can I troubleshoot/follow the upgrade?
*Should the task sequence (SCCM MDT) contain a particular step or can we use the same as a bare metal (PXE) deploy (we do not want to keep any data from the pc)?
Please advise,
J.
Jan Hoedt

Do I understand it correct, that you are trying a Client Push Installation? If so, then start with looking at the ccm.log on the server-side for errors. That log file contains all the information about the push action.
You should be able to use the same task sequence. Just check the deployment settings and the first action of the task sequence (make sure it restarts in WinPE).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Help me how migrate SCCM 2007 queries into SCCM 2012 queries

Hi,
I know query migration is not possible to 2012 SCCM. Any possible way ..?
Like powershell or script?

Hi,
These might be helpful for you to create your own script.
http://msdn.microsoft.com/en-us/library/hh949058.aspx
http://msdn.microsoft.com/en-us/library/cc145430.aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 Secondary Site Migration

we have to migrate more then 50 Secondary Site to SCCM 2012 Secondary Site. Since we have to low-bandwidth connection for the remote site we prefer to go with SCCM 2012 Secondary site inside of DP.
I know we can migrate SCCM 2007 Secondary to SCCM 2012 DP and SCCM 2007 DP to SCCM 2012 DP.
But is there a way i can move the distribution point package from SCCM 2007 Secondary to SCCM 2012 Secondary Site?
when i try to migrate migrate SCCM 2007 Secondary Site DP to SCCM Secondary Site 2012, it uninstall the 2007 Secondary site and upgrade the DP to SCCM 2012 under the 2012 Secondary site.
But my requirement is to move the old SCCM 2007 secondary site package to SCCM 2012 Secondary site DP, is there any tool to manage this activity?
or what is the best practice to do this migration.

Hi,
You could use prestage content in SCCM 2012 to send packages to remote DP.
Configuration Manager 2012: Content Prestaging and Remote Content Distribution
http://blogs.technet.com/b/inside_osd/archive/2011/04/11/configuration-manger-2012-content-prestaging.aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Migrate Windows XP to Windows 7 in secondary site using sccm 2007

Hi all,
I have migrated Windows XP to Windows 7 using SCCM 2007 R3 SP2 in the primary site and a DHCP server is available. Now I need to do the same exercise to an XP machine in a secondary site but there is no DHCP server, all machines are configured with static
IPs. Do I need to install temporary DHCP server there or I have other options?

As mentioned, to my knowledge, there's nothing built in to handle this. You can try using the capture tasks as I mentioned but I don't think that they will preserve the IP all the way into the deployed Windows instance. For this, you will have to build
some type of custom solution.A quick search of the web should turn up results:
http://www.bing.com/search?q=osd+without+dhcp&src=IE-TopResult&FORM=IETR02&conversationid=
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2007 - All clients from primary site have vanished from central site collections

Hi all,
we have a SCCM 2007 R2 setup with one central site, one Primary Site (A) with a secondary site hanging off it and another Primary Site (B). Suddenly all the clients from the Primary Site A (and also it's Secondary Site) have vanished from the central
site. All the clients are still present when we check Collections from the admin console on Primary Site A site server - they have simply disappeared when we check Collections from the Central Site admin console.
Can anyone provide any info on a good starting point for troubleshooting this issue? As a sidenote, we can still push packages out to the Primary Site A distribution point and both the Primary and Central site can communicate/ping each other.
Any help/info would be much appreciated!
Thanks

Check the
site replication on central site, is that SQL is working fine, and also see the
inbox folder in central site, might be there is backlog and those DDR files are
not processing, and after maintenance they got deleted.<o:p></o:p>
please run
the heartbeat discovery by hour or day, and once the clients will sent all the
DDR files then they will appears again.<o:p></o:p>
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

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

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 Secondary to SCCM 2012 Secondary Site

Similar Messages

Maybe you are looking for