This will help you identify most mixed collections.
select
fcm.CollectionID 'Collection ID',
coll.Name
from v_FullCollectionMembership fcm
left join v_Collection coll on coll.CollectionID=fcm.CollectionID
group by
fcm.CollectionID, coll.Name
having
count(distinct fcm.ResourceType) > 1
Ted Koopman
From: [email protected] [mailto:[email protected]] On
Behalf Of Daniel Ratliff
Sent: Tuesday, June 04, 2013 6: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.
