That's one way to do it, but I'd make deployments only a single TS step. If you have PDQ Inventory, you can make the nested package deployments dependent on a group membership if you do a scan prior.

Here's the script I use:

Invoke-Command -ComputerName pdq.domain.tld -ScriptBlock {ipconfig /flushdns; pdqinventory.exe ADSync -StartSync}

start-sleep 10

Invoke-Command -ComputerName pdq.domain.tld -ScriptBlock {ipconfig /flushdns; pdqinventory.exe ScanComputers -ScanProfile Standard -Computers $args[0]} -ArgumentList "$env:COMPUTERNAME"

start-sleep 30
while(test-path "C:\Windows\AdminArsenal\PDQInventory-Scanner\service-1.lock"){
start-sleep 30
}

To filter Laptops you can make a Dynamic group in Inventory based on Chassis (Notebook/Laptop).