The TrialWorks 9.37a release has been available for about one week now. The majority of the changed focused on internal functions associated with the Outlook Plug-In for TrialWorks (using the new MSG functions). In addition, we have added a feature to streamline access to the TrialWorks Account Manager.
In regards to the TrialWorks/Outlook integration, 9.37 addresses several problems that affected ability to file certain types of messages. Primarily, errors that were caused by repeated opening and closing of previously filed e-mails (this item is locked error messages). In addition, it enahances the Public Folder to MSG Migration options with new procedures to verify the migration.
As far as the Account Manager is concerned, we have added a Help Menu item that automatically populates the firm's logon credentials. The Account Manager can be used to submit trouble tickets, view basic account information, and schedule/download upgrades.
//kj
Wednesday, October 3, 2007
Wednesday, September 5, 2007
Creating PDF's on Terminal Server
We have had various issues with utilizing Adobe Acrobat Professional on the terminal server when making documents from Word. The installed Adobe Pro uses a macro built into Microsoft Word to create the PDF file, but it has proven to be very unreliable. From a development standpoint, we are working on building an API (programming interface) into TrialWorks that will create PDFs without the need of Adobe; that project is in progress.
In the mean time, we installed PDFCreator on the hosting server to facilitate PDF creation. It works simply but effectively. If you want to use it, simply go to PRINT in any application and use the "PDFCreator" printer. A screen will come up asking you to author the file -- very easy very quick. The file can still be opened in Adobe.
The right-click "Send as PDF" option in TrialWorks will continue to have issues until we release the new PDF creating API in TrialWorks. Check out our regular blog for info on that (we'll post it as soon as we have it http://trialworks.blogspot.com.
/author KJ
In the mean time, we installed PDFCreator on the hosting server to facilitate PDF creation. It works simply but effectively. If you want to use it, simply go to PRINT in any application and use the "PDFCreator" printer. A screen will come up asking you to author the file -- very easy very quick. The file can still be opened in Adobe.
The right-click "Send as PDF" option in TrialWorks will continue to have issues until we release the new PDF creating API in TrialWorks. Check out our regular blog for info on that (we'll post it as soon as we have it http://trialworks.blogspot.com.
/author KJ
Friday, August 31, 2007
Speed issues at 10AM, 12PM, 2PM, 4PM EST
We had a customer report a slow down at the above mentioned times during our hosting system. Those slowdowns last under 15 minutes and happen repeatedly. Those times are selected for scheduled 120 minute incremental backups of the hosting environment.
We have a sophisticated system in place that not only allows us to backup frequently, it also allows us to restore in case of a massive failure quickly. In fact, a standard restore would take 24-48 hours, we can get it done in way under 120 minutes. Hopefully we never have to try it, but its good to know the system is protected.
Performance problems with this type of backup strategy are rare, but can happen when large amounts of data are being changed during the day - as we have seen. Given the new information we will adjust the backup routine to increase performance.
Next week we will address the issue in two stages to see which solution works best (unfortunately we need to do a little trial/error). First stage will be to up the frequency of the backups to once every 15 minutes, and see if doing more "smaller" backups works better than less "larger". If the system experiences lag we will shift in the opposite direction and do less backups alltogether, and schedule them when usge is not at its peak.
We appreciate your cooperation.
We have a sophisticated system in place that not only allows us to backup frequently, it also allows us to restore in case of a massive failure quickly. In fact, a standard restore would take 24-48 hours, we can get it done in way under 120 minutes. Hopefully we never have to try it, but its good to know the system is protected.
Performance problems with this type of backup strategy are rare, but can happen when large amounts of data are being changed during the day - as we have seen. Given the new information we will adjust the backup routine to increase performance.
Next week we will address the issue in two stages to see which solution works best (unfortunately we need to do a little trial/error). First stage will be to up the frequency of the backups to once every 15 minutes, and see if doing more "smaller" backups works better than less "larger". If the system experiences lag we will shift in the opposite direction and do less backups alltogether, and schedule them when usge is not at its peak.
We appreciate your cooperation.
Monday, August 13, 2007
Anti-Spam Measures on Hosted Exchange
As of 3 PM EST on 8/13/2007 we activated a new anti-spam system that is currently being evaluated. The evaluation period will be 14 days. A new folder called "Spam.cloudmark" is now part of every user's mailbox. We will be gathering statistics and information over the next 2 weeks to better understand where the spam is going.
Our Exchange Servers already do a high level of filtration that utilizes Reverse DNS lookup, SBL/XBL listings, and TrendMicro Client/Server/Messaging SMB Anti-Spam. Recently we've had many customers report that even with the levels of filtration set on High a large bulk of Spam is getting through.
Our Exchange Servers already do a high level of filtration that utilizes Reverse DNS lookup, SBL/XBL listings, and TrendMicro Client/Server/Messaging SMB Anti-Spam. Recently we've had many customers report that even with the levels of filtration set on High a large bulk of Spam is getting through.
Component Upgrade: Microsoft SQL Server 2000 to 2005 Upgrade.
As part of the ongoing effort to preserve system continuity and take advantage of new technologies, the TrialWorks Technical team will upgrade the Hosting environment to Microsoft SQL 2005. This change, primarily, is designed to take advantage of the data protection options offered by SQL Server. Users will experience moments of downtime during the maintenance window - currently scheduled for for Thursday Aug 16, 2007. The downtime is anticipated to last about 90 minutes and will be scheduled later this week.
The current plan is to facilitate an in-place upgrade of SQL, which means that users will not notice any changes and do not need to make any setting changes. After the upgrade the data protection (backup) system in place will be capable of restoring data closer to a point of failure.
To learn more about SQL Server: http://www.microsoft.com/sql/default.mspx .
The current plan is to facilitate an in-place upgrade of SQL, which means that users will not notice any changes and do not need to make any setting changes. After the upgrade the data protection (backup) system in place will be capable of restoring data closer to a point of failure.
To learn more about SQL Server: http://www.microsoft.com/sql/default.mspx .
Security Changes Affecting Microsoft SQL Server
Sunday night 8/12/2007 the system underwent routine security modifications which affected primary server accesss and major components during the maintenance window. All systems confirmed online shortly thereafter. Affected sysmts included:
- Microsoft SQL Server (TrialWorks databases).
- Microsoft Exchange
- BlackBerry Server
/posted by kj
Welcome to the TrialWorks Hosting Blog!
The TrialWorks Hosting Blog is desgined to speed up information syndication to our Hosting Customers. Any important information pertaining to the Hosted environment will be made available here first.
This blog is intended for infromation purposes only, provided "AS IS" with no warranties. TrialWorks.BlogSpot.Com, and all other blogs associated with TrialWorks, are operated using Blogger.com / Blogspot.com, all users must agree to their privacy policy located: http://www.trialworks.com/form_blog.htm. Lawex Corporation / TrialWorks / or the authors of this blog take no responsibility for the usage of the provided information. Any technical modifications should be tested/evaluated by your network administrators and only put into practice after complete understanding and testing. We recommend using http://www.microsoft.com and all of its resources for dealing with Microsoft applications. Technical information on this site is here only to inform of potential issues or new technologies. Warning: because the blog is hosted by blogspot, users browsing other blogs may be exposed to offensive or inapporopriate content. Blogspot/Blogger is not affiliated with Lawex Corporation. Use at your own risk.
This blog is intended for infromation purposes only, provided "AS IS" with no warranties. TrialWorks.BlogSpot.Com, and all other blogs associated with TrialWorks, are operated using Blogger.com / Blogspot.com, all users must agree to their privacy policy located: http://www.trialworks.com/form_blog.htm. Lawex Corporation / TrialWorks / or the authors of this blog take no responsibility for the usage of the provided information. Any technical modifications should be tested/evaluated by your network administrators and only put into practice after complete understanding and testing. We recommend using http://www.microsoft.com and all of its resources for dealing with Microsoft applications. Technical information on this site is here only to inform of potential issues or new technologies. Warning: because the blog is hosted by blogspot, users browsing other blogs may be exposed to offensive or inapporopriate content. Blogspot/Blogger is not affiliated with Lawex Corporation. Use at your own risk.
Subscribe to:
Posts (Atom)