Choosing Yammer, Skype, Onedrive, Groups, Teams or Sharepoint

Yammer, Skype, Onedrive, Groups, Teams, Sharepoint.

It’s Not About Choosing, But Knowing When to Use Each

Here are my notes:

Yammer

Yammer is an enterprise social network. It is an enhanced communication platform to build a culture of transparency, keeping everyone from leadership to First line Workers informed, aligned, and moving forward. Build communities of interest to bring people together around shared topics, interests, or areas of practice. Gather ideas and feedback from across your network of colleagues to build on the work of others and achieve better outcomes.

Yammer is a company’s private social network. Team members can instantly exchange latest ideas about their projects, events or just share information.

Yammer does not include video-chat,

Yammer is Real-time conversations, compatible with other apps (Github, Zendesk), file-sharing, co-editing, compatible with desktop & mobile, HIPAA certified.

Yammer is a Facebook and Twitter hybrid made specifically with business objectives in mind.

A partner can join a Yammer network created and post questions. Each thread that is started gets its own URL, as the nature of these conversations is often expected to be with delayed responses, so it’s important to be able to link back to it. In this type of scenario, Yammer is the perfect tool.

Yammer works well when it’s expected to have a longer response time to conversations (hours/days)

Yammer works well when we need to use a conversation as a reference somewhere else (Yammer produces unique URLs to each thread)

Yammer works well when you want to isolate external communications to a network, but give complete access to guests to see and interact with current and past conversations.

Skype

Skype is for doing things together, whenever you’re apart. Skype’s text, voice and video make it simple to share experiences with the people that matter to you, wherever they are.

Skype for Business provides with users instantly and in real-time with online meetings, video calls and instant messaging.

Skype is instant and one time. You set up a call, a meet or a chat with a single person or group.

Microsoft’s road map has Skype being rolled into Teams.

Onedrive

OneDrive is an Internet-based storage platform. Think of it as a hard drive in the cloud, which you can share, with a few extra benefits thrown in.

OneDrive for Business is meant to be your “me” place at the office.

You get a personal document library, and an offline sync engine

If a document is a collaborative effort related to a project, then saving to an Office 365 Team site might be a better choice than onedrive

OneDrive for Business is a place where you can store files from your computer into the cloud, and access them from any device, or share them with others.

Documents you place in OneDrive for Business are private until you share them. This makes OneDrive for Business your best option for draft documents or personal documents that no one else needs to see.

OneDrive for Business is a place where you can store files that you plan to share individually and with a limited scope or lifecycle.

You might save your files to Onedrive if you can’t identify an existing Office 365 Team site where your document belongs, and you don’t think the purpose of the document warrants creating a new one.

Groups

Microsoft Office 365 Groups is a cloud collaboration feature for communication, coordinating group efforts and sharing information. Office 365 Groups allows users to create and manage ad hoc “groups” for collaboration.

Microsoft Groups provides email content, calendar sharing and storage space

The Office 365 Group will control membership in one central location, while giving the administrators the peace of mind that comes with knowing that their content is staying within a perimeter they have access to.

When a meeting gets created for a group of which you are a member, it will automatically replicate in your calendar with a different name so you know it comes from the group’s calendar.

Doesn’t include advanced features of SharePoint Document libraries, like versioning, views, metadata and workflow.

Groups work best when you have a department that answers requests, like sales, the IT helpdesk, or customer support. They can use a shared email address to receive and review emails, schedule meetings with customers in the calendar and use tags on email to take ownership and share progress in OneNote.

Since Shared mailboxes cannot be added to a mobile device. A Groups calendar can.

  • Shared mailboxes can have sub-folders in the mailbox, whereas Group mailboxes can’t.
  • Shared mailboxes have more granular permissions available than Groups do.

If it’s a requirement for your employees to know the details about time and dates of events, and especially to be able to access this information from mobile, the Groups feature allows them to access their calendar from the field to view any meetings/events that were added via the Groups feature.

Teams

Microsoft Teams is a platform that combines workplace chat, meetings, notes, and attachments. The service integrates with the company’s Office 365 subscription office productivity suite, including Microsoft Office and Skype, and features extensions that can integrate with non-Microsoft products.

Microsoft teams build on the foundation of Groups as a “chat-based workplace,” where all communication (whether in Skype, email, text, etc.) happens in one place.

