Sunday, May 31, 2015

Steve Goodman: The next challenge…

awardsIt’s with great pleasure that I’m announcing that this Monday, 1st June, I’ll be joining multiple award-winning Microsoft partner, Content and Code as Head of Unified Communications. My role will be responsible for our Exchange and Skype for Business offerings, primarily in Office 365.

I’ve had a fantastic time at Ciber, where I’ve learnt from some of the best and been able to help them in many ways. I’ve had the opportunity to win and work on a range of interesting Office 365 projects, mostly complicated and often for large organizations. Sometimes though it is time to take on a new challenge.

Content and Code are a company that I’ve had my eye on for a while – I’ve been to their offices before as they host events, like the Messaging User Group and Office 365 User Group, and as the UK’s leading Office 365 partner our paths have crossed on quite a few occasions. Common customers often had glowing comments about their capabilities. For an MVP who wants to work with others who share that same drive to share knowledge, be great at what they do and delight customers, it’s a pretty good match.

For the blog, it’s business as usual. I’ll still be writing on here, SearchExchange, MSExchange.org, writing the odd book, hosting The UC Architects Podcast and speaking at conferences. I’ll also continue to help lead the UC Birmingham User Group and UC Day UK. You’ll also see me around the London user groups a little more often as well.



from Exchange News Full Article

Saturday, May 30, 2015

msexchange.org: Windows Phone 8.1 Update and Emulators v8.10.14141.167

The Windows Phone 8.1 Update Emulators package adds additional emulator images to an existing installation of Visual Studio 2013 Update 2 or later. With this update installed, you can create and test apps that will run on devices that have Windows Phone 8.1 Update.

from Exchange News Full Article

Subject Exchange: Weekend reading



from Exchange News Full Article

Friday, May 29, 2015

The EXPTA {blog}: How to Create Dynamically Adjusting Exchange Retention Policies

Exchange has supported message retention policies since Exchange 2010. Retention Policies are collections of Retention Tags that dictate how emails are retained in Exchange. Usually this is done to comply with business policies on data retention and/or used as a way to move data from the user's primary mailbox to an archive mailbox.

Retention Policies
The retention policy shown above includes several personal policy tags and one default policy tag that moves emails older than 6 months to the archive. You can customize or create new retention policies for your users based on your company's data retention policies. For example, you can create a retention policy to move all emails to the archive mailbox after 1 year and permanently delete all emails older than 5 years.

Only one mailbox retention policy can be assigned to a mailbox at a time. While you can easily change which retention policy is assigned to a mailbox using the the Exchange Management Shell or the Exchange Admin Center, this can be somewhat tedious.

Note that retention tags are time-based, not size-based. If you're trying to manage your mailbox storage with retention policies the same time-based retention policy may result in widely varying mailbox sizes within the Exchange database store, depending on the user. I developed the following process to dynamically adjust user's retention policy based on mailbox size. The larger the mailbox gets, the more aggressive the retention policy applied.

Start by creating multiple default archive and/or delete retention tags. Make sure to select "applied automatically to entire mailbox (default)" to ensure that it applies to all email items. For example,

  • Default one year move to archive
  • Default 6 months move to archive
  • Default 3 months move to archive
  • Default 7 year delete
  • Default 5 year delete
  • Default 3 year delete
Creating a Default retention tag
Next create multiple retention policies that include the default retention tags you created. For example,
  • High Retention - Default one year move to archive, Default 7 year delete
  • Medium Retention - Default 6 months move to archive, Default 5 year delete
  • Low Retention - Default 3 months move to archive, Default 3 year delete
Apply the High Retention policy to all mailboxes using the following EMS command:
Get-Mailbox -ResultSize unlimited | Set-Mailbox -RetentionPolicy "High Retention"

Note that archive retention tags only apply if the mailbox has an archive mailbox, otherwise the archive tags are ignored.

Copy the following script and save it to one of your Exchange servers in the C:\Scripts folder as Apply-RetentionPolicies.ps1:
$mbx = Get-Mailbox -ResultSize unlimited
$mbx | ForEach-Object -Process {
$size = ( Get-MailboxStatistics $_.Alias ).TotalItemSize
If ( $size -gt "10GB" ) {
  Set-Mailbox $_.Alias -RetentionPolicy "Low Retention Policy"
  }
elseif ( $size -gt "8GB" ) {
  Set-Mailbox $_.Alias -RetentionPolicy "Medium Retention Policy"
  }
else {
  Set-Mailbox $_.Alias -RetentionPolicy "High Retention Policy"
  }
}

