Client logs for OSD are constantly purged and overwritten. This can make troubleshooting difficult in a standard environment. For example, logs are saved to X:\Windows\Temp during winPE phases. This file system is destroyed upon reboot. Even after the WinPE phases, log files (especially smsts.log) are constantly overwritten.
Please prevent logs from being lost or overwritten during OSD.7 votes
Sometimes when making changes to a task sequence, you may be manipulating steps that reference a package with a common name. You can view the TS Package Reference but it doesn't tell you exactly which step may reference that package.
If you could view the package ID referenced by a step, when viewing that step, this would solve the problem!7 votescompleted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating to completed, shipped with our 1702 release. More details here – https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1702
Thanks for the feedback – it’s a solid improvement to help folks find referenced content.
When looking at the driver files that are in a boot image, the only information available is the name of the driver. Many drivers have multiple versions but the same name. The only way to truly distinguish drivers with the same name is by the name of the inf file, which is not visible in the boot image drivers tab. This information can be found on the individual driver usage tab, but that requires selecting each driver individually and seeing if it's in the boot image. If there was a column in the boot image drivers page showing the name of the inf file, it would be very easy to identify which specific driver file it is.
When looking at the driver files that are in a boot image, the only information available is the name of the driver. Many drivers have multiple versions but the same name. The only way to truly distinguish drivers with the same name is by the name of the inf file, which is not visible in the boot image drivers tab. This information can be found on the individual driver usage tab, but that requires selecting each driver individually and seeing if it's in the boot image. If there was a column in the boot image drivers page showing the name…7 votescompleted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to complete – see https://blogs.technet.microsoft.com/enterprisemobility/2017/07/28/now-available-update-1706-for-system-center-configuration-manager/
Thanks for the feedback and suggestion
In SCCM 1702 only the middle text field of "user notification message text" will be taken!7 votescompleted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to completed.
The issue was there was another code path to the ‘old’ code which wasn’t addressed when the customization was added in 1702. This was corrected in our 1802 release
Marking this as Completed. The post was updated 3/2/2016 with Hotfix available – see https://support.microsoft.com/en-us/kb/3143760 for details on the fix.
Updated by bobmn for sangeev/OSD
with configmgr 1802 internet based clients need to download the complete ts content over the cloud dp. it would be great to only download needed content for the tasksequence6 votes
Thanks for all your feedback and suggestions. Updating status to completed – see https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each status.
This is the opt-in phase of our 1910 release (fast ring) and it is now live. Customers can opt-in and then download 1910 through their Admin Console now. In a couple weeks, we’ll open it up to everybody (slow ring), to enable downloading without the need to opt-in.
Download all content when needed by the task sequence is now supported for this scenario –
If you have a TS with an Install Software Update step, the TS can not be exported and imported. The Import Wizard fails with a null pointer exception. After removing the Install Software Update step, the TS can be exporteted and imported. The same happens with the Import-CMTaskSequence Commandlet. Please fix this error.6 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
this is fixed in 1606 RU1.
We have implemented Configuration Manager 2012 R2 SP1 CU1, We verified Management point affinity works however it doesn’t work for PXE and PXE point randomly selects any Management Point.
We have a lot of firewalls and several MPs.
I could see below mentioned article with a workaround for untrusted forest.
System Center 2012 Configuration Manager Client PXE boot may fail if the Management Point is in an untrusted forest
I could see similar not same feedback request
OSD should not connect to "Internet-only" Management Points
It will be good idea to have PXE affinity like Management Point affinity6 votes
Updating to completed as SCCM 1610 is now released – see https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1610 for more details
Thanks for all feedback
When I run DISM to add a language pack, I'm told that the recommended scratch space for WinPE is >1024MB. In ConfigMgr, I can only select up to 512MB for WinPE scratch space in my Boot Image. Could we add an option for 1024MB?6 votes
Closing for 1802 release. Thanks for confirming /ScratchDir vs. Scratch space
I consistently run into issues with TS's when making changes to them. Upon closing the TS or applying changes I will receive an error that says "There are too many steps in your TS...". But if I close the console and reopen it, I am able to make the exact changes and they will save fine. The problem usually happens towards the end of the day so I believe it is a memory leak of some kind. I started seeing the issue in 1610 and figured it would go away with new versions. Just updated to 1710 and the issue persists.
I consistently run into issues with TS's when making changes to them. Upon closing the TS or applying changes I will receive an error that says "There are too many steps in your TS...". But if I close the console and reopen it, I am able to make the exact changes and they will save fine. The problem usually happens towards the end of the day so I believe it is a memory leak of some kind. I started seeing the issue in 1610 and figured it would go away with new versions. Just updated to 1710 and the issue…5 votes
Add a column to the Operating System Images node for OS Build version. This is especially valuable with Windows 10 as you may have multiple images for different releases. Ideally this would be just like the Boot Images 'OS Version' node.5 votes
Updating status to completed – see https://blogs.technet.microsoft.com/enterprisemobility/2017/07/28/now-available-update-1706-for-system-center-configuration-manager/
Thanks for all the feedback
When you create an OSD Task Sequence and get to the section where you install applications it gets really tedious is large deployments when you can only add 1 application at a time to the Install application step. I know the step can take upto 9 applications so why can't we have a checkbox next to each application and select them all at once rather than re-opening the wizard and browsing through a folder structure? I think this would simplify task sequence creation and management.5 votes
Updating status to completed. Multi-select for Apps in the Install Application task sequence step is added in SCCM 1702 – see https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1702 for more info.
Thanks for all the suggestions and feedback
Server 2016 no longer has a min-gui feature. With this removal, it is only possible to deploy a distribution point that supports Operating System Deployment to a server with a full gui.
Distribution points are perfect candidates for server core! They should be fully supported, including PXE booting for Operating System Deployment.5 votes
Updating status to complete, this is now available with our 1806 release
Thanks for the suggestion and feedback
When I used the new feature that makes it possible to run a Task Sequence within a Task Sequence the option to "Access content directly from distrubution point" disappears. Is it possible to keep that option accessible? It's nice to only have one TS with all drivers and run that within any other task sequence while keeping that option enabled. Driver installation without that option is alot slower in my experience.4 votes
Thanks for the feedback.
The option to use “Access content directly from distrubution point” was regressed from another code change late in our 1802 release. This was addressed in 1806, updating status to completed.
It would be beneficial if you could set breakpoints at any line item in the task sequence, just like when coding, to stop the task sequence progress. Have a dialog pop up with which you can continue to the next break point.4 votes
This was completed – I missed setting the status to completed.
Updating status to completed – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion
This ask is addressed with our new task sequence debugger now available with our 1906 release.
Global PXE boot password change so that you do not have to change it on every DP.4 votes
Thanks again for the feedback. I’m updating this to Complete and returning your votes (more OSD please!) as this can be completed with the PSH added earlier.
The scripts that are created and approved in \Software Library\Scripts allow them to be used during a task sequence that way you do not need to create a package to contain the script file and download. That way you can avoid using the run command line step if the script is long.4 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Fixed in #SCCM 1902 which shipped today.
Place a file on the BootMedia to identify it with the PackageID and the Package Source Version. If you have different BootMedias (Test, Prod, ...) or FieldService that does not know which one they used to create the USB Stick, it would be very helpful, to easily find the PackageID and the Version of the Media.4 votes
Thanks for all your suggestions and feedback, updating status to completed.
SCCM 1902 fast Ring released today
When using the Run PowerShell Script task sequence, it would be beneficial to be able to pass task sequence variables in the parameters field, especially when using different credentials where PowerShell no longer has access to Microsoft.SMS.TSEnvironment.4 votes
Updating status to complete.
The opt-in phase of our 2002 release (fast ring) is now live and contains the changes asked for with this item.
You can opt-in and then download 2002 through their Admin Console now.
Support Information: https://aka.ms/cmcssreleaseinfo
I need an ability to run executable content, especially posh scripts, in winpe from RAMdisk. I mean, then there is no initialised or partitioned disks in the system.4 votes
Updating status to completed.
Hoping the guidance provided from Carsten and myself helped out.
SCCM 1902 fast Ring released today
- Don't see your idea?