With Teams requests can be funneled to appropriate levels depending on the complexity of the issue. So a Level 1 support person who needs assistance can send the question and it will be seen by all members in Level 2 support, and get a reply to it. If the question requires additional communication with the next level, they can then be included in the discussion.

In Teams you can assign people to a task, or tag them. They will get an email notification and can collaborate using OneNote.

In Teams, when you need to do a presentation and have several people working on it, each doing different subtasks, it’s easy for you to tag and track each person in the channel. They can then upload their work and you can review it in the subchannel created for them. If at any point they require assistance from a colleague, they can tag that person to send an email notification. This allows you to maintain an overview on what each person is doing.

If a document is a collaborative effort related to a project, then saving to a Team site might be a better choice than onedrive

You should save documents to a team site library when you want team members to recognize the document as being relevant to an ongoing project, You want to spread ownership and permissions across a wider collection of people, you want permissions to be granted on a site basis, instead of on individual documents, other project-related documents are already saved to the team site library, and others expect to find it there, you want to create a check-in workflow that assigns the document to someone else.

If a documents grow in importance and become relevant to a project that document can be copied from OneDrive for Business to a team site.

SharePoint

Microsoft SharePoint is a browser-based collaboration and document management/collaboration platform. It’s a content management system. … SharePoint is an enterprise information portal that can be configured to run Intranet, Extranet and Internet sites.

SharePoint is the best option for collaborating using specific items such as tickets, documents, or inventory and Governance, consistency, and structure are very important.

Includes advanced features such as Document libraries, versioning, views, metadata, wikis, workflows, and document publishing.

Workflow for things like Vacation Calendar with approval process.

A project task list can be set up where people can have parts of the project assigned to them. Once a task is completed, the person that finished it marks it complete, and the project can go on to the next person. This makes tasks very easy to track, report and manage.

SharePoint is the only fully on-prem option

 

 

 

 

 

Advertisements

Exchange Server build numbers

Product name

Release date

Build number

Exchange Server 2016 RTM  (2013 SP1)

2015-Oct-01

15.01.0225.042

Exchange Server 2016 Preview (2013 SP1 Beta)

2015-Jul-22

15.01.0225.016

Exchange Server 2013 CU10

2015-Sep-15

15.00.1130.007

Exchange Server 2013 CU9

2015-Jun-17

15.00.1104.005

Exchange Server 2013 CU8

2015-Mar-17

15.00.1076.009

Exchange Server 2013 CU7

2014-Dec-09

15.00.1044.025

Exchange Server 2013 CU6

2014-Aug-26

15.00.0995.029

Exchange Server 2013 CU5

2014-May-27

15.00.0913.022

Exchange Server 2013 SP1

2014-Feb-25

15.00.0847.032

Exchange Server 2013 CU3

2013-Nov-25

15.00.0775.038

Exchange Server 2013 CU2

2013-Jul-09

15.00.0712.024

Exchange Server 2013 CU1

2013-Apr-02

15.00.0620.029

Exchange Server 2013 RTM

2012-Dec-03

15.00.0516.032

Update Rollup 11 for Exchange Server 2010 SP3

2015-Sep-15

14.03.0266.002

Update Rollup 10 for Exchange Server 2010 SP3

2015-Jun-17

14.03.0248.002

Update Rollup 9 for Exchange Server 2010 SP3

2015-Mar-17

14.03.0235.001

Update Rollup 8v2 for Exchange Server 2010 SP3

2014-Dec-12

14.03.0224.002

Update Rollup 8v1 for Exchange Server 2010 SP3 (recalled)

2014-Dec-09

14.03.0224.001

Update Rollup 7 for Exchange Server 2010 SP3

2014-Aug-26

14.03.0210.002

Update Rollup 6 for Exchange Server 2010 SP3

2014-May-27

14.03.0195.001

Update Rollup 5 for Exchange Server 2010 SP3

2014-Feb-24

14.03.0181.006

Update Rollup 4 for Exchange Server 2010 SP3

2013-Dec-09

14.03.0174.001

Update Rollup 3 for Exchange Server 2010 SP3

2013-Nov-25

14.03.0169.001

Update Rollup 2 for Exchange Server 2010 SP3

2013-Aug-08

14.03.0158.001