Adjust the mailbox sizes in the script to meet your company's retention needs. In the example script above mailboxes greater than 10GB get the Low Retention Policy, mailboxes between 8-10GB get the Medium Retention Policy, and everyone else gets the High Retention Policy.

Next, create a scheduled task that runs the Apply-RetentionPolicies.ps1 script once per day.

Set the "Program/Script" property to:
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
And set the "Add arguments (optional)" to:
-NonInteractive -WindowStyle Hidden -command $ep = (Get-Item env:"ExchangeInstallPath").Value; . $ep\bin\RemoteExchange.ps1; Connect-ExchangeServer -auto; . C:\Scripts\Apply-RetentionPolicies.ps1
Creating a Basic Scheduled Task
The scheduled task must run using the credentials of an account with Organization Management rights.

With this process, as a mailbox gets smaller from a more aggressive retention policy it will automatically get a longer retention policy.



from Exchange News Full Article

msexchange.org: EMS Webinar Series: Compare point solutions for enterprise mobility to Microsoft EMS

Interesting webinar about mobile device management, with a strong focus on Microsoft EMS.

from Exchange News Full Article

msexchange.org: Enterprise Mobility Suite Poster

The EMS Poster will help you to better understand key capabilities and to better integrate mobile device management with your Exchange implementation.

from Exchange News Full Article

msexchange.org: Office Mechanics videos

For a tech enthusiast, it's not enough to read about the latest innovations, seeing is believing. Office Mechanics gives you a deeper first look at how the latest tech works from the people behind it. Every Wednesday, we'll try to inform and entertain you in about 10 minutes each week. More demos and less talk so you can catch up at your own pace wherever you are.

from Exchange News Full Article

Thursday, May 28, 2015

Steve Goodman: Registration is open for UC Day UK

AvatarFor the last few months, I’ve been involved (with a few others) in helping to organize the first ever one-day conference in the UK dedicated to Microsoft Unified Communications – we call it UC Day UK.

What we’re doing is simple; we’re putting on a mini MEC (Microsoft Exchange Conference) and Lync Conference for IT Pros primarily in the UK (though everyone’s welcome) – including those working at partners, vendors and on the customer side, you are all welcome.

In lieu of an “Ignite Europe” it’s going to give you independent, real world, deep-dive sessions; the kind that you’d normally travel overseas for, right on your doorstep. You’ll get bang-up-to-date sessions on Exchange 2016, Skype for Business 2015 and for importantly the cloud-based equivalents in Office 365.

Why a UC Day?

One question I have been asked is why isn’t it just a generic Office 365 conference?

Really for Office 365 you need to cover many different areas – Office Pro Plus, Azure AD, Yammer, AD FS, Azure AD Sync / Azure AD Connect, SharePoint Online, OneDrive for Business, Office 365 development, Hybrid Search in SharePoint, not to mention Exchange Online, Skype for Business Online and bigger topics like workplace transformation, adoption or add-on offerings.

An Office 365 conference or summit really can’t be *done justice* in a single day event. It needs a few days to skim the surface and even over three days with multiple tracks we’ll end up with groups of people specialising in different areas.

So – we focused on IT professionals specialising in Microsoft UC, who are usually managing some sort of mix of Exchange, Lync/SfB in Office 365 and on-premises.

Office 365 is mature enough now that the offerings are complete enough and used in such complex ways that to get the most out of it still needs specialist skills. On-premises, the same rules apply. Wherever it is hosted I still see the same Unified Comms teams managing Exchange + SfB/Lync.

In the early days of Office 365 we all perhaps thought that there would be more crossover – and especially in mid-size organizations where there is a lot of new technologies added, and less specialist requirements, IT pros grow into a new more generic roles, but still need to understand some of the more critical things, like optimizing the network for Skype for Business online.

For larger enterprises though, the UC team is not going to start doing stuff like managing deployments of Office; that will stay with the same teams that dealt with that in the past. In some cases teams shrink but in general – because we’ve got so much new stuff coming out on a regular basis, change needs to be triaged and new features assessed to see the business value they add, then plans to adopt drawn up. It’s like being forced to upgrade to a whole new version every few months!

