Migate from Sccm 2007 to 2012 and WSUS functionality

We are doing a side-by-side migration from 2007 to 2012.
At present WSUS is installed on the same server as SCCM 2007.
If we do a side-by-side migration, can we use the existing WSUS on the 2007 server whilst in co-existance?
or will we have to install WSUS on the new SCCM 2012 as a full replica.
cheers Mike

You can migrate from 2007 but you need to configure the new environment with exactly the same products and classifications or the migration will fail - you cannot choose some and omit others.
I agree with grundlichkeit and Jörgen. Why would you migrate years of updates for no good reason? Don't worry about XP.
If we do a side-by-side migration, can we use the existing WSUS on the 2007 server whilst in co-existance?
or will we have to install WSUS on the new SCCM 2012 as a full replica.
So, in answer to your question, no you would not re-use the 2007 WSUS. You would also not have a replica on the 2012 server. You would start afresh.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

SCCM 2012: clients from SCCM 2007 to 2012: software available instead of installed

Hi,
We have migrated some Windows 7 clients from SCCM 2007 to SCCM 2012 (in which already hundreds of working W7 clients and their apps -most of them migrated from SCCM 2007).
Now applications are shown as available instead of installed. F.e. Adobe Acrobat is installed but it shows as available.
Please advise howto correct.
J.
Jan Hoedt

Hi,
Does it show the right status after you click "Install" of an application?
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.

Part of a migration project from SCCM 2007 to 2012 SP1 CU3 - Updates no longer working and reporting not correct

Been working on a migration from 2007 sp1 to 2012 sp1 cu3. I first installed directly to sp1 but realized we had a few 8.1 clients being built so I added the cu3 mid-stream. I moved over two small subnets and pushed out some clients.
I was able to push out updates from the 2012 server for OS realted updates to a collection. After CU3 I tried to do the same process with Office 2013 updates and it just seems to sit there with the enforcement state showing unknown in the report.
Also I checked the version of client on the machines and they have the CU3 version but when I run a report to show client versions it does not show these machines with the latest version but version for sp1. It's almost like my management point
is not working. (just guessing). I checked in the component status and everything is showing green. I tried a wbemtest on one of the clients in the collection for the targeted updates and that is coming back with acceptable results.
Not sure where to look next.
I am not real proficient in 2012 yet and still bumping my way along. Any help reviewing specific logs, etc. would be appreciated. I have been searching for a solotion for several days now.

Hi,
1.Please make sure the update deployment is show up on the Deployment tab(Assets and Compliance -> Overview -> Devices -> the specific client properties)
2.Check PolicyAgent.log on the client to see whether the specific client have received the deployment policy. If not, try to run the Actions about software updates on the Configuration Manager Properties from the client.
3.Examine UpdatesDeployment.log, UpdatesHandler.log. UpdatesStore.log on the client.
Best Regards,
Joyce Li
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 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

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

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via SCCM 2007 PACKAGE

I can migrate sccm clients from sccm 2007 to sccm 2012 using sccm 2007 package with sccm 2012 client?
Thanks!
Atenciosamente Julio Araujo

Thanks for help me Peter and Torsten but this documentation says:
"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."
I Need migrate clients from sccm 2007 to sccm 2012 r2 and
I thought ofcreate a package in sccm 2007 with a sccm 2012 client.
Atenciosamente Julio Araujo

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

Client Migration from SCCM 2007 to SCCM 2012 via GPO

what
installation properties i can use to migrate client from sccm 2007 to sccm 2012 via gpo?
Thanks!!
Atenciosamente Julio Araujo

It all depends on your needs, I suggest that you look at this first :
All properties can be set by using GPO, it's not different from push.
http://technet.microsoft.com/en-us/library/bb632469.aspx
http://technet.microsoft.com/en-us/library/bb633010.aspx
http://social.technet.microsoft.com/wiki/contents/articles/25118.deploying-sccm-2012-r2-clients-using-group-policy.aspx
Benoit Lecours | Blog: System Center Dudes

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via GPO

Hello.
I can do the migration of customers from SCCM 2007 to SCCM 2012 via GPO?
When I'm migrating customers from SCCM 2007 to SCCM 2012 I have to keep the boundaries of SCCM 2007 or just the SCCM 2012?
Atenciosamente Julio Araujo

For migrating the clients you can use any client deployment method that's available (see for planning your strategy: (http://technet.microsoft.com/en-us/library/gg712283.aspx).
During the client migration I would also start with migrating your boundaries. The most important thing is that you have no overlapping boundaries for site assignment when you are using auto assignment.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

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

After migration from sccm 2007, there are many systems with no client installed

Hi Everyone,
We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
There may be some stale systems in AD.
Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

You could also remove the objects without a client and adjust the settings in the
Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 and WSUS

