Windows 365 is automatically deprovisioned after 30 days of inactivity.

We use VDI and noticed that many employees do not use them or never connect. We would like to configure it so that 30 days after the VDI workstation is not used it will automatically be deprovisioned

glebgreenspan 1,290 Reputation points

2024-04-08T13:50:19.6366667+00:00
Hello Kirill

Use PowerShell Script: Create a PowerShell script that queries the last login or activity timestamp of VDI workstations.

Example PowerShell script to retrieve last logon time for a specific user session on a VDI workstation:

powershellCopy code

$userName = "username" # Replace 'username' with the actual username of the VDI session $lastLogon = (Get-WmiObject -Class Win32_ComputerSystem -ComputerName .).UserName Write-Output "Last logon time for $userName: $lastLogon"

Step 2: Schedule Deprovisioning Task

Create Deprovisioning PowerShell Script: Develop a PowerShell script that deprovisions (terminates or deletes) inactive VDI workstations.

Example PowerShell script to deprovision an inactive VDI workstation:

powershellCopy code

$computerName = "VDI-ComputerName" # Replace 'VDI-ComputerName' with the name of the inactive VDI workstation # Command to deprovision the VDI workstation (e.g., using VMware Horizon View PowerCLI or equivalent) Disconnect-HVMSession -VMName $computerName -Confirm:$false

Schedule PowerShell Script Execution: Use Windows Task Scheduler to schedule the execution of the deprovisioning PowerShell script.

Open Task Scheduler on the VDI management server.

Create a new task with the following settings:

Trigger: Set the trigger to execute the task daily or periodically.

Action: Configure the action to run the PowerShell script (powershell.exe) with appropriate parameters to deprovision inactive VDI workstations.

Step 3: Implement Deprovisioning Logic

Define Inactivity Threshold: Determine the threshold (e.g., 30 days) after which a VDI workstation is considered inactive and eligible for deprovisioning.

Include Logic in PowerShell Script: Modify your PowerShell script to include logic that checks the last activity timestamp of VDI workstations and initiates deprovisioning for those that exceed the defined inactivity threshold.

Example logic in PowerShell script:

powershellCopy code

$inactiveThresholdDays = 30 # Retrieve last logon time for VDI workstations $lastLogonTime = Get-LastLogonTimeForVDIWorkstations # Compare last logon time with current date $inactiveWorkstations = $lastLogonTime | Where-Object { (Get-Date) - $_.LastLogonDate -gt $inactiveThresholdDays } # Deprovision inactive VDI workstations foreach ($workstation in $inactiveWorkstations) { Deprovision-VDIWorkstation -ComputerName $workstation.Name }

Use PowerShell Script: Create a PowerShell script that queries the last login or activity timestamp of VDI workstations.

Example PowerShell script to retrieve last logon time for a specific user session on a VDI workstation:

powershellCopy code

$userName = "username" # Replace 'username' with the actual username of the VDI session $lastLogon = (Get-WmiObject -Class Win32_ComputerSystem -ComputerName .).UserName Write-Output "Last logon time for $userName: $lastLogon"

Step 2: Schedule Deprovisioning Task

Create Deprovisioning PowerShell Script: Develop a PowerShell script that deprovisions (terminates or deletes) inactive VDI workstations.

Example PowerShell script to deprovision an inactive VDI workstation:

powershellCopy code

$computerName = "VDI-ComputerName" # Replace 'VDI-ComputerName' with the name of the inactive VDI workstation # Command to deprovision the VDI workstation (e.g., using VMware Horizon View PowerCLI or equivalent) Disconnect-HVMSession -VMName $computerName -Confirm:$false

Schedule PowerShell Script Execution: Use Windows Task Scheduler to schedule the execution of the deprovisioning PowerShell script.

Open Task Scheduler on the VDI management server.

Create a new task with the following settings:

Trigger: Set the trigger to execute the task daily or periodically.

Action: Configure the action to run the PowerShell script (powershell.exe) with appropriate parameters to deprovision inactive VDI workstations.

Step 3: Implement Deprovisioning Logic

Define Inactivity Threshold: Determine the threshold (e.g., 30 days) after which a VDI workstation is considered inactive and eligible for deprovisioning.

Include Logic in PowerShell Script: Modify your PowerShell script to include logic that checks the last activity timestamp of VDI workstations and initiates deprovisioning for those that exceed the defined inactivity threshold.

Example logic in PowerShell script:

powershellCopy code

$inactiveThresholdDays = 30 # Retrieve last logon time for VDI workstations $lastLogonTime = Get-LastLogonTimeForVDIWorkstations # Compare last logon time with current date $inactiveWorkstations = $lastLogonTime | Where-Object { (Get-Date) - $_.LastLogonDate -gt $inactiveThresholdDays } # Deprovision inactive VDI workstations foreach ($workstation in $inactiveWorkstations) { Deprovision-VDIWorkstation -ComputerName $workstation.Name }

1 answer

ZhoumingDuan-MSFT 8,060 Reputation points Microsoft Vendor

2024-04-09T02:01:33.7866667+00:00
@Кирилл Миронов,Thanks for posting in Q&A.

To automatically delete an Azure VDI machine when a user has not logged in for 30 days, you can use Azure Automation and a PowerShell script. Here are the high-level steps:

Create an Azure Automation account in your Azure subscription.

Create a new PowerShell runbook in the Azure Automation account.

Write a PowerShell script that checks the last login time for each user on the VDI machine and deletes the machine if no user has logged in for 30 days.

Schedule the PowerShell runbook to run on a regular basis (e.g., daily) using a recurring schedule in Azure Automation.

Here is an example PowerShell script that you can use as a starting point:

$vmName = "MyVDIMachine"

$daysToKeep = 30

$lastLogon = (Get-WmiObject -Class Win32_UserProfile -ComputerName $vmName | Select-Object -Property LastUseTime | Measure-Object -Property LastUseTime -Maximum).Maximum

$daysSinceLastLogon = (New-TimeSpan -Start $lastLogon).Days

if ($daysSinceLastLogon -gt $daysToKeep) {

Remove-AzVM -ResourceGroupName "MyResourceGroup" -Name $vmName -Force

}

This script uses the Get-WmiObject cmdlet to retrieve the last login time for each user on the VDI machine, calculates the number of days since the last login, and deletes the machine if no user has logged in for 30 days.

Note that you will need to modify the script to use the appropriate Azure PowerShell cmdlets for your environment and to specify the correct resource group and VM name.

Hope it will help.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
ZhoumingDuan-MSFT 8,060 Reputation points Microsoft Vendor

2024-04-11T07:42:37.22+00:00

@Кирилл Миронов,Hope things going well.

If there is any update, feel free to let us know.

ZhoumingDuan-MSFT 8,060 Reputation points Microsoft Vendor

2024-04-23T06:23:42.37+00:00

@Кирилл Миронов,Hope you have a nice day!

If the answer is helpful, please click "Accept Answer" and kindly upvote it to help others with the same problem as soon as possible.
Sign in to comment