Hello Community

    With Outlook 2007 you can create a link that when clicked Exchange Server appears but how
do you make "New Message/Send to" appear and the user's email address of your choice appear automatically by default?

    Thank you
    Shabeaut

Hi,

I am running with Exchange 2010 SP1 in DAG & CAS/HUB in cluster mode. need to upgrade to SP3. few things need to know

1. Schema upgrade will be done I as read in the article. can this create any issue? what is the best measure to safeguard any problems of schema upgrade. Do we do this along with exchange setup or we should run schema upgrade prior to install exchange 2010 SP3?

2. Any impact on active sync, outlook anywhere & HUB connectors side post SP3?

3. Do we need to take any exchange related backups as we are running mailbox, CAS/HUB servers in redundant mode?

Please share your experiences.

Regards,

VIpin

I am starting my transition to Exchange 2013 and I have a few questions. 

First, I am installing my mailbox servers. The management want a phased rollout and install the CAS servers next month. Are the mailbox servers OK to run on their own until then?

Second, I have some new and old namespaces, and I want to know how I configure these.

Old names:

internal webmail : https://webmail.domain.com.owa

activesync: webmail.domain.com

internal autodiscover: autodiscover.domain.com

CAS Array name: mapi.domain.com (MXserver10 and MXserver11)

We also have a DR with:

DRactivesync: DRwebmail.domain.com

We want to use the following names in our environment. Is it still wise to have different names for our DR activesync?

We are not using a CAS Array. We will be running exchange.domain.com as a CNAME to both serverCAS01 and serverCAS02

EAS: email.domain.com

DR EAS DRemail.domain.com

Am I missing something? Please help! How do I go about setting these names so that all mail for my 2010 servers gets routed through Exchange 213, and so that there is no disruption when i set these things up.

We are running Exchange 2010.  For our e-mail addresses we use the formatfirstname.lastname@domain name.    This works fine until we get a username with a number after it.

E.g. 1st John Doe ->  jdoe - > John.Doe@happy.com

       2nd John Doe -> jdoe1 -?  John.Doe1@happy.com

       3rd  John Doe - > jdoe2 -> John.Doe2@happy.com

Is there any way to configure the e-mail addresses in Exhange so that the correct e-mail address is associated with the account when the exchange mailbox is created.  Currently we have to manually fix any account that do exactly matchfirstname.lastname@happy.com 

Windows Server 2013; Exchange Server 2013 with Cumulative Update 1

Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with

[xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.  See the Exchange setup log for more information on this error.
[xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
[xxx] [0] [ERROR] The supplied credential is invalid.

(Crosses - XXX - replace original values.)

I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely conincidental:

The Security System could not establish a secured connection with the server ldap/xxx.xxx/xxx.xxx@XXX.XXX. No authentication protocol was available.

Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

When I log on as Administrator to either .../ecp or .../owa, authenticaion, I believe, succeeds but then I get HTTP 500.

When I do this on another server hosting the Exchange server for the same Organisation, I succeed - can get into both the mailbox and the Exchange server ECP interface. Unlike the first server, this Exchange server does not host any mailboxes but otherwise has identical Exchange roles installed.

When I log on as another non-administrator user to the first server that hosts mailboxes, I again succeed.

The problem seems to relate the administrative interface that the first server somehow fails to display but what could be the reason for that?

Thank you.

Hello,

I am migrating all on-premise exchange 2010 SP3 to Exchange 2013 SP1. I am testing mailbox migrations, each mailbox that gets moved to 2013 the user keeps getting prompted for credentials. I have read several posts in the forums yet none which solve my problem. Can someone point me in the right direction. All 2013 setting are currently at default.

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

Hello,

I would like to install Exchange 2013 into my existing Exchange 2010 / Office 365 environment but I do not want to introduce it into "production" until I had a play with it and configured it the way I want to before I allow it to accept connections and proxy to EXCH2010 for clients connecting up.

My understanding is until I update the AD SCP to point to new server and my internal/external DNS, the new EXCH2013 installation will not be detected by clients.

I also need to make sure the EXCH2013 will not modify any settings on my existing EXCH2010 (such as virtual directory URLs, etc..)

Is this correct?

Hi guys,

I'm hoping for a bit of assistance. I have stepped into an environment where there is one production Exchange 2010 server and one Exchange 2013 server. The Exchange 2013 server is in a unrecoverable state however it contains the domain administrators mailbox and therefore I cannot remove it manually. As it was a vm, I took it offline, created an identical server (name, os version(Windows 2008 R2 with latest updates), ip address etc.), installed all the prerequisite components and then ran setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms. Everything runs through successfully until it gets to the Mailbox role: Transport service where it fails with "Unable to set shared config DC.". After some searching on Google, it suggests that ipv6 is disabled on the DC. We have two DC's in our environment and both have ipv6 enabled as does the exchange server. If I try to re-run the installation for the role alone, i.e. Setup /mode:install /IAcceptExchangeServerLicenseTerms /role:HubTransport, it fails with "The machine is not configured for installing "BridgeheadRole" Datacenter Role." 

Any help would be greatly appreciated. 

Hi,

When user changing their password in email ,alert msg should go to their mobile, is it possible .In our organisation customer asking the above requirements

I am trying to migrate our public folders over to Exchange Online after having successfully executed a cutover migration.

I am following this guide: http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx

I submitted the migration request 11 hours ago. It has since then had the status "queued" and PercentComplete at 0. Is this normal or healthy?

This is how I submitted the request in a remote powershell session on my own laptop connected to Office 365:

$source_credential = Get-Credential xx\xx
$source_remoteMailboxLegacyDN = "/o=xx/ou=Exchange Administrative Group (xx)/cn=Recipients/cn=xx"
$source_remotePublicFolderServerLegacyFQDN = "/o=xx/ou=Exchange Administrative Group (xx)/cn=Configuration/cn=Servers/cn=EXCHANGE"
$source_OutlookAnywhereExternalHostName = "mail.xx.com"

New-PublicFolderMigrationRequest -OutlookAnywhereHostName: $source_OutlookAnywhereExternalHostName -CSVData (Get-Content FolderToMailboxMapPath.csv -Encoding Byte) -RemoteCredential: $source_credential -RemoteMailboxLegacyDN: $source_remoteMailboxLegacyDN -RemoteMailboxServerLegacyDN: $source_remotePublicFolderServerLegacyFQDN -AuthenticationMethod Basic

I get status like this:

Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List

RunspaceId                       : [guid]
Name                             : PublicFolderMigration
Status                           : Queued
StatusDetail                     : Queued
SyncStage                        : None
Flags                            : CrossOrg, Pull, SuspendWhenReadyToComplete
RequestStyle                     : CrossOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : False
SourceVersion                    : Version 14.3 (Build 195.0)
SourceDatabase                   :
SourceServer                     : exchange
BatchName                        :
OutlookAnywhereHostName          : mail.xx.com
RemoteCredentialUsername         : xx
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : /o=xx/ou=Exchange Administrative Group (xx)/cn=Recipients/cn=xx
RemoteMailboxServerLegacyDN      : /o=xx/ou=Exchange Administrative Group (xx)/cn=Configuration/cn=Servers/cn=EXCHANGE
BadItemLimit                     : 0
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {<FolderToMailboxMapping><FolderName>\</FolderName><MailboxGuid>d9aae95d-0e27-40bd-aae9-cde8047a18e2</MailboxGuid></FolderToMailboxMapping>}
QueuedTimestamp                  : 17-07-2014 20:48:37
StartTimestamp                   :
LastUpdateTimestamp              : 17-07-2014 20:49:01
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp               :
CompletionTimestamp              :
SuspendedTimestamp               :
OverallDuration                  : 11:30:40
TotalFinalizationDuration        :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration           :
TotalFailedDuration              :
TotalQueuedDuration              : 11:30:40
TotalInProgressDuration          :
TotalStalledDueToCIDuration      :
TotalStalledDueToHADuration      :
TotalStalledDueToReadThrottle    :
TotalStalledDueToWriteThrottle   :
TotalStalledDueToReadCpu         :
TotalStalledDueToWriteCpu        :
TotalStalledDueToReadUnknown     :
TotalStalledDueToWriteUnknown    :
TotalTransientFailureDuration    :
TotalIdleDuration                :
MRSServerName                    :
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 :
BytesTransferredPerMinute        :
ItemsTransferred                 :
PercentComplete                  : 0
PositionInQueue                  : 1/1 (Position/Queue Length)
PreventCompletion                : True
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          :
FailureTimestamp                 :
IsValid                          : True
ValidationMessage                :
OrganizationId                   : EURPR01A002.prod.outlook.com/Microsoft Exchange Hosted Organizations/xx.onmicrosoft.com - EURPR01A002.prod.outlook.com/ConfigurationUnits/xx.onmicrosoft.com/Configuration                                  
RequestGuid                      : [guid]
RequestQueue                     : EURPR01DG002-db020
ExchangeGuid                     : [guid]
Identity                         : xx.onmicrosoft.com\[guid]
DiagnosticInfo                   :
Report                           : 17-07-2014 18:48:36 [xx] 'EURPR01A002.prod.outlook.com/Microsoft Exchange Hosted Organizations/xx.onmicrosoft.com/xx' created request.
ObjectState                      : New

Also posted to Office 365 forum since both are involved: http://community.office365.com/en-us/f/156/p/252752/776437.aspx#776437

i've add all user in AD to mailbox exchange 2013 except one user,when I add this user mailbox from existing user in AD, it's show error bellow :

Active Directory operation failed on domain-1.corporate.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150BC1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

when I create as new user for this one user with same account in AD, it's show error:

The value "xxx@corporate.com" of property "UserPrincipalName" is used by another recipient object "". Please specify a unique value.

i've does below :

*E:\ExchangeSvr2013>setup.exe /preparead /IAcceptExchangeServerLicenseTerms

*Use ADSIEdit to re-enable inheritance on on the object in AD

Any suggest for this problem?

Thank You

I am not an expert in Exchange. I did set up and administer an Exchange server for a customer years ago, and I just persuaded another customer to purchase and install Exchange Server 2013 SP1.

I downloaded the ISO file and extracted it and then did the install. It told me some Hotfixes needed to be installed, so I installed all that were required. It's worth noting at this point that the link to the KB974405 was wrong and I had to search for the hotfix. But eventually all prerequisites were installed and installation began. Apart from taking a long time, it appeared to work.

After installation completed I clicked to allow administration to open and I was unable to administer anything. The link to Exchange Administrative Center failed with a 404. I opened IIS and noticed that Exchange Back End was installed on port 444. Subsequently I observed that the Exchange website appeared to be installed twice, once as Exchange Back End and once under Default Web Site. The first problem was a complaint that a module, which name now escapes me, but which was installed locally had been compiled with a later version of .Net than the website is using. The website is using .Net 4.5.1. In case it matters I had installed Exchange with both the mailbox and client access roles.

After messing around with it for a long time and finding no relevant help on Google, I decided to uninstall and start over. The uninstalled failed because there are mailboxes. Heaven knows where the mailboxes came from since I had never managed to administer Exchange. I attempted to use Get-Mailbox cmdlet but got a response the Get-Mailbox was an unknown cmdlet.

I am considering reverting the server back to a backup prior to the install and starting over, but I am not sure it would be any different the second time around. Does Microsoft have any suggestions. I suppose I could ask for a refund, but then I am left with a dissatisfied customer. 

Please help, I am desperate!

having problems on new server so I followed instructions to remove Exchange Server 2013 Sp1 using ADSI edit p;er these instructions:

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

now when I re-run setup for exchange 2013 SP1 I get the error :    

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

David Sheetz MCP

I am in the process of migrating resources from an existing AD forest to a new AD forest. There is a 2 way trust configured between the 2 forests. In the old forest we have an Exchange 2007 estate, which we are moving to an Exchange 2013 estate. The new Exchange 2013 environment has been configured and is working correctly. Both forests consist of multiple sites and the Exchange 2007 estate has 2 CAS servers (these are not behind a load balancer) that carry out CAS-CAS proxying to connect to the mailbox servers (that are also CASs) in 4 sites local to users from our single Internet ingress point. On the Exchange 2013 side there are 3 CASs using DNS round robin to connect to 2 DAGs.

I have used the prepare-moveresquest.ps1 script and ADMT to move a user object from old forest to new forest and then attempted to carry out a new-moverequest (from Exchange 2013 servers). However, this is failing with the following error:

[PS] C:\Windows\system32>New-MoveRequest -Identity admt2@es.ec.local -RemoteLegacy -TargetDatabase BedeA-M -Remot
Catalog esbndcesf01b.es.ec.local -RemoteCredential $remote -TargetDeliveryDomain esf-schools.org.uk
The call to 'net.tcp://dcexmb1.esf-schools.org.uk/Microsoft.Exchange.MailboxReplicationService
DCEXMB1.esf-schools.org.uk (15.0.847.31 caps:03FF)' timed out. Error details: This request operation sent to
net.tcp://dcexmb1.esf-schools.org.uk/Microsoft.Exchange.MailboxReplicationService did not receive a reply within
configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.
may be because the service is still processing the operation or because the service was unable to send a reply
message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and
setting the OperationTimeout property) and ensure that the service is able to connect to the client.+ CategoryInfo          : NotSpecified: (:) [New-MoveRequest], TimeoutErrorTransientException+ FullyQualifiedErrorId : [Server=DCEXMB1,RequestId=cf7e69ab-b6fa-41f9-b4db-bcade3619166,TimeStamp=18/07/2014
   8:31] [FailureCategory=Cmdlet-TimeoutErrorTransientException] 705CD530,Microsoft.Exchange.Management.Recipient
  s.NewMoveRequest+ PSComputerName        : dcexmb1.esf-schools.org.uk

Any ideas how I can solve this?

Thanks

I have a standalone active directory server and another server that I want to dedicate to exchange. 

I have everything setup properly. I think..

I can send email's fine. But if I reply or send a new email to an account on the exchange server about a day later I get a failure message: 

The error that the other server returned was:451 4.7.0 Temporary server error. Please try again later. PRX2

I know my domain DNS is setup properly because if I install Small Business Server 2011 everything works fine. 

The only thing I can think of that is different is SBS comes with a DNS and DHCP server already installed. I am letting my router handle that currently. Is there an issue with that?

Thank you for your help.

Hello,

We have 2 Exchange 2013 (build 712) servers in a DAG with distinct subnets. Cisco ASA in between was set to have no filtering between servers in subnet.

We cannot add database copies nor move mailboxes.

Tes-Mapiconnectivty fails with

unspaceId  : e8a087f1-6197-48df-b094-d5c93a7b6070
Server      : CLI-SRV01
Database    : CLI-MDB01
Mailbox     : SystemMailbox{376e8d54-7154-484a-a0a3-58f22d73236f}
MailboxGuid :
IsArchive   :
Result      : *FAILURE*
Latency     : 00:00:00
Error       : [Microsoft.Exchange.Data.Storage.MailboxOfflineException]: Cannot open mailbox /o=First
              Organization/ou=Exchange Administrative Group
              (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLI-SRV01/cn=Microsoft System Attendant. Inner error
              [Microsoft.Mapi.MapiExceptionMdbOffline]: MapiExceptionMdbOffline: Unable to make connection to the
              server. (hr=0x80004005, ec=1142)

In event log:

Adding database copy fails with

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'CLI-SRV02.CLI.ch'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running. [Database: CLI-PFDB02, Server: CLI-SRV01.CLI.ch]

How can I further verify communication from CLI-SRV02 to CLI-SRV01 ?

Any help welcome

/Patrice

In Exchange 2013, the RPC client access service now runs exclusively on mailbox role and no longer on CAS servers.  THis has caused a rather unique issue wit ha client I'm at.

Said client uses a firewall to separate client machines from server VLAN.  While thye normally only expose RPC/HTTP to the CAS servers in 2010, in 2013 this causes problems.  WHat happens currently is if a client queries for an RPC CAS server he will get the current CAS 2010 servers and the 2013 MBX servers... which have no client ports open to them (nor do they want them).  Eventually the problem will be solved on it's own when clients are upgraded to 2013, things are defaulted to MAPI over HTTPS etc ... but for now what it means is if anyone tries to setup a new profile there is a chance the service will attempt to bind to a mailbox server to which the client has no port access to.

with the remove-rpcclientaccessserver cmdlet gone in 2013, is there any way to disable the the publishing of the mailbox clienta ccess service in 2013?  If I used the blockedclientversions option on just the 2013 servers ... would clients auto-attempt to connect to the 2010 CAS?  

The goal here is to get the clients to ignore the 2013 RPC service until all upgrades and migrations are ready rather than exposing the mailbox servers before they've been tested/cleared.