MVP - Most Valuable Professional
rss

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft Technologies like Exchange, Office 365, Azure and Cloud Security.

The community script Copy-ReceiveConnector has been updated. Receive Connectors that do exist on a specified target server can now be updated.

Besides the receive connector communication the assigned permissions of the source connector can be copied as well.
 

Links

 


Are you unsure, if you should migrate to Office 365? You want to know more about security of cloud applications and services? Your Exchange Server infrastructure requires an upgrade? Contact me via email: thomas@mcsmemail.de

Read More »

Problem

When you use Symantec NetBackup 7.x you might encounter Error 5, when you try to restore an Exchange Server 2013 DAG mailbox database backup to a Recovery database or to the original datrabase.

The error message in Backup, Archive, and Restore Tool looks similar to this

Screenshot NetBackup Error 5

Enabling NetBackup debug logging by using the mklogdir.bat file located in C:\Program Files\Veritas\NetBackup\logs does not necessarily provide additional input. The restore job fails before entering the job section for local restore activities. So no TAR log is being created.

 

Solution

When following the NetBackup Admin Guide and several Symantec HowTo’s you have already configured the following two services to run using a dedicated Service Account

  • NetBackup Client Service
  • NetBackup Legacy Client Service

Screenshot NetBackup Legacy Network Service running with LocalSystem

There are some circumstances (not clearly defined by Symantec) when an additional NetBackup Service performs Exchange PowerShell commands as part of a restore process. Therefore the following NetBackup service must be configured to run using the same Service Account as the other two NetBackup services.

  • NetBackup Legacy Network Service

Screenshot NetBackup Legacy Network Service running with Service Account

In addition be aware that the Service Account required Debug permission on the Exchange Server. It might be helpful to propagate the permissions for the Service Account using a GPO.

  • Computer Configuration\Windows Settings\Security Settings\LocalPolicies
    • User Rights Assignment
      • Debug programs
      • Log on as a service
    • Restricted Groups
      • Administrators

Links

Read More »

Graphic Whitepaper: Improve Your Exchange Deployment by Learning from a Massive ScaleGiven Microsoft’s success in building Exchange Online running on its Office 365 cloud platform, it has undoubtedly learned a few valuable lessons that can be applied to on-premises deployments.

In this whitepaper, ENow board member and Microsoft Exchange MVP Tony Redmond reveals how standardization, automation and monitoring played into Microsoft’s success with scaling its platform.

Download the Whitepaper here: http://enowsoftware.com/whitepaper/Improve-Your-Exchange-Deployment-by-Learning-from-Massive-Scale.pdf

 

 

 

 

 


Are you unsure, if you should migrate to Office 365? You want to know more about security of cloud applications and services? Your Exchange Server infrastructure requires an upgrade? Contact me via email: thomas@mcsmemail.de

Read More »

A new community PowerShell script to simplify Exchange Server mailbox migrations has been published to TechNet Gallery and Github.

Features

  • Validate CSV file for required column EmailAddress prior to creating migration batch in Exchange
  • Automatic batch naming based on CSV file name
  • Common notification email address settings
  • Variable AutoComplete of batches
  • Common logging of script activities

See script help for examples.

Links

 


Checkout the professional services provided by Granikos for planning and migration your exisiting Exchange Server infrastructure to the cloud. Protect your cloud services using the CloudSOC™ technology provided by Elastica.

Read More »
On September 15, 2014
0 Comment
3110 Views

Exchange and other MTAs use DSNs (Delivery Status Notifications) and NDRs (Non Delivery Reports) to notify the sender or sending MTAs (Message Transfer Agents aka Mail Servers) about the varioius statuses of a given email message. In Exchange those messages are generated primarily by the categorizer component of the transport service.

You can use the New-SystemMessage cmdlet to create new messages. These messages can even be localized and can contain Html tags for properly styled notifications.

From a system perspective the various notifications used are named and fulfill a specific purpose.

Report and receipt types (Exchange Version independent) used for notification

  • Delivery Receipt (DR)

    Report confirming that a message was delivered to its intended recipient

  • Delivery Status Notification (DSN)
    Report describing the result of an attempt to deliver a message

  • Message disposition Notification (MDN)
    Report describing the status of a message after it has been successfully delivered to a recipient. Examples: read notification (RN) or non-read notification (NRN)
    Defined by RFC 2298 and controlled by Disposition-Notification-To header

  • Non-Delivery Report (NDR)
    Report indicating to the message sender that the message could not be delivered to the intended recipients

  • Non-Read Notification (NRN)
    Report indicating that a message was deleted before is was read, when a read receipt was requested

  • Out Of Office/Facility (OOF)
    Report indicating that the recipient will not respond to a new message
    OF referes to the Microsoft original term „out of facility

  • Read Notification (RN)
    Report indicating that a message was read

  • Recall Report (RR)
    Report indicating the status of a recall request for a specific recispient
    A recall request is used when a sender tries to recall a sent message by using Outlook

Links

 


This post has first been published in my personal legacy blog here.

Read More »