Tag: Exchange 2010

FREE Exchange 2010 Training available

Exchange 2010 Upgrade and Deployment (HOLO)

This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

Training includes the following curriculum:

Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

Course (Online): Configuring Mail Flow and Outlook Web Access

Course (Online): Moving Mailboxes to Exchange 2010

Course (Online): Moving Other Services to Exchange 2010 (Part 1)

Course (Online): Moving Other Services to Exchange 2010 (Part 2)
exchange 2010

Thanks to

Bryan Von Axelson

Migrating to Exchange 2010 & PDA Sync Issues

Some day’s ago I was testing some PDA’s Windows Mobile and Nokia’s for a Exchange Migration to Exchange 2010.

I created a little procure to test it.

1. PDA sync at first with ISA 2006 against Exchange 2007.

2. Shutdown the ISA 2006 Server

3. Starting the TMG Server

4. Checking if the PDA would sync. (The PDA should be sync with legacy.wardvissers.nl automatically )

5. Move the Mailbox to Exchange 2010 and check again if the PDA sync works.

 

Windows Mobile PDA (6.1).

1. Works fine

2.

3.

4. The PDA will be redirected to legacy.wardvissers.nl and pda sync works great. The User had nothing to do.

5. Moving the Mailbox to Exchange 2010 there is no problem. The user will automatically redirected from legacy.wardvissers.nl to webmail.wardvissers.nl with out any problems.

Nokia E71/E72 (Mail for Exchange Client 3.0.73)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Nokia E71/E72 With (Road Sync 4.0/5.0)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Conclusion

Moving PDA users to Exchange 2010 can be a pain in the ass. Best practice is create a list of all PDA users and move them first to Exchange 2010 and than all other users.

Exchange 2010 PST Import

Mailbox Import Role

When you want to import some pst’s you need some rights from doing this. This is a one time setting.

New-ManagementRoleAssignment ?Role ?Mailbox Import Export? ?User Administrator

Name                           Role              RoleAssigneeName  RoleAssigneeType  AssignmentMethod  EffectiveUserName

—-                           —-              —————-  —————-  —————-  —————-

Mailbox Import Export-Admin… Mailbox Import… Administrator     User              Direc

Set Mailbox Language

Set-MailboxRegionalConfiguration -Identity ward -Language nl-nl -DateFormat "dd-mm-yyyy

If you want this for multiple mailboxes you case the following script

$a=get-Mailbox *
$a | Set-MailboxRegionalConfiguration -language nl-nl -DateFormat "dd-mm-yyyy

Import a mailbox

New-MailboxImportRequest -Mailbox ward -FilePath \\win701\c$\ward.pst

Remove  newmailimportRequest

Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

Status

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics | ft TargetAlias,Percent*,BytesTransferred*

Multiple Mailboxes at the same time

