今回は Exchange Server 2010 から 2016 へユーザーを移行した環境で開封通知のメールを件名で仕分けする際に仕分けルールが動作しない事象についてご紹介いたします。
 
事象
Exchange Server 2010 から Exchange Server 2016 へ移行後、開封通知のメールに対する Outlook の仕分けルールが正常に動作しなくなった。

・適用していたルールの条件：件名に “開封” を含むメール
・Outlook より手動で仕分けルールを再実行すると、正常に仕分けされる。
 
原因
トランスポート サービスで配信処理が行われる際に、件名が Outlook 上で表示される “開封: 〇〇〇” ではなく、“Read: 〇〇〇” として処理されることが原因で発生します。
以下は、”テストメール” という件名のメールに対する開封通知がトランスポート サービスによって処理される際の追跡ログの例となります。

例) 追跡ログ 抜粋
————————————
2017-06-20T11:29:04.653Z,172.30.35.18,MBX02,,MBX01.***.com,”MDB:***, Mailbox:***, Event:10018369, MessageClass:REPORT.IPM.Note.IPNRN, CreationTime:2017-06-20T11:29:03.788Z, ClientType:MOMT, SubmissionAssistant:MailboxTransportSubmissionEmailAssistant”,,STOREDRIVER,SUBMIT,,,***,User02@***.com,,,1,,,Read: テストメール,User01@***.com
————————————

上記のような開封通知に対する追跡ログは、お客様環境におきましても以下のコマンドから確認することができます。

Get-MailboxServer | Get-MessageTrackingLog -MessageSubject “Read:”

実行結果)
[PS] C:Windowssystem32>Get-MailboxServer | Get-MessageTrackingLog -MessageSubject “Read:”
EventId Source Sender Recipients MessageSubject
——- —— —— ———- ————–
HAREC… SMTP user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
RECEIVE STORE… user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
SUBMIT STORE… user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
DELIVER STORE… user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
HARED… SMTP user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
RECEIVE SMTP user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
AGENT… AGENT user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10
SEND SMTP user10@tailspintoys.com {Administrator@tailspintoys.com} Read: 01test to user10

※ 上記ではテストメールとして “01test to user10” に対する開封通知を設定していましたので、“Read: 01test to user10” という開封通知が出力されます。
 
Exchange Server 2010 では、トランスポート サービスで仕分けルールが適用される前に、件名の接頭語を示すプロパティである PR_SUBJECT_PREFIX の “Read:” が日本語の “開封:” に置換して処理していましたが、Exchange Server 2013 以降ではこの処理工程が変更されており、トランスポート サービスで仕分けルールが適用された後に “Read:” と “開封:” の置換が行われるため、仕分けルールとして件名に “開封” を含むことを条件としている場合、開封通知を仕分けることができません。
 
対処策
Outlook の仕分けルール (メールボックスの InboxRule) の条件として「開封」と「Read」の両方を条件として設定することで回避できます。

弊社製品の仕様変更により、仕分けルールによる振り分けを実施している皆様にはご不便をおかけする事となりますが、改めて仕分けルールの内容をご確認いただき、必要に応じて上述の [対処策] として記載の対処をご実施いただければと思います。

なお、上記の仕様変更はExchange Server 2013 より行われており、Exchange Server 2013 環境でも発生しますので併せてご確認ください。
 
※本情報の内容（添付文書、リンク先などを含む）は、作成日時点でのものであり、予告なく変更される場合があります。

Aktion Mensch und Microsoft haben mit den #neueNähe-Hackathons eine Plattform geschaffen, in der sich Expertenteams aus verschiedenen Kreisen an Anwendungsideen rund um das Thema Inklusion, Teilhabe und Barrierefreiheit versuchen können. Nach dem erfolgreichen Auftakt 2016 in Berlin freue ich mich auch am kommenden Wochenende (30. Juni – 2. Juli 2017) in Erlangen dabei zu sein.

Diese #neueNähe-Initiative kommt genau zur rechten Zeit, denn es findet unter dem Titel „Deep Learning“ gerade eine regelrechte Revolution des Umgangs von Menschen mit Computern und umgekehrt statt. Dies wird auch erheblichen Einfluss auf die Entwicklung von Mensch-Maschine-Schnittstellen im Allgemeinen aber eben auch Inklusionsangeboten im Besonderen haben.

Beim ersten Hackathon letztes Jahr in Berlin waren bereits etliche Ideen vertreten, die sich explizit maschinellen Lernens bedient haben, um zum Beispiel Bildinhalte zu analysieren oder Sprache zu verstehen.

Eine moderne Interpretation von Mimik und Gestik

Maschinelles Lernen ermöglicht es Computern mit Hilfe neuer Algorithmen und entsprechender Sensorik, typisch menschliche Alltagssituationen zu Interpretieren und Hilfestellungen anzubieten. Dies kann zum Beispiel das Verstehen der menschlichen Sprache und der Intention hinter einer Äußerung, deren Übersetzung oder aber das Interpretieren von Mimik und Gestik sein.

In diese Richtung ging auch das Projekt vom Team Metrilus beim Hackathon 2016 in Berlin: Wir haben eine Software geschrieben, die Personen detektiert und versucht, an deren Mimik und Stimme den emotionalen Zustand der Personen zu bestimmen. Dies soll Menschen in Gesprächen helfen, die von sich aus mit der Erkennung von Emotionen Schwierigkeiten haben. Diese Anwendung verwendet als Sensor eine Microsoft Kinect-Kamera. Die liefert neben einem konventionellen Farbbild auch 3D-Informationen, anhand derer Personen detektiert werden können. Zudem kann über das Mikrofon auch Sprache zu verschriftlichen. Diese Daten verwenden wir, um die Gesichter zu extrahieren und an die Emotion API der Microsoft Cognitive Services zu schicken. Der Text wird vom Tone Analyzer der IBM Watson API analysiert.

Wer Erfahrung mit Programmierung hat, kann sich das Projekt hier herunterladen und selber ausprobieren. Natürlich ist auch jeder herzlich eingeladen, zur Weiterentwicklung beizutragen.

Deep-Learning ist für alle gemacht

Das ist nur ein Beispiel der vielen Möglichkeiten, die Deep Learning-Anwendungen bieten. Und das Beste dabei ist, dass diese Möglichkeiten nicht nur einigen wenigen großen Firmen vorbehalten sind: Praktisch alle großen Cloud-Anbieter stellen Dienste bereit, mit denen jeder mit Grundkenntnissen in Programmierung seine Ideen ausprobieren kann, ohne selbst einen Algorithmus entwickeln zu müssen.  Und das ist für experimentelle Zwecke meist gratis. Eine gute Gelegenheit zum Ausprobieren ist zum Beispiel der nächste #NeueNähe-Hackathon vom 30. Juni bis 2. Juli 2017 in Erlangen – sehen wir uns dort? Du kannst dich jetzt hier anmelden.

