Introduction
This document provides step-by-step instructions to deploy Windows Login v2.0 using Microsoft Configuration Manager (SCCM). It covers the creation of the application, configuration of deployment settings, detection methods, and deployment to target device collections.
Prerequisites
You must have admin access to Microsoft Configuration Manager (SCCM).
You must have the installation script file (
install.ps1) required for deployment.You must have the Windows Login v2.0 version number that will be used in the detection script.
The installation source files must be stored in a shared network location (UNC path) that is accessible from the Configuration Manager site server.
For example:
\\<server>\Sources\Oloid Passwordless\Note: Ensure the following source files are available in the shared location:
Oloid Passwordless v2 installer (
.exe)Installation script (
.ps1)AutoPairConfig file (
.txt)
Target device collections must be created and available in Microsoft Configuration Manager.
Distribution Points must be configured and accessible within your Configuration Manager environment.
Steps to Deploy Windows Login v2.0
The Windows Login v2.0 is deployed successfully.
Create Application
Launch the Microsoft Configuration Manager.
The Microsoft Manager home screen is displayed.
Navigate to Software Library > Application Management > Applications.
The Applications screen is displayed.
Right click > select Create Application.
The Create Application Wizard pop-up box is displayed.
On General tab, select Manually specify the application information > click Next.
The General Information tab is displayed.
On General Information tab, do the following.
On Software Center tab, do the following.
Note: The Software Center tab allows admin to configure how the application appears to client devices in Software Center.
On Deployment Types tab, do the following:
On Create Deployment Type Wizard, do the following:
On General tab, select Manually specify the application information > click Next.
The General Information tab is displayed.
On General Information tab, do the following.
On Content tab, do the following.
Enter Content Location.
Note: UNC path to the source files.
Enter Installation Program.
Note: Use the following command.
%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File .\install.ps1Enter Uninstallation Program.
Note: Use the following command.
%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "Uninstall-Package -Name 'Oloid Passwordless Login' -Force"Select Run installation and uninstall program as 32-bit process on 64-bit clients.
Click Next.
The Detection Method tab is displayed.
On Detection Method tab, do the following:
Select Use a custom script to detect the presence of this deployment type.
Click Edit.
The Script Editor pop-up box is displayed.
Do the following:
Select PowerShell as script type.
Enter the Script in Script Contents.
Note:
i. In the expected field enters the app version number.
ii. Use the following script.
$ErrorActionPreference = 'SilentlyContinue'$expected = 'x.x.xx'$found = $false$app = Get-ItemProperty 'HKLM:\SOFTWARE\OLOID\Oloid Passwordless Login' -ErrorAction SilentlyContinueif ($app -and $app.Version -eq $expected) { $found = $true }if (-not $found) {$paths = @('HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*')$entry = Get-ItemProperty $paths -ErrorAction SilentlyContinue |Where-Object { $_.DisplayName -match 'Oloid' -and $_.DisplayVersion -eq $expected }if ($entry) { $found = $true }}if ($found) { Write-Output 'Installed' }exit 0Click OK.
The Detection Method screen is displayed.
Confirm the Script length and click Next.
The User Experience tab is displayed.
On User Experience screen, do the following:
On Requirements tab, click Next.
The Dependencies tab is displayed.
On Dependencies tab, click Next.
The Summary tab is displayed.
On Summary tab, review the general details and click Next.
The Progress tab is displayed.
On Progress tab, click Next.
The Completion screen is displayed.
The deployment type wizard is created and configured successfully. The Deployment Types page is displayed.
Click Next.
The Summary tab is displayed.
On Summary tab, review the general details and click Next.
The Progress tab is displayed.
The Completion tab is displayed.
Click Close.
The app is created successfully and listed on the Applications page.
Deploy the Application
On the Applications page, right-click the application that you created and select Deploy.
The Deploy Software Wizard screen is displayed.
On General tab, do the following:
Click Browse to select the collection
The Select Collection pop-up box is displayed.
From the collection type drop-down list, select Device Collections.
Note: Select User Collections if you want to deploy the application to users instead of devices.
The available device collections are displayed in the right side.
Select the Device Collection > click OK.
The General page is displayed.
Click Next.
The Content tab is displayed.
On Content tab, do the following:
On Deployment Settings tab, do the following:
On Scheduling tab, do the following:
On User Experience tab, do the following:
On Alerts tab, click Next.
The Summary tab is displayed.
Review the General information and click Next.
The Progress tab is displayed.
The Completion tab is displayed.Click Close.
The app is deployed successfully and listed in the deployment list.
Monitor the Deployment (Optional)
Go to the home page of the Microsoft SCCM and click Overview > Deployments.
The Deployment list of software is displayed.
Locate the deployment in the list. The bottom panel shows completion statistics (Success / In Progress / Error / Requirements Not Met / Unknown).
Keywords
| Windows Login v2.0 deployment via SCCM | Deploy Windows Login v2.0 via Microsoft Configuration Manager |



