With that in mind there’s more than enough content to cover in a single day, and the role of UC more than ever is important due to the explosion of adoption through Office 365. The tech’s there and ready to use – it’s up to us to deliver it to the business as a transformational solution.

What kind of content should you expect?

Our speaker and session list is still being decided – but even at this early stage we are looking at a multitude of Exchange and Skype for Business MVPs including MCMs in both areas. The absolute most important part of UC Day is to make sure that you go away having learned lots, from people who love their subject – and hopefully everyone will have had a good time doing so.

How much does it cost, where is it and when is it – and how do I register?

Registration for UC Day is open now. Tickets would be approximately £80-90 to cover costs – but thanks to sponsorship from some of the biggest names we are able to offer tickets for FREE for at least the first 500 attendees.

The format of the day is like any conference – registration opens early then after the keynote we will split up into a number of tracks, with attendees free to pick sessions. Breakfast and lunch is provided and we’ll run through till late in the afternoon. It’s going to be a packed day.

Better still we’ll also be having a pre-conference event the night before. This is a networking and social – a chance to have a few drinks with people sharing similar interests and we’ll stage a live recording of The UC Architects podcast. This’ll be rather special as we’ll be hosting it as a quiz. I’d try and dress it up, but basically we’re talking a pub quiz with UC questions. I might even buy disco lights!

Our venue is the National Motorcycle Museum, right by Birmingham Airport in the UK. It’s been home to the VMware User Groups’ national event for the last 4 years running and having attended two of those I’ve found it to be a great venue.

The date is the 28th September 2015 – so plan to arrive the night before, on the Sunday evening for the social event (partner hotel, TBD), so you can be fresh for the conference on the Monday. It’ll be a great value day and in my opinion a very valuable day away from the office to learn from some of the best.

Visit the UC Day website and sign up – scroll down to Ticket Registration



from Exchange News Full Article

MSExchange.org: Exchange Archiving: On-Premises vs Cloud-Based (Part 2)

Configuring and deploying In-Place Archiving (On-Premises).

from Exchange News Full Article

msexchange.org: Microsoft Message Analyzer v1.3

Message Analyzer enables you to capture, display, and analyze protocol messaging traffic; and to trace and assess system events and other messages from Windows components.

from Exchange News Full Article

Wednesday, May 27, 2015

The EXPTA {blog}: New Skype for Business Visio Server Stencils


Now you can download the latest Microsoft server stencils for Visio. These stencils contain more than 300 icons to help you create visual representations of Microsoft Office or Microsoft Office 365 deployments including Microsoft Skype for Business, Microsoft Exchange Server 2013, and Microsoft SharePoint Server 2013. The zip file now includes both stencil sets from 2012 and 2014.

The 2012 stencils include Lync Server and Exchange 2010 stencils, while the 2014 stencils include Skype for Business and Exchange 2013 stencils. Perfect for that next migration diagram!



from Exchange News Full Article

Tuesday, May 26, 2015

MSExchange.org: Exchange Server 2013 offsite protection using DPM and Microsoft Azure (Part 2)

Completing the final steps to configure Mailbox Databases protection being stored in Microsoft Azure using DPM.

from Exchange News Full Article

Friday, May 22, 2015

msexchange.org: Things to Consider before moving to Office 365

Guest post by Mark Mulcahy, Technical Director at Waterford Technologies

from Exchange News Full Article

msexchange.org: Friday podcast: Sleep like a log with BES12 Monitoring



from Exchange News Full Article

Subject Exchange: Weekend reading



from Exchange News Full Article

msexchange.org: Microsoft Office for Mac 2011 14.5.1 Update

This update fixes critical issues and also helps to improve security. It includes fixes for vulnerabilities that an attacker can use to overwrite the contents of your computer's memory with malicious code.

from Exchange News Full Article

msexchange.org: ENow Enables Enterprise Email Management for Small & Midsized Businesses at 75% Off

Email management leader ENow has just announced a program that makes its highly acclaimed Mailscapeemail management solution available to companies with fewer than 550 email users at 75% off its standard price for a limited time.

from Exchange News Full Article

Thursday, May 21, 2015

MSExchange.org: Migrating a small organization from Exchange 2010 to Exchange 2013 (Part 2)

