April 4, 2016
We’ve recently made some changes to the Invoice System to make things more clear and easier for our clients who bill their clients individually. We now have a csv generator for invoices. If you navigate to your company in the support portal then click on the Invoice tab you will find all of your invoices going back to when your services started with us.
Simply click on the csv next to a specific invoice it will generate a csv for your use that can be opened in Excel. It’s generated to group the categories of service types together.
This is a cleaner alternative to the old way of copying the invoice from the portal and pasting it into excel that we’ve seen some of our service providers do in the past. Now you can split, subdivide, categorize with ease. If you would like even greater control over individual accounts so they can always exist within their own company, provision accounts directly through your own Shockey Monkey portal.
If you have any questions regarding this feature email me at email@example.com
A major feature folks have been requesting from ExchangeDefender for a long time is better password policies. The first step in that direction is going to be having the ability to support password expiration. We have moved forward with this request as we realize the importance of forcing password changes on a security platform. One feature that was implemented recently that you guys might have seen pop up in your admin portal is domain Password Expiration.
If you navigate to a specific domain’s configuration you can see you now have the option to implement 30, 60, or 90 day password expiration for all the users on a domain. Initially when the feature is enabled it will tag all the current accounts on the domain / domain aliases, then depending on what option you selected 30,60,90 days out upon logging into the admin portal it’ll require the user’s to change their password before allowing any other functionality. Clients can be proactive about changing their password regularly and avoid the prompt by using the Password Change in their own settings after logging into the portal.
However, I think we know that that will not generally be the case. Once their password has expired upon logging into the Admin Portal they will be redirected to change their password before they will be allowed to login.
If you have any questions regarding this feature email me at firstname.lastname@example.org
February 10, 2015
Throughout the day we receive hundreds of requests for new services and existing account modifications. Luckily we automated this process from a very early stage and this helped to prevent 99% of account provisioning errors. Believe it or not, there was once a time where everything was processed manually!
However on occasion when there is a hiccup, then it’s simple a matter of locating the source of the issue. While issues on our end are rather easy to diagnose and fix, it’s not always as simple on the partner’s side. There can be a handful of issues that can arise if the account is not properly configured or contains an invalid parameter.
This is why we’ve implemented a well overdue feature integrated directly inside the service manager. If you select the drop down box next to any Hosted Exchange account, you will see a new option called “Check Configuration”.
After selecting this option you will be brought directly to the “Check Configuration” page. It will automatically populate the email address from the previous screen and run the initial check. Also keep in mind that you are able to test other accounts without leaving this page.
It will perform several checks including: Syntax, Server Location, Provisioning, MX Record, Autodiscover and validates that the account is protected by ExchangeDefender. In the event an issue arises you have the option to either “Email” or “Open Ticket” which will automatically include the onscreen results.
We believe that solving the issue promptly makes for a better long term relationship. So if there are any features or adjustments we can make to help smooth the transaction between you and your clients, don’t hesitate to let us know! Our support staff eagerly awaits the opportunity to speak with you about how we can continue to improve our process!
September 2, 2014
Over the past few months I’ve taken the time to update several different aspects of our product offerings. The updates and products we decided to implement were prioritized based on bugs & feature requests that had been submitted properly through our internal support portal.
First on the list was our Outlook 2010 & 2013 SMTP Security Add-in, which also applies to the desktop agent. We’ve added several new features, improved performance and fixed a few bugs. Listed below are the enhancements we’ve added based on user feedback.
- Added the ability to view & manage alias accounts.
- Added the ability to disable automatic refresh.
- Added a direct link to the user’s web portal.
- Fixed a link causing quick links to not work properly.
- Added version numbers to the settings page.
- Updated the “Dismiss All” label to “Review All”.
- Window size & state are now persistent between restarts.
- Added the ability to resize the window.
- Added the ability to resize columns.
- SPAM counts are now listed next to the addresses.
- Right click menu has been added.
- We’ve added the ability to trust an entire domain.
- Updated Documentation
- Updated Publisher Information
We’ve also went through an updated most of the online documentation since we’ve undergone such dramatic changes throughout the years. New images have replaced old instructional images, revised steps and procedures for various platforms and even structured the documents to allow for easy navigation. You can find all of the updated documentation here: http://www.exchangedefender.com/documentation.php
Several core internal programs have also been updated to allow our highly trained support staff to escalate and speed up response time for some of our more complex requests. One area of improvement has been geared towards Compliance Archive and simplifying the process to retrieve an export of a user’s mailbox.
We’re currently working on bringing several enhancements to LocalCloud. We’ve had several clients report issues with client stability. So we are working on a performance update, which will also allow for automatic updates in the future. We are also working on enhancing the Web Sharing file uploading service, by enhancing the upload controls and server-side timeouts.
August 14, 2014
Here at ExchangeDefender we have a wide range of products and service offerings. With close to seven years with ExchangeDefender, I’ve designed and written a majority of the software that is offered as a part of continuously growing platform. This includes several of our key systems such as: Encryption, Compliance Archive, Web Sharing, LocalCloud and even our service ordering & account provisioning! The only areas that I don’t touch directly are mobile applications, we have additional developers who designs and tackles any issues that may arise on our mobile platforms.
Throughout the course of the day I find myself working on various bugs and communicating with our team to ensure that bugs and new feature requests are considered and placed within our internal development pipeline. Recently I’ve been going through our old documentation and working on updating that with fresh information detailing step, by step how to use our products.
Keep in mind that it takes a while to develop and test fixes to assure they don’t introduce other problems. There are no quick fixes or features, everything we implement needs to work well across web, desktop and mobile devices and our support staff needs to be trained and alerted of these upcoming features. So if you have a bug or feature request that is absolutely something that we must fix and/or implement, we would love to hear about it! However, due to my schedule and workload I’m typically a very hard person to reach. So first open a ticket in our portal, our highly trained technicians will review your ticket and possibly collect further information. After which, they will then escalate the ticket into a bug or feature request. Once in this section, it will be reviewed every Friday to see just how we can make our services even better!
Here at ExchangeDefender we want to help you fill your services portfolio with everything your client needs to operate their business successfully. We strive every day to be the absolute best for all of your service needs. So please (I cannot stress this enough) if you think we are falling short due to a software glitch or missing feature, let us know!
July 16, 2014
Today we’ve published an update to the Outlook 2010, 2013 and Desktop Client SMTP Security application. This update addresses several bugs, performance issues and even a few feature requests!
- We’ve added the ability to view and manage alias accounts. (See Figure 1)
- An issue where the submission of multiple spam messages at once has been fixed.
- Messages submitted as SPAM are now sent to the “Junk” folder.
- Fixed several performance issues relating to “Hanging” or “Freezing”.
- We’ve fixed the issue that was causing the “Add-In” tab to be renamed.
- We’ve added the ability to disable the automatic refresh cycle. (See Figure 2)
- Fixed an issue that was causing compliance messages to not populate.
- Fixed an issue that caused the quick links to not work correctly. (See Figure 3)
If you currently have the add-in installed, simply close and re-launch outlook. If you had our most recent version previously, the add-in should automatically update. However, if you notice that an automatic update did not occur, simply uninstall the old version and obtain the latest version.
Figure 1 – Ability to view and manage alias accounts.
You alias accounts will populate in this list in the order of the main account, then followed by domain and users alphabetically.
Figure 2 – Ability to disable automatic refresh intervals.
You now have the option to disable the automatic synchronization.
Figure 3 – Fixed an issue that caused the quick links to not work correctly.
Clicking this link will sign you into your web management console automatically!
August 16, 2013
We’ve released an update to the desktop version of ExchangeDefender LocalCloud. We’ve spent a few days sifting through bugs reported via (The bug section) @ support.ownwebnow.com for ExchangeDefender LocalCloud and those are the ones we focused on and fixed. Listed below are the hand full of bugs that were isolated and corrected. You can find the most recent version (v1.2), here.
· Fixed an issue that would cause the application to crash upon launch.
o This issue was caused by invalid .ICO files being supplied for branding. Even though it explicitly states that you must provide .ICO files for the Product Icon:, we had users uploading (jpg, gif, png) files.
· Fixed an issue that would prevent files from being deleted from the cloud upon request.
· Fixed an issue that would cause the application to continuously download/synchronize files.
While out team was busy correcting the issues reported for the desktop version of LocalCloud, we finalized our initial Web Version of the file sharing software. The web interface is a slightly trimmed down version of the Desktop Software, for what should be obvious reasons.
The Web Interface Offers, (Fully Integrated – into the admin.exchangedefender.com (USER) control panel.) the ability to view, download and upload files to your personal /shared LocalCloud accounts.
The accounts you have access to will be located in the left panel and their content is located to the right. You can easily transverse through the file structures to either upload or download a desired file. Complete with real time file upload & download status and located at the bottom of the screen is your storage quota. Now you can view & access your files from virtually anywhere.
September 7, 2012
This blog post is a follow up to Hosted Exchange Outbound Suspensions posted on June 20th, 2012.
Yesterday we began to roll out a custom transport agent on our Hosted Exchange network to perform automated monitoring of sent message counts for each user. The first phase of this roll out is to collect analytics and fine tune our threshold values.
Starting Monday, September 10th 2012 all hosted exchange users will be monitored for threshold breaches of outgoing (external) messages against a “Short time” and a “Daily” threshold value.
Monitor length: 15 minutes
Value: 100 messages
Monitor length: 24 hours
Any user who breaches threshold during the analytics period will receive a courtesy email to warn them about their threshold breach against our current threshold values. Once the analytics period ends (Estimated for the end of September 2012) we will send warning messages once the user is near 80% of the threshold and then an automated suspension will be issued once threshold is breached.
VP, Network Operations, ExchangeDefender
(877) 546-0316 x757
April 19, 2012
Here at ExchangeDefender, we have finally resolved the issue with our Outlook 2007 SMTP Security add-in. This project has been a thorn in our side for quite some time and I’m proud to announce that our development team has finally got it working! We spent the good part of the week going over and over Outlook 2007 & 2010 documentation and implementation methods for Outlook controls. After hours and hours of troubleshooting and testing new scenarios we’ve finally got all the pieces to fit together correctly. I’ll briefly describe the development cycle of this project, to help enlighten those who think bugs/feature requests get brushed aside and forgotten about.
Our original Outlook 2007 add-in was created years ago and was at a time where Outlook add-ins weren’t really supported NATIVELY. So part of the conflict was restructuring our code to take advantage of the native Office 2010 hooks, since they are backwards compatible for 2007. We had to phase out all of our old methods that had a heavy dependence on a 3rd party Outlook .dll called (Redemption). That was our first hurdle.
Then we found out while everything would compile without any conflict, the add-in still wouldn’t load correctly inside of the Outlook application. So we went back to the drawing board and examined what was happening on a lower level. To our surprise, the compiler (Visual Studio 2010) kept replacing the Outlook 2007 included references with the newest 2010 files. This was completely unexpected and unwarranted behavior in comparison to what we were expecting. So to keep things on par, we moved the development environment to a virtual machine running Windows XP, Office 2007 & Visual Studio 2010. This resolved the conflict of Visual Studio fetching incorrect .dll files and replacing them at compile time.
Perfect right? Everything should work…
Nope, the next issue was the worst! The add-in would not load and didn’t generate any errors…
A developer’s worst nightmare: Trying to figure out what’s wrong with absolutely nothing to formulate a reason for the failure. We’ll apparently there was a slight conflict between the old way of handling the .manifest file and loading the ribbon controls. So after we tweaked the registry controls and load behaviors, we then rewrote some of the ribbon controls to support the newest version of VSTO. That’s when things started to work!!!
So, as you should be able to conclude, it was no walk in the park. We would have loved to get this working a very long time ago, but at the time we simply didn’t have the time or resources to address the issue directly.
VP Development, ExchangeDefender
March 16, 2012
This week our development team here at Shockey Monkey has finished the SOAP Callback framework and has published this new release to all portals. This new framework enables you to configure automatic code level responses when certain conditions are triggered. Current the only supported triggered events are related to tickets (create, update, close). Over the course of this year we will expand the available list of triggerable events as demand for them increases.
The most elegant design feature of this entire framework is the dynamic interface structure that allows virtually any SOAP interface to communicate with our software. Let me briefly walk you through the process for configuring the callback mechanism.
Settings -> Callback
The first time you visit this page, it will seem fairly empty but these two fields you should notice at the top. Simply provide the remote SOAP WSDL location and press “Validate”.
Now, the system will examine the URL and fetch any valid methods that exist inside of the requested module. You should notice the section below; it will become populated with new fields.
You should now see that you have three sections.
One for (Create Ticket, Update Ticket, and Close Ticket).
Select a method from the dropdown list. You will notice these are all valid methods from the request API that we defined above in the previous step.
Once you have selected a method from the dropdown list, you will notice additional (parameter) fields. These fields are loaded dynamically depending on the parameters available in the provided SOAP API.
Note: One thing to keep in mind is complex types. If your method requires complex parameter types such as (arrays, objects, etc.) they will not be supported at this time. Basic types like (strings and integers), should be used mostly for parameter types.
The text box next to each listed textbox is where you will enter the desired value for this parameter. If you would like your method to use TICKET variables (“which is most likely”), they are provided in the dropdown menu to the right of the text field. Click the list and select the desired variable and it will prefill that variable into the text field to the left.
Also keep in mind each trigger is optional. You don’t have to assign a method for every section, only the ones you want to use. After you have finished assigning each of your methods and their corresponding parameters, click “Save”.
That’s it, callbacks are now enabled and you should begin to see the results!
VP Development, ExchangeDefender
Older Posts »