cstark

Hello fellow school master of tech... I got nothing. IMO, SCCM has gotten to the point that it's easier to just backup and rebuild than it is to worry about some "P2V" converter screwing something up, at least for smaller setups like the one I maintain. But then again, if you have the capability of converting to a test machine, checking with the SCCM Toolkit to verify everything was transferred correctly, it's worth a shot. Please note, what follows is what worked for me, not necessarily best practice or recommended, but this worked for the most part so I'm sticking with it. If you do decide to do the backup and nuke, what I did recently was go through the Assets & Compliance and Software Library workspaces and exported anything that I valued (collections, Compliance Settings, Applications, Packages, Driver Packages, Task Sequences). SCCM will export anything it needs for them to the location you specified, you can skip exporting the content assuming you will rebuild the server with the same shares. Once everything is exported, build the new SCCM server w/ any required fixings. Once the new SCCM server is up and running, migrate the files from the old server to the new and setup the necessary shares. Go through the workspaces and import the exported items. When it comes to the Collections, SCCM tends to derp and has no error checking on if it is using a user collection in a device collection and will cause a bad day, if you run into this, check what I did to fix it https://www.windows-noob.com/forums/topic/14002-imported-device-collection-using-user-collection-as-limit/#entry53677. This is in no way a bullet proof method, there are some things that I am still cleaning up like some imported packages are not being distributed correctly, but re-making the packages manually fixes that. Hope this helps, if you need more help, let me know, us school admins need to stick together!

OK, so I think I dodged a bullet at this point and it appears I got it working again. In case if anybody has this issue or if I don't learn my lesson and I derp this up again, this is what I did to fix it: 1. Open SQL Server Management Studio 2. Find the dbo.Collections_G table and Edit Top 200 Rows (I don't have 200 collections, so I can get away with this, YMMV) 3. In the LimitToCollectionID Column, edit the trouble entries to be the correct ID. 4. Refresh SCCM (click a different workspace or something to cause it to requery) 5. Note the limiting collection is now a new collection There was some more finagling I had to do, but in the end, I am now able to properly manage the collections from within SCCM again.

Our previous SCCM instance decided that nothing can remain on the primary DP, so since it was still in it's infancy, I exported anything that I could (applications, TS, collections...) and started the migration process. I now started the import process and apparently the exported collections reference other collection by ID and apparently the imported collections did not get the same ID, so now, I have device collections that are using user collections as the limiting collection (slight flaw in the logic if you ask me). Now, when I try to change the limiting collection, no mater what device collection I choose, it's apparently a circular reference, when I try to delete the collections in question, I get an error of "Mismatched Collection Type: {DeviceCollectionID} -> {UserCollectionID}". I'm officially stuck. Currently, we are at the 1511 release, the 1602 release is being installed as I type this, so once that is done, maybe they already have a fix for this in there, so I'll give it a shot once the upgrade is complete. Is there a magical command I can run to just tell SCCM to nuke all my imported collections so I can re-create them manually to get rid of this? We are still only rocking the trial of SCCM as we started using SCCM after we renewed our MS licensing, so if anybody knows of a way that I can contact MS to get support even with a trial license, I would be greatly appreciative. Edit: 1602 completed install, to no surprise, tried to delete a device collection, got the mismatch collection error. Tried to change limiting collection, got circular reference. Didn't think 1602 would fix this.