<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Microsoft-Laps on Jon's Notes</title><link>https://4c4806b4.configjon-blog.pages.dev/category/microsoft-laps/</link><description>Recent content in Microsoft-Laps on Jon's Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Apr 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://4c4806b4.configjon-blog.pages.dev/category/microsoft-laps/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft LAPS Step by Step - Part 1</title><link>https://4c4806b4.configjon-blog.pages.dev/microsoft-laps-step-by-step-part-1/</link><pubDate>Tue, 02 Apr 2019 00:00:00 +0000</pubDate><guid>https://4c4806b4.configjon-blog.pages.dev/microsoft-laps-step-by-step-part-1/</guid><description>&lt;p&gt;This is an updated version of a post I made on the Now Micro blog last year. The original version of this post can be read &lt;a href="https://blog.nowmicro.com/2018/02/28/configuring-laps-part-1-configuring-active-directory/"&gt;&lt;strong&gt;Here&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why is Local Administrator Password Management Needed?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The question of how to deal with users having administrative rights on computers or other network resources is one that has many different answers and has evolved over time. While the scenarios around network and domain administrative access may be more complex, the local administrative rights scenario should be very similar for almost everyone.&lt;/p&gt;</description></item><item><title>Microsoft LAPS Step by Step - Part 2</title><link>https://4c4806b4.configjon-blog.pages.dev/microsoft-laps-step-by-step-part-2/</link><pubDate>Tue, 02 Apr 2019 00:00:00 +0000</pubDate><guid>https://4c4806b4.configjon-blog.pages.dev/microsoft-laps-step-by-step-part-2/</guid><description>&lt;p&gt;This post is the second part of a two-part series on configuring and deploying the Microsoft Local Administrator Password Solution (LAPS). The &lt;a href="https://4c4806b4.configjon-blog.pages.dev/microsoft-laps-step-by-step-part-1/"&gt;&lt;strong&gt;First Post&lt;/strong&gt;&lt;/a&gt; covered the steps needed to configure Active Directory to support LAPS. This post will cover the steps needed to enable the LAPS functionally on devices.&lt;/p&gt;
&lt;p&gt;In order for the local administrator password to be randomized on devices, two conditions need to be met.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;ol&gt;
&lt;li&gt;The client needs to have a group policy object linked that enables LAPS&lt;/li&gt;
&lt;li&gt;The client needs to have the LAPS group policy client-side extensions installed so it knows what LAPS is&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="configure-group-policy-to-deploy-laps-settings"&gt;Configure Group Policy to Deploy LAPS Settings&lt;/h2&gt;
&lt;p&gt;Group Policy is used to configure LAPS settings and to enable the LAPS functionally on targeted devices. The LAPS settings can be added to an existing group policy object, however in this example, a new group policy object will be created to deploy the settings.&lt;/p&gt;</description></item></channel></rss>