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]] 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.
