Over the years one of the biggest requests has been for two additional components to this software. The first request was to have the ability to restrict\/block an account on the server from being included in the automatic provision list<\/b>. The second request was to implement a way to synchronize passwords between ExchangeDefender and the remote Exchange server<\/b>. These requests have finally come to surface in our newest release of XDSYNC! <\/p>\n
![](\"https:\/\/www.exchangedefender.com\/images\/xdsyn2.png\")
<\/p>\n
Exclusion List<\/u><\/b> <\/p>\n
The exclusion list is very straight forward. Upon configuration of XDSYNC you will notice an additional tab within the software. This tab will be populated with the current list of mail users on the Exchange Server.<\/i> You simply check any accounts you wish for the software to ignore from the processing component and they will not be sent to Exchange Defender<\/a>. <\/p>\n Password Sync<\/u><\/b> <\/p>\n This process is currently being designed in a single direction<\/b> due to limitations within the Windows environment.<\/i> Initially it will not touch any existing users that existed before installation. The password change event will be triggered upon a password change request within ExchangeDefender<\/a>. <\/p>\n For Example:<\/u><\/b> <\/p>\n \u00b7 Either an admin or users changes the password on \u201ctest@yourdomain.com<\/b>\u201d. <\/p>\n \u00b7 This account is now flagged for \u201cPassword Sync<\/b>\u201d, if enabled. <\/p>\n \u00b7 The next time XDSYNC pings for changes, it will be included on the list. <\/p>\n \u00b7 The change gets processed and the password is updated on the Exchange server. <\/p>\n You may also notice from the screenshot we have included a \u201cNotifications\u201d<\/b> section. This will allow you to enable and configure a recipient to be notified each time an account is either added\/removed from <\/i>ExchangeDefender<\/i><\/a> via XDSYNC.<\/i> <\/p>\n We are very excited to release this new version as it takes advantage of many code advancements<\/i><\/b> and should operate at much higher level of performance than the previous version. Good news is that the new version is currently undergoing testing and should be released Friday of this week!<\/u><\/b> <\/p>\n Hank Newman […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-332","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/332","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=332"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/332\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
VP Development, ExchangeDefender
hank@ownwebnow.com <\/p>\n","protected":false},"excerpt":{"rendered":"