Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/03/2018 in all areas

  1. My testing so far suggests to me that during the upgrade from Windows 10 1709 (16299) to Windows 10 1803 (17134) some security settings related to Windows services are not being carried forward correctly. In the case of the Retrospect Client this is preventing it from correctly interacting with VSS for system volumes. The test machine I have 1803 installed on has two volumes — a system volume and a data volume. The system volume fails with the above error but the data volume completes without error. Initial comparison of some security permissions between a 1709 Client and the 1803 Client show some settings missing. However to be certain it is not something I changed in the past I'll need to do some more checking and do an 1803 clean install on something.
    1 point
  2. Oh well, #sigh I have a few Macs. All on WIFi All on DHCP They have to be this way, because they roam from office-to-office, client-to-client, home-to-work-to-home ... like laptops do. The error -530 and associated -519 has be around in almost every version of retrospect I have used for the past 20 years. I can never find the solution, apart from a full client reinstall, and I can not be doing that every week TBH! Is there ever going to be a stable answer? Each Mac, Client and Server has no firewall or anti-virus FYI. The fixed desktop Laptops that do not leave the office have no issues. The laptops returning to the office login automatically to the WIFI and have no network issues for everyday work; email, www, ftp, server shares, printing ... what so ever. Server: Mac OSX 10.11.6 Client: OSX 10.12.6 Retrospect 13.5 Please don't say 'upgrade to the latest version of Retrospect or I may have to slap you :-) That has never been an answer to this issue.
    1 point
×
×
  • Create New...