Scan, Download, Deploy.... well what about copy to Workstation but don't deploy?

Scan, Download, Deploy.... well what about copy to Workstation but don't deploy?

My current patch setup is that I still manually kick off the Deployment stage on the weekends I choose. I have the Scan and Downloads running on an automated schedule.

As I understand what this means is that the server scans workstations, determines the patches necessary, and then downloads them to itself, then during the deploy mode, patches are actually copied to the workstation and then deployed.

In the interest of time(say when a workstation has been turned off for nights in a row for a month or so due to after hrs construction) it seems like I could have some time off when I have a huge update to do if there was an additional pre-staging stage after the Download that would copy the necessary patches needed to the workstations that needed them. Then when I kicked off deploy I'd really just be kicking off the installation of those patches as oppose to the copy of the patches to the workstation and THEN the installation.

Any thoughts or do I not have a full understanding of the patch management process?

                  New to ADSelfService Plus?