Hi guys. my scenario is as the following:

I have SCCM 2012 R2 SP1 CU1 with ADK 10

I have 2 task sequence deployments on my All Systems collection:

1. Win7 32bit with WinPE 10 x86 boot image
2. Win7 64bit with WinPE 10 x64 boot image

PXE is set with DHCP with option 67 set on SMSBoot\x64\wdsnbp.com

doesn't matter from what device I boot - I look at the SMSPXE.log on my DP and see that the first advertisement chosen is the Win7 32bit with the WinPE 10 x86.

the most common deployment in our environment is the x64. so I always need to choose the deployment, wait for the right PE to be provisioned , press enter, restart and only then start the deployment...

I want the 64bit deployment to be in a higher priority. how can I do it?

I know I can change both of the task sequences to work with WinPE 10 x86 but keep in mind I want to have the ability to allow deployments on UEFI computers that as far as I know - require x64 boot images.

I also know it doesn't work the other way around and I cannot change both of them to work with the WinPE x64 as the 32bit deployment fails with a known error of wrong PE Platform.

any suggestions? 

Having required OS deployments to 'All Systems' is not really a good idea. You will end-up imaging even your SCCM servers.

I suggest that you create two collections - one for your 32-bit target OS and another for your 64-bit target OS.

guys, relax. who said something about "Required" deployments?!

I know how to manage my environment, the "All Systems" decision only make sense for our organization and I have enough protections on top of it so my organization won't be all wiped by SCCM.
we're not talking about how to manage risk assessments, but to help with a solution for an important issue.

so lets assume we're not talking about "All Systems".
My question is on how to prioritize 2 TS deployments on the same collection?
I'll see if I understood what Jason posted.

if you have any other ideas - I'd be glad to hear about them

If they deployments are not required, then there is no need for prioritization. All the optional deployments will show up in one list and it is up to the user to pick which one should run.

How about:

1. de-select the "Deploy this boot image from the PXE-enabled distribution point" for the WinPE 10 x86 boot image. 2. Open the defaul "Boot image (x86)", choose "Deploy this boot image from the PXE-enabled distribution point", and distritute "Boot image (x86)" to your DPs.

3. Open "WinPE 10 x64 boot image", choose "Deploy this boot image from the PXE-enabled distribution point".

Hi Sandy

Well... what you say makes kinda sense,

as I said, 90% of the times I wanna deploy the x64 deployment so I don't mind for the other 10% to load the x64 boot image, choose the x86 deployment, wait for the x86 boot image to be provisioned and then restart.

so... my better idea is to just remove the x86 boot image from PXE for good.

that way, the x64 boot image will be always boot from PXE and both of the deployments will be available.

I'll try it out on Tuesday just to make sure it works. if so, simpler than I thought :P

Hi Sandy

Well... what you say makes kinda sense,

as I said, 90% of the times I wanna deploy the x64 deployment so I don't mind for the other 10% to load the x64 boot image, choose the x86 deployment, wait for the x86 boot image to be provisioned and then restart.

so... my better idea is to just remove the x86 boot image from PXE for good.

that way, the x64 boot image will be always boot from PXE and both of the deployments will be available.

I'll try it out on Tuesday just to make sure it works. if so, simpler than I thou

no problem, so I'll put some dummy x86 boot image without any related deployments attached to it just for the file creation under the remoteinstall dir.

we'll know if it's working tomorrow

Well guys, bad news :/

unfortunately it didn't help

I added another x86 boot image which helped to not break the PXE service

but on the SMSPXE.log of the DP I still see it searches for the boot image of the x86 deployment :/

and for unknown reason, It always prefers the x86 deployment first