I am getting ready to deploy Win10Ent within our organization. I do not want to import installs (Managed & Scripted) from K1000 to the K2000, here is my approach I will be taking. 1. I will deploy the Win10 scripted install from the K2000 and USMT's and then add those newly imaged PC's to patch labels and application Labels based on department so that each newly imaged PC get all patches and department dependent applications from the K1000. I did something similar with SCCM 2012 in which I added new devices to multiple collections for patching and application distribution. Any thoughts on this process or maybe a better approach?

Having to create and edit a single package or script to run on either the K1 or K2 would be amazing.

Whats the latest on this @Bob?

Will this mean we can share installs back and forth between the K2 and K1?

That feature would be great.

I second the comment below, to make it a two-way process. That would be most useful.

will this also be available from k2000 to k1000?

thanks!

Seems odd that I need to reupload some of my K1000 distribution for post installation tasks in the K2000.

An alternative solution would be to add the ability to add k1000 labels to a machine as a post-install task. That way an MI can be deployed to a label that can be added by the install script.

One can already import scripts from the K1 to the K2, just not Managed Installs.