In this series we rapidly migrate from Exchange 2010 to 2013. In part one we decided on server specifications and then installed and began to configure the base operating system. In part two of this series we complete the configuration, install Exchange 2013 then begin to configure the server.

from Exchange News Full Article

Wednesday, May 20, 2015

Tony Redmond: Write some code and you can influence DAG failovers (until Exchange 2016 comes along)

A recent debate on the Exchange 2013 (unofficial) Facebook group started off with the question “can I built my own failover criteria in a DAG?” and pointed to the TechNet page on Active Manager.

The debate began with sheer denials, mostly on the basis that it didn’t seem to make sense for someone to attempt to second-guess the Exchange development engineers who have been working on this problem for many years. As the erudite Boris Lokhvitsky remarked: “In your car, do you have the desire to modify the combustion sequence or rearrange the valves in the engine so that it would run faster?”

In fact, Exchange 2013 evolved the failover criteria used by Exchange 2010 to take account of server health when Active Manager makes a decision about what target server to select to host a failing database in BCSS, or “best copy and server selection.”

But after a while, the esteemed Scott Schnoll weighed in to say that there is a way because Exchange accommodates a method called an Active Manager Extension, part of the third-party replication (TPR) API that exists in both Exchange 2010 and Exchange 2013. The TPR allows storage vendors to write their own continuous replication code and then stitch it together with the rest of the DAG components so that everything works together seamlessly. At least, that’s the theory.

TechNet says: “Exchange 2013 also includes a third-party replication API that enables organizations to use third-party synchronous replication solutions instead of the built-in continuous replication feature. Microsoft supports third-party solutions that use this API, provided that the solution provides the necessary functionality to replace all native continuous replication functionality that’s disabled as a result of using the API. Solutions are supported only when the API is used within a DAG to manage and activate mailbox database copies.”

On the surface, TPR seems like a wonderful idea. But the sad fact is that only EMC has ever implemented TPR in a solution called “Zero-Loss Protection for Exchange”, where they distinguish between “Native Database Availability Groups” (the normal kind) and “Synchronous Database Availability Groups” (the kind you’d use with an EMC CLARiiON SAN). The EMC Replication Enabler for Exchange is the component that leverages TPR.

I’m sure that EMC was very excited when Microsoft told them about the TPR because it must have seemed like a great way for EMC to defend their SAN installed base at a time when Microsoft was telling customers that they were engineering Exchange to exploit low-cost storage solutions. Since then the evidence is that not many people have actually used EMC’s solution and no other storage company appears to have been too interested in taking on the cost to develop and maintain their own replication solution for a DAG.

Indeed, given the hype around JBOD-type storage for Exchange, especially in the two years since Microsoft shipped Exchange 2013, anyone who proposed building a third-party replication solution for expensive SANs might be regarded as a candidate for lying down in a cool dark room until the idea passed. Even EMC is quite on the topic of using their code with Exchange 2013 and I imagine that the Replication Enabler is heading to the great byte wastebasket soon, if it hasn’t already reached there.

So Scott was right in his assertion that there is a way for someone to affect the way that Active Manager handles database failovers. You simply have to crack open your favorite IDE and write the code to leverage TPR. Simple. Just like that. Or maybe not. But the bad news is that your code will only work for Exchange 2010 and Exchange 2013 because Microsoft announced their intention to deprecate the API in Exchange 2016 at the recent Ignite conference.

As for me, I think I’ll let the Exchange developers take care of how replication happens inside DAGs. It just seems easier all round.

Follow Tony @12Knocksinna




from Exchange News Full Article

msexchange.org: The New Office 365 Mailbox Migration Troubleshooter

The New Office 365 Mailbox Migration Troubleshooter that was announced at Ignite can be found here: Http://aka.ms/HMTSEmail

from Exchange News Full Article

msexchange.org: The UC Architects Podcast Episodes 51 & 52

The latest "UC Architects Podcast" are now available for listening.

from Exchange News Full Article

msexchange.org: Microsoft Security Intelligence Report, Volume 18

If you want to stay informed with the latest threats in cyber-security (including email), read this detailed report, provided by Microsoft.

from Exchange News Full Article

msexchange.org: Successful meetings with Skype for Business

Download and read the latest "Work Smart Guide, by Microsoft IT".

from Exchange News Full Article