Update Rollup 1 for Exchange Server 2010 SP3

2013-May-29

14.03.0146.000

Exchange Server 2010 SP3

2013-Feb-12

14.03.0123.004

Update Rollup 8 for Exchange Server 2010 SP2

2013-Dec-09

14.02.0390.003

Update Rollup 7 for Exchange Server 2010 SP2

2013-Aug-03

14.02.0375.000

Update Rollup 6 for Exchange Server 2010 SP2

2013-Feb-12

14.02.0342.003

Update Rollup 5v2 for Exchange Server 2010 SP2

2012-Dec-10

14.02.0328.010

Update Rollup 5 for Exchange Server 2010 SP2

2012-Nov-13

14.03.0328.005

Update Rollup 4v2 for Exchange Server 2010 SP2

2012-Oct-09

14.02.0318.004

Update Rollup 4 for Exchange Server 2010 SP2

2012-Aug-13

14.02.0318.002

Update Rollup 3 for Exchange Server 2010 SP2

2012-May-29

14.02.0309.002

Update Rollup 2 for Exchange Server 2010 SP2

2012-Apr-16

14.02.0298.004

Update Rollup 1 for Exchange Server 2010 SP2

2012-Feb-13

14.02.0283.003

Exchange Server 2010 SP2

2011-Dec-04

14.2.247.5

Update Rollup 8 for Exchange Server 2010 SP1

2012-Dec-10

14.01.0438.000

Update Rollup 7 v3 for Exchange Server 2010 SP1

2012-Nov-13

14.01.0421.003

Update Rollup 7 v2 for Exchange Server 2010 SP1

2012-Oct-10

14.01.0421.002

Update Rollup 7 for Exchange Server 2010 SP1

2012-Aug-08

14.01.0421.000

Update Rollup 6 for Exchange Server 2010 SP1

2011-Oct-27

14.01.0355.002

Update Rollup 5 for Exchange Server 2010 SP1

2011-Aug-23

14.1.339.1

Update Rollup 4 for Exchange Server 2010 SP1

2011-Jul-27

14.1.323.6

Update Rollup 3 for Exchange Server 2010 SP1

2011-Apr-06

14.01.0289.007

Update Rollup 2 for Exchange Server 2010 SP1

2010-Dec-09

14.01.0270.001

Update Rollup 1 for Exchange Server 2010 SP1

2010-Oct-04

14.1.255.2

Exchange Server 2010 SP1

2010-Aug-23

14.01.0218.015

Update Rollup 5 for Exchange Server 2010

2010-Dec-13

14.0.726.0

Update Rollup 4 for Exchange Server 2010

2010-Jun-10

14.0.702.1

Update Rollup 3 for Exchange Server 2010

2010-Apr-13

14.0.694.0

Update Rollup 2 for Exchange Server 2010

2010-Mar-04

14.0.689.0

Update Rollup 1 for Exchange Server 2010

2009-Dec-09

14.0.682.1

Exchange Server 2010

2009-Nov-09

14.00.0639.021

Update Rollup 17 for Exchange Server 2007 SP3

2015-Jun-17

08.03.0417.001

Update Rollup 16 for Exchange Server 2007 SP3

2015-Mar-17

08.03.0406.000

Update Rollup 15 for Exchange Server 2007 SP3

2014-Dec-09

08.03.0389.002

Update Rollup 14 for Exchange Server 2007 SP3

2014-Aug-26

08.03.0379.002

Update Rollup 13 for Exchange Server 2007 SP3

2014-Feb-24

08.03.0348.002

Update Rollup 12 for Exchange Server 2007 SP3

2013-Dec-09

08.03.0342.004

Update Rollup 11 for Exchange Server 2007 SP3

2013-Aug-13

08.03.0327.001

Update Rollup 10 for Exchange Server 2007 SP3

2013-Feb-11

08.03.0298.003

Update Rollup 9 for Exchange Server 2007 SP3

2012-Dec-10

08.03.0297.002

Update Rollup 8-v3 for Exchange Server 2007 SP3

2012-Nov-13

08.03.0279.006

Update Rollup 8-v2 for Exchange Server 2007 SP3

2012-Oct-09

08.03.0279.005

Update Rollup 8 for Exchange Server 2007 SP3

2012-Aug-13

08.03.0279.003