Dir \\win701\c$\Exmerge-PSTS\*.pst | %{

    New-MailboxImportRequest ?Name ImportOfPst ?BatchName ImportPstFiles `

        ?Mailbox $_.BaseName ?FilePath $_.FullName

}

Exchange 2010 & Outlook 2010 Automatically Shared Mailboxes

When you set full access permissions with the Exchange 2010 management console on a mailbox,the user which has be giving full access right now there will filed a new property.
image

The property is MSExchDelegateListLink. You can check it with adsiedit.
image

When you open now Outlook 2010 you can now see that Wardtest is automatilly Added

image

And additional mailboxes is empty
image

When you migrating from Exchange 2007 to Exchange 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great Open-mouthed smile
Source

Exchange 2010 Getting an overview of all ActiveSync devices in the Exchange-organization

If you want a list with al the pda’s that are connected to your Exchange Organization.

You can use the following Powershell command let.
Get-Mailbox –resultsize unlimited | Get-ActiveSyncDevice | fl userdisplayname,DeviceModel,Devicetype, DeviceUserAgent > c:\pdas.txt

image

Microsoft Exchange Server 2010 Best Practices Covers SP1

Exchange 2010 Best Practices

If your are an Exchange Admin I can recommend the following book Microsoft Exchange Server 2010 Best Practices. It covers SP1. It  contains the following Chapters.

Part I  Preparing for Exchange Server 2010

Chapter 1: Introducing Exchange Server 2010

Chapter 2: Exchange Deployment Projects

Chapter 3: Exchange Environmental Considerations

Part II  Designing Exchange Server 2010

Chapter 4: Client Access in Exchange 2010

Chapter 5: Routing and Transporting

Chapter 6: Mailbox Services

Chapter 7: Edge Transport and Messaging Security

Chapter 8: Automated Message Processing, Compliance, and Archiving

Chapter 9: Unified Messaging

Chapter 10: Federated Delegation

Chapter 11: Designing High Availability

Chapter 12: Backup, Restore, and Disaster Recovery

Chapter 13: Hardware Planning for Exchange Server 2010

Part III  Upgrading to Exchange Server 2010

Chapter 14: Upgrading from Exchange Server 2003 and Exchange Server 2007

Part IV  Deploying and Managing Exchange Server 2010

Chapter 15: Preparing for a Deploying Exchange Server 2010

Chapter 16: Managing Exchange

Chapter 17: Operating and Troubleshooting Exchange Server 2010

This book is also not a preparation guide for Exam 70-662: TS: Microsoft Exchange Server 2010, Configuring, or Exam 70-663: Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010, even though when you apply the knowledge and experience covered in this book, it will help you to pass these exams.

Exchange 2007 OWA Redirect Bug Introduced with Exchange 2010 SP1

The Customer where I now work has a mix of Exchange 2007 and Exchange 2010 users.  It seems that SP1 has introduced a obvious bug.  Before I get into that, I’ll give some background on how Exchange 2010 coexists with previous versions of Exchange.
When you have a mix of Exchange 2010 and older versions in your environment, you have to do a bit of work to make the two work together for your external users.  In a nutshell, you use Exchange 2010 Client Access Server (CAS) as your primary entry point for all external users. 
Say you use webmail.wardvissers.nl as your externally accessible URL.  If an Exchange 2010 user logs in from the Internet, the Exchange 2010 CAS will do its thing and the user will get a nice Outlook Web App screen.
If an Exchange 2007 user logs in using webmail.wardvissers.nl, the Exchange 2010 CAS will redirect the user to an externally accessible Exchange 2007 CAS using a different URL (like legacy.wardvissers.nl).  The redirection is silent, but the user may notice their browser changed to legacy.wardvissers.nl
How the redirect is handled is managed by the LegacyRedirectType setting in the Exchange 2010 OWA virtual directory.  In most cases, LegacyRedirectType is set to Silent.  To see what the setting is in your environment, run:Get-OWAVirtualDirectory -Server <CASservername> | FL Identity, LegacyRedirectType

In SP1, this redirection is no longer silent.  When your Exchange 2007 user logs in via webmail.wardvissers.nl, they are presented with this screen:

The text reads:

A temporary change has occurred that requires you to connect to a different server.  To connect, click the button below.  For security reasons, you’ll be asked to enter your user name and password again.

Sure enough, when you click Connect, you are redirected to legacy.wardvissers.nl, where you have to re-enter your user information.
Thankfully, the same sort of thing doesn’t seem to happen with Outlook Anywhere or ActiveSync clients.
I checked the LegacyRedirectType value on my 2010 SP1 CAS boxes and they are all still set to Silent.  The issue occurs because the OWA virtual directory value for LegacyRedirectType is being ignored.  This is an extraordinarily unfortunate thing to have been introduced with SP1.   If you have a mixed Exchange 2007/2010 environment, I suggest you wait until the rollup 2 is out before deploying SP1. 

Update 15 December 2010

Update 2 for Exchange 2010 and the fix is there described 2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

You can download the rollup HERE

Exchange SP1 2010 Setting rights with Public Folder Management Console

For Exchange 2007 you had PFDAVAdmin to set rights on the Public Folder store.

For Exchange 2010 (RTM & SP1) you have the tool ExFolder to set rights on the public Folder store.

But the Exchange Team did a great job to add Public Folder Rights to the Public Folder Management Console.

When you right click on the a public folder you can set permission on two ways.

1. Right click on the public folder and choose Manage Settings

I give my self Owner rights for this little demo.

image image
imageimage
imageimage
image

2. Select Properties from the public folder and then select the Permissions tab.
image

Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1

Microsoft released some days ago Forefront TMG Update 1:

SafeSearch Enforcement. Forefront TMG can enforce blocking adult text, images and videos from search results by popular search engines. SafeSearch can be enforced on specific groups or to the entire organization.
Including non-primary URL filtering categorizations. Forefront TMG uses an algorithm to select a URL’s “primary” category from among up to four categorizations provided by Microsoft Reputation Services (MRS). In Update 1 you can control access to sites that match any of the non-primary categorizations provided by MRS. For example, a URL with a primary categorization of News can now match a rule by any of its non-primary categorizations (such as Web Mail).
Support for Exchange 2010 SP1
Bug fixes and various other improvements. For details, see http://go.microsoft.com/fwlink/?LinkId=201151.

Download

Translate »