CamRodMC

Hi. Well it wasn't all on your end, but the Google authenticator requirement kind of threw me off. I didn't have the app and had to install it in order to post. There were issues with getting the app installed... just seemed like overkill as I have no sensitive data on this site. I kind of inherited this task sequence and process so I'll try to explain to the best of my ability. First let me describe what we are using these computers for, maybe you or someone else has a better suggestion of what to do, even if it is a completely different process. Basically we have these computers setup for end users to access the internet during their breaks or off time. They only need to access the internet and print. The task sequence we have in a co-managed environment is for Autopilot so at the end of the task sequence we run these two steps to sysprep/set the PC in OOBE mode. "Prepare Configuration Manager Client" and "Prepare Windows for Capture" are the last two steps. The in house documentation we have states that when the task sequence is finished, we should end up at the OOBE screen, but instead of selecting a country and clicking next, the documentation states to use the Shift + F10 key to open CMD. From CMD we are supposed to type explorer and hit enter which will open Windows Explorer, from which we can right click on This PC, go to properties and change the computer name, then reboot and login. The reason for this step is we have a policy deployed to a group in Intune (Endpoint). The group is based off of computer name, so if we don't rename the computer at this point and just login, it will not get the policy from Intune (Endpoint) due to the computer name being generic, something like DESKTOP-MININT. I've tested with W10 20H2, W10 1909, W11 21H2 and also W10 1607 (I tried 1607 since that is the last version of Windows 10 that Shift + F10 should work according to my searches). I'm not able to Shift + F10 on any of these versions. I tried your fix from this thread, using the task sequence variable OSDSetupAdditionalUpgradeOptions. I put this step after "Apply Network Settings" and "Setup Windows and Configuration Manager". It did not work. I also tried putting this PowerShell script at the end of the task sequence to prompt for a computer name change but this did not work either. $Input = Read-Host “Type the computer name for this computer.” Rename-Computer -NewName $Input -PassThru -Force Also, to answer your question, these are not existing devices on our domain or tenant. It is a brand new computer with a new image from this task sequence. Hopefully that all makes sense. Thank you for your time.

Hi Anyweb. First of all, thanks for all your guides and help. You've gotten me out of many issues. Second, signing up to post on this site was quite a pain. I've logged into bank accounts easier than this. Back to the topic at hand. Do you know if there is some sort of fix like this for a brand new image, not an OS upgrade? We have an autopilot task sequence that for part of our process, we would use Shift F10 after the image has completed and is at the OOBE screen in order to change the computer name before initial login. If we login before we change the computer name, it will never get the proper policy from Endpoint (InTune). Now that we can no longer use Shift F10, the computer never gets the proper policy and we are stuck. I looked to see if I could find any other Task Sequence variables such as OSDSetupAdditionalOptions and I also tested with OSDSetupAdditionalUpgradeOptions but it does not work. I'm currently testing a PowerShell script towards the end of the task sequence to change the name but if you have any suggestions or methods to enable Shift F10 or cmd prompt at OOBE screen, please let me know.