Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Jeroen Bakker

My feedback

  1. 3 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 →
    Jeroen Bakker commented  · 

    I suspect the variable may give the desired results if you expand the wait time to a value between 300 and 600 seconds. The second reboot will usually not occur within 120 seconds after boot.

    I've had good results with this option in my task sequences but the correct wait time may require some testing to find. Don't configure it to narrow beacuse some months the required time may be longer than others.

  2. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Jeroen Bakker commented  · 

    This can partially be achieved with an existing client setting:
    Setting "Client Policy - Enable user policy on clients" to "No" will prevent any user targeted software from installing. We use this setting on all of our (Remote Desktop) servers to prevent users from accidentally triggering installations.
    https://docs.microsoft.com/en-us/sccm/core/clients/deploy/about-client-settings#enable-user-policy-on-clients

  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Jeroen Bakker commented  · 

    The BITS jobs can be removed when running under the system account.

  4. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Jeroen Bakker commented  · 

    It would be extremely useful if we can set a deployment to user collections to globally publish the app-v. The difference in publishing mode between our Citrix (always system targeted installations --> global app-v publishing) and Windows client (mostly user targeted installations --> user app-v publishing) increases the required effort to manage shortcuts etcetera.

    Jeroen Bakker supported this idea  · 
  5. 2 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 →
    Noted  ·  sangeev responded

    The Task Sequence can be set to use ‘Run from Net’ – OS Image, Client Package etc. have to be set to use Package Share – part of the properties, visible on the ‘Data Access’ tab. Would that option help?

    Updated by bobmn for sangeev/OSD

    Jeroen Bakker supported this idea  · 
    Jeroen Bakker commented  · 

    With new (larger) Windows PE versions I sometimes have an issue with the lack of unencrypted local storage. Specifically when I boot into WinPE (from network or media) and the TS I choose to deploy requires a switchover to another WinPE image (mainly X86 <-> X64) then local storage is required for download of the image. If there is no/ to little unencrypted space the download and the TS fail.
    In my environment only the BDE partition was available as unencrypted storage. I've had to enlarge this twice now, first for WINPE 8.1 and now for WinPE 10.
    When I run into this problem only option is to repartition manually, a repartition step in the TS doesn't save me becaiuse this runs after booting into WinPE (which can't be downloaded).

  6. 76 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

    Jeroen Bakker commented  · 

    I Ran into the same issue and created a custom solution.
    I set this as first step after booting to the OS and remove it as last step in the TS.

    I do thisby copying a customized backgrounddefault.jpg into %windir%\system32\oobe\info\backgrounds (or sysnative) and setting a reg key to use it as logon screen.
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background, dword: OEMBackground with value 00000001

    Jeroen Bakker supported this idea  · 

Feedback and Knowledge Base