Ein Gastbeitrag von Michael Balda
Geschäftsführer der Metrilus GmbH, Erlangen

Windows As a Service…

Windows 10 propose un nouveau modèle aux organisations pour déployer et mettre à niveau Windows, en fournissant des mises à jour des fonctionnalités par le biais d’un processus continu.

Généralement, de nouvelles versions de Windows sont publiées à quelques années d’intervalle. Le déploiement de ces nouvelles versions au sein d’une organisation devient un projet, reposant soit sur un processus de réinitialisation et chargement pour déployer la nouvelle version de système d’exploitation sur les ordinateurs existants, soit sur la migration vers la nouvelle version de système d’exploitation dans le cadre d’un cycle de remplacement de matériel. Dans les deux cas, les organisations investissent du temps et des efforts considérables pour effectuer les tâches requises.

Avec Windows 10, un nouveau modèle est adopté. Plutôt que d’ajouter de nouvelles fonctionnalités uniquement avec l’adoption de nouvelles versions à  quelques années d’intervalle, l’objectif est de fournir de nouvelles fonctionnalités deux à  trois fois par an, en intégrant en continu de nouvelles fonctionnalités tout en assurant un niveau élevé de compatibilité matérielle et applicative. Ce nouveau modèle, appelé Windows As A Service, invite les organisations à  repenser leur mode de déploiement et de mise à niveau de Windows. Il ne s’agit plus d’un projet qui intervient à  quelques années d’intervalle, mais d’un processus continu.

L’article complet ici :

https://technet.microsoft.com/library/mt574263(v=vs.85).aspx

N’oubliez pas, c’est le Windows que vous connaissez, mais en mieux !

Guide-utilisateur-Windows-10-Janvier-2017

Today’s tip…

The Server Management Tools (SMT) preview service will be discontinued on June 30, 2017.

For more information, check out the below blog post by Samuel Li.

Reference: “SMT preview service is being retired on June 30, 2017″ – https://blogs.technet.microsoft.com/servermanagement/2017/05/17/smt-preview-service-is-being-retired-on-june-30-2017/

Introduction:

After a successful rollout of Microsoft Teams using the assets and resources in Success with Teams, it’s now time to start thinking about the amazing capabilities in the tool that enables the online service to be a platform from which organizations can build impactful solutions that drives the organization towards a specific business outcome or goal. As a result, organizations using Microsoft Teams can transform not only how business is conducted, but other areas of the business can also be influenced by this technology, such as:

• Employees’ productivity as a result of streamlined business processes, thus impacting morale
• Recruitment of future employees
• Reduction in tools needed on a daily basis
• Better collaboration among workers that span multiple floors, buildings, cities, and countries.
• Single pane of glass for project teams to collaborate, store and organize information
• Faster response to internal and external customers, increasing satisfaction
• Many more!

Microsoft Teams, already has built-in capabilities that enable a fantastic collaborative experience using chat, SharePoint and other Office 365 features. When Apps, Connectors, Extensions and Bots within Microsoft Teams are added to that experience, the end user benefits tremendously.

The journey starts with the Overview of Microsoft Teams Developer Platform and Introducing the Microsoft Teams Developer Platform, to understand the differences between Tabs, Connectors, Extensions, Bots and Apps within Microsoft Teams and better understand the types of solutions that can be created:

Tabs: Easily pin Tabs to a Microsoft Teams channel, to quickly collaborate on a document, visibility to a PowerBI dashboard, Microsoft Planner, a team Business Review deck in PowerPoint, or take shared notes in OneNote. Tabs can be scoped for an entire team to view and collaborate on, or for an individual to have their own personalized view. For more information see Getting started with tabs for Microsoft Teams.

An excellent resource to help you with generating ideas for building Tabs in Microsoft Teams is Build a great tab for your Microsoft Teams app.

Figure 1: Example Tabs in Microsoft Teams

Bots: Interactive intelligent bots can assist end-users within Microsoft Teams to accomplish a task, faster and more efficient by automating the way that task is performed. This can be a bot that feeds in help desk tickets to a Microsoft Teams channel, querying information from an external system or simply asking for help. Bots created using the Microsoft Bot Framework is an excellent way to integrate a bot across Office 365, Cortana, Microsoft Teams, Skype for Business, etc. For an understanding of bots in Microsoft Teams, review Custom Bots and  Getting Started with Bots for Microsoft Teams. Another interesting development capability that pertains to bots is Notifying your users through the activity feed. This is exciting because personal messages can be sent to the feed to notify a user on the activity of your custom application.

To aid you in your understanding of Bots for Microsoft Teams, check out the Channel9 vide Build a great bot for your Microsoft Teams app

Figure 2: Example “T-Bot” in Microsoft Teams

Extensions: Insert content from a web service into a chat in Microsoft Teams, see Extensions for more information. What makes this really interesting is “Compose Extensions”. A Compose Extension allows you to insert content into the conversation window when sending a message to an individual or team. This content can range from  reports, media content, workflows, etc. Check out Build a compose extension for your Microsoft Teams app video on Channel9 for more in-depth information.

Figure 3: Example Compose Extension

Connectors: Connectors allow you to input information (or content) into Microsoft Teams and notify a team channel. The sources can be an web application or service such as RSS feed, Trello, Wunderlist, Yammer, Twitter or GitHub or a custom application that you wrote. For more information see Connectors. A very exciting capability is leveraging the Microsoft Flow connector with Microsoft Teams to automate tasks and activities. For more information see Introducing the Microsoft Teams connector for Flow. In addition, Microsoft has provided example Flow templates for Microsoft Teams

Figure 4: Example Connectors in Microsoft Teams.

Apps: Apps within Microsoft Teams enable users to access applications individually or for an entire team, to boost collaboration or productivity. Examples include web bots, data visualization tools, help desk engagement, etc. Check out the Channel 9 vide Notify your users through your Microsoft Teams app for more information.

Figure 5: Example of Discovering Apps in Microsoft Teams

My Favorite Examples of using Microsoft Teams to Transform:

Developer:

• An interesting and often popular use case of Microsoft Teams is within developer organizations to provide integration of developer tools within a single pane of glass, and never have to leave the service.  By doing so, developers  can streamline their daily tasks such as management of backlogs, closing bugs, run sample code within a tab, integration with GitHub, quality assurance, product roadmaps, integration with Visual Studio, etc.  For more information, check out the Channel 9 video (12 mins): Microsoft Teams Developer Tool Integrations

Education:

