We use this functionality to add helpful scripts for our Desktop Techs to run if needed in OOBE if they encounter issues during Autopilot or Provisioning. Here is an example of that the installs the 'Autopilot Diagnostics Community' script. We typ...

Application Workspace only supports 256 bit Certificates. The AW will fail to read 384 bit Certificates (with the log showing an unsupported Certificate type error). The Banking industry is moving to 384 bit Certificates as the default and Recast ...

On Azure Virtual Desktop (AVD), but also RDS, Citrix and VDI solutions, we would like to disable the Distribution and Installation of packages by users. This will create problems with inconsistent Cloud machines where on AVD machine 1 say AutoCAD ...

Native support for universal agent for Windows ARM64

On the “Skip” action, add the ability to skip, but not it mark successful. Currently, if you use this action and skip, it marks the Action Set as successful. What would be nice is the ability to not mark it successful so that it can be run again.

At this time, it is not possible to create drive mappings using the drive letters A, B, or C . While I understand this restriction may be in place due to historical conventions or system-level reservations, I believe the application should not enf...

Having the default set to Windows Pro Retail probably covers 80-90% of deployments, but for the rest it would be great to see the OA3 data queried so that techs do not necessarily have to touch the OS Edition drop down menu and therefore reduce th...

Liquit Agent uninstall does not completely remove the Liquit Agent from the machine. Please add an option to completely remove all files and certificates created by Liquit when performing an uninstall.

At large companies they many times use vitual environments. We also see extending application testing periods, for example more the 2 months. To be able to test the new application version, we need to be able to deploy a Acceptance environment nex...

I am trying to "validate" that Deploy-OSDCloud was "Successful". The problem is, i don't have anything to key off that tells you its ok to reboot. I thought looking for a string in the X:\windows\temp\osdcloud-logs\transcript.log would do it, but ...