MagnumVP Posted October 10, 2019 Report post Posted October 10, 2019 I have inherited a system where there are 50+ workstations that are running Windows 7 Ultimate OEM 32Bit. I want to push out a Task Sequence that performs the following; Captures the PC Name Reboots the PC Goes into WinPE Installs Windows 10 Enterprise Joins the domain All user docs are redirected to the servers so I do not need to save the users settings I have tried to create numerous tasks sequences but always running into can't upgrade 32-64 bit, OEM license won't allow you to run an upgrade.... I just want to Wipe and Replace but don't want to walk to each workstations. Can someone please assist in pointing me in the correct direction of a guide, Step-By-Step (which this site is great for) or some guidance? Thank You Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 11, 2019 Report post Posted October 11, 2019 I haven't tested that exact scenario so can't guarantee this will work but you could try this approach and see what happens https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/ Quote Share this post Link to post Share on other sites More sharing options...
Config Mangler Posted October 11, 2019 Report post Posted October 11, 2019 The "Install an existing image package" task sequence option pretty much does that in that order. I would manage the subnets with SCCM then push the SCCM client to the W7 machines. Once they have inventoried the computer name will be in SCCM then you can deploy the task sequence to them. Obviously import the drivers for the hardware and test first! Don't see why you would get upgrade licence problems on a wipe n load. Quote Share this post Link to post Share on other sites More sharing options...
MagnumVP Posted October 11, 2019 Report post Posted October 11, 2019 I'm sure it matters, but I'm running SCCM 2012 R2 SP1 with the latest ADK for 1903. @anyweb is the exact scenario different than normal? What's weird that is different from your "exact scenario" . Is it the "Capture Name" I'm kind of surprised that a wipe and reload is out of the ordinary for a SCCM OS push install. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 15, 2019 Report post Posted October 15, 2019 @MagnumVP what's weird is the upgrade scenario, i have not tested migrating anything from 32 bit to 64bit Quote Share this post Link to post Share on other sites More sharing options...