• Microsoft Teams can be used in the education environment to provide assignments to students, persistent conversations within different channels for discussing class projects or homework assignments with peers, and integration with other Office products such as OneNote Class Notebooks and even having ad-hoc video calls between students and faculty. What’s more is this can be done from any device, anywhere at anytime enabling flexibility. For more information, see the following blog post by Sam MNeill “Microsoft Teams for Education is Here – And It Is Awesome” and Microsoft Teams in Education.

Other Great Examples:

• Dun & Bradstreet powers data driven insight in Microsoft Teams and Excel

“Learn how D&B is empowering business-critical decisions by making information on more than 270M businesses available in Microsoft Teams, and through the D&B Business Solutions app in Excel.”

• Sapho connects legacy systems with Microsoft Teams

“Microsoft Teams is new and exciting, however it is not obvious how to connect in legacy on-premises systems. In this Tech Talk, we will show how Sapho detects events in legacy systems including SAP ERP and Oracle EBS and turns the events into actionable cards in Microsoft Teams, as well as how users can query those systems with bot questions.”

Wrap Up:

Now that you have an idea of how to get started developing for Microsoft Teams, the next step is to develop your book of dreams and determine what business challenges exist within your organization and brainstorm how a solution using Microsoft Teams can help to mitigate that challenge, or at the very least make life easier. Sound off in the comments below on your ideas and how you are developing for Microsoft Teams!

Heading to Microsoft Inspire? Here’s four ways to connect with other MSPs. 

With Microsoft Inspire just under two weeks away, now’s the perfect time to explore ways to meet and connect with other MSPs during the conference. Here are four key networking opportunities to add to your plans.

Visit the MSP Guide to Microsoft Inspire–our curated list of sessions and events you won’t want to miss–to see the full agenda.

1. Attend the MSP Networking Event

Monday, 7-10pm, at the Fig & Olive Restaurant
The Microsoft MSP team is hosting a networking reception and you’re invited. This acclaimed Mediterranean restaurant  is the perfect environment to spend an evening networking with other service provider partners and the Microsoft Managed Service Provider team. We look forward to your attendance. Note that spaces are limited, so please RSVP right away.
RSVP to Attend

2. Visit the MSP Booth

Microsoft Partner Experience in the Commons at the Convention Center
open Monday – Wednesday, 11am-6pm

Join us at the Microsoft Partner Experience booth for interactive conversations, connections, informative presentations and valuable customer and partner stories. This will be the place to connect with subject matter experts from both Microsoft and the partner ecosystem to learn about the Managed Service Partner opportunity and gain valuable resources.

3. Set up Connect Meetings

Quickly and easily set up meetings with attending Managed Service Provider leaders. Use the MyInspire event planning tool to set up Connect meetings with fellow partners and Microsoft employees. Visit the MSP guide to start planning your visit!

4. Attend the keynote

Empowering digital transformation with hosting and managed service providers
Tuesday, 1 – 2pm, Room 201
Speaker: Aziz Benmalek

In this session hear from Microsoft VP of WW Cloud & Hosting Service Providers on how Microsoft with its partners are empowering digital transformation with customers.
Wishing you a successful visit to Microsoft Inspire,
– The Microsoft MSP team

As it has in previous years, Morocco suspended its daylight saving time (DST) period for the observation of the Muslim month of Ramadan. On May 21, 2017, clocks turned back at 03:00 to 02:00 to end DST observation.

On July 2, clocks will be set ahead at 02:00 to 03:00 to resume DST observation. DST observance in Morocco will end as scheduled on October 29, 2017 at 03:00. To ensure this transition takes place correctly, we recommend customers install this update. More details about this update can be found here.

This update also addresses the change announced by the government of Haiti to start observing DST again. DST in Haiti is scheduled to end on November 5, 2017 at 02:00.

Windows 10 customers should ensure they have the latest updates installed. Details of this can be found here.

As customers discover the upcoming Access Apps retirement, some of the first questions are:

   – Are we using Access Apps?

  – How many Access Apps do we have?

  – Where are these Access Apps?

With the recent release of the Access App scanner, you are now able to easily get inventory and usage information for the Access Apps in your SharePoint Online tenant.

Go to http://aka.ms/sppnp-accessappscanner and follow the steps within the Quick start guide to get started!

Walking through the steps within the quick start guide, I noticed the PowerShell directions within the section Scanning SharePoint Online MT environment are a bit obscure.

Here are some more detailed steps:

• Launch Windows PowerShell from you Start menu
• Change the current directory to the folder location where you downloaded/extracted the AccessAppScanner.exe
  •  If you extracted the scanner to C:ToolsAccessAppScanner.exe, then change directory to the Tools folder

CD C:Tools

• When running the script itself, you need to include “.” at the beginning of the script so the example provided in the quick start guide should look like this:

                 .accessappscanner -t <tenant> -c <clientid> -s <clientsecret>

Exchange 2013 CU17 has been released to the Microsoft download centre!  Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one.  Exchange 2013 SP1 was in effect CU4, and CU17 is the thirteenth post SP1 release.

This is build 15.00.1320.004 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu17.exe.  Which is a great improvement over the initial CUs that all had the same file name!  Details for the release are contained in KB 4012114.

Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post.  There may be additional RBAC definitions, so PrepareAD should be executed prior to installing CU17.  If setup detects that PrepareAD is required it should be automatically executed if the account running setup has the necessary permissions.  This was an issue first discussed in the MessageCopyForSentAsEnabled  post and in Unexpected Exchange AD Object Values.

.NET Framework 4.7 is not supported at the time of writing.

No Exchange 2010 updates were released today since Exchange 2010 is in extended support.  Updates will be released as per the extended support lifecycle policy.

Exchange 2007 is no longer supported, updates are not provided once a product has exited out of extended support.

Updates Of Particular Note

CU17 contains the latest time zone updates.

As announced in the Exchange CU16 release post the .NET framework requirement has changed.  Exchange 2013 CU16 onwards require .NET framework 4.6.2.  Please see Exchange 2013 CU16 and Exchange 2016 CU5 .NET Framework Requirement for more details.

Issues Resolved

KB4024652 Repeated IMAP SEARCH BODY requests may not return newly delivered messages in Exchange Server

KB4024651 The “MessageRetrievalMimeFormat” setting isn’t honored for plain text-only email messages in IMAP in Exchange Server

KB4024650 Emoji is displayed as question marks in iOS clients in an Exchange Server environment

KB4024647 “The property is too long” error when you update the “Department” field of user mailbox in Exchange Server 2013

KB4024646 “Insufficient access rights” error when you run setup.exe as member of “Delegated Setup” group in Exchange Server 2013

Some Items For Consideration

As with previous CUs, this one also follows the new servicing paradigm which was previously discussed on the blog.  The CU package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation.  You do not need to install Cumulative Update 4 or 5 for Exchange Server 2013 when you are installing the latest CU.  Cumulative Updates are well, cumulative.  What else can I say…

