SMoRZ3

You still need the unattend.xml to tell the OS what settings to use. So no matter how you get the settings into the unattend.xml (static or declaring a variable) its still required. As long as the variables are declared before the "Setup Windows and ConfigMgr" step it should work out. Technically the "Apply Operating System Image" and other pre-OS steps are creating/modifying an unattend.xml file for you.

If you don't need flexibility with your unattend.xml file (for changing out different language and regional settings) you can just add the code to it. For example Inputlocale is for keyboard layout. I happen to leave the variable, and in my task sequence set it to "en-us;cs-cz" to set it to US layout as default but with the option to switch to the Czech keyboard layout. So you can just replace your "%OSDInputLocale%" with "pl-PL" or "pl-PL;en-us" or something like that.

You can either define the variable using the Create TS Variable step, or you can modify the unattened.xml and hardcode the language value instead of using a variable.

https://docs.microsoft.com/en-us/sccm/core/servers/manage/checklist-for-installing-update-1710#post-update-checklist Did you verify the 1710 upgrade went through all the way? I would verify everything is at 1710 otherwise you might not qualify for the other updates as far as SCCM is concerned.

Some other locations you can check are... C:\ProgramData\Microsoft\Microsoft Security Client\Support C:\ProgramData\Microsoft\Microsoft Forefront Endpoint Protection 2010 Server Management\Support C:\ProgramData\Microsoft\Windows Defender\Support C:\Windows\WindowsUpdate.log* (Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.) Usually I find that the client health is bad when they have issues like this and if you sort those out, SCEP will work like intended.

Ahh ok. That makes sense. I'm using a "borrowed" export so it could be that its not the same Win 10 version I'm currently using. Or in general I've never re-created it after upgrading to the newer Win 10 version. I'll have to see if that solves my particular issue. Thanks.

I've noticed mine is set to Adobe Reader, but eventually "Windows" decides its not working right and sets the default back to Edge. The below link may help. Hack Adobe Reader to be Default

The very bottom of the post has a "downloads" section with a link to a zip file with the scripts. How can I install System Center Configuration Manager version 1702 (Current Branch) on Windows Server 2016 with SQL 2016 --> Scripts.zip How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 - Part 1 --> scripts.zip

Have your application install for the system, but deploy the app to the users. This way it installs in the system context, but your users are still the 'target' of the deployment.

Requires you to have Active Directory User Discovery running.

dism.exe /Quiet /Add-Package /Image:%OSDTargetSystemDrive%\ /PackagePath:. /LogPath:%_SMSTSLogPath%\dism-lang.log The above is the command I use to inject the driver package. That is a "Run Command Line" TS Step, using a package with the specific language pack I want injected into the OS. I have both the language pack and also the language features in the package so I can use speech to text and other features. I use a TS Var to determine which ones get installed/injected. This is placed right after Apply Operating System, but before Drivers and Setup Windows and Configuration Manager steps. This works using ADK 1803, SCCM 1802 + HF1, deploying Win 10 1703. Thanks,

I too second adding that line to your unattend.xml to get rid of it. I had the same issue until that was added.

Gary uses this to pause a TS. https://garytown.com/task-sequence-message-pause-with-no-package You can also import some of his other examples from here. https://garytown.com/configmgr-task-sequence-collection

I made a application I use during TS to install it. Command I use is ""%SystemRoot%\System32\Dism.exe" /Online /LogLevel:4 /Add-Package /PackagePath:"microsoft-windows-netfx3-ondemand-package.cab" /NoRestart /Quiet" for Win10 1703. Make sure the source of the CAB file matches the OS you're deploying. Hope this helps.

I would be careful using the GPOs for site assignment. I only say that because its something outside of SCCM that is forcing a SCCM type settinging which might not be too obvious in the future. When i migrated from my old SCCM instance to a new one, it was those GPOs that caused a lot of my clients to not migrate. And then I had to delete those reg-keys with a different GPO to get them migrated. It was a mess but eventually it got sorted out. You gotta do what you gotta do but as a new admin taking over the SCCM it cause me a lot of confusion as to why my clients kept reverting back to the old site code.

Check the registry at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client" and see if there are any registry keys starting with "GPO". If there are that means you have GPO settings defining your old site code which will prevent your clients from connecting properly to the new SCCM site. If you find GPO settings defining your site, disabling the GPO will only prevent the registry keys from being made, it wont remove them. You will need to remove the keys manually or create a new GPO to delete the registry keys the other GPO was creating. I would also recommend installing the client using the command prompt and switches to at least define the management point Example: "ccmsetup.exe /mp:sccmsiteserver.domain.com" otherwise it will try and find a site which your environment might still have pointers to the old. Also, when installing the client, it will only install the minimum until it connects to the site server, gets its policy, and installs any other features it may need based on the policies. Its not too strange to only have a few actions when its first installed. Also check ADSI for your old site code. Under CN = System, CN = System Management. If its listed there that might be why clients are trying to use the old site still. As always, have back ups and use caution when editing the registry or making system wide changes with AD / GPO etc.

I have a similar issue I'm still trying to resolve. I think it has to do with it trying to add the PC to a different OU than where it currently is. Join domain doesn't move or delete the current AD object, I think it just makes another instance of it which is causing the same issue in SCCM for me. That is my thought anyways, I haven't really dug into the issue far enough to prove that theory out yet.

What was the fix for future reference?

Have you right clicked your task sequence, gone to properties, advanced tab, and then made sure the new boot image is selected?

Ive had issues with SCCM using older revisions of stuff. To work around this and get my newer changes quicker / and reliably I have started copying a task sequence, making changes, and then deploying that one. Then when I deploy it I get only that version of the TS. So I have a lot of "%OS VERSION% - %TODAYS DATE% - %VERSION%" Example "Win 10 ENT 1703 x64 - 9-27-17 - V1" test TS when I'm perfecting my TS for production.... Try copying your TS and seeing if the boot error goes away....

Have you tried recreating your boot media? Anytime you mess with your boot images its usually a good idea to re-create your media.

Run as 32 needs to be selected to get around a failed to extract error during OSD.

Take a look at these, these might not be exactly what you need, but might get you closer.... https://gallery.technet.microsoft.com/Set-of-Operational-SCCM-19fa8178