Hi All,

I have customer has Exchange 2010 deployed in one active directory site. He is looking to migrate to Exchange 2013 but with business need to deploy the new Exchange 2013 in different active directory site. So we will have 2 active directory sites one has Exchange 2010 and the other one has Exchange 2013. The WAN connection between those two active directory sites is slow little bit. So we suggested for the coexistence between Exchange 2010 and Exchange 2013 is to use separate name space for Exchange 2013. I want to ask about the coexistence plan for all the web services like OWA, Anywhere Auto-discover, Active Sync and this will work with Exchange 2010.

Ahmad Hashash, Senior Microsoft Systems Engineer, Voice Specialist

Hi every one,

I can't remove several users photos from their contacts

Some of them Work online mode and cache mode.

I remove the Value from Active Directory thumbnailphoto and logo Attribute i set it to (Not Set) value.

I run powershell command (Update-GlobalAddressList and Update-OfflineAddresBook).

Please Help, Can't Can not get rid of it.

Example:

Zvi Alikyan

Hi,

i am not able to send or receive mails internally from exchange 2013. the users who are at exchange 2013 server  mailbox are not able to send or receive mail and the mails are going to draft folder and from their they are not going.

aslam

Hi,

Hope someone can help, was just wondering if there were any tipe for setting up and securing Outlook Anywhere on a Single Exchange Server?  Are the steps for setting up just the same and are there any extra steps that may need to be carried out to secure the access if it is running on a single server?

Thanks,

D

Hi all,

Currently i am trying to setup exchange 2013 into coexist exchange server 2007. The setup has completed successfully, so does mailbox migration test from 2007 database to 2013 database.

My questions is, when i accessing 2013 ECP, select Server Menu, i can see the coexist 2007 server along with 2013 server, but on database tab, there are only databases belong to 2013. The user from 2007 database cannot access his mailbox from 2013 OWA.

My questions are:

1. Is it normal, that 2013 ECP will not listed the 2007 database? If not, what are the configurations i have missed?

2. If it is normal, then let say that i would like to do mailbox migration gradually (because it will take very long downtime to migrate a bunch of mailbox), how user can still access mail.domain.com from outside organization and the 2013 CAS will understand whether this user's belong to 2013 mailbox (user has been migrated) or 2007 mailbox (user that has not been migrated)?

Thanks.

I need to plan the Edge for their organization.

But I can not find any documentation on planning Edge.
In http://technet.microsoft.com/en-us/library/dd346701(v=exchg.141).aspx says you need to know: Connections per second; Messages per second; Average message size. But there is no calculation.

Help with the calculation requirements.
What information is necessary have for the calculations and how to calculate?

Hi,

I installed new Exchange server 2013 on a separate windows server 2012.

already finished migration database from old server exchange 2007 to new 2013.

Now, I have some issues as below:;

1. client can use OWA by server IP address only. cannot use by name.

2. outlook client cannot auto change setting to new server. new server name appear strange: "0c1d1c80-7eb5-45d9-9ac4-d8f3dbb18ea2@company.com"

3. after opening outlook, error noticed: "There is a problem with the proxy server's security certificate. The name on the security sertificate is invalid or deos not match the name of the target site mail.company.com. Outlook is unable to connect to the proxy server (error code 10)"

But test email send/receive is ok.

Can you please help or advice any solution.

Thanks.

Ha.

Hello

I need to be able to calculate how much Drive space I need to have on my MBX server.

318 MB Delivered Daily

90 MB Transfered Daily

This is the Statistics right now.

How can I calculate how much Space I need on my Database Drive and Transaction Drive for a good period of time?

How about the Transaction files?

I read that if I move/Migrate Mailboxes to Exhange 2013 and a Mailbox have a size of 5GB the Transaction Logs will be 5GB för that mailbox also.

But when Will the Transaction logs get moved(deleted) is it on the first Full backup after all the mailboxes is moved to our new Exchange 2013 Enviorment? Or will they disapear a short while just after we move a mailbox to the new Exchange Server?

