Comments on: How to Move Collections in ConfigMgr

By: Richard

Richard — Thu, 27 Oct 2011 06:55:26 +0000

Hey, If you want to automate this, you can find a script for it here:
http://www.filemilk.se

Ping back :-D

By: Jarvis

Jarvis — Thu, 19 Aug 2010 02:46:09 +0000

I haven’t dealt with that exact situation before, but my guess would be to simply delete the link that you don’t want.

By: Steven Zhang

Steven Zhang — Wed, 18 Aug 2010 22:29:45 +0000

We has a Center Site server and a child primary site server. I create a collection on the Child site and then create sub-collection by link to the collection on the center site. Now I want remove this linked collection on the child site server. How to do it without delete the original collection on the Center site?

By: Jarvis

Jarvis — Fri, 09 Jul 2010 17:44:15 +0000

Glad it helped. cleaning up the collection clutter makes it so much easier to navigate! Sherry rocks. I haven’t been able to talk with her since MMS, but she is always a fount of good advice. the other guys at Wells Fargo (where she works) can’t say enough good things about her.

By: Bill Hobson

Bill Hobson — Fri, 09 Jul 2010 15:30:58 +0000

Jarvis – you rock! I really used this technique to full advantage. I have many specialized collections and Sherry Kissinger (an SCCM MVP) pointed me in your direction as a solution to my “collection clutter”.

By: Jarvis

Jarvis — Fri, 04 Jun 2010 04:31:17 +0000

Not as far as I know. The original IDs are maintained…so “All Systems” is still SMS00001. I seem to recall doing an upgrade (SP2 or R2) after moving the collections a long time back without incident. Your mileage may vary.

By: chelsea stevenson

chelsea stevenson — Thu, 03 Jun 2010 22:15:27 +0000

I am wondering if this has any negative effects when doing upgrades. Such as causing the upgrades to fail or causing sccm to recreate the default collections.

By: Karl

Karl — Thu, 24 Dec 2009 13:19:15 +0000

I was looking for a solution like this. First I wanted to make a folder to put them all into but I saw it wasn’t possible untill I stumbled onto this post.

Thanks!

By: Mike

Mike — Wed, 30 Sep 2009 13:31:37 +0000

I think I figured it out. I looked again at the original collection I intended to move and clicked the “+” mark next to it. Under that I found the new parent and sub-collections that I was trying to move it to. Since it was a duplicate, I simply deleted the parent and the wizard (pictured above) informed me that it was indeed a dup. It’s good-to-go.

By: Mike

Mike — Wed, 30 Sep 2009 13:04:39 +0000

This is a very useful change that I implimented several months ago. But today I wanted to move a collection from one parent collection to another and have a bit of a problem.

I was going from memory and mixed up the method above, so I clicked on the collection I wanted to move, chose New Link to Collection, and then pointed it to the new parent collection I wanted to move it into (which is also parent of many other sub-collections.) Instead of creating a new link inside that new parent, it created a link from my original collection to the new parent, and subsequently to all sub-collections.

Now an advertisement intended for only the first collection is applying to all the sub-collections in the new parent. However, when I look under advertisements the advertisement still only applies to the original small collection. Does anyone know where links reside so I can remove it or back out of this somehow?