Michael Wu

The Life of a Cloud Engineer

  • Home
  • Resume
  • Blog
  • Contact

Posted on 04.01.16

How to deploy the LAPS by SCCM – Part 2

In this series of posts, I will demonstrate the steps to deploy Local Administrator Password Solution(LAPS) by SCCM. This is the second post covered the deployment procedure in SCCM. You can also check the other posts by the below links:

  • How to deploy the LAPS by SCCM – Part 1
  • How to deploy the LAPS by SCCM – Part 3

Create Task Sequence

You can deploy the package directly to device collections. However, SCCM will show errors even the deployment is successful.  This is because that the package deployment does not recognize the exit code. Therefore, we will use task sequence to deploy the package. It will give us more flexibility for the deployment.

LAPS_SCCM_PackageError

  • Create a new custom task sequence

LAPS_SCCM_Task_Sequence_1

  • In the Task Sequence Editor, create a Install Package task

LAPS_SCCM_Task_Sequence_2

  • On the Properties, browse the LAPS package that we created before and select the Copy File program

LAPS_SCCM_Task_Sequence_3

  • On the Options, add condition for Operating System Version. Select all 64-bit operating systems as needed. Repeat the same procedure for x86 version.

LAPS_SCCM_Task_Sequence_4

  • Add a Run Command Line task

LAPS_SCCM_Task_Sequence_5

  • In the Command line area, copy the below command to it. This command will register the DLL silently. You should have three tasks in the Task Sequence. Click OK to complete. You can deploy the Task Sequence to device collections now.
regsvr32.exe %windir%\AdmPwd.dll /s

LAPS_SCCM_Task_Sequence_6

Deploy Task Sequence

We have to make sure that the LAPS will be installed silently into client computers. Here are some configurations we may need in the deployment.

  • In Deploy Software Wizard, select Required

LAPS_SCCM_Deployment1

  • In User Experience, uncheck Show Task Sequence progress. We don`t want to interrupt users.

LAPS_SCCM_Deployment2

Verify the deployment

  • You can see the result and progress on the Monitoring of SCCM console

LAPS_SCCM_Verify1

  • To verify it really works, check the file in the local machine

LAPS_SCCM_Verify2

At this point, the client computer should be ready for the LAPS. Besides, there are still some works need to be done such as extend Schema, machine permissions, and Group Policy.  We will discuss them in the next post.

See More

  • How to deploy the LAPS by SCCM – Part 1
  • How to deploy the LAPS by SCCM – Part 3

Categories:SCCM

Recent Posts

  • Automating Resource Restriction in Azure subscriptions with Budget Alert, Automation Account, and Azure Policy
  • How to configure the Security Center via Azure Resource Manager (ARM) template
  • How to restrict Account Operators to see the password in LAPS
  • How to join a VM to a domain by PowerShell in Azure
  • How to push an existing repository from VS Code to Azure DevOps by PowerShell

Search

Categories

  • Azure
  • IIS
  • PowerShell
  • SCCM
  • VMware
  • Windows Server

Contact

Email: [email protected] | Powered By the 太初網路

Copyright © 2024 mikewu.org Disclaimer

Connect

FacebookTwitterGoogle +Linkedin