11:42:58:833 1172 d2c Handler :: END :: Handler: Command Line Install Return code = 0x00000002, Result = Failed, Reboot required = false 11:42:58:817 1172 d2c Handler : WARNING: Command line install completed. 11:42:53:357 1172 d2c Handler :: START :: Handler: Command Line Install Here's the entry from WindowsUpdate.log on my Win7 test VM.Īgent * Title = Notepad++ v6.5.3 (Upgrade) Once again I tried to deploy 6.5.3 upgrade and it failed again. So I went back and published and deployed the 6.5.2 upgrade to one of my test VMs and it worked just fine.
Figured it was a long shot but thought maybe it wasn't happy about me skipping versions.
Thinking something could be wrong with my downloaded installer file I tried manually upgrading a machine by running the npp.6.5.3.Installer.exe directly. Figured I'd just jump right to 6.5.3 so I published and deployed the 6.5.3 upgrade, but it failed to install on all machines. Once again manually downloaded the npp.6.5.2.Installer.exe and npp.6.5.3.Installer.exe files. Early January I noticed 6.5.2 and 6.5.3 had been released. I successfully published and deployed the v6.5.1 upgrade package to all machines that needed it. The Notepad++ home site is blocked by our firewall so I manually downloaded the npp.6.5.1.Installer.exe installation package from a DMZ workstation. Back in early December 2013 I started managing the few Notepad++ installs we have around here with Patch Manager.
0 kommentar(er)
