Securing the Local Admin Account (LAPS Password Manger) [Windows Server 2019]

Поділитися
Вставка
  • Опубліковано 1 лис 2024

КОМЕНТАРІ • 18

  • @hermonkidane1503
    @hermonkidane1503 Рік тому +1

    Oh man how much I would love for Rob to post more videos more often, he's an absolute Gem. Love everything you do here. Just wish if you could do more if time allows it

    • @OsbornePro
      @OsbornePro  Рік тому

      Thanks for watching! I appreciate the support. I do plan on making more videos again. I have just had a lot on my plate recently with work. I am working with Orange Ava publishing to write a book on network monitoring using PRTG which is very time consuming.

    • @hermonkidane1503
      @hermonkidane1503 Рік тому

      @@OsbornePro Understood. Appreciate everything you do here.

    • @OsbornePro
      @OsbornePro  Рік тому

      @@hermonkidane1503 thanks!

  • @RodrigoLelesMiranda
    @RodrigoLelesMiranda Рік тому +1

    Rob is very impressive things that you do. This class is very cool... PLEASE PLEASE share more with us.

    • @OsbornePro
      @OsbornePro  Рік тому

      Thanks Rodrigo! Appreciate you watching and your support. I was recently asked to write a book on network monitoring using PRTG so I just started that project. I do need to create more videos it has been a while. I will look at doing it again.

  • @r.e.434
    @r.e.434 3 роки тому +1

    Very Cool! Keep up the great content!

  • @hermonkidane1503
    @hermonkidane1503 Рік тому +1

    May I ask about the backup for passwords, I didn't get that fully.

    • @OsbornePro
      @OsbornePro  Рік тому

      I put that script together is to keep a backup history of the local admin passwords. The reason you want to keep a backup of the passwords has to deal with restoring backups of a server. For example, if my Windows DHCP server had a local admin password set to "Password123!" yesterday. Today, LAPS changed the password to "SuperPassword321!". The machine suddenly crashes and I have to restore a backup from yesterday. The local admin password is no longer going to be "SuperPassword321!". It is going to be "Password123!". The Active Directory attribute is still going to return a value of "SuperStrongPassword321!". The backup history allows you to find that information

    • @hermonkidane1503
      @hermonkidane1503 Рік тому

      @@OsbornePro Understood thank you.

    • @OsbornePro
      @OsbornePro  Рік тому

      @@hermonkidane1503 No problem!

  • @Akira29H
    @Akira29H 9 місяців тому +1

    Using Laps can manage Domain account?

    • @OsbornePro
      @OsbornePro  9 місяців тому +1

      Thanks for watching! No unfortunately LAPS can only manage the local admin account of systems and not domain accounts

    • @Akira29H
      @Akira29H 9 місяців тому +1

      @@OsbornePro if you disabled user local user/ admins after setting up Laps whats the point setting up esp if device is not authenticated back to domain for period of time?

    • @OsbornePro
      @OsbornePro  9 місяців тому

      @@Akira29H you may need to enable the local admin account at some point to rejoin to a domain for example and the account may not vSomeone setting up a device for the first time may set a weak password to get through the setup and log in easily. It’s just defense in depth to keep track of the password in case you need it. If setting longer expirations works better for you because of offline machines there is no harm in doing that

    • @Akira29H
      @Akira29H 9 місяців тому +1

      @@OsbornePro thanks for all learning advice. I have question. I have different domain admin accounts but i dont have any controls to them like user account pw reset or join pc to domain i want these users to have min access to AD. A video would be appreciated. Tq very much.

    • @OsbornePro
      @OsbornePro  9 місяців тому +1

      @@Akira29H no problem thanks for the idea. I will do a next video on delegate permissions for some scenarios I have had requested before and include yours