40 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started – see https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 2001 Technical preview is release and the Check Readiness steps has some new additions.
For more info:
Try it out and let us know your feedback, thanks.
Thanks for your suggestion and feedback.
Updating status to Noted – see https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
83 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started – see https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each status value.
Our 1912 Technical preview is now release.
For more information
Vlad ask to pass this on:
He can try at the beginning of TS to add steps to set variables that I listed in my reply to the same strings that he entered in the UI of Network Settings step? Which will result in Network Settings step take the values from these global variables (not from UI, even though they may be the same). But it will also have a side effect that these variables will be available during task sequence for whatever he wants to user them for.
I’ll have a bit of time at the weekend. I’ve a couple of ideas about removing the LDPA:\\ you mentioned. Can you describe the scenario you want to address, please?
Marty, you can try (before the Network Settings step) to add steps setting TS variables that are listed in my previous message. You can set them to the same strings that are entered in the UI of Network Settings step (or to something different). Which will result in Network Settings step take the values from these global variables (not from value in UI which will be ignored). This will also have a side effect that these variables will be available during task sequence for whatever purpose that you want to use them for in your scripts.
Task sequence step "Apply Network Settings" internally is using task sequence variables, so if someone wants to read them, they already can:
OsdNetworkJoinType // 0=Domain, 1=Workgroup
Documentation already lists OSDDomainName and OSDDomainOUName:
Updating status to Noted
Thanks for your feedback.
Updating status to noted, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.
We’ve addressed this in our 1902 release as well as the ability to import a single .wim from the multi-index .wim.
As Vlad mentioned, the New-CMOperatingSystemImageUpdateSchedule CmdLet has -RemoveSupersededUpdates
I’ll update the status to completed if this addressed your ask. If not, then let us know any gaps.
such parameter was added together with the UI option: it is called RemoveSupersededUpdates (alias is CleanUp)
No longer an issue. Apps and packages that are part of task sequence should not be removed from stand-alone media and this option is removed in 1906 release
In 1810 release of ConfigMgr the order of packages being added to the list after 'Apply' button is pressed will be preserved.
Aaron, could provide some details of the PS script that is working for you? Want to see if we can built it in for everybody.
Thanks for the feedback, updating status to Noted.
I am a developer in ConfigMgr team. We fixed the issue when Install Application task did not use local Prestaged Media content for application content and downloaded it from a DP instead. The fix should be available in 1610 release of ConfigMgr.