Update Rollup 7 for Exchange Server 2007 SP3

2012-Apr-16

08.03.0264.000

Update Rollup 6 for Exchange Server 2007 SP3

2012-Jan-26

8.03.0245.002

Update Rollup 5 for Exchange Server 2007 SP3

2011-Sep-21

8.03.0213.001

Update Rollup 4 for Exchange Server 2007 SP3

2011-May-28

8.03.0192.001

Update Rollup 3-v2 for Exchange Server 2007 SP3

2011-Mar-30

8.03.0159.002

Update Rollup 2 for Exchange Server 2007 SP3

2010-Dec-10

8.03.0137.003

Update Rollup 1 for Exchange Server 2007 SP3

2010-Sep-09

8.03.0106.002

Exchange Server 2007 SP3

2010-Jun-07

8.03.0083.006

Update Rollup 5 for Exchange Server 2007 SP2

2010-Dec-07

8.2.305.3

Update Rollup 4 for Exchange Server 2007 SP2

2010-Apr-09

8.2.254.0

Update Rollup 3 for Exchange Server 2007 SP2

2010-Mar-17

8.2.247.2

Update Rollup 2 for Exchange Server 2007 SP2

2010-Jan-22

8.2.234.1

Update Rollup 1 for Exchange Server 2007 SP2

2009-Nov-19

8.2.217.3

Exchange Server 2007 SP2

2009-Aug-24

8.02.0176.002

Update Rollup 10 for Exchange Server 2007 SP1

2010-Apr-13

8.1.436.0

Update Rollup 9 for Exchange Server 2007 SP1

2009-Jul-16

8.1.393.1

Update Rollup 8 for Exchange Server 2007 SP1

2009-May-19

8.1.375.2

Update Rollup 7 for Exchange Server 2007 SP1

2009-Mar-18

8.1.359.2

Update Rollup 6 for Exchange Server 2007 SP1

2009-Feb-10

8.1.340.1

Update Rollup 5 for Exchange Server 2007 SP1

2008-Nov-20

8.1.336.1

Update Rollup 4 for Exchange Server 2007 SP1

2008-Oct-07

8.1.311.3

Update Rollup 3 for Exchange Server 2007 SP1

2008-Jul-08

8.1.291.2

Update Rollup 2 for Exchange Server 2007 SP1

2008-May-09

8.1.278.2

Update Rollup 1 for Exchange Server 2007 SP1

2008-Feb-28

8.1.263.1

Exchange Server 2007 SP1

2007-Nov-29

8.01.0240.006

Update Rollup 7 for Exchange Server 2007

2008-Jul-08

8.0.813.0

Update Rollup 6 for Exchange Server 2007

2008-Feb-21

8.0.783.2

Update Rollup 5 for Exchange Server 2007

2007-Oct-25

8.0.754.0

Update Rollup 4 for Exchange Server 2007

2007-Aug-23

8.0.744.0

Update Rollup 3 for Exchange Server 2007

2007-Jun-28

8.0.730.1

Update Rollup 2 for Exchange Server 2007

2007-May-08

8.0.711.2

Update Rollup 1 for Exchange Server 2007

2007-Apr-17

8.0.708.3

Exchange Server 2007

2007-Mar-08

8.0.685.25

Exchange Server 2003 post- SP2

2008-Aug-01

6.5.7654.4

Exchange Server 2003 post-SP2

2008-Mar-01

6.5.7653.33

Exchange Server 2003 SP2

2005-Oct-19

6.5.7683

Exchange Server 2003 SP1

2004-May-25

6.5.7226

Exchange Server 2003

2003-Sep-28

6.5.6944

Exchange 2000 Server build numbers

Product name

Release date

Build number

Exchange 2000 Server post-SP3

August 2008

6.0.6620.7

Exchange 2000 Server post-SP3

March 2008

6.0.6620.5

Exchange 2000 Server post-SP3

August 2004

6.0.6603

Exchange 2000 Server post-SP3

April 2004

6.0.6556

Exchange 2000 Server post-SP3

September 2003

6.0.6487

Exchange 2000 Server SP3

July 18, 2002

6.0.6249

Exchange 2000 Server SP2

November 29, 2001

6.0.5762

Exchange 2000 Server SP1

June 21, 2001

6.0.4712

Exchange 2000 Server

November 29, 2000