msexchange.org: Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool v.15.0.4727.1000

This download includes Group Policy Administrative Template (ADMX/ADML) and Office Customization Tool (OPAX/OPAL) files for Microsoft Office 2013.

from Exchange News Full Article

Tuesday, May 19, 2015

Subject Exchange: Update for Outlook Junk E-mail Filter – May 2015

Microsoft has recently released the May updates for the Outlook 2007/2010/2013 Junk E-mail Filter.

This update provides the Junk E-mail Filter in Microsoft Office Outlook with a more current definition of which e-mail messages should be considered junk e-mail.

The update is available for Outlook 2007, Outlook 2010 (32-bit, 64-bit) and Outlook 2013 (32-bit, 64-bit) or you can use Microsoft Update. As usual, the updates come with the corresponding Knowledge Base article:



from Exchange News Full Article

MSExchange.org: Deploying an Exchange 2013 Hybrid Lab Environment in Windows Azure (Part 27)

In this article we will verify the hybrid configuration that has been configured on the on-premises side.

from Exchange News Full Article

msexchange.org: Microsoft Advanced Threat Analytics (ATA) documentation

Currently in preview, Microsoft Advanced Threat Analytics (ATA) is an on-premises product that helps IT security professionals protect their enterprise from advanced targeted attacks by automatically analyzing, learning, and identifying normal and abnormal behavior among entities (users, devices, and resources). ATA also helps identify known malicious attacks, security issues and risks using world-class, cutting edge research in behavioral analytics to help enterprises identify security breaches before they cause damage.

from Exchange News Full Article

Saturday, May 16, 2015

EighTwOne: Exchange data: NTFS vs. ReFS

chartFor Exchange, NTFS has been the file system of choice since time immemorial. In 2012, Windows Server 2012 introduced a new file system: Resilient File System or just ReFS. ReFS was designed to overcome some of the limitations of NTFS, in particular in the area of maintaining data integrity. More information on ReFS in comparison to NTFS can be found here.

At that time Windows Server 2012 went RTM, the latest version of Exchange, Exchange 2010, was not supported to run on ReFS. Present day, Exchange 2010 still doesn’t support ReFS. However, when Exchange 2013 entered the arena shortly after Windows Server 2012, it came with support for both NTFS and ReFS file systems. NTFS was still considered best practice, with ReFS being a supported option with the added recommendation to turn off ReFS’ integrity checking feature, and disabling it for Content Index-exclusive volume is optional. It may therefor come as no surprise that nearly all customers are deploying Exchange 2013 on NTFS volumes only.

That may change with Exchange 2016. As announced at Ignite 2015, for Exchange 2016 more emphasis will be put on following the Preferred Architecture design when deploying Exchange on-premises. The Exchange 2016 Preferred Architecture contains guidance to use ReFS formatted, BitLocker encrypted data volumes with Exchange 2016. The latter option is of course to protect organizations against theft of physical storage devices.

With some time to spare, I was interested to see what the impact would be on the storage performance when using NTFS or ReFS, and especially the performance penalty when enabling BitLocker on a volume. Similar to a comparison I did between Exchange 2010 and Exchange 2013 on different operating systems, I ran a JetStress 2013 test utilizing these 3 file systems to get a sense of what to expect.

The ESE engine files from Exchange 2013 CU8 were used for testing, along with the following parameters:

Mode Test Disk Subsystem Throughput
Thread Count 12 (fixed)
Min/Max DB Cache 32 MB / 256 MB
Ins / Del / Repl / Read % 40/20/5/35
Lazy Commits 70%
Run Background DB Maintenance True
Databases 1 x DB (186GB), 3 Copies
Running Time 2 Hours

Databases and logs were stored on a DAS SSD drive, and the volume was GPT partitioned and utilizing 64K allocation units. ReFS Integrity checking was disabled for the volume using:

Format-Volume –DriveLetter X -FileSystem ReFS -AllocationUnitSize 65536 -SetIntegrityStreams $false

The drive supported hardware encryption for BitLocker, which offloads encryption to the drive. You can verify that hardware encryption is used after enabling BitLocker on the volume by inspecting the BitLocker status using the manage-bde utility or Get-BitLockerVolume cmdlet:

image