There is Circular Loging but thats not a good Best Practise.

we are Migrating the mailboxes from a Lotus Notes/Domino Server.

If we have 300GB Mailboxsize total and migrate it to Exchange 2013:

Do I need to have a Database Drive of 300 GB and a Transaction Log Drive of 300 GB?

and consider that we Delivere 318 MB mail per day and Transfer 90 MB mail per day.

How much does the two Drives need to be so the Exchange 2013 Enviorment will continue to work maybe 50-100 Days without Expanding the Drives.

Thanks For all the Help!

Hello, everyone. While trying to install Exchange 2013 on my Windows Server 2008 R2 server I've ran into an impasse. What I have done so far was follow Microsoft's recommendations for pre installation at their site http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx (Instructions for Windows Server 2008 R2 Sp1; Mailbox server role or Combined Mailbox and Client Access Server roles). However, when I got to step 8 of installing the recommended software (Update KB2533623) I received an error that the update was not applicable for my server.

I decided to skip installing the last update (KB2533623) and proceeded with installing Exch 2013. During the installation I received several errors that all indicated that I could not proceed with the install because the account that I was using to install the installation was not a member of the Organization Management role group. When I tried to run powershell on my new server (that is a part of my domain), I receive the following error: 

Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\> Add-RoleGroupMember
Add-RoleGroupMember : The term 'Add-RoleGroupMember' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
At line:1 char:1
+ Add-RoleGroupMember
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Add-RoleGroupMember:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Some things to consider are:

• The install of Exchange 2013 is being installed on a brand new server that is a part of my work's domain and a server that has no other software installed on it
• My company still has a live, separate Exchange 2010 server
• I'm not yet trying to move any accounts over to my 2013 server, I only want the Exchange software loaded for the moment

I would greatly appreciate your assistance on this

Hello,

Our team is involved in migration of Exchange 2007 deployed in three sites. In every site an Exchange 2013 CAS and Mailbox role servers were deployed.

The question: should we change the AutoDiscoverServiceInternalUri  on Exchange 2007 CAS servers to point to Exchange 2013 CAS?

Exchange 2013 CAS will give to Exchange 2007 clients the correct legacy information (like legacy.contoso.com) instead of mail.contoso.com (primary namespace moved from Exchange 2007 to Exchange 2013)?

Thanks,

Andrei Moraru Endava

Hi All,

With E15 we have the Frontend & Backends with Scaled deployments.

1. I am working on getting multiple namespaces to work for OWA since we have some political issues.

2. It used to be simple in E2010 where there was no BackEnd dir on mailbox servers, it was straight.

3. I think its good now as well that I can just run the same command to specify what role the OWA Vdir is getting created Via roles.

4. Problem is cant get the cmdlet to work with -Role Switch. Below is the error.

[PS]C:\Windows\system32>New-OwaVirtualDirectory -WebSiteName "My Site" -Server cas1 -Role FrontEnd -WhatIf
Cannot process argument transformation on parameter 'Role'. Cannot convert value "FrontEnd" to type
"Microsoft.Exchange.Management.SystemConfigurationTasks.VirtualDirectoryRole". Error: "Unable to match the identifier
name FrontEnd to a valid enumerator name.  Specify one of the following enumerator names and try again: ClientAccess,
Mailbox"
    + CategoryInfo          : InvalidData: (:) [New-OwaVirtualDirectory], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,New-OwaVirtualDirectory
    + PSComputerName        : cas1.shared.local

>>>>>>. looking at TechNet and PS the parameter can be found as below & is a named position as well. I have tried

1. -Role FrontEnd

2. -Role:$Frontend

3. Don't know what to do ;-)

[PS] C:\Windows\system32>Get-Help New-OwaVirtualDirectory -Parameter role

