Maser Posted July 25, 2012 Report Share Posted July 25, 2012 Is there an official statement on this? Is the current 9.0.2 build (client and server) compatible with ML? - Steve Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 25, 2012 Report Share Posted July 25, 2012 This article lists the only issue we currently know about: http://kb.retrospect.com/articles/Retrospect_Article/Retrospect-9-0-and-earlier-with-Mountain-Lion/ Quote Link to comment Share on other sites More sharing options...
amkassir Posted July 26, 2012 Report Share Posted July 26, 2012 I look forward to hearing others' experiences with Retrospect 9.0.2 and Mountain Lion before I take the plunge. Hopefully Retrospect Inc. will update Retrospect to obviate the need to change security prefs. Is this a certificate issue with Gatekeeper? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 26, 2012 Report Share Posted July 26, 2012 Gatekeeper requires a new certificate, so all software developers who don't use the App store will need to release a new version with a new certificate. At least that is my understanding. We will add a new certificate in our next release. Quote Link to comment Share on other sites More sharing options...
dbiehler Posted July 26, 2012 Report Share Posted July 26, 2012 I upgraded to Mountain Lion and now the Retrospect Client 9.0.2 (102) will not turn on. Even changed the Security preferences and tried reloading the client. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 26, 2012 Report Share Posted July 26, 2012 Try to uninstall the re-install the Retrospect Client. You may also need to try to delete the retroclient.state file in library preferences. Quote Link to comment Share on other sites More sharing options...
Maser Posted July 26, 2012 Author Report Share Posted July 26, 2012 I upgraded to Mountain Lion and now the Retrospect Client 9.0.2 (102) will not turn on. Even changed the Security preferences and tried reloading the client. I have not seen this problem in the machines I've upgraded. If the client was on prior to the upgrade, it's been on after the upgrade finished... 1 Quote Link to comment Share on other sites More sharing options...
Maser Posted July 26, 2012 Author Report Share Posted July 26, 2012 Gatekeeper requires a new certificate, so all software developers who don't use the App store will need to release a new version with a new certificate. At least that is my understanding. We will add a new certificate in our next release. And, FWIW -- I did not have to modify GateKeeper settings to launch the 9.0.2 Console on my engine computer --it is currently set to "Mac App Store and identified developers". Which goes against what your KB article says. Am I missing something? Quote Link to comment Share on other sites More sharing options...
AntonRang Posted July 27, 2012 Report Share Posted July 27, 2012 And, FWIW -- I did not have to modify GateKeeper settings to launch the 9.0.2 Console on my engine computer --it is currently set to "Mac App Store and identified developers". Gatekeeper only applies to newly downloaded applications (technically, to applications which still have the quarantine attribute). So if you had Retrospect installed before Mountain Lion, and had run it at least once, you don’t need to change Gatekeeper settings. Actually, you probably could just control-click and choose “Open” — that will bypass Gatekeeper (after a confirmation dialog) without having to change the preference. 1 Quote Link to comment Share on other sites More sharing options...
dbiehler Posted July 27, 2012 Report Share Posted July 27, 2012 Try to uninstall the re-install the Retrospect Client. You may also need to try to delete the retroclient.state file in library preferences. Thanks, I did this and now it seems to be working again. Quote Link to comment Share on other sites More sharing options...
Maser Posted July 27, 2012 Author Report Share Posted July 27, 2012 So, I bounced my engine machine to 10.8. From what I can tell, all my backups -- including the few clients I updated to 10.8 -- are working. Seems pretty painless so far... Quote Link to comment Share on other sites More sharing options...
Glibbs Posted August 13, 2012 Report Share Posted August 13, 2012 Hi, there's a possibility that proactive backups will revert to the schedule in the script. I quite often re-shedule client backups to the early hours of the morning but after a system re-boot the schedules are reset to the last time the client was backed up plus the scripts 'backup sources every' setting. Quote Link to comment Share on other sites More sharing options...
Daniels Posted August 14, 2012 Report Share Posted August 14, 2012 I have found that if the client was installed before upgrading to Mountain Lion the security setting does not need to be changed. 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.