Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Vladimir Sorokin (Configuration Manager team @ MSFT)

My feedback

  1. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Vladimir Sorokin (Configuration Manager team @ MSFT) supported this idea  · 
  2. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Vladimir Sorokin (Configuration Manager team @ MSFT) supported this idea  · 
  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Marty,

    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?

    Thanks

    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    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.

    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    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
    OsdWorkGroupName
    OsdDomainName
    OsdDomainOUName

    Documentation already lists OSDDomainName and OSDDomainOUName:
    https://docs.microsoft.com/en-us/sccm/osd/understand/task-sequence-variables#OSDDomainName

  4. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Vladimir Sorokin (Configuration Manager team @ MSFT) supported this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

    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.
    https://docs.microsoft.com/en-us/sccm/osd/get-started/manage-operating-system-images#BKMK_AddOSImages

    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.

    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    such parameter was added together with the UI option: it is called RemoveSupersededUpdates (alias is CleanUp)

  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  1 comment  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    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

  8. 228 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  8 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    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.

  9. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vladimir Sorokin (Configuration Manager team @ MSFT) commented  · 

    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.

    --
    Vladimir

Feedback and Knowledge Base