For customers with a hybrid Exchange deployment, must keep their on-premises Exchange servers updated to the latest update or the one immediately prior ( N or N-1).

After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2013. If you uninstall this cumulative update package, Exchange 2013 is removed from the server.

• Test the CU in a lab which is representative of your environment
• Review this post to also factor in AD preparation which is to be done ahead of installing the CU onto the first Exchange server
• Follow your organisation’s change management process, and factor the approval time into your change request
• Provide appropriate notifications as per your process.  This may be to IT teams, or to end users.
• Place the server into SCOM maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
• Place the server into Exchange maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
• I personally like to restart prior to installing CU.  This helps identifies if an issue was due to the CU or happened in this prior restart, and also completes any pending file rename operations.  3rd party AV products are often guilty of this
• Restart the server after installing the CU
• Ensure that all the relevant services are running
• Ensure that event logs are clean, with no errors
• Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, backup, mobility and management services
• Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter
• Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.  See KB981474
• Disable file system antivirus prior to installing.  Do this through the appropriate console.  Typically this will be a central admin console, not the local machine
• Verify file system antivirus is actually disabled
• Once server has been restarted, re-enable file system antivirus
• Note that customised configuration files are overwritten on installation.  Make sure you have any changes fully documented!
• While CU17 does not add any new AD Schema changes.  If you are on an out-dated CU currently, then deploying CU17 may contain AD Schema updates for your organisation – please test and plan accordingly!  Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post.  Additional RBAC definitions may also be required.

Please enjoy the update responsibly!

What do I mean by that?  Well, you need to ensure that you are fully informed about the caveats with the CU  and are aware of all of the changes that it will make within your environment.  Additionally you will need to test the CU your lab which is representative of your production environment.

Cheers,

Rhoderick

Recently resolved a case with a Windows 7 – 10 IPU issue that I wrote a help document internally with the help of Frank Rojas but has now been posted publicly (https://support.microsoft.com/en-us/help/4020149/updates-fix-in-place-upgrade-to-windows-10-version-1607-problem) Additional details about it can be found below.

ISSUE

When upgrading Windows 7 to 10 via SCCM with the integrated Operating System Upgrade task sequence using the Windows 10 1607 Enterprise media.  We are continuously running into the error of 0xC1900208 which is flagged as a compatibility error on the workstation.  However, using the same exact media loaded onto a thumb drive or network share, I receive no compatibility errors.

SMSTS.log shows these entries:

02-16-2017 10:04:55.970    OSDUpgradeWindows    4940 (0x134c)    Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.

02-16-2017 10:04:55.970    OSDUpgradeWindows    4940 (0x134c)    Failing this task sequence step

NOTICE THAT setupact.log stops abruptly at:

02-27-2017 13:14:23.000    CONX       Windows::Compat::Appraiser::WicaApplicationInventory::GetInventory (263):   Starting Application Inventory.

02-27-2017 13:14:23.000    CONX       Windows::Compat::Appraiser::DriverInventory::GetInventory (204):   Starting Driver Inventory.

CAUSE

Windows 10 1607 known issue

RESOLUTION/WORKAROUND

Apply compatibility update for upgrading to Windows 10 Version 1607: January 10, 2017 or later

https://support.microsoft.com/en-us/help/3211309/compatibility-update-for-upgrading-to-windows-10-version-1607-january-10,-2017

The hotfix description is a bit generic and unfortunately does not describe the issues it corrects, including this issue. Also this hotfix is implemented a bit different than your standard hotfix. Please take the following steps to apply the hotfix:

1)     Download the hotfix from https://www.catalog.update.microsoft.com/Search.aspx?q=3211309

2)     After downloading the CAB file, extract its contents.

3)     Determine the source directory of your Windows 10 1607 installation files. You can find this in the properties of the Upgrade Operating System Package

4)     After determining the source directory, copy the contents of the extracted CAB file into the Source folder of the Windows 10 1607 installation files. Click yes to overwrite any existing files

5)     Update the DPs for the Upgrade Operating System Package

6)     Once the DPs have been updated, retry the deployments and see if the issue is corrected

MORE INFORMATION:

NOTE: KB 3211309 has been superseded twice by KB4013420 on March 14, 2017 which was later superseded by KB4016654 on April 11, 2017

https://support.microsoft.com/en-us/help/4013420/compatibility-update-for-upgrading-to-windows-10-version-1607-and-windows-server-2016-march-14-2017

https://support.microsoft.com/en-us/help/4016654/compatibilityupdateforupgradingtowindows10version1607andwindowsserver2016april11,2017

~Kevin Lee

Support Escalation Engineer | Microsoft System Center Configuration Manager

Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights.

ISSUE

When deploying Windows 7 OSD – drivers are randomly not applying . Some workstations fails at application of different drivers (USB/video/NIC)

smsts.log
Current OS version is 10.0.15063.0
..
OS version is 6.1 ( OS system file version found to be 6.1.7601.23572 )
..
Executing command line: "X:windowssystem32dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:_SMSTaskSequencePkgMgrTempdrivers.xml" /logpath:"C:_SMSTaskSequencePkgMgrTempdism.log"
Process completed with exit code 2147500037
uExitCode == 0, HRESULT=80004005 (e:nts_sccm_releasesmsclientosdeploymentosddriverclientsysprepdriverinstaller.cpp,548)
Dism failed with return code -2147467259
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:nts_sccm_releasesmsclientosdeploymentosddriverclientsysprepdriverinstaller.cpp,658)
Failed to add driver to driver store. Code 0x80004005
InstallDriver( pDriver->getContent()->getContentId(), sSource, 0 ), HRESULT=80004005 (e:nts_sccm_releasesmsclientosdeploymentosddriverclientdriverinstaller.cpp,622)


dism.log
Failed to load offline schema.dat hive from '\?C:Windowssystem32smistoreMachineschema.dat' into registry key '{abc123-ab12-1234-ab12-abc12345678}C:/Windows/system32/smi/store/Machine/schema.dat'. [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
Failed to load SMI schema hive [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
Unloading offline registry hive: {abc123-ab12-1234-ab12-abc12345678}C:/Windows/System32/config/SOFTWARE
Failed to unload offline registry: {abc123-ab12-1234-ab12-abc12345678}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
...
DISM Package Manager: PID=1812 Failed initializing the session - CDISMPackageManager::RefreshInstanceAndLock(hr:0x80070020)
DISM Package Manager: PID=1812 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x80070020)
DISM Provider Store: PID=1812 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070020)
DISM Provider Store: PID=1812 Failed to Load the provider: C:_SMSTaskSequencePkgMgrTempabc123-ab12-1234-ab12-abc12345678CbsProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070020)