6.0.4417

Exchange Server 5.5 build numbers

Product name

Release date

Build number

Exchange Server version 5.5 SP4

November 1, 2000

5.5.2653

Exchange Server version 5.5 SP3

September 9, 1999

5.5.2650

Exchange Server version 5.5 SP2

December 23, 1998

5.5.2448

Exchange Server version 5.5 SP1

August 5, 1998

5.5.2232

Exchange Server version 5.5

February 3, 1998

5.5.1960

Exchange Server 5.0 build numbers

Product name

Release date

Build number

Exchange Server 5.0 SP2

February 19, 1998

5.0.1460

Exchange Server 5.0 SP1

June 18, 1997

5.0.1458

Exchange Server 5.0

May 23, 1997

5.0.1457

Exchange Server 4.0 build numbers

Product name

Release date

Build number

Exchange Server 4.0 SP5

May5, 1998

4.0.996

Exchange Server 4.0 SP4

March 28, 1997

4.0.995

Exchange Server 4.0 SP3

October 29, 1996

4.0.994

Exchange Server 4.0 SP2

July 19, 1996

4.0.993

Exchange Server 4.0 SP1

May 1, 1996

4.0.838

Exchange Server 4.0 Standard Edition

June 11, 1996

4.0.837

https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

Quest Migration Manager doesn’t see the Network

From within Quest Migration Manager I was getting the following error

“the list of servers for this workgroup is not currently available”

Wins was set up and working.

But when I would turn on Network Sharing, it would just turn off again.

To make it work I had to enable the 2 following services.

  • SSDP Discovery
  • UPnP Device Host

Once these were set I could turn on Network Discovery and Quest Migration Manager was happy.

image

Creating Users from a Spreadsheet with New-ADUser

Working in my lab, I needed a script to create some AD users. Here is what I came up with.

 

 

##################### Start of script ########################
#########################################################
#########################################################
#########################################################
### Written by Don Wilwol
###
### 3-2014
### atthedatacenter.wordpress.com
###
###Creates users from a CSV file
###Just add firstname, lastname and (important) header in the input file
###
###It logs to the log file path
###It sets the SamAccountName to first initial lastname
##It sets the UPN to the SamAccountName@domain
###It sets a primary Email address as the UPN
###It sets the SIP address as the UPN
###It surpresses the errors in the shell
###to see the errors rem out $ErrorActionPreference = "SilentlyContinue"
###Creation of a user with appended suffix is logged
###The script defaults to a password of P@ssw0rd" but the line can be changed
###Change the line with this on for "first initial, last initial, !12345"
# -AccountPassword(Convertto-Securestring -AsPlaintext ($_.Firstname.SubString(0,1) + $_.lastname.SubString(0,1) + "!12345") -Force)`

$date = (get-date).toString(‘yyyy-MM-dd’)

 

##Set input file path
$CSVPath ="c:\users.csv"

##Set YOUR domain name
$DomainN = "student.Source.lab"

##Set the OU Path you would like the users created
$Path = "OU=TestUsers,DC=Source,DC=Lab"

### Set the description for this group of users
$Description = "Student Account for Some Year, Maybe 2019"

###Set the log file path
$LogFile = "C:\$date-CreateUserlogfile.txt"

#########################################################
#########################################################
#########################################################

$ErrorActionPreference = "SilentlyContinue"

 

