gatorcb Posted August 6, 2013 Report post Posted August 6, 2013 I'm in the process of running through scenarios of migrating cm2007 objects to 2012 in a lab. To make things a bit more tricky I'm trying to leave off the default scope (use another). I'm seeing some weird issues I’ve noticed that if the admin acct used to create the migration job doesn’t have the “default” scope it doesn’t run the job and it skips several of the wizard windows. For instance it won’t show the package screen. My end goal is to have a scope for the workstation side and one for the server side, but allow the workstation side folks to migrate everything. I have successfully split out the workstation/server collections and updates functions already. Workstation Admins won't have access to all systems, but rather a workstation systems (to be used for limiting) collection. Note full admins would have access to all scopes. At this it seems my only option is to allow the default scope for now and make sure all the migrated objects have the workstation scope ticked during the migration job. Anybody run across this or figured out a similar plan? Thanks Quote Share this post Link to post Share on other sites More sharing options...