-Role <ClientAccess | Mailbox>
    The Role parameter specifies the configuration that should be used when the virtual directory is created. The
    following are the values that can be used with this parameter:
    * FrontEnd Configures the virtual directory for use on a Client Access server.
    * BackEnd Configures the virtual directory for use on a Mailbox server.

    Required?                    false
    Position?                    Named
    Default value
    Accept pipeline input?       False
    Accept wildcard characters?  false

Setup:

5 MBX + HT in DAG (Multi-Site)

6 CAS Servers (Currently Running out of Default Website / Everythin OK Except that I have to run 12 Different OWA's)

...... Phewwwwwwwwwwww.

Sharique 'W@rbuG' Ahmed. 2 b or not 2 b

Hello,

I have successfully migrated 30 mailboxes from Exchange 2007 to exchange 2013 except 1 mailbox failed. It give me the following error:

username@mydomain.com

Status: Failed

Error:MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'gmsinc.local/GMSINC - Huntington Beach/Executive/Username‎'. --> Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'gmsinc.local/GMSINC - Huntington Beach/Executive/Username‎'.
Report: Download the report for this user

Please help.

Regards,

Jimmy

I recently migrated/transitioned from Exchange server 2003 sp2 to Exchange server 2010 sp3. It seems after the migration any calendar events that were not recurring have disappeared or been deleted. I have verifed that they are also missing from the OWA calendar. I also started migrating the mailboxes to outlook 365 and when logging in there they are missing also.

I get the error below when installing exchange 2013 in my Exchange 2010 Environment.

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
              $mailboxId = [Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter]::MigrationMailboxName;
              $dispName = "Microsoft Exchange Migration";
              $mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
              $migrationMailbox = $null;

              if ($mbxs.Length -eq 0)
              {
                  Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
                  $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                  if ($dbs.Length -ne 0)
                  {
                      Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
                      $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                      {
                          Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
                          $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
                      }
                  }
              }
              else
              {
                  $migrationMailbox = $mbxs[0];
              }

              # Set the Organization Capabilities and quotas needed for this mailbox
              if ($migrationMailbox -ne $null)
              {
                  Set-Mailbox -Arbitration -Identity $migrationMailbox -ProhibitSendReceiveQuota 300MB -ProhibitSendQuota 300MB -IssueWarningQuota 150MB -RecoverableItemsQuota 30GB -RecoverableItemsWarningQuota 20GB -UseDatabaseQuotaDefaults $false -SCLDeleteEnabled $false -SCLJunkEnabled $false -SCLQuarantineEnabled $false -SCLRejectEnabled $false -HiddenFromAddressListsEnabled $true -DisplayName $dispName -Management:$true -Force;
              }
              else
              {
                  Write-ExchangeSetupLog -Info ("Cannot find migration mailbox with name=$mailboxId.");
              }
          }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
              $mailboxId = [Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter]::MigrationMailboxName;
              $dispName = "Microsoft Exchange Migration";
              $mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
              $migrationMailbox = $null;

              if ($mbxs.Length -eq 0)
              {
                  Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
                  $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                  if ($dbs.Length -ne 0)
                  {
                      Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
                      $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                      {
                          Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
                          $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
                      }
                  }
              }
              else
              {
                  $migrationMailbox = $mbxs[0];
              }

              # Set the Organization Capabilities and quotas needed for this mailbox
              if ($migrationMailbox -ne $null)
              {
                  Set-Mailbox -Arbitration -Identity $migrationMailbox -ProhibitSendReceiveQuota 300MB -ProhibitSendQuota 300MB -IssueWarningQuota 150MB -RecoverableItemsQuota 30GB -RecoverableItemsWarningQuota 20GB -UseDatabaseQuotaDefaults $false -SCLDeleteEnabled $false -SCLJunkEnabled $false -SCLQuarantineEnabled $false -SCLRejectEnabled $false -HiddenFromAddressListsEnabled $true -DisplayName $dispName -Management:$true -Force;
              }
              else
              {
                  Write-ExchangeSetupLog -Info ("Cannot find migration mailbox with name=$mailboxId.");
              }
          }
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".

