Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

ivan borghetti

My feedback

  1. 147 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    37 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  2. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Additional Services » Team Services  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  3. 506 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  4. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Monitor » Webhook  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  5. 226 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    47 comments  ·  Azure Management Groups » New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  6. 72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Automation » Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  7. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →
    ivan borghetti supported this idea  · 
  8. 53 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Update Management » Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently reviewing enhancements around approved and time-delayed patching.

    In the interim – there are two ways to achieve your scenario “exactly same updates” in Dev & then Prod, by either manipulating the OS behavior or tweaking the AUM config:

    1. - Host the updates locally using Microsoft WSUS [https://docs.microsoft.com/azure/automation/automation-configure-windows-update#make-wsus-configuration-settings] or Reposync utility from RedHat [https://access.redhat.com/solutions/23016]or Ubuntu Landscape [https://docs.ubuntu.com/landscape/], etc. And the configure the update service or package manager of all your machines to use the local update source. In this way the updates installed when using Update Management will only be what is available in your local patch server which is running (say) WSUS or RH Reposync. And if the patch server remain unchanged in 2-3 weeks when you start update schedule for Prod, they will also fetch updates from same local patch server and have exactly same updates as your non-prod.
    1. - Use the…
    An error occurred while saving the comment
    ivan borghetti commented  · 

    the selection of patches that we want to include is a good option however i think the request is different , i will put an example in Linux since i am not very experienced with Windows. Lets say i patch my dev environment today and we have 50 patches in the repo that i apply to my servers. In 2 weeks i will need to patch my prod servers however in the repo there are now 60 patches and in some cases there are also new versions for patches that i applied in dev. A good example would be a kernel versión. In this case it would be really difficult to be able to manage all those variables which today in onprem or with different tolos are managed with local repos (sccm , red hat satellite , tanium ) or with the package reléase dates , for instance , apply the packahes released from x to y only .

    ivan borghetti supported this idea  · 
  9. 97 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →

    Update Management is a wrapper which uses your machine’s OS update service or package manager – to fetch & install updates.

    On Windows Server OS – the Microsoft Update Service can be configured fetch & updates for MS products. And hence UM, then can allow installing MS updates as well. More details here: https://docs.microsoft.com/azure/automation/update-management/configure-wuagent#enable-updates-for-other-microsoft-products

    Microsoft Update Service on Windows Server OS doesn’t update 3rd party software say Adobe or Java. Hence update management solution can’t also in-turn do the same. Unless tools like Wsus Package Publisher ( https://github.com/DCourtel/Wsus_Package_Publisher ) is used which can publish third-party applications into your WSUS.

    ivan borghetti supported this idea  · 

Feedback and Knowledge Base