ashleycsse.uwa.edu.au Posted September 2, 2009 Report Share Posted September 2, 2009 Well we have Retrospect 7.6 Server and we got some new Windows 7 (Final MSDN release) clients. But as soon as I try to add the retrospect clients to the retrospect server. I get "Sorry couldn't add backup client, error -560 (invalid private/public key)" I don't have this problem with any other clients including WinXP, Mac OSX 10.4 / 10.5 nor some Windows Server 2003. It seems its only on Windows 7. I noticed that there were earlier post about this ie http://forums.dantz.com/showtopic.php?tid/27581/ Which basically mentions Copying the "pubkey.dat" of the server and put it on the client. But none of the two Retrospect Server even has this file. So does the latest Retrospect 7 client offically support Windows 7 or its still in the works? Client -> Windows 7 (MSDN Official) -> Running 7.6.106 Client Server -> Windows 2003 Server -> Running Multi Server 7.6.123 with driver 7.6.2.101 hotfix Quote Link to comment Share on other sites More sharing options...
Mayoff Posted September 2, 2009 Report Share Posted September 2, 2009 Retrospect 7.6 does not fully support Windows 7. A new release is planned to address all known issues. Did you try to uninstall and Reinstall the Retrospect client? Quote Link to comment Share on other sites More sharing options...
ashleycsse.uwa.edu.au Posted September 3, 2009 Author Report Share Posted September 3, 2009 I've just taken another look at it and yes the problem persist on another fresh machine with Windows 7 with "Sorry couldn't add backup client, error -560 (invalid private/public key)" Funny thing is that I tried it on a Retrospect 7.5.387, it gets further ie asking for a password but fails the password check. The Next version, will it be an incremental upgrade or do we have to purchase an upgrade. Quote Link to comment Share on other sites More sharing options...
TimRice Posted February 26, 2010 Report Share Posted February 26, 2010 Retrospect 7.7 Server still exhibits the same problem described above. I've tested my client installs on WinXP clients and it works fine there. When I TEST to my Win7 device, it finds and identifies the client, but when I try to ADD the client, it gives me the "Sorry, couldn't add backup client, error -560 (invalid private/public key). Anyone have any suggestions? Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted February 26, 2010 Report Share Posted February 26, 2010 Do you have 'Automatically add clients' set in your Preferences / Clients > Adding area? I've seen a simular thing with this enabled, but once you copy over the key to the client it seems to work fine. Ideally you need this file to be copied by some network script to automate the installation process. Rich Quote Link to comment Share on other sites More sharing options...
TimRice Posted February 26, 2010 Report Share Posted February 26, 2010 I do have "Automatically Add" enabled. It seems that the Public Key didn't copy in when the client was installed on Windows 7. Where should it go? Quote Link to comment Share on other sites More sharing options...
mwilliamson Posted February 26, 2010 Report Share Posted February 26, 2010 When I've seen that error I just "forgot" the client from the list, uninstalled the client, reinstalled the client, and readded the client....and it seems to work. I was backing up Windows 7 for a while on RS7.6....am now on RS7.7 and can't backup much of anything. If you are using the Documents and Settings selector be sure to add "or path matches pattern C:\Users" to the spec. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted March 1, 2010 Report Share Posted March 1, 2010 You need to grab the key from c:\document...\all users..\retrospect...\ ...and copy it to your Retrospect directory on the client. I can't recall if you have to reinstall the client again before it'll be picked up - I don't think so. Overall, the client install experience is very clunky, especially if you need to upgrade from 7.6 to 7.7 or want to do a network install (due to the script.msi file being required, which can't be automated without breaking things). Richard Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.