RESOLUTION

3 Workarounds can be found on the System Center blog by Frank Rojas

In my customer’s case, he used workaround 2 and was pleased with the result.

Workaround 2 does not use the Apply Driver Package at all. Instead it uses the Download Package Content task to first download the Driver Package to a specified directory and then using more or less the same command line from Workaround 1, it installs the drivers. This workaround also resolves the problem by only having to initiate one registry load/unload during the DISM driver injection process. Since the Download Package Content task is only available with ConfigMgr Current Branch, this workaround cannot be used with older versions of ConfigMgr (ConfigMgr 2012 SP2/R2 SP1 or ConfigMgr 2007).

https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2016/12/28/apply-driver-package-task-fails-when-the-adk-is-upgrade-to-adk-10-1607/

~Kevin Lee

Support Escalation Engineer | Microsoft System Center Configuration Manager

Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights.

(この記事は2017  年 6 月 20 日にMicrosoft Partner Network blog に掲載された記事 How to Lead the Talent Transformation の翻訳です。最新情報についてはリンク元のページをご参照ください。)

7 月 9 ～ 13 日に米国ワシントン D.C. で開催される Microsoft Inspire (英語) にて、私は「クラウドが実現するデジタル トランスフォーメーション (英語)」と題したセッションを行います。今日のデジタル トランスフォーメーションは、新たなソリューションを開発する才能をいかに伸ばせるかにかかっています。だれもが知っていることですが、クラウドの巨大なビジネス チャンスを妨げる最大の課題の 1 つは、スキルの不足です。そしてまた、チャンスが拡大するにつれ、必要とされるスキルや能力のレベルは高まる一方となっています。

MDC Research が実施した 2016 年マイクロソフト クラウド プラクティス開発スタディによると、回答者の 21% が「最も苦労した点はスキルのある人材を見つけて採用すること」と答えています。そうした課題を抱えているパートナー様に朗報です。Azure の技術を向上させることができる、これまでにない新しい学習方法があります。また、すばらしいオプションも 2 種類ご用意しています。無料の Massively Open Online Courses (MOOC) と、人気の高い Azure 認定資格です。

MOOC が高く評価されている理由

マイクロソフトの MOOC では、無料のオンライン コースで提供される徹底した教材プログラム、動画、実習ラボ、試験を通じて、必要なスキルに焦点を当てて学習することができます。1 つのコースは 4 ～ 18 時間で、場所を問わずどこからでも受講でき、自分のペースで進められます。どのコースでも修了すればデジタル修了証が発行されます。これは、プロフェッショナル向けの SNS で公開することが可能です。

コース数は、このプログラムが開始された 7 か月前から約 3 倍に増えています。現在、MOOC を通じて Azure のトレーニングを行ったことのあるユーザーは 88,000 人を越え、受講されたコースは述べ 150,000 コースに上ります。パートナー様がこのコースをこれほどまでに高く評価している理由は、必要なスキルに特化したコースのラインナップと、選択の柔軟性にあります。MOOC では、特定のプロジェクトに合わせてトレーニングを行ったり、必要に応じて大人数の社員で受講したりすることができるのです。

「MOOC は、大人数の社員が Azure の基礎知識を身に付けることができるすばらしいオプションです。MOOC なら、世界各地に散らばる社員が各自のペースでトレーニングを受けられます。Azure の使用経験がある開発者も、プロジェクトで必要となる特定のトピックや個人の興味に基づいて、コースを選択できます」

– Wipro Ltd.、プラクティス マネージャー、Avijit Das 氏

新しいコース

私が以前こちらの記事 (英語) を投稿した後に新設されたコースをご紹介しましょう。以下のコースなどです。

• Architecting Microsoft Azure Solutions (英語)
• Securing Data in Azure and SQL Server (英語)
• Getting Started with Azure App Service: Web Apps (英語)
• Developing IoT Solutions with Azure IoT (英語)

また、近日公開予定のコースには次のようなものがあります。

• Recovering Data in Azure and SQL Server
• Azure Stack Operations
• Azure Stack Deployment
• DevOps for Databases
• Mobile DevOps
• Developing Big Data Solutions with Azure Machine Learning
• Building Your Azure Toolkit
• Managing Organizational Data Sources with Azure Data Catalog

Azure MCP 試験の割引キャンペーンが間もなく終了

認定資格には、どれだけの価値があるのでしょうか。MDC Research の調査によると、新規採用の際に何を最も重視するかというアンケートで、「技能資格の有無」は「職歴」「組織風土との相性」「経験年数」についで 4 位でした。つまり、マイクロソフト認定プロフェッショナル (MCP) の資格を取得すれば、開発者としての評価に差を付けることができます。マイクロソフトでは、皆様にこの資格を取得していただけるように、Azure に焦点を当てた MCP 試験のトレーニング プランを特別価格でご提供してまいりました。ただし、割引期間が間もなく終了となります。MCP 試験割引キャンペーンは 6 月 30 日までですので、どうぞお早めにご利用ください!

7 月 1 日に日付が変わるまでに試験バウチャーを購入しておけば、受験するのは後日でも構いません。Azure Single Pack の試験バウチャーは購入日から 3 か月間、Azure Triple Pack の試験バウチャーは購入日から 6 か月間有効です。また、このパックには不合格時の再受験と模擬試験が含まれています。

MCP 試験対策の詳しいアドバイスについては、よく視聴されている動画「マイクロソフト認定資格試験対策マスター (英語)」や、Microsoft Virtual Academy で公開されている以下のような Azure 試験対策セッションをご覧ください。

• Implementing Microsoft Azure Infrastructure Solutions (英語)
• Designing and Implementing Big Data Analytics Solutions (英語)
• Designing and Implementing Cloud Data Platform Solutions (英語)
• Developing Microsoft Azure Solutions (英語)
• Architecting Microsoft Azure Solutions (英語)

MOOC のトレーニングを受けたことはありますか。マイクロソフトでは受講経験がある皆様からのご感想をお待ちしております。

Over on Channel9 the OEMTV team have posted three videos on hybrid cloud, targeting different sized customers.

(Part 1) Hybrid Cloud for Small Businesses

In this first video in a three part series on Hybrid Cloud, we will define what hybrid cloud is as well as thoroughly examine the value of hybrid cloud solutions over fully on premise or fully cloud based scenarios. This video will provide a highly detailed examination of how small business customers can take advantage of hybrid cloud today.

(Part 2) Hybrid Cloud for Medium Sized Businesses

In this second video in a three part series on Hybrid Cloud, we will explore the value and efficiencies of hybrid cloud vs. fully on premise or fully cloud based scenarios. You will learn how to free up capacity in your datacenter for high demand and high critical workloads, build out state of the art low cost test environments, deploy apps to multi site locations easier and improve overall security through a balanced hybrid cloud approach.