As you can see from the EncryptionMethod property, this volume is protected using hardware-based BitLocker encryption. Perhaps needless to say, but when using BitLocker with software encryption, the CPU performance penalty is substantial, and this is not to be used with I/O intensive applications like Exchange.

The results from the JetStress tests are show in the following table:

JetStress Version 15.0.658.4
ESE.DLL 15.0.1076.9
Operating System 6.2.9200.0
Overall Test Result

Passed

Passed

 

Passed

Achieved Transactional IOPS

1,613.13

1,407.55

-13%

1,379.98

-14%

Database Reads Average Latency (msec)

8.53

10.50

-23%

9.73

-14%

Database Writes Average Latency (msec)

12.80

20.80

-63%

19.98

-56%

Database Reads/sec

895.25

787.08

-12%

769.47

-14%

Database Writes/sec

726.48

628.55

-13%

618.65

-15%

Database Reads Average Bytes

35,220.22

35,375.26

0%

35,437.64

1%

Database Writes Average Bytes

34,389.82

34,510.95

0%

34,496.88

0%

Log Reads Average Latency (msec)

4.64

5.06

-9%

5.00

-8%

Log Writes Average Latency (msec)

5.16

7.22

-40%

6.73

-30%

Log Reads/sec

18.64

16.29

-13%

16.08

-14%

Log Writes/sec

87.25

72.81

-17%

73.82

-15%

Log Reads Average Bytes

232,562.72

232,562.01

0%

232,562.30

0%

Log Writes Average Bytes

25,005.97

26,210.03

5%

25,589.45

2%

Avg. % Processor Time

4.28

3.66

14%

3.60

16%

Some observations and notes:

  • ReFS took a near 15% IOPS performance hit when compared to NTFS.
  • Usage of ReFS resulted in increased I/O latencies, especially for write operations.
  • ReFS seem to have a positive impact on the processor utilization, lowering average utilization by around 15%.
  • For some strange reason, average write latencies seemed lower when using ReFS with BitLocker than without BitLocker (~10%).

Given the impact of file system choice on I/O performance and CPU utilization, I hope next versions of Exchange Server Role Calculator will feature an option to select which file system will be used to store Exchange data, as the difference in I/O performance and CPU utilization between NTFS and ReFS seems significant.

The JetStress reports can be found here.

I will finish with a short disclaimer: This test was only performed to get an indication of performance impact of using different file systems with Exchange 2013 utilizing identical hardware. The results are purely indicative and not meant to provide guidance or proof. Your mileage may vary.


Filed under: Exchange 2013 Tagged: Design, Planning, Storage

from Exchange News Full Article

Friday, May 15, 2015

Subject Exchange: Weekend reading



from Exchange News Full Article

Thursday, May 14, 2015

MSExchange.org: DKIM and DMARC in Office 365 (Part 2)

In the first part of this article series, we had an overview of what DKIM is, how it works and what its purpose is. In this article we will look at DMARC.

from Exchange News Full Article

Wednesday, May 13, 2015

msexchange.org: Clarifications on Dropbox integration with Office Online



from Exchange News Full Article

msexchange.org: Exchange @ Ignite 2015



from Exchange News Full Article

msexchange.org: Managing Send as and Send on Behalf to in Distribution Groups



from Exchange News Full Article

msexchange.org: Pulling out users who are connecting using Outlook 2003 in your Exchange 2010 environment



from Exchange News Full Article

msexchange.org: New OneDrive for Business roadmap



from Exchange News Full Article

Tony Redmond: Using PowerShell to convert Exchange Distribution Groups to Office 365 Groups

At last week’s Microsoft Ignite conference, I had the chance of attending a session called “Evolving distribution lists with Office 365 Groups” (a recording of the session is available online). The session described the integration with Outlook 2016 (no plans exist to back port the technology to Outlook 2013) and then went on to investigate how Microsoft views Office 365 Groups as a better alternative to old-style distribution groups. There’s no denying this fact. Distribution groups have been around since the dawn of email and haven’t evolved too much since. The last time Microsoft did anything to improve matters was the introduction of dynamic distribution lists in Exchange 2003.

Of course, the big issue with Office 365 Groups is that they will only ever live in the cloud. Microsoft is not going to incorporate them into the on-premises version of Exchange. You’ll be able to synchronize Office 365 Groups with on-premises Exchange via AADConnect if you operate a hybrid environment, but you won’t be able to create these groups on-premises.

