Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Anonymous

My feedback

  1. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 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 →
    Anonymous shared this idea  · 
  5. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    To clarify, Microsoft should provide the interfaces necessary for calling the Configuration Manager Management Point SDK API from within WinPE. This relates to the operation of the 1E Nomad agent, an Alternate Content Provider.

    Right now it is not possible to use the Client SDK within WinPE (or so we have been told by Microsoft).

    Anonymous shared this idea  · 

Feedback and Knowledge Base