(Part 3) Hybrid Cloud for Enterprise Businesses

In this last video in a three part series on Hybrid Cloud, we will explore the value and efficiencies of hybrid cloud vs. fully on premise or fully cloud based scenarios for enterprise customers. Gain insights into how to increase developer productivity, SQL Server efficiency and peak network performance while reducing overall costs.

Exchange 2016 CU6 has been released to the Microsoft download centre!  Exchange 2016 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2016 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 has the same servicing methodology.

This is build 15.01.1034.026 of Exchange 2016 and the update is helpfully named ExchangeServer2016-x64-CU6.iso which allows us to easily identify the update.  Details for the release are contained in KB 4012108.

.NET Framework 4.7 is not supported at the time of writing.

No Exchange 2010 updates were released today since Exchange 2010 is in extended support.  Updates will be released as per the extended support lifecycle policy.

Exchange 2007 is no longer supported, updates are not provided once a product has exited out of extended support.

Updates Of Particular Note

CU6 contains the latest time zone updates

There  is now improved support for TLS 1.2.  TLS 1.0 and 1.1 should not be disabled at this time.

As announced in the Exchange 2016 CU5 release post the .NET framework requirement has changed.  Exchange 2016 CU5 onwards require .NET framework 4.6.2.  Please see Exchange 2013 CU16 and Exchange 2016 CU5 .NET Framework Requirement for more details.

Two major features were added to Exchange 2016 with the CU6 release: Sent Items Behaviour Control and Original Folder Item Recovery.  The latter is a feature which has been requested for many, many years.  Admins, rejoice!!

Issues Resolved

KB4024658 FIX: The EAS web.config file is not updated on the CAFE server during a build-to-build upgrade

KB4024654 POP/IMAP clients can’t log on with NTLM when Alias and SamAccountName are different in Exchange Server 2016

KB4024653 Active Monitoring probes fail when you use a new accepted domain as the default domain in Exchange Server 2016

KB4024652 Repeated IMAP SEARCH BODY requests may not return newly delivered messages in Exchange Server

KB4024651 The “MessageRetrievalMimeFormat” setting isn’t honored for plain text-only email messages in IMAP in Exchange Server

KB4024650 Emoji is displayed as question marks in iOS clients in an Exchange Server environment

KB4024649 The Read or Unread flag isn’t synchronized correctly after you turn off an ActiveSync device overnight in Exchange Server

KB4024648 FIX: A new contact created in OWA may be merged into an existing contact on Exchange Server 2016

Some Items For Consideration

Exchange 2016 follows the same servicing paradigm for Exchange 2013 which was previously discussed on the blog.  The CU package can be used to perform a new installation, or to upgrade an existing Exchange Server 2016 installation to this CU.  Cumulative Updates are well, cumulative.  What else can I say…

For customers with a hybrid Exchange deployment, must keep their on-premises Exchange servers updated to the latest update or the one immediately prior ( N or N-1).

• Test the CU in a lab which is representative of your environment
• Review this post to also factor in AD preparation which is to be done ahead of installing the CU onto the first Exchange server
• Follow your organisation’s change management process, and factor the approval time into your change request
• Provide appropriate notifications as per your process.  This may be to IT teams, or to end users.
• After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2016. If you uninstall this cumulative update package, Exchange 2016 is removed from the server.
• Place the server into SCOM maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
• Place the server into Exchange maintenance mode prior to installing, confirm the install then take the server out of maintenance mode

• I personally like to restart prior to installing CU.  This helps identifies if an issue was due to the CU or happened in this prior restart, and also completes any pending file rename operations.  3rd party AV products are often guilty of this
• Restart the server after installing the CU
• Ensure that all the relevant services are running
• Ensure that event logs are clean, with no errors
• Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, backup, mobility and management services.
• Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter.
• Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.  See KB981474.
• Disable file system antivirus prior to installing. Do this through the appropriate console.  Typically this will be a central admin console, not the local machine.
• Verify file system antivirus is actually disabled
• Once server has been restarted, re-enable file system antivirus.
• Note that customised configuration files are overwritten on installation.  Make sure you have any changes fully documented!
• CU5 does contain new AD Schema updates for your organisation.

Please enjoy the update responsibly!

What do I mean by that?  Well, you need to ensure that you are fully informed about the caveats with the CU  and are aware of all of the changes that it will make within your environment.  Additionally you will need to test the CU your lab which is representative of your production environment.

Cheers,

Rhoderick

(この記事は 2015 年 4 月 15 日に Office Blogs に投稿された記事 Office 365 now supports larger email messages—up to 150 MB の翻訳です。最新情報については、翻訳元の記事をご参照ください。)

今回は、Office 365 チームのシニア プログラム マネージャーを務める Kevin Shaughnessy と、テクニカル プロダクト マネージャーを務める Shobhit Sahay の記事をご紹介します。

ここ数年間、Office 365 で送受信できる電子メール メッセージは最大 25 MB でした。25 MB というサイズは、ほとんどの電子メールにとっては十分すぎるほどですが、大きなプレゼンテーション、スプレッドシート、動画は、この制限により送信できない場合もあります。Office 365 の Outlook Web App (OWA) では、簡単な方法で OneDrive for Business の保存場所へのリンクを送信する形でドキュメントを「添付」することができます。これは、サイズの大きなファイルを共有する場合にたいへん便利な機能です。しかし、リンクではなく、実際の添付ファイルとしてサイズの大きなファイルを送信したいときもあります。こうしたケースを想定して、今回メッセージ サイズの上限を 150 MB に引き上げました。Office 365 管理者は、最大メッセージ サイズを 1 MB ～ 150 MB の間に設定することができます。

なお、Office 365 メールボックスの既定のメッセージ サイズは 25 MB のままです。既存アカウントの設定をマイクロソフト側で変更することはありません。これは、25 MB よりもさらに小さいサイズの設定を希望しているお客様がいらっしゃることと、多くのお客様が現在の設定を変更したくないと考えていることが判明したためです。そこで、すべてのお客様に一律なサイズ設定を強制するのではなく、Office 365 のお客様が各自に適した最大サイズを自由に選択できるようにしました。

最大メッセージ サイズのカスタマイズ

あらゆるメールボックスのメッセージ サイズの上限を適切なサイズにカスタマイズすることができます。たとえば、すべてのユーザーに 100 MB のメッセージの送受信を許可することも、学校で生徒には最大 5 MB、教員には最大 50 MB の送受信を設定することも可能です。また、電子メールをハイブリッド (一部のメールボックスはオンプレミス、一部のメールボックスはクラウド) に展開していて、双方の環境にあるすべてのメールボックスに一貫して 10 MB の制限を設けるシナリオにも対応しています。1 MB ～ 150 MB の範囲内であれば、1 つまたは複数のメールボックスを指定しても、すべてのメールボックスに対しても、自由にカスタム構成を適用することが可能です。

