Will exiting Batchpatch continue the remote process?

[TheCaptain]

Hi everyone,

New here, my name is Rick and I’m an IT admin. We total about 500 people (~260 users spread over 8 sites in the Netherlands). Since management is still undecided on if they want mobile/flex workplaces, we are holding onto HP thinclients and about 140 of them are still Windows 7 models.

I’m trying to secure them as best as I can, and part of that is getting them uptodate as much as possible. Since HP Device Management has limited possibilities I stumbled onto Batchpatch and am currently running the evaluation version and do consider a purchase. So far I managed to remotely uninstall Flash Player on a few clients, 4 at a time. I have also made a batchscript that lets the client set up a networkdrive to a share, runs a bunch of Windows KB updates and then removes the network drive again which is going great, almost…

Now all those Windows 7 thinclients are identical in both hardware and software, though some are at our head office and some at our other company sites across the country. Regardless of location, some thinclients take really really long to run the Windows updates. Since there isn’t a progress indicator I was wondering if the update process will continue on the client when I close Batchpatch? Or does the remote installation process get cancelled when I close batchpatch?

Thanks in advance

[doug]

So, you’re executing a remote script that calls some KB .MSU files directly… Yes, in most cases if you close BatchPatch, the remote script execution that you describe will continue, but I can’t make any guarantees.

[TheCaptain]

Basically I give Batchpatch the local admin credentials for the clients. I then push a batchfile to the client that maps a network drive using the ‘pushd’ command. Once the drive is mapped the script executes the .cab files that are on the network drive using ‘dism /Online /Add-Package /PackagePath:”path\filename.cab”. And then remove the network mapping again with the ‘popd’ command.

[doug]

I would expect the script to generally continue executing on the target computer in that case even if you were to close BatchPatch, but it’s certainly something that you can just test and see what happens.

[Author]

Posts