17.1.8 looks like a complete reinstall, is there a patchfile option?

At 1.44 GB, the 17.1.8 "update" looks like a complete reinstall, which is a drag to say the least. 16.1 had an end-of-year patchfile that I was able to script with to automate the updates. Is there the prospect of something like that this go-round?

Parents
  • 0

    Did you ever figure this out?  It looks like a complete reinstall for my server and all my workstations?  This is ridiculous.

  • 0 in reply to Jason Light

    Complete reinstall on server and 105 workstations, big PITA, and weird slowdown with My Assistant client included for free!

    The new feature that updating the server updates the content of the WinInst installation at least worked, but that meant no scripting to distribute the patch at all.

    40% of reinstalls failed for various reason, so a full install was required. I received no reports of the .DSK desktop configuration files changing, though, so there is that. 

    Also, with many installs, after the installation is complete and the workstation reboots, the user account used for the upgrade MUST login again to let the installer scripts complete, or the start menu will be empty for the normal user of the workstation. I use different administrative accounts for my helpdesk / workstation administration for delegation and accountability, and if a normal user logged back in first, BLAMMO! Wiped out the install. 

    Very weird update, but we can close the dang year so good enough.

Reply
  • 0 in reply to Jason Light

    Complete reinstall on server and 105 workstations, big PITA, and weird slowdown with My Assistant client included for free!

    The new feature that updating the server updates the content of the WinInst installation at least worked, but that meant no scripting to distribute the patch at all.

    40% of reinstalls failed for various reason, so a full install was required. I received no reports of the .DSK desktop configuration files changing, though, so there is that. 

    Also, with many installs, after the installation is complete and the workstation reboots, the user account used for the upgrade MUST login again to let the installer scripts complete, or the start menu will be empty for the normal user of the workstation. I use different administrative accounts for my helpdesk / workstation administration for delegation and accountability, and if a normal user logged back in first, BLAMMO! Wiped out the install. 

    Very weird update, but we can close the dang year so good enough.

Children