メッセージ サイズのカスタマイズは、Exchange 管理センターで実行できます。これには、グローバル管理者権限が必要となります。

組織全体の既定のサイズを変更するには、既定のメッセージ サイズ制限を調整します。[recipients] > [mailboxes] > […] の順にクリックして [Set default message size restrictions] を選択します。

ここで、新規メールボックス (今後作成するメールボックス) の最大メッセージ サイズを指定できます。

複数のメールボックスの設定を変更するには、[recipients] > [mailboxes] の順にクリックして複数のメールボックスを選択します。次に、[Bulk Edit] ウィンドウの [Message Size Restrictions] で [Update…] を選択します。

単一のメールボックスのみの設定をカスタマイズするには、[recipients] > [mailboxes] の順にクリックしてユーザーのメールボックスを 1 つ選択します。編集アイコンをクリックし、[Message Size Restrictions] で [View details] を選択して最大メッセージ サイズを指定します。

Exchange 管理センターまたはリモート PowerShell の使用

お客様の組織で使用しているメールボックスの数が 1,000 以下である場合は、おそらく Exchange 管理センターのユーザー インターフェイスを使用して変更を行うでしょう。しかし、1,000 人以上のユーザーを抱える組織で変更を行うなら、リモート PowerShell を使用することをお勧めします。何千ものメールボックスを一度に更新すると、完了までに時間がかかります。大まかな目安としては、メールボックス 1,000 個につき 5 ～ 10 分です。また、サービス全体に更新を反映する作業に通常さらに 15 分ほどかかり、新しい設定をテストするには更新プロセスの完了後 30 分以上経ってから行う必要があります。

以下に、リモート PowerShell でこれらの設定をカスタマイズする場合に使用する一般的なコマンドの例を挙げます。

技術的な詳細

25 MB よりも大きなメッセージを送受信する場合には、数点の技術的な詳細について理解しておく必要があります。

まず、メッセージは、メール システム間で転送されると元のサイズよりも大きくなる可能性があります。これは、異なるメール システムを経由するときにトランスコード (Base64/MIME の変換) が発生する場合があるためです。特にオンプレミスの Exchange とクラウドの間で転送されるケースに多く見受けられます。トランスコードの結果、メッセージのサイズは送信時よりも 33% 大きくなります。今回、メッセージ サイズの上限が 150 MB に引き上げられましたが、これはトランスコードが発生した後のメッセージ サイズの上限です。メッセージがトランスコードされる場合、送信できるメッセージ サイズは最大 112 MB に制限されます。ただし、すべてのメッセージに対してトランスコードが実行されるわけではありません。たとえば、Office 365 内にホストされているメールボックス間で送信されるメッセージの大半はトランスコードされないため、150 MB の限度いっぱいのサイズにも対応できます。

次に、電子メール クライアントによって、大きなサイズのメッセージ送信のサポート状況は異なります。たとえば、Outlook では、トランスコードが発生しない場合、150 MB のファイルを添付して送信できます。そして、送信先もクラウドでホストされており、150 MB のメッセージを受信するように設定していれば、そのメッセージを受信することができます。しかし OWA では、送信できるメッセージのサイズが、設定された最大送信サイズの 75% に制限されています。これは、トランスコードによりメッセージ サイズが増加する可能性を前もって考慮しているためです。たとえば、最大送信サイズを 100 MB に設定して OWA を使用した場合、最大 75 MB のメッセージしか送信できません。また、OWA では各添付ファイルのサイズが最大 25 MB に制限されているので、最大送信サイズを 100 MB に設定して OWA を使用する場合には、1 件のメッセージにつき 25 MB のファイルを 3 点まで添付して送信できます。なお、これらの条件は今後変更される可能性があります。各種電子メール クライアントでサポートされているメッセージ サイズの最新情報については、Office 365 の公式ドキュメントを確認してください。

最後に、Office 365 ユーザーが設定を 150 MB にカスタマイズした場合、そのユーザーは最大 150 MB のメッセージを送受信できても、他のユーザーはできない可能性があります。送信先のメールボックスが大きなメッセージ サイズをサポートしない別の電子メール サービスまたはシステムでホストされていたり、Office 365 ユーザーであっても設定を変更していなかったりなど、理由はさまざまですが、送信先のユーザーは大きなサイズのメッセージを受信できない場合があります。そのため、メッセージが 25 MB を超える場合には、事前に送信先のユーザーに確認するようにしてください。

—Kevin Shaughnessy、Shobhit Sahay

※ 本情報の内容 (添付文書、リンク先などを含む) は、作成日時点でのものであり、予告なく変更される場合があります。

There will be a couple of members of the Australian OEM team heading over to Microsoft Inspire in Washington D.C. for over 9-13 July. If you are also heading over, make sure you let us know, and we can keep an eye out for each other during sessions and events.

Some of the sessions that might be of interest to OEM and System Builder partners include the following…

CE414 Identity-driven security

CE415 Managed mobile productivity

CE416t Use Microsoft Graph API to programmatically manage EMS

CE503 A truly consistent hybrid cloud for digital transformation

CE508 Realize the massive opportunity to modernize legacy .NET applications with containers and Windows Server

IND07 Education networking lunch and FY18 strategy and priorities

IND09 Innovation and solutions in education

IND10 Product innovations addressing education needs

MSP09 Grow your SMB business with the power of 3

Win02p Make your existing Windows applications ready for digital transformation

WIN23t Modern desktop services on AppCompat readiness and deployment

WIN26t Deploying 10 at scale

WIN03p Modernizing Windows 10 deployments with new Windows tools

WIN33t Realize digital transformation with Windows and devices

WIN08 Detect and respond to advanced and targeted attacks with Windows Defender ATP

WIN09 Windows in CSP: What’s new, what’s coming, and why you should include Windows in your managed service offerings

WIN12 K-12 education business with new Microsoft

WIN13 Accelerate Windows Pro devices sales

WIN15 Reinventing services around the modern desktop

WIN16 New, integrated Office 365 and Windows solution for small and midsize businesses delivers more value and streamlines CSP managed service offerings

The mailbox server.

We are now going to install the exchange mailbox server role. Do keep in mind what mailbox is used for. Microsoft documentation says the following is the role of a mailbox server

• Mailbox servers contain the transport services that are used to route mail. For more information, see Mail flow and the transport pipeline
• Mailbox servers contain mailbox databases that process, render, and store data.
• Mailbox servers contain the client access services that accept client connections for all protocols.

