> ## Documentation Index > Fetch the complete documentation index at: https://docs.oloid-demo.com/llms.txt > Use this file to discover all available pages before exploring further. # Windows Login v2.0 - How to Deploy Windows Login v2.0 using Microsoft Configuration Manager (SCCM) > SCCM console access with rights to create and deploy applications. ## Introduction ## Prerequisites SCCM console access with rights to create and deploy applications. Source files staged on a UNC path reachable by the site server (e.g. \\\\\\Sources\Oloid Passwordless\\). Source files: Oloid Passwordless V2 installer (.exe file) Installation script (powershell script) AutoPairConfig file (.txt file) * A Distribution Point available to host content. * A Device Collection containing the target machines. ## Steps to Deploy Windows Login v2.0 Create Application Deploy Application The Windows Login v2.0 is deployed successfully. ### Create the Application 1. Log in to Open Application Management 1. Navigate to **Software Library → Application Management → Applications**. 2. Launch the Create Application wizard Right-click in the Applications pane and choose **Create Application**. 3. Select Manual specification Choose **Manually specify the application information**, then **Next**. 4. General Information Fill in **Name**, **Software version**. Owner and Support contacts default to Administrator. 5. Software Center entry Set the **Localized application name** (and optional description, keywords, icon) shown to end users in Software Center. 6. Add a Deployment Type On the Deployment Types page, click **Add…**. 7. Deployment Type — Manual Select **Manually specify the deployment type information** → **Next**. 8. Deployment Type — General Information Enter the **Name** of the deployment type → **Next**. 9. Deployment Type — Content * **Content location**: UNC path to the source files. **Installation program**: full command ``` %SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File .\install.ps1 ``` **Uninstall program**: full uninstall command. ``` %SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "Uninstall-Package -Name 'Oloid Passwordless Login' -Force" ``` * Enable **Run installation and uninstall program as 32-bit process on 64-bit clients** only if required by the installer. 10. Detection Method Select **Use a custom script to detect the presence of this deployment type**, then click **Edit…**. 11. Detection Script Set **Script type = PowerShell** and paste the detection script. The script must write any output to stdout when the application is **installed**, and write nothing when it is not. Click **OK**. Detection script: replace x.x.xxx in line 3 with the version number of Oloid Passwordless being deployed. ``` $ErrorActionPreference = 'SilentlyContinue' $expected = 'x.x.xx' $found = $false $app = Get-ItemProperty 'HKLM:\SOFTWARE\OLOID\Oloid Passwordless Login' -ErrorAction SilentlyContinue if ($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 0 ``` Confirm the script length shows on the Detection Method page, then **Next**. 12. User Experience * **Installation behavior**: Install for system * **Logon requirement**: Whether or not a user is logged on * **Installation program visibility**: Hidden * Set **Maximum allowed run time** as appropriate (default 120 min). **Next** 13. Requirements No requirements to be configured. **Next**. 14. Dependencies No dependencies to be configured, click **Next**. 15. Deployment Type Summary Review and confirm. **Next** to commit the deployment type. 16. Application Summary Review the full application. **Next** to create. 17. Wizard progress and completion Wait for the wizard to finish, then **Close**. *** ### Deploy the Application 18. Start the deployment Select the new application in the Applications list and click **Deploy** on the ribbon. 19. Deploy Software Wizard — General The **Software** field is pre-filled. Click **Browse…** next to **Collection**. 20. Select target collection Choose **Device Collections**, pick the target collection (e.g. jagad), then **OK**. 21. Content destination Under **Additional distribution points…**, click **Add → Distribution Point**. 22. Select Distribution Point Pick the on-premises DP that will host the content. **OK**. 23. Confirm DP selection Verify the DP is selected. **OK**. The DP now appears in the destination list. **Next**. 24. Deployment Settings * **Action**: Install * **Purpose**: Required (use Available for opt-in via Software Center) * Enable **When a resource is no longer a member of the collection, uninstall this application** if you want removal on collection exit. 25. Scheduling Set **Available time** and **Installation deadline**. Default As soon as possible after the available time is acceptable for immediate rollouts. 26. User Experience * **User notifications**: Display in Software Center and show all notifications * Tick **Software installation** and **System restart** under "deadline reached" only if forced behavior is required. 27. Alerts Configure CM / Operations Manager thresholds if alerting is needed. Otherwise leave defaults. **Next**. 28. Summary and commit Review the deployment summary. **Next** to create the deployment. Wait for the wizard to finish. *** ### Part 3 — Monitor the Deployment 29. Open Monitoring Go to **Monitoring → Deployments**. 30. Review status Locate the deployment in the list. The bottom pane shows completion statistics (Success / In Progress / Error / Requirements Not Met / Unknown).