import-csv $CSVPath | foreach {

$SamAccountname = ($_.Firstname.SubString(0,1) + $_.lastname)
If(get-ADUser $SamAccountname) {$SamAccountname = $SamAccountname + "2";write-output "**Secondary SamAccountName**  $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "3";write-output "**3rd SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "4";write-output "**4th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "5";write-output "**5th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "6";write-output "**6th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "7";write-output "**7th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "8";write-output "**8th SamAccountName** $SamAccountName" >> $LogFile}

 

$error.clear()
$UPN = $SamAccountname + "@$DomainN"
$Dname = ($_.Firstname + " " + $_.lastname)
new-aduser -Path $Path `
-Name $Dname -GivenName $_.Firstname`
-Surname $_.Lastname`
-AccountPassword(Convertto-Securestring -AsPlaintext "P@ssw0rd" -Force)`
-enabled $true `
-EmailAddress $UPN `
-SamAccountname $SamAccountname  `
-Description $Description `
-DisplayName $Dname `
-ChangePasswordAtLogon $True
write-host   ("Creating User (" + $SamAccountname + ")  " + $_.Firstname + " " + $_.lastname)
write-output "" >> $LogFile
write-output ("Creating User (" + $SamAccountname + ")  " + $_.Firstname + " " + $_.lastname) $error >> $LogFile
write-output "" >> $LogFile 

Set-Aduser -Identity $SamAccountname -Add @{userPrincipalName = $UPN;`
proxyAddresses = "SMTP:$UPN","SIP;$UPN";`
}
}

##################### End of script ########################

 

The spreadsheet is a very simple format.

firstname,lastname

Joe,Somebody

Harry,Helper

Fred,Flinstone

Register a DAG IP (ipconfig /registerdns for DAG’S)

I ran into an issue recently where I needed to register the IP of a DAG. I discovered this wasn’t well documented and it took a while to figure out how to get it registered.

 

I first tried running ipconfig /registerdns on the primary active manager. To find the primary active manager you must run

 

get-databaseavailabilitygroup <name> -status | select name,primaryactivemanager

 

But that did not work. What does work is running,

cluster . res "Cluster Name" /registerdns

on any of the cluster nodes.

 

Also note:

The DAG will attempt to register on its own at some random time within 2 hours of midnight.

 

Hope it helps.

dw

Co-existence With Exchange 2013

As of this writing, co-existence with Exchange 2007 and Exchange 2013 and Exchange 2010 and Exchange 2013 will come later on.

http://technet.microsoft.com/en-us/library/aa996719.aspx

 

No co-exitence with Exchange 2003 is planned, so get to 2010 asap.

 

Right now, if you want to play around in your lab, you are somewhat limited. Remember no co-existence is supported at this time, but some work can be done if you’re just looking to learn.

 

Installing Exchange 2013 into a Exchange 2013 organization isn’t possible.

the installation stops with an Error that says “Exchange 2013 all exchange 2010 servers in the organization must have Exchange 2010 Service Pack 3 or later installed” and points to this.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.e15e14CoexistenceMinMajorVersionrequirement.aspx

MustHave 2010 SP3 error

 

So no playing around for the Exchange 2010-2013 configurations until Exchange 2010 SP3 is released.

 

Installation into an Exchange 2007 org went as planned.

 

Note a warning stating no Exchange 2010 can be installed into the organization after the Exchange 2013 setup was complete.

 

A few notes on the installation. I installed with the Administrator account which had its mailbox on the Exchange 2007 server. This meant that I couldn’t open the Exchange 2013 ECP. To fix it, I created a user in AD with the appropriate permissions and ran the enable-mailbox command from the Exchange shell. I’m sure I could have also run the New-MoveRequest command and moved a mailbox as well.

Web mail Gibberish from 2003 to 2010 Exchange

I was migrating from Exchange 2003 to Exchange 2010. Email was configured to route through Exchange 2010 and out to the Internet if needed. If a user sent and email from the Web interface of Exchange 2003 to an outside internet recipient, the message looked like the following

䠼TML dir=ltr>䠼EAD>㰊META content="text/html; charset=unicode" http-equiv=Content-Type>㰊META name=GENERATOR content="MSHTML 8.00.6001.19328"㰾/HEAD>㰊BODY> 䐼IV㰾FONT color=#000000 size=2 face=Arial>OWA 2003 Gibberish Test㱴/FONT>⼼DIV>⼼BODY㰾/HTML>

 

Note the red was the actual message. If the same thing was sent to a recipient on Exchange 2010 the message appeared just fine.

 

The issue happened once a disclaimer was set up as a transport rule. So the disclaimer was causing the issue. Disable the transport rule, the issue goes away. Enable the rule, it comes back.

 

Cause:

This problem occurs because Outlook Web Access for Exchange 2003 sets an e-mail message to an incorrect character set. When the message is routed by the Exchange 2007 or 2010 server that has the Disclaimer rule enabled, the e-mail message is converted to incorrect HTML tagging based on the incorrect character set. Then, the message is corrupted by the incorrect tagging.

 

The fix?

A patch just for this issue. Once the patch was applied to all of the Exchange 2003 servers, all was well.

 

http://support.microsoft.com/kb/935489

 

hope it helps

dw