PowerShell for Windows Deployment Services lacking and/or broken
Trying to automate the process of building boot image and installation image into WDS. It is nice to see some PowerShell commands, but there are still things that appear not to be possible to do with PowerShell and must resort to WDSutil. For example, I cannot find a cmdlet to create a new driver group. I have to issue the wdsutil command to create the driver group. I can then add all my drivers into the group using PowerShell, but then there does not appear to be a way to use PowerShell to filter the drivers by group to be applied to an image. So I figured I would loop through the drivers by using Get-WdsDriverPackage.
Get-WdsDriverPackage has a bug. The description of the cmdlet states "If you do not specify a name or ID, the cmdlet gets all driver packages in the store." It appears to work in groups of five. I have 26 drivers in my WDS store. When I issue a Get-WdsDriverPackage, it returns only the last one. If I delete the last one, it then returns only the last five. If I delete one of the last five, it returns only the last four. If I delete one of those last four, it returns only the last three. In other words it is returning the remainder of (total number of drivers/5), and if the remainder is 5, it returns 5. It makes it impossible to work through all the drivers that are loaded. And since I can't get all the drivers via PowerShell, I am back to trying it with wdsutil again.