Reduce VDI User Logon Time - Improve UX

VDIWarmUp improves logon times for users by pre-logging onto the VM at system startup.

The VDIWarmUp user connects to the VM via RDP and optionally runs a profile logon script that calls common processes to improve application launch times for subsequent users.

• Supports pre-existing VMs
• Supports Specialized Images
• Supports Generalized Images
• Supports Active Directory
• Supports Entra ID
• Supports AVD Session Hosts
• Supports Citrix VDAs
• Integrates with AVDManage
• Digitally Signed

4

6

8
14

33
46

1

2

4
7

10
31

Run VDIWarmUp.msi (as Administrator)

Click Next

Run logon script at startup.

Choose to delete the VDIWarmUp user account and scheduled tasks when VDIWarmUp completes.
VDIWarmUp will only run on the first boot.

Click Next

To prevent VDIWarmUp from running during deployment, select the appropriate option.

This will also prevent VDIWarmUp from running when starting the Master Image VM.

Click Next

To prevent AVD user connections while VDIWarmUp is running, VDIWarmUp can stop the Remote Desktop Agent Bootloader service at startup, and enable and start the service when VDIWarmUp completes.

To prevent Citrix user connections while VDIWarmUp is running, VDIWarmUp can stop the Citrix Desktop Service at startup, and enable and start the service when VDIWarmUp completes.

Specify a maximum session duration. This should be greater than the time required to run the logon script.

When installation is complete.

Modify C:\Windows\System32\Repl\Import\Scripts\VDIWarmUp.cmd based on your application environment.

Run VDIWarmUp.exe /config (as Administrator) to create the VDIWarmUp user account, and the VDIWarmUpConfig and VDIWarmUp Scheduled Tasks.

Run VDIWarmUp.exe /test (as Administrator) to launch an RDP Connection, create the VDIWarmUp user profile and validate your configuration.

Validate C:\Windows\Temp\VDIWarmUp-<USERNAME>.log.

Validate the VDIWarmUp scheduled task.

You can run either task manually. No connection window will be visible however you can monitor progress by watching the Users tab in Task Manager and by reviewing the VDIWarmUp-SYSTEM.log and VDIWarmUp-VDIWarmUp.log files.

/config

/launch

/delete

rem Chawn VDIWarmUp Logon Script
rem ------------------------------------------------------Start common apps.
start notepad
start explorer /SEPARATE
start msedge
start taskmgr
start ms-settings:

rem ------------------------------------------------------Start your apps. Edit as necessary
rem start winword
rem start excel
rem start outlook
rem start acrobat

rem ------------------------------------------------------Deploy AppX Packages - start Teams and OneDrive - increase RDPTIMEOUT to 180
rem powershell.exe -WindowStyle Maximized -ExecutionPolicy Bypass -File "C:\Windows\System32\Repl\Import\Scripts\Add-AppxPackages.ps1"

rem ------------------------------------------------------Wait for apps to load
timeout /t 30 /nobreak

rem ------------------------------------------------------LogOff
shutdown /l

On a single user operating system, Windows will not permit more than one RDP connection so the following is displayed.

This is a successful test. You can either click OK or wait 60 seconds until disconnection.

Reboot the VM and review VDIWarmUp.log to confirm a successful configuration.

VDIWarmUp.exe /test will ignore the following parameters.

DELETEVDIWARMUP
WAITONENTRA
WAITONAD
STARTAVDAGENT
STARTCITRIX

Install VDIWarmUp. During installation, set 'Start only if Active Directory joined' (WAITONAD=1), even if you intend to join Entra ID, and 'Start AVD Agent if disabled' (STARTAVDAGENT=1).

Create C:\Scripts\AVD-Config.ps1.

AVD-Turbo will run AVD-Config.ps1 after joining Active Directory or Entra ID and optionally joining an AVD Host Pool.

DisService RDAgentBootLoader

# Disable Logons - we don't want users logging on until after the reboot
stop-service RDAgentBootLoader

# Check if VM is Entra joined
$IsEntraJoined='NO'
CheckEntraID

# Check if VM is AD joined
$DomainJoined=((gwmi win32_computersystem).partofdomain);