Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

 
alt

Daniel Nashed

 

    Windows Updates are the highest challenge in patience

    Daniel Nashed  25 February 2023 12:01:17

    After upgrading my ESXi to version 8.0 I am looking again into updating my Windows 11 machine.

    Turns out Intel NUCs have no supported TPM 2.0 module.
    And the software module only works with vSphere and not a stand-alone ESXi server.

    But I found a way convincing the Windows 11 installer specifying registry keys during boot to install.

    The installation was very quick. But the updates took quite long. Now I am waiting since at least 30 minutes for the machine coming up after reboot..

    Most admins can't avoid using Windows completely. But I can't understand why someone would prefer to run an application like Domino on Windows.
    The complete setup for a Linux machine takes minutes. Updates are installed automatically if configured and the resources needed are much lower.

    If you manually update it's just a "yum update" (RHEL/CentOS), "apt update" (Ubuntu/Debian), zypper update (SUSE).
    Some Linux distributions like current Ubuntu and SUSE even tell you which services need to restart.

    I have auto updated enabled on all of my Domino on Linux servers hosted and just get a daily mail with updates installed.

    Automation is so much easier in the Linux world..

    Most of my Domino servers in production run on Docker or Podman with native volumes.
    A Domino update is just a "dominoctl update" in my environment.


    I would really like to hear from you how you run your environment and if admins are looking into modern container basted deployments and why (or why not...)

    Blog post done, restart after first reboot is still not finished .. Hmmm...

    -- Daniel


    Image:Windows Updates are the highest challenge in patience


    Image:Windows Updates are the highest challenge in patience


    Links

      Archives


      • [HCL Domino]
      • [Domino on Linux]
      • [Nash!Com]
      • [Daniel Nashed]