I know this horse has been beat, and is probably just dust now but I am still having a problem. I am not sure what to do next. I see others have had this problem but their resolutions have not worked.
Site Config:
OS - Windows Server 2012 Datacenter
SQL - SQL Server 2012 Enterprise SP1
SCCM - SCCM 2012 SP1
WSUS : Database and WSUS Services
I have done the setup in the Server Manager window and can open the console. Below are the errors I am getting.
From SMS_WSUS_SYNC_MANAGER
WSUS Synchronization failed.
Message: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details..
From SMS_WSUS_CONFIGURATION_MANAGER
WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "SERVER".
Error in WCM.log
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Error in wsyncmgr.log
Sync failed: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=CM1 PID=1548 TID=1740 GMTDATE=Fri Sep 13 19:08:50.063 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on
site CM1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minutes

Re-set the WSUS and SUP roles according to your doco, which is nice by the way, but I am still getting errors in WCM.
Assembly WSUSMSP loaded in .NET runtime v4.0.30319.17929 SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Set DBServerName property in SCF to 'VRC1SCCMPRIP01' on this site for <SERVER.DOMAIN>. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (<SERVER.DOMAIN>) is submitting SDK changes from site(CM1) SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93 (Windows 8.1 Dynamic Update) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:3e5cc385-f312-4fff-bd5e-b88dcf29b476 (Windows 8 Language Interface Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6407468e-edc7-4ecd-8c32-521f64cee65e (Windows 8.1) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:97c4cee8-b2ae-4c43-a5ee-08367dab8796 (Windows 8 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:f4b9c883-f4db-4fb5-b204-3343c11fa021 (Windows Embedded Standard 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:37:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:38:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:39:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:22 PM 5108 (0x13F4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
From SUPSetup.log
<09/17/13 13:36:13> ====================================================================
<09/17/13 13:36:13> SMSWSUS Setup Started....
<09/17/13 13:36:13> Parameters: I:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:<SERVER.DOMAIN> SMSWSUS 0
<09/17/13 13:36:13> Installing Pre Reqs for SMSWSUS
<09/17/13 13:36:13> ======== Installing Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Found 1 Pre Reqs for Role SMSWSUS
<09/17/13 13:36:13> Pre Req SqlNativeClient found.
<09/17/13 13:36:13> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<09/17/13 13:36:13> Pre Req SqlNativeClient is already installed. Skipping it.
<09/17/13 13:36:13> ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Installing the SMSWSUS
<09/17/13 13:36:13> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
<09/17/13 13:36:13> Checking runtime v2.0.50727...
<09/17/13 13:36:13> Did not find supported version of assembly Microsoft.UpdateServices.Administration.
<09/17/13 13:36:13> Checking runtime v4.0.30319...
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Supported WSUS version found
<09/17/13 13:36:13> Supported WSUS Server version (6.2.9200.16384) is installed.
<09/17/13 13:36:13> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
<09/17/13 13:36:13> CTool::RegisterManagedBinary: Registered I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
<09/17/13 13:36:13> Registered DLL I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
<09/17/13 13:36:13> Installation was successful.
<09/17/13 13:36:13> ~RoleSetup().
Second to last line shows completion.

SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256. We have set this up as the software update point.
For the purposes of this discussion, these are the server names (obviously obfuscated):
Primary site server: sccm.domain.local
Database server: sccmdb.domain.local
WSUS server: wsus.domain.local
On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
Log Name:      Application
Source:        SMS Server
Date:          8/6/2013 11:03:11 AM
Event ID:      6613
Task Category: SMS_WSUS_CONFIGURATION_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sccm.domain.local
Description:
On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported: WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
to the Software Updates Point.
As well as this in the WMC.log:
PublishApplication(9D5353E5-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013
11:03:11.787+240><thread=3704 (0xE78)>
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
Is there a way around this, without having to upgrade the WSUS server to Server 2012?
Thanks for any thoughts you may have!

Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
No management is ever done in WSUS.
So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
essentially be automatic (from a client functionality perspective).
Jason | http://blog.configmgrftw.com

Roadmap Migration from SCCM 2007 to SCCM 2012

Hi Experts,
Can anyone please indicate high-level and detailed steps to migrate our SCCM 2007 infrastructure to SCCM 2012?
From your experience, what best practices should I follow?
Any links, docs, thoughts would be really appreciated
System Requirements for SCCM 2012?
Franki

Hi,
The documentation for SCCM 2012 is up on Technet
http://technet.microsoft.com/en-us/library/gg682006.aspx
Questions related to SCCM 2012 should be placed at
http://connect.microsoft.com join the configuration Manager open beta and you can see all asked question and ask your own.
regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
You could literally answer every single question about SCCM with this answer.. Most people come here having actually already looked at many available resources and we still have questions. All you did was waste time typing this. Not sure how this ended
up getting the blue check mark. OP must be generous.

Migate from Sccm 2007 to 2012 and WSUS functionality

Similar Messages

Maybe you are looking for