Sage 100

 View Only
  • 1.  Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 05:55
    Does anyone have the full version of FRx 6.7? Client's backup that had originals also hit by CryptoBlocker. We have all of the registration info.


  • 2.  RE: Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 06:00
    https://www.dropbox.com/s/ofg4bi40g15o6vn/FRX%206.7.8.zip?dl=0


  • 3.  RE: Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 06:01
    Then SP 11 https://www.dropbox.com/s/5gzlrdyvgwhcmza/FRx67011027.exe?dl=0


  • 4.  RE: Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 06:02
    And from there you have to wade through several potential issues depending upon system configuration - register MSXML, etc. Be sure you do everything with an admin / run as admin. Don't fall for ""oh we made you what we think is an admin"" ...


  • 5.  RE: Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 06:42
    BTW, on this note, there is some new technology coming down the pike to detect a ransomeware attack and shut it down before it becomes too extensive. Our OEM we use for our disaster recovery solution is embedding something similar into the technology so it sounds like there may be hope on the horizon. http://www.bbc.com/news/technology-36772461


  • 6.  RE: Does anyone have the full version of FRx 6.7? Cli

    Posted 10-28-2016 06:46
    Because even if you have an excellent disaster recovery system, typically they are 'snapshotting' hourly. However, you could get hit with ransomeware say at 2:10pm. But someone may not open a file that got encrypted for a few hours later. Plus, ransomeware can take hours to do its deed, it's not instant as it has to read all the files, encrypt them and write them back. That's alot of CPU and network traffic. Then when people can't open one of the files, they may think its just the file, or 'I'll call IT in the morning'. Long and short, it could be 3+ hours of work being done in the organization before somebody realizes what's really happening. Then calls a tech, they get there etc. Remote people may not have a clue and continue doing their work. So now your disaster recovery system comes into play, and you do a restore from 2pm which is when your tech figured out was the last good backup. Say you have 50 employees and they worked for 4 hours after the attack. 50*4 is 200 manhours. Say an average loaded cost of $50/hour and wham, you just lost $10,000 bucks