Windows 10: SCCM Windows 1809 feature upgrade Task Sequence with OEM keys

Hello,


in my company, we want to upgrade all laptops to Win 10 Pro 1809, primarily from Win 10 Pro 1607, 1703 and 1709). All out devices are using OEM keys.

Is this possible and legal to do?

I have found information that I cannot upgrade from Win 7 to Win 10 or from other editions to Pro. I am not clear though on a simply feature upgrade. Assuming this is OK but want to avoid any issues.


Hopefully, someone can clarify, thanks in advance.

:)

 

Execute a command from SCCM Task sequence step "Run a Command line"

Hi,

Thanks for your suggestion.

That will work indeed, however I need to run it from the SCCM Task Sequence's Run Command Line Step and I am not able to figure out how to do that.

Can we change line while executing command from SCCM Task Sequence's Run Command Line Step?

Regards

 

Unable to import task sequence for x64 to in-place upgrade to Windows 10 by task sequence.

Original Title: Windows 10 In-Place Upgrade

I am trying Windows-10 In-Place upgrade by downloading the task sequence from the below Microsoft website and following the steps as mentioned in the site (Below is the link which I am referring to )

https://technet.microsoft.com/en-us...ws-10-with-system-center-configuraton-manager

I am able to successfully import the task sequence for Windowsx86, but when I am trying to import the same task sequence for x64, it's tries replace the exiting package (TS)

• Is it possible to rename the package name in the script, if possible please let me know how to do this
• After the windows10 migration, administrator account is disabled and not able to login to the system. What would be the solution for this ?

 

SCCM 1606 and Failed Windows 10 1607 Upgrade

I created a SCCM task sequence using the 'Upgrade an operating system from an upgrade package' template and the task sequence works provided there is not an issue during the upgrade. If the upgrade fails Windows automatically reverts back to Windows 7. This
is great, but the task sequence never continues and the 'Rollback on Failure' group never executes.

I have post processing that needs to be executed after a rollback that installs applications which were uninstalled prior to the 'Upgrade Operating System' step being run.

I found after the rollback that the ccmexec service is disabled. Looking through the logs it is disabled by the 'Upgrade Operating System' step in the task sequence.

If I manually enable the ccmexec service and restart the machine, Software Center is empty. Forcing a Machine Policy Retrieval & Evaluation Cycle does not fix the problem. Reinstalling the client by running ccmsetup does not fix the problem. The only way
to get Software Center to show applications is to completely uninstall the SCCM client and then run ccmsetup again.

Any ideas on how to get the 'Rollback on Failure' group to execute?

Thanks,

Scott