I've been tasked with seeing if it is possible to script the creation of Migration Jobs to migrate objects from SCCM 2007 to 2012 R2.
I've been wrestling with the New-CMMigrationJob command but I'm struggling. I'm given a list of package IDs of packages in SCCM 2007 that need to be migrated. If a package is not on this list then it should not be migrated. >From the description of the command, I'm hoping that I can (somehow) feed it >an array of the packageIDs. But I'm not having any luck with the >-MigrationObject parameter. I'm getting nowhere and decided it's best to ask >for help. Has anyone been using this command or have scripted creating migration jobs? Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA, MS [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
