ConfiMgr 2012 R2 > ConfigMgr CB Package Migration drops Windows 10 (64bit) Requirement Setting

[surfincow]

Hello,

 

Just happened to notice that on all my 2012R2 packages, the "Requirements" tab on the Program seems to have not migrated the "All Windows 10 (64-bit)" setting. (I guess I can't say all but I'm through the 1st 10 packages and none of them have this checked as is on the source package.

 

 

 

Anyone else notice this or is this a known bug?

[surfincow]

OK so made it through all the packages (65) and none of them retained this previous setting.

[GarthMJ]

Post a screenshots of CM12 where Win10 x64 is selected. If you can reproduce the issue then I would contact MS support they will work on getting a fix/solution created.

[surfincow]

Hello,

 

I was able to duplicate it twice. Imaged attached.

 

So looks like a bug? Whats the easiest way to report? Same method as opening a support case?

[GarthMJ]

Yes the easiest way to report it is to open a support case. Remember that since it is a bug, it will not cost you anything. However if it as a miss configuration then it will.. Don't let the support guys tell you it is fixed with a PowerShell script to turn on all the Windows 10 option in CMCB. Tell them "Thank you but this is still a bug and therefore the case needs to be treat as such."

 

BTW, I will give the Product team a head up about this.

[GarthMJ]

I have confirmed that it is a bug and will get fixed in an up-coming release.

[surfincow]

Yep, got the confirmation from Microsoft as well. This affects not only packages, but also Task Sequences.

 

No fix as of yet so hopefully will be in the next update/version for Configmgr.

[surfincow]

Also will mention that I noticed none of our Windows 10 packages appear to be running even though they are deployed. Further checking revealed a large majority of the packages were set to disabled rather than enabled.

 

I'm unable to duplicate the issue so not sure if its a bug or just something odd on our end. MS was unable to duplicate the issue as well but said there were a lot of bugs in regards to migration in the current version which will hopefully be fixed in the next CU.

 

Just a heads up in case anyone ran into something similar.