MicrosoftThanks for the updates. I will spend time reading all the documentation to see if my question is answered there. In the meantime, in an effort to get ahead of my reviewing the docs and allowing all you wonderful folks to help provide more information/context, I will pose it here now.
I have been a customer of the "legacy LAPS" since it's introduction. In fact, at that time, there was another version offered only to premier customers. Let's call this "legacy LAPS-E". Several of the capabilities you mention with the new update have been in use by my organization for years. For example, the encrypted password, password history, Powershell modules, event audit. So I am curious how this might affect our current implementation. The "legacy LAPS-E" was similar to "legacy LAPS" in regards to the need to install via an MSI what amounts to a very small client-side extension that provided the Group Policy capabilities. This also require the implementation of 2 infrastructure servers (for redundancy in a primary/secondary relationship) that provided the encryption capabilities. Can I assume that when we move this the now "modern/native" approach to this solution, that I will be able to phase out and eventually destroy those encryption servers, SCCM packages which ensure the MSI is installed on all clients, DNS SRV records (failover primary/secondary), etc???
Thanks in advance for any thoughts/guidance.
Now I will have to get to reading those documents and learn if the answers are in there somewhere!
