> One other thing that also still concerns me is the new licensing > scheme. It seems like this might have been one of the issues, any while > you might be confident that it is working fine now and is supportable, I > really want to know how it works from a flow-chart perspective. For > instance, I don't want to run into issues during an outage where I am > recovering from a backup onto a different server only to find that > things aren't working because of some licensing mechanism. I know that > this might trip Windows Server 2003 to require re-register with them, > but it will work for 30 days without that. I have no idea if Declude > needs to be immediately re-registered, how you might choose to block > such things, and otherwise what ever else I might have to look out for > such as server outages on your end. A recent experience of my own with > BackupExec doubled the time of an outage because of a simple default > setting in their software that didn't allow me to catalog imported > backup media properly without changing. Something as simple as that is > such a big deal that I decided that I can no longer trust BackupExec as > a disaster recovery solution since this is definitely not the only quirk > that I have come across and I don't have the time to be any more > proactive in identifying these things ahead of time. I also really, > really hope that you created a backdoor registration work-around so that > in the event of something happening to Declude that this information > could be distributed in order for us to continue using the software. > Even TiVo is reported to have a backdoor that is closely held and so far > secure that they can distribute to keep their units from becoming > completely useless without the required updates (otherwise they could > only be used to play previously recorded content).
FYI, while I was one of the ones having licensing issues, I will clearly state that the software kept working, with the exception of what I called 2.0_releaseB, which apparently had a major bug. That means that even though the Declude license check was having problems, declude.exe was still firing and processing mail. In fact, I will state something here: On one of the servers I actively work on, I went by knowledge that the SA was up to date, in that it should have been renewed in September of last year. I went and installed versions 2.0.x on there and it was working, even though the license was not verifying. In working with Declude on the problem, Barry gave me a call to let me know that there was no SA for that server. Turns out the SA was renewed, but the person that did it put down different information and it did not match. That has now been corrected. Anyway, point is as far as Declude was concerned at the time, there was no SA and no legal way version 2.0.x should have been used on that server, yet it was working. In other words, the program will work, but Declude will actively know that something is running that should not be and they can take action. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