We are using VMware Esxi t.1 for our virtual servers. I am planning to install a new Exchange 2010 SP1 mailbox server for a set of users. I used the latest Exchange mailbox server calculator to determine the system requirements for the new server. There are 2 methods for creating the Exchange VM:

1. Create it as just a straight up VM. It will be a 200gb C: (system, app), 200 gb E: (DB), 40gb F: (log). Each disk will be a separate VMDK file that will be configured as a direct attached SCSI disks as far as the OS and app are concerned.
2. Create the VM with a 200gb C:, but then present via the iSCSI initiator on the VM the 200gb E: and 40gb F:.

The reason option #1 is most appealing is that it does not require the overhead of MPIO and the iSCSI initiator on the VM. It doesn't require any additional provisioning steps from our SAN type devices. Everything about that method is simple to build, support, expand, etc. 

The reason option #2 may be required. Our new blade vSphere ESX host datastores are on NetApp presented via NFS. Even though the VMs see their storage as local SCSI disks, I don't know that it qualifies as non-NAS by Microsoft. If they are STILL taking a hard line against NAS then we might be stuck with the far more complicated iSCSI route.

Are there any red flags for using method 1 in this case?

Thanks!

Hi guys,

Having issues with our Outlook 2010 clients in our pre-pilot deployment.

If mailboxes of the test users resides in DB01 and we restart the server currently holding the active database, the clients gets disconnected but it takes up to 1 hour before they are connected again, or if we restart Outlook.

If we do a database "switchover" from the shell or from within EAC the clients gets disconnected for 2-3 secs, then they connect perfectly.

We have the following Exchange Server 2013 environment:

- 3 Multirole servers hosting active/passive databases

- 1 multirole server hosting passive lagged copies

Hardware load balancer / HTTPS traffic for autodiscover.company.com and mail.company.com

- LB method: Round Robin (between server 1-3, not the lagged one)

- Persistance: none

- Monitor: SSL TCP, 5 sec interval, 2 sec time-out, 3 retries, 30 sec downtime

While we initiate a server reboot and the databases are mounted on another server (we monitor this via powershell), I can at the same time in outlook under Connection Status see that it lost some proxy servers and dont reconnect automatically.

If I press Reconnect, all proxyservers are removed and that list is empty...

So.. Howcome I can initiate a databaswe switchover and things are running perfect but when initiating a serverfailure it doesnt work. Is this HLB related, outlook related or Exchange related?

Help appreciated!

I performing cross-forest migration from Ex2003 to Ex2010, and I configured Shared SMTP namespace but when I send e-mails to a mailbox that migrated from Ex2003 to Ex2010 forest, I got the following error in E-mail:

A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. (NDR 5.4.6)

How can I solve this?

Thanks.

Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb | E-mail: msilforums@ben-shushan.net

Здравствуйте.

При установке нового Microsoft Exchange Server 2013 выдало ошибку и два предупреждения. При том, что установка проходит на полной версии Windows 2012 Server Standart. Были выполнены все необходимые действия из справки: http://technet.microsoft.com/ru-RU/library/bb691354%28v=exchg.150%29.aspx

Ошибка:
Обнаружена неподдерживаемая ОС. Роли серверов клиентского доступа и почтовых ящиков Exchange Server 2013 поддерживают Windows Server 2008 R2 с пакетом обновления 1 (SP1) или более поздние версии и Windows Server 2012.
Дополнительные сведения: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx

Предупреждение:
На этом компьютере необходимо установить пакеты фильтров Microsoft Office 2010 — версия 2.0. Загрузите программное обеспечение с веб-сайта http://go.microsoft.com/fwlink/?LinkID=191548.
Дополнительные сведения: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MSFilterPackV2NotInstalled.aspx

Предупреждение:
Для этого компьютера нужны пакеты фильтров Microsoft Office 2010 версии 2.0 с пакетом обновления 1 (SP1). Установите это ПО со страницы http://go.microsoft.com/fwlink/?LinkId=262358.
Дополнительные сведения: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MSFilterPackV2SP1NotInstalled.aspx