Just keep this in mind: the actual mail is stored in a database that is stored on the mailbox server so if in the entire infrastructure- your mailbox server gets formatted (chees!) there is no way you can recover your emails. Now as this is one heck of a critical piece- Microsoft has provisioned redundancy for it. It is called DAG. A DAG is the clustered host of machine which will share the responsibilities of sharing the mailbox databases so that even if one server goes down- we can fall back to the other functional host.

This is not much to do apart from following the wizard, this technet article explains what you should do, only thing to keep in mind which is not written in this is to run UcmaRuntimeSetup.exe on the exchange mailbox which this link has not mentioned so far. https://technet.microsoft.com/EN-US/library/bb124778(v=exchg.160).aspx

There are couple of “gotchas” here- first, when you install the related features by the wizard- you will see that the wizard has failed complaining that some features are still missing. Well- its actually installed and you just have to reboot the machine to take this to effect. So just reboot the machine and then start the wizard again.

Now once the exchange gets installed, first thing we have to is to log inside exchange to see how things look like. the management tool for exchange is called exchange messaging center. This is a web based console used for managing and maintaining the Exchange. Though it is a very good tool to begin with for the rookies- it is best to familiarise yourself with the Grand dady of the Messaging center. It is called Exchange management Shell. EMS as it is called is the Powershell shell for managing exchange. There are many things that you cannot do with the Messaging center but can achieve with the Exchange messaging services. So to be an expert in exchange- you know what you have to do!

A quick tip- to open Exchange messaging center- you have to use https://localhost/ecp on the local host. On a member server; you will have to use: https://NameofServer/ecp. In my case the name of my mailbox server is exchange2016 so the URL for accessing the messaging center is https://exchange2016.mayanks.ga/ecp. Please note my domain is mayanks.ga- this is a publically registered domain for free. (checkout www.freenom.com for registering a free domain name for yourself!)

Well- once the exchange mailbox server is installed; believe it on or not- you have a basic exchange 2016 up and running! you can create new users with email enabled and can enable email services for the existing users. We will move in to the next blog for the general housekeeping tasks to begin with.

微軟發佈了一個知識庫文章，其描述的內容包含一系列用於 OMS 中 Operations Manager 的客戶端附加模式和 Direct Agent Access的步驟、程序、和故障排除方法。

其中包含了以下幾個項目：

• 作業管理員註冊錯誤

說明當您註冊作業管理員 (OpsMgr) 管理群組，可能會遇到的兩個錯誤訊息。

• Proxy 登錄或組態步驟

說明如何設定要讓傳輸作業的見解 proxy 伺服器 （如果您有的話）。

• 確認登錄後的進行部署

整合式的作業管理員附加模式以及直接連線的代理程式，請提供疑難排解步驟。也說明如何檢查資料流，以及尋找常見的錯誤，以及如何修正它們。

• 其他已知的問題及因應措施的作業管理員

描述其他從作業管理員作業的見解 onboarding 相關的其他問題。

詳情請參閱：如何疑難排解作業管理套件 onboarding 問題。

In part 2 of this blog Here we have installed and configured the exchange mailbox and have opened the exchange messaging center. Needless to say that this is important to do the tasks from the Messanging shell because there lies all the power of exchange! So here are the couple of extremely basic things that you’d like to do with your exchange.

Creating a new user.

When a new user joins a company; the first thing is that he is handed over an email address. Well- here is what we are going to do just now. In the examples below a chap called Mike Rogers will get his email screwed up by us. Lets start by creating an email for him. The following command on exchange management shell will create a mailbox for Mike Rogers.

New-Mailbox -Name “Mike Rogers” -UserPrincipalName Mike@mayanks.ga -Password (ConvertTo-SecureString -String ‘Hcl@123’ -AsPlainText -Force) -FirstName Mike -LastName Rogers

To confirm that that user account has indeed been created- we will use the following command.

Get-Mailbox -Identity “Mike Rogers” | Format-List Name,DisplayName,Alias,PrimarySmtpAddress,Database

This is what I see when I run this command, Take a look at the Database name. We are going to speak a lot about it in coming blogs however if it is not clear to you already- please note, the user mailbox will be hosted on the databases. There can be 10 databases hosting 1000 users or just one database hosting 1000 user mailboxes. We will keep this discussion in abeyance until we do our basic tasks first.

Enabling email support for an existing user.

So what happens when you already have an active directory user before you installed exchange on it. Its actually pretty simple to enable email access for him. the following command will enable the email access to the user. Lets create an email for the corrupt ex-president of United states Francis Underwood.

Enable-Mailbox -Identity frank@mayanks.ga -Database “Mailbox Database 1895211678”

 

See how easy it is. Now if Mr Underwood wants to manipulate things.. like he do; he would like to send an email as someone else as well, hiding his own identity. In the boring world of the IT- lets say a company A has recently been acquired by the company B. Company A originally has an emails configured like a@A.com and for company B it was b@B.com. Now all the users will be using @B.com domain. You now want to make sure that the users of company A keep getting the emails from their original email address. So you will add an alternate email address to the mailbox.

Set-Mailbox “Francis Underwood” -EmailAddresses @{add=”Frank@president.us”}

Now any email that will be sent to frank@president.us will be forwarded to the mailbox of Francis underwood in addition to the any email sent on frank.mayanks.ga! Keep in mind- the Francis could not identify if the email was sent to him from @president.us. once he logs in the web login in outlook as frank@mayanks.ga.

Since I want to keep Frank in check, I can check the email address of Frank by running the following command:

Get-Mailbox “Francis Underwood” | fl EmailAddresses

Now if Francis wants to see all the emails sent to Poor Mike Rogers like Peter Russo- he can run the following command so that all the emails of Mike will be forwarded to Franks account.

Set-Mailbox -Identity “Mike Rogers” -DeliverToMailboxAndForward $false -ForwardingSMTPAddress “Frank@mayanks.ga”

Take a look at this: DeliverToMailboxAndForward is set to false- meaning all emails will be sent to frank without even Mike’s knowledge. 

Since I am the director of the show- I will decide who will do what. So I can know whos email is being seen by whom and how to turn in back to how it was.

Get-Mailbox | Where {$_.ForwardingAddress -ne $null} | Set-Mailbox -ForwardingAddress $null -DeliverToMailboxAndForward $false

Lastly how to make sure that no one outside can make any contact with Poor chap Mike? its easy..

Set-Mailbox -Identity “Robin Wood” -RequireSenderAuthenticationEnabled $true

when RequireSenderAuthenticationEnabled is set to $true Mike can only receive the email  only in your organization.

I hope you’d found this blog useful, in Next blog- we will discuss some other interesting aspects of mailbox servers.

Cheers!

Mayank