tuntun 0 Posted November 21, 2013 Share Posted November 21, 2013 Version 5.0.2225.0 Added: Windows 8.1 compatibility Fixed: Increased login time for domain user's first login Fixed: User cannot access encrypted USB drive on Windows 7 Fixed: Rollback restores incorrect module architecture on Windows 7 64-bit Fixed: Wrong display of network path in GUI logs Fixed: Occasional crashing of Microsoft Outlook 2013 when sending a message on Windows 7 32-bit Fixed: Client logs sent multiple times to ESET Remote Administrator when the optimization button is pushed Fixed: Problem with automatic Send/Receive in Microsoft Outlook 2013 on Windows 7 Fixed: Quarantined files (false positives) are not restored to their original location with automatic restore after the update of virus signature database Fixed: Email plugin not integrated correctly on Windows Live Messenger 2012 on Windows 8 32-bit Fixed: Blue screen error (BSOD) after integration of Device Control on Windows XP SP2 and older Fixed: Occasional blocking of printers and Bluetooth without adding rules to Device control Fixed: Error when sending message with no sender address Fixed: Scanning of Microsoft Outlook messages with Symantec Enterprise Vault integrated causes the attachment icon to disappear Fixed: Microsoft Outlook crashes upon exit when connected to Kerio Mail Server via Kerio Outlook Connector v8 on Windows XP, Windows 7 Fixed: Issues mounting Elpro Libero PDF logger device Link to comment Share on other sites More sharing options...
jimwillsher 64 Posted November 22, 2013 Share Posted November 22, 2013 Hi I've tried to deploy this to five clients from five servers (ERAC "Remote Install" > "Upgrade Windows Client") and every one has returned "No upgrade for this client". The clients are all on 5.0.2126 or 5.0.2214. I'll raise a formal support ticket, but wanted to give a headsup here. Jim Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 944 Posted November 22, 2013 ESET Moderators Share Posted November 22, 2013 Hello, which version of ERAS do you have deployed? Link to comment Share on other sites More sharing options...
jimwillsher 64 Posted November 22, 2013 Share Posted November 22, 2013 Hi Peter I have 5.0.119. I have tried to upgrade ERAS to 5.1.34 on no less than FIVE servers and all do not detect 5.0.119. That was my first thought - upgrade ERAS/ERAC - but even that won't work. I've raised support tickets but the confirmation email helpfully gives no reference number. I've also posted details of the problem into the remote admin forum. Jim PS 120 clients across 5 servers - no way I'm doing it manually :-) Link to comment Share on other sites More sharing options...
jimwillsher 64 Posted November 22, 2013 Share Posted November 22, 2013 Upgrading to ERAS 5.1.34 solved it. The KB article for the ERAS upgrade is wrong so I cancelled it, but I should have proceeded as it worked okay. Link to comment Share on other sites More sharing options...
MietekN 2 Posted March 26, 2016 Share Posted March 26, 2016 The same problem with ERAS 5.3.33 and 5.1.34 and update Eset Endpoint Antivirus from version 5.0.2237 to version 5.0.2260: "No upgrade for this client" Link to comment Share on other sites More sharing options...
daveh 0 Posted March 28, 2016 Share Posted March 28, 2016 I have the same problem with ERAS 5.3.33 and the upgrade from version 5.0.2254 and 5.0.2260. All clients return "No upgrade for this client". Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted March 29, 2016 Administrators Share Posted March 29, 2016 Did you create an install package for both x86 and x64 platforms? Does creating a new package just for the particular platform make a difference? Also do the following: - stop the ERA service - delete the log "C:\ProgramData\ESET\ESET Remote Administrator\Server\logs\era.log" -start the ERA service - reproduce the error - stop the ERA service - rename the log - start the ERA service - supply me with the renamed log. Link to comment Share on other sites More sharing options...
MietekN 2 Posted March 30, 2016 Share Posted March 30, 2016 (edited) [2016-03-30 07:32:46.330] V2 [56f480e80000] [000014d0] <SESSION_USERACTION_INFO> ConsoleProcessRequest: C2S_CREATE_REMOTE_INSTALL_TASK, <ERA Server> user [Administrator] created remote install task for computer: ComputerName=work-comp1, PromaryServer=work-server, MACAddress=35a6d8180101, AlternativeIpString=192.168.001.201[2016-03-30 07:34:26.094] V2 [56f480e80000] [000014d0] <SESSION_USERACTION_INFO> ConsoleProcessRequest: C2S_SET_COMMAND_LINE, <ERA Server> user [Administrator] has set the commandline of package with Name=ESET Endpoint Antivirus 5.0.2260.1 x64 only to CommandLine=/qn REBOOT="ReallySuppress"[2016-03-30 07:34:52.766] V2 [56f480e80000] [000014d0] <SESSION_USERACTION_INFO> ConsoleProcessRequest: C2S_CREATE_REMOTE_INSTALL_TASK, <ERA Server> user [Administrator] created remote install task for computer: ComputerName=work-comp2, PromaryServer=work-server, MACAddress=b0831265e9a1, AlternativeIpString=192.168.001.202[2016-03-30 07:36:48.187] V2 [56fb65eca93d] [00001070] <RINSTALL_ERROR> HandleClientUpgrade failed, code 3, error code: 5, gle: 0[2016-03-30 07:37:29.679] V2 [56fb6619a948] [00001070] <RINSTALL_ERROR> HandleClientUpgrade failed, code 3, error code: 5, gle: 0 work-comp1 - intall package for both x86 and x64 work-comp2 - intall package for x64 only Edited March 30, 2016 by MietekN Link to comment Share on other sites More sharing options...
rockshox 5 Posted April 15, 2016 Share Posted April 15, 2016 FYI - We are experiencing the same issue trying to "Upgrade Client" from 5.0.2254 to 5.0.2260 using ERAS 5.3.33.0. The package was built with both x86 and x64 and confirmed the settings are identical to previous packages that were used to upgrade the clients to 5.0.2254. I am able to deploy the client using "Windows push" to a computer without ESET, however "Windows upgrade client" fails with "No upgrade for this client". [2016-04-15 08:03:21.461] V2 [570e1c4f0000] [00000f9c] <SESSION_USERACTION_INFO> ConsoleProcessRequest: C2S_CREATE_REMOTE_INSTALL_TASK, <ERA Server> user [Administrator] created remote install task for computer: ComputerName=xxxxx, PromaryServer=ServerName, MACAddress=xxxxxxxxxxxx, AlternativeIpString=xxx.xxx.xxx.103 [2016-04-15 08:04:54.038] V2 [5711031272c2] [00000e20] <RINSTALL_ERROR> HandleClientUpgrade failed, code 3, error code: 5, gle: 0 Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted April 15, 2016 Administrators Share Posted April 15, 2016 The "Upgrade client" task won't work for Endpoint v5.0.2260 due to a new signature that cannot be verified neither by ERA nor the existing Endpoint. Use push install instead. Link to comment Share on other sites More sharing options...
MietekN 2 Posted July 16, 2016 Share Posted July 16, 2016 (edited) ERAS 5.3.39.0 and "Upgrade Client" from 5.0.2260 to 5.0.2265 updates successful Edited July 16, 2016 by MietekN Link to comment Share on other sites More sharing options...
Recommended Posts