It would be nice to install the Applications assigned to device and to Primary user inside the Task-Sequence.
Criteria could be followed:
- Install Deployment (not available)
- not retired
- last Version / Revision of Application / DeploymentType

Maybe, some more criteria are possible or required :-)

Benefit:
If the Task-Sequence finished, Client is ready to use without waiting of install applications aso.

Integrate SCCM OSD task sequence domain-join process with CyberArk secure password management. The task to use the domain-join process does not have the capability of going to the CyberArk API and retrieving an encrypted password (dynamic) during each OSD deployment.

Due to us upgrading Office and Windows 10 versions we have noticed that a number of users are logging in and breaking the Office upgrades it would be appreciated if SCCM had an option to not allow the user the ability to sign back into the device until the task sequence has finished running.

An example of this is when the task sequence runs in WINPE mode.

Until 20H1 this was able to be done by setting the CsEnabled registry key to 0 during the build, this key is no longer present in windows. We need a way to prevent devices with Modern Standby from going to sleep during the build.

This was reported in UV https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8422794-osd-deploy-ts-to-user-groups?tracking_code=ac5f2659e8181c3495b2ad929ac07082 and was marked completed, except that it only supported non-OSD task sequences.

Can we have a where used tab in Operating System images and upgrades?

Hi

Please could you add the package reference in the "Run Powershell Script" Step in Task sequence. The option to select a packaged Script is possible, but when running an "entered" script and referencing a package is not there. This is possible in the "run Command line" entry.

Regards Adriaan

With the ability to add powershell to your boot wim (adds 100mb), + drivers for your machines and a couple of tools the 512MB is not sufficient especially if say you want to update the bios as part of a bare metal build. I.e. Dell tool + bios update program + bios file - you cannot reboot the machine back to the wim because there is not enough RamDisk space to hold it all. 512MB is tiny in todays terms, please can we have a much larger upper limit.

To improve download content experience for computers with very low network bandwith. It's only managed with standalone media.

It would've been nice to have the ability to resize the new "Enter a PowerShell script" window to chech that everything looks good. The default windows is quite narrow. Maybe add som nice colour formatting to get a better overview.

Hi,

Allow to resume a download package step.

When a user run a TS with a "Download Package Step" downloading a 20Gb .wim file ; when this user restart his computer ; Download Package Step is restarting from 0

During OSD, specifically the Setup Windows & Configuration Manager Step, the step creates the file DisableCMDRequest.TAG right before rebooting from WinPE into the Full OS

This disables the F10 prompt during the Windows Setup.

Could you allow us to change this behavior via TS variable?
Example: SMTSTDisableCMDRequest = False

[Bonus] Then also automatically set the it to false if TSDebugMode = True

This would be helpful for troubleshooting Windows Errors during Setup before the TS kicks back in after setup. (SetupComplete.cmd runs)

Often times, when WinPE boots and there is an error before OSD completely loads, WinPE simply reboots without showing any errors and does not give you the opportunity to gather log files via console. While this issue is typically a driver or time issue, it's impossible to know for sure without looking at the logs. This forces the techs to submit tickets and for the SysAdmins to guess as to the cause of the issue.

We need a builtin task sequence variable indicating computer is virtual or not (like TS builtin variable _SMSTSBootUEFI)

The current ISO for Windows 10 2016 LTSB (build 14393.0) does not identify any OS upgrades from SCCM. An investigation determined that the windows upgrade engine was "too old" to talk to current SCCM infrastructure and you have to manually upgrade the newly deployed operating system so that it can be patched. We don't see that as MS supporting the operating system.

A Task sequence >>Run PowerShell Script<< step is executed as a >>-Command<< Apparently this leads to reduced functionality, events registered with (Register-ObjectEvent) does not fire. Suggest possibility to choose Run as file, using the PS -File switch + argument.