The biggest cause that I’ve run across for collections that will not migrate is multiple limiting collections. This query will show you all of the collections that have limiting collections. You don’t have to worry about the ones that only have 1, so they are at the bottom of the list. You can tweak as your query writing skills allow to fine tune it
SELECT COL.Name, COUNT(CRQ.LimitToCollectionID) as 'Limiting Collections' FROM v_Collection COL JOIN v_CollectionRuleQuery CRQ on CRQ.COllectionID = COL.CollectionID WHERE CRQ.LimitToCollectionID != ' ' GROUP BY COL.Name ORDER BY COUNT(CRQ.LimitToCollectionID) DESC Hope this gets you started - BH From: [email protected] [mailto:[email protected]] On Behalf Of Bradnan, Jerry Sent: Wednesday, June 05, 2013 8:03 AM To: [email protected] Subject: RE: [mssms] SCCM 2012 Collection Migration I see. My goal is to develop a list for planning purposes, so the collections that need to be addressed can be looked at prior to migration. Thanks, Jerry From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, June 04, 2013 5:32 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM 2012 Collection Migration There wont be any reports that tell you what ‘wont migrate’, you just to do the migration and the migration report tells you. I was referring to running the migration, then using the built in reports to get data on the reports that didn’t migrate. From what we saw, the only collections that didnt migrate were collections that had both users and computers. Everything else came over just fine! Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bradnan, Jerry Sent: Tuesday, June 04, 2013 3:57 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM 2012 Collection Migration Interesting; I do not see any reports that return information on collections that cannot migrate (I assume your referring to the SCCM 2012 reports). I have also been looking the tables and views in the both the 2007 and 2012 BDs, but cannot seem to find the information I need to determine what collections cannot migrate based on the 2012 limitation/rules. Jerry From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Daniel Ratliff Sent: Tuesday, June 04, 2013 9:21 AM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] SCCM 2012 Collection Migration PowerShell or just the built in reports. How many collections you need to see might determine which solution you want to use. You could also query the db itself. All three are fairly easy to do. -----Original Message----- From: Bradnan, Jerry [[email protected]<mailto:[email protected]>] Sent: Tuesday, June 04, 2013 08:51 AM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM 2012 Collection Migration Has anyone found a way to export, or report on the collections that cannot be migrated in a SCCM 2007 to SCCM 2012 migration? I realize that when creating a migration job, there is the option to look at the list, but it would be nice to be able to generate a list of the collections that need to be addressed. Thanks, Jerry The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
