Thursday, February 21, 2013 4:22 PM
Since I had lots of trouble upgrading our current MDT 2010 to 2012 Update 1, probably due to alot of junk in the old deployment shares, I have setup a completely new server with MDT 2012 Update 1 and created a new deployment share.
I've exported the Applications to a tab delimited list but find no straightforward way of importing them into MDT 2012 Update 1.
Is it possible to migrate only the Applications from MDT 2010 to 2012 Update 1?
Thursday, February 21, 2013 4:36 PM
I haven't tried this, but it may work. Backup first! : )
If you've added no applications yet to your new MDT 2012 U1 Deployment Share, I'd try it this way:
- Make sure all 2012 U1 console pointing to the new share are closed.
- Copy \\oldshare\Applications folder to \\newshare\Applications folder [this gives you all the actual content and scripts]
- Copy from \\oldshare\Control\ the ApplicationGroups.xml and Applications.xml files (also PackageGroups.xml and Packages.xml if you use those) to \\newshare\Control overwriting the current files.
- Open 2012 U1 Console and see if you have your apps!
MDT data is pretty much all based in the XML files. I don't know if the format of these specific files changed between 2010 and 2012U1, but there's only one way to find out! : )
David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek
- Marked As Answer by korpx Tuesday, February 26, 2013 1:39 PM
Thursday, February 21, 2013 4:53 PM
There's some old post tools for this:
Post back and let us know how you get on, please.
Thursday, February 21, 2013 6:02 PMAdditionally, if the old deployment share is still available, couldn't you make an "Applications" selection profile, link the shares, and replicate content?
Tuesday, February 26, 2013 1:53 PM
DCtheGeek, I went with your suggestion since that felt like the quickest route to fix the problem at hand and I can't see any negative effects so far :)
Thanks alot for the suggestions guys! Most or all of the other alternatives probably work too but since time is short I'll leave it at this.
Another option to consider if this would be a frequently occuring thing is to export the list of applications to a csv on the old MDT server, copy the Application-folder to the new server, and then use PowerShell to import the csv using import-MDTApplication from the Microsoft.BDD.PSSnapIn
(see http://blogs.technet.com/b/heyscriptingguy/archive/2011/12/28/use-powershell-to-organize-mdt-application-and-driver-folders.aspx for hints of usage)
Edit: On closer inspection that's pretty much exactly what your links are about Andrew Barnes. Thanks!
- Edited by korpx Tuesday, February 26, 2013 1:54 PM