
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 12:59 PM
Hello,
I am creating a package that upgrade the bios of computers.
Everything is fine until the reboot. Indeed, i have to reboot the computer to apply changes.
The problem is that when the computers are rebooting, the link between LanSweeper Server and the computer is disconected, so i can only see the red line "Shutting down Access is denied." on my deployment's logs.
Is it possible to avoid it?
Moreover, ideally, i would like to check the bios version after reboot.
Thank you for your time!
I am creating a package that upgrade the bios of computers.
Everything is fine until the reboot. Indeed, i have to reboot the computer to apply changes.
The problem is that when the computers are rebooting, the link between LanSweeper Server and the computer is disconected, so i can only see the red line "Shutting down Access is denied." on my deployment's logs.
Is it possible to avoid it?
Moreover, ideally, i would like to check the bios version after reboot.
Thank you for your time!
Labels:
- Labels:
-
General Discussion
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-19-2017 07:55 PM
The only way to avoid it would be to make sure that the last step of the package is run before the computer reboots.
I assume that not further action is required after the reboot for the update to complete. If so, the best thing would be to create a second deployment package with the remaining steps.
For checking the BIOS version, you could create a report based on the table tblBIOS. This contains the version of the bios too. Just make sure to fully rescan your assets after a deployment or change the item scan time as mentioned here: https://www.lansweeper.com/kb/115/managing-how-often-specific-data-is-scanned.html
I assume that not further action is required after the reboot for the update to complete. If so, the best thing would be to create a second deployment package with the remaining steps.
For checking the BIOS version, you could create a report based on the table tblBIOS. This contains the version of the bios too. Just make sure to fully rescan your assets after a deployment or change the item scan time as mentioned here: https://www.lansweeper.com/kb/115/managing-how-often-specific-data-is-scanned.html