One reason why this is so is the position that Office 365 Groups are moving to occupy within the Office 365 ecosystem as a single entity that permits access to many different forms of data available within the service. Today, membership of an Office 365 Group allows a user to access a shared mailbox, shared calendar, shared OneNote notebook, and a document library. The signs are that more resources will be accessible in the future, all granted through group membership.

Anyway, if you want more information about Office 365 Groups, you can read it in chapter 7 of “Office 365 for Exchange Professionals”.

Speaking of which, keeping the content of an eBook about Office 365 requires you to pay a lot of attention to what Microsoft is saying to customers at conferences such as Ignite. You never know when a speaker provides some information that should be included in the book or requires a change to the book’s content. In this case, I was interested in how Alfons Staerk approached the topic of migration from old-style distribution groups to Office 365 Groups.

It looks very much as if customers will be left to their own devices to migrate distribution groups as they wish. Of course, distribution groups bring their own complexities to the table. How should you deal with nested groups, for instance. What do you do with groups that include mail-enabled public folders, mail contacts, and shared mailboxes in their membership as none of these objects are supported in Office 365 Groups. And, of course, Office 365 Groups use their own mechanism to access resources across different parts of the service, so what do you do with mail-enabled universal security groups?

Microsoft demonstrated a program called “Hummingbird” that will soon be available (when the lawyers are happy) that can migrate a distribution group to an Office 365 group, subject to the caveats expressed above. Apparently the source code of the program will also be available to allow you to do your own thing.

But the approach taken to migrate a distribution group with a PowerShell script was more interesting. Up to recently, the PowerShell support for Office 365 Groups was just plain bad. You couldn’t create a new group or update group membership, both of which seem like fundamental operations. Microsoft is currently rolling out a new set of cmdlets to Office 365 tenants that address the problem. These are the *-UnifiedGroup cmdlet set to maintain group objects and the *–UnifiedGroupLinks cmdlet set to maintain group membership.

The script shown by Alfons was rudimentary but effective, but only for very simple distribution groups whose membership is solely composed of mailboxes. Everyone loves a challenge, and I decided that it would be a good thing to learn more about how to use the new cmdlets to work with Office 365 Groups, so I set about working on the ConvertDLtoO365Group.ps1 PowerShell script. After all, we need to bring out a second edition of “Office 365 for Exchange Professionals” (probably in September) that should cover this topic.

I’m no programmer. At least, I haven’t been for many years. My COBOL and VAX BASIC skills are rusty now but, as Jeffrey Snover keeps on reminding me, the joy of PowerShell is its ability to put things together bit by bit until something really good is done. PowerShell is like Lego bricks in that respect.

I hacked my way through several versions of the script. The current version is available in the TechNet gallery for anyone to download (and hopefully improve). The script runs in the context of a PowerShell session that is already connected to Exchange Online and does the following:

  • Takes the alias or name of a distribution group as the input parameter.
  • Performs some initial checks to see whether the distribution group exists or an Office 365 Group with the same alias exists. And that it’s an object of type MailUniversalDistributionGroup, which is the only type we can convert.
  • Checks the members of the input group to strip out those that can’t be added to the target Office 365 Group.
  • Checks whether the input group has member join restrictions. If it has (the group is “Closed” or “ApprovalRequired”), the admin is prompted to decide whether they want to create a private Office 365 Group. You can’t currently change the group type, so this is an important decision.
  • Tells the admin what’s happening and asks to proceed.
  • The new Office 365 Group is created with the New-UnifiedGroup It uses the same alias as the input distribution group because a new alias is given to that group.
  • As many of the properties of the input distribution group as possible are moved to the new Office 365 Group (not all can be because there isn’t a direct 1-to-1 mapping between the two object types). The Set-UnifiedGroup cmdlet is used for this purpose.
  • In particular, the Office 365 Group is set to auto-subscribe new members so that it mimics the distribution of new content via email as members expect from a distribution group.
  • The membership is added to the new Office 365 Group using the Add-UnifiedGroupLinks
  • Group members can be in three sets of links (owners, members, and subscribers). Because the new Office 365 Group is intended to behave like an email distribution group, the members are added to the members and subscribers sets.
  • The owners/managers of the input distribution group are added as owners of the Office 365 Group.
  • The email address of the input distribution group is switched to the new Office 365 Group so that new traffic goes there.
