---
title: "Scalefusion April 10th, 2023 Release Notes"
slug: "april-10th-2023-release-notes"
description: "\"Explore Scalefusion's April 10, 2023, release to simplify Windows device enrollment. Learn about auto-enrollment post-installation and support for AutoCreate Kiosk User in Multi-App Kiosk. Upgrade to version v43.0.0 for a seamless experience.\""
updated: 2023-09-26T17:10:20Z
published: 2023-09-26T17:10:20Z
canonical: "help.scalefusion.com/april-10th-2023-release-notes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.scalefusion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scalefusion April 10th, 2023 Release Notes

## Version Information:

**Scalefusion Dashboard:** v43.0.0

**Scalefusion MDM Agent (Application for Windows):** v9.0.12

**Windows SF Deployer:** v1.0.2.0

## Release Notes:

1. **Windows Auto-Enrollment:** The Windows Agent app can be configured to auto-enrol post installation using either Serial# or Enrollment Code by following any of the two approaches below. This will help drive enrollment of company-owned devices on Windows.
  1. The Windows agent can be deployed via other MDMs or MSI deployment tools by configuring additional command line parameters to indicate that a silent enrollment post installation is required. Visit [here](/docs/agent-based-enrollment-using-admin-account) for more information.
  2. IT Admins can use SF Deployer to generate a custom SF agent and pass command line parameters so that when the end user installs this SF Agent it would auto-enrol. Visit [here](/docs/agent-based-enrollment-in-non-admin-mode) for more details.
2. [**Support for AutoCreate Kiosk User in Multi-App Kiosk via Agent:**](/docs/configure-multi-app-kiosk-custom-launcher-ui-on-windows) We now support an auto-user account to be created with the given name and without a password in multi-app kiosk mode driven via the agent. This will help with agent-driven Multi-App Kiosk/Single App Mode cases where a user without a password needs to be created.
3. **Support for** [**$device.enrollmendUserSID in App Locker Policy:**](/docs/configure-app-locker-policy-on-windows) Now, the App Locker can be applied only to the user that enrolled the device by simply specifying $device.enrolledUsersid. This will ensure that the policy is applied only to the user who enrolled the device rather than any other group.

**Team:**

Development: Shubham Dhakad

QA: Abhishek Pal, Sagar Lasurkar