Converting an Exchange Distribution Group with ConvertDLtoO365Group.ps1

Converting an Exchange Distribution Group with ConvertDLtoO365Group.ps1

Phew! That’s a lot of processing. There are some known issues. For example, the –AccessType parameter for the New-UnifiedGroup cmdlet doesn’t work at present, so only public groups can be created. This is a known bug and is being fixed by Microsoft. Another issue is that running Add-UnifiedGroupLinks to add mailboxes as subscribers doesn’t work. This bug is also known and a fix will be available shortly.

However, the point is that it’s a PowerShell script and because it’s a script the code is there and available for all to see – and hopefully improve.

Thanks to Alfons Staerk and Sam Koppes of Microsoft for their encouragement. I think they quite liked seeing the demo script shown by Alfons take on a life of its own…

Enjoy!

Follow Tony @12Knocksinna




from Exchange News Full Article

Tuesday, May 12, 2015

Exchange Team Blog: Exchange @ Ignite 2015

clip_image002We were joined by thousands of Exchange and Office 365 customers at Microsoft Ignite in Chicago last week. It was full of announcements, new content, and opportunities for the Exchange community to reconnect. For those who were on site we thank you for your enthusiastic participation and engaging questions. We spent time geeking out on everything from architecture designs to mobile clients, and everything in between. It was enough to drive creativity to new levels – in fact, in one discussion Tim McMichael broke out in singing “Everything is awesome... Everything is cool when you deploy a DAG…” Sounds like a new Exchange hit in the making to me!

If you weren’t able to join us, no worries–every session at Ignite was recorded and published to Channel 9. Here’s a recap of the top Exchange-related news of the week, and links to session recordings where you can get all the details.

Highlights

EXCHANGE SERVER 2016

We introduced Exchange Server 2016, our next on-premises Exchange Server release. Exchange Server 2016 includes exciting new features for on-premises customers, including a new approach to document collaboration, enhanced search, and a modern Outlook Web App experience to name a few. The server also has a robust architecture that is cloud-inspired and proven. We demoed elements of Exchange Server 2016 for the first time ever in the Meet Exchange Server 2016 session. It is on track to be released later this calendar year following a public beta during the summer.

Meet Exchange Server 2016

Exchange Server
Preferred Architecture

Deploying Exchange Server 2016

clip_image002

clip_image004

clip_image006

OUTLOOK

The Office 2016 public preview was made available last week, allowing everyone to gain access to the new version of desktop Outlook. Outlook 2016 complements many of the features in Exchange Server 2016, but of course it is also unlocks new capabilities in Office 365. We also provided a close look at the new Outlook Mail and Outlook Calendar apps on Windows 10 mobile devices. Outlook for Mac 2016 was also demoed and discussed in detail at Ignite. Check out these sessions to get caught up on all of the Outlook news.

Desktop Outlook:
Evolved and Redefined

Outlook on Mobile Devices

Meet the new Outlook
for Mac 2016

DEPLOYMENT OPTIONS

We also made two announcements that provide new deployment options for Exchange Server 2013. First we announced support for deploying Exchange Server 2013 on Azure IaaS VMs for production use with Azure Premium storage. We have added this option to provide customers deployment flexibility, but we continue to recommend deploying Exchange server on physical hardware as the best and most cost effective way to run Exchange outside of Office 365. We also announced that Exchange 2013 will support use of Hyper-V dynamic VHDX (not VHD) disks. Previous guidance required use of fixed virtual disks for support. Refer to these sessions for more details on these topics.

Exchange on IaaS:
Concerns, Tradeoffs, and Best Practices

Exchange Storage for Insiders: It's ESE

Content

Ignite included a dizzying number of sessions which are all published on Channel 9. To help you find the most relevant content for Exchange–both on-premises and online–we have complied this table of quick links. You can view session recordings over the web, download them to your phone or tablet, and access PowerPoint decks used in the sessions. Happy learning.

Exchange Server:

New Feature Scenarios:

Office 365:

Outlook:

Compliance:

Office Developer:

See you next year

We had a fantastic time in Chicago, and we’re already thinking of ways to make year’s event even better. Mark your calendars for May 9-13, 2016 and we’ll see you there!

image

Jon Orton



from Exchange News Full Article