Hi everyone,

I've successfully installed multiple Mailbox and CAS 2013 SP1 servers into an existing Exchange 2010 environment.

However, when I get to the Edge Transport role on a separate server, at step 7 of 9, it throws the following error:

Error:

The following error was generated when "$error.Clear();
	new-ExchangeServer" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId:	this is a GUID based ADObjectId.".

Any ideas what could be causing this? I haven't been able to find anything of significance while searching around...

Thanks!

I am preparing to migrate an Exchange 2010 infrastructure to 2013.  My test setup is a small-scale setup of our production environment consisting of two Exchange 2010 servers and two Exchange 2013 servers, both instances are multi-role.

Currently all on-premise Outlook 2013 clients connect to our existing production Exchange 2010 servers using RPC/TCP. 

Am I right in thinking that before I switch client connections over to the Exchange 2013 servers I need to first switch over the protocol that Outlook client use to connect to Exchange  using RPC/HTTP (ie OutlookAnywhere). ?  If so how do I do this on the clients, do I just roll out a grouppolicy to client machines to set enable the following properties

• “On fast networks , connect using HTTP first, then connect using TCP/IP” .
• enable "connect to microsoft using HTTP
• enter URl to connect to proxy server for Exchange
• set "only connect to proxy server that have this principle name in their certificate
• on slow networks connect uisng HTTO first then connect using TCP/ip
  

In terms of Outlook Anywhere server settings, what are the optimum settings to use:

On Exchange 2010: Client authenticationmethod = Basic / IISAuthenticationMethods=NTL

On Exchange 2013: externalclientAuthenticationMethos = NTLM / internalautheticationmethod= NTLM / IISAuthenticationMethods = Basic, NTLM, Negotiate

Thanks in advance

Hi Guys,

Recently I configured exchange 2013 hybrid for a client .. the client wanted password sync so I had to deploy AAD Connect. During the course of the deployment, I found out that to have password sync, I had to retain at least one exchange server on  premise. 

Now my query is this, what if I cut over to exchange online, do a PST import to exchange online (no hybrid), decommission all exchange servers on premise. Can I still deploy AAD Connect for password sync and still be able to manage mailboxes in the cloud without an on premise exchange server?

I was advised that to have password sync I need to keep an instance of exchange on premise to adequately manage mailboxes.

I appreciate your comments and advice ..

~Richard

..forever is just a minute away*

I am preparing to migrate an Exchange 2010 infrastructure to 2013. My test setup is a small-scale setup of our production environment consisting of two Exchange 2010 servers and two Exchange 2013 servers, both instances are multi-role.

I have now pointed all client connections to pass through the Exchange 2013 server. My outlook 2013 client connects fine to an Exchange 2010 mailbox but when I try to access a 2013 mailbox uisng Outlook 2013 I get the following error “The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action". A further pop box appears with below error.

I can connect to both Exchange 2010 & 2013 mailboxes via Outlook Web App with no issue. On my Windows 7 pc I can browser to https://autodiscover.domain.com/autodiscover/autodiscover.xml which indicates that autodiscover is working as it should. 

Any suggestions on how to proceed.   Thanks in advance

I found these error while installing the Exchange 2013 on Window server 2008-R2 with DC

" Setup encountered a problem while validating the state of Active Directory: The Active Directory organization  configuration version (15844) is higher than Setup's version(15449). Therefore, PrepareAD can't be executed."

Please help me

Hi,

If i install the Microsoft Exchange 2013 from there :

http://www.microsoft.com/en-us/evalcenter/evaluate-exchange-server-2013

In Step 8, Give me Error

IF i click Exit, and re-install, he give me a message

"Incomplete Installation Detected" followed by "Setup has detected that a previous installation of exchange on this computer didn't complete successfully.  Setup will try to complete this installation.  Click next to continue."

If i Click Next, He still all time in 0%

Please Help Me

"i have images but my account not yet verified"

Hello.

I'm doing some development work for an open-source project, and I need to be able to test using Microsoft Exchange.  All I need to be able to do is essentially have an account on an Exchange server so that I can use the calendar feature.  So, because I don't belong to an organization with Exchange, I wanted to run a local Exchange server on my PC.

I downloaded the Exchange Server 2013 executable from https://www.microsoft.com/en-us/evalcenter/evaluate-exchange-server-2013?i=1, and I ran the setup.exe application that was included.  But in trying to install Exchange, I got a bunch of errors.

So, is there a way that I can easily set up an Exchange server on my personal computer?  I should only need this for about a week to do this development work.  If I need to pay a little bit of money, that's all right.

Alternatively, is there another way that I could do the testing I need?  I gather that I'm not able to do that with a Microsoft account just using an @outlook.com email address.

Here's the output I get from running the setup executable:

Dear all,

I need your help on my following issue:

My currently customer has five Active Directory sites (actually, there are more sites than that but they are linked to part Exchange on these 5 sites),

On the other hand, when I access these servers with the account "FRxxx.usertest", the results are different:

On XXX01, the OWA redirection is done well and I'm redirected on the mailbox which is located on the MBX2007.

Thanks in advance for your help.

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.

Hi,

Currently, I'm trying to migrate the Mailboxes from Exchange 2010 to Exchange 2013 CU12.

- Coexistence configuration for exchange 2010 and 2013 is configured properly.

- OWA/Activesync/Outlookanywhere redirection is working properly.

- Autodiscover is working fine.

- All remote connectivity analyzer test from  https://testconnectivity.microsoft.com/  is successful.

When I tried to move the mailbox to Exchange 2013,  user mailbox has disconnected. The behavior is as per following:

1. Move Request Showing Completed 100 Percent.

2. And at the client outlook, pop-up the message to restart the outlook after the move requested completed.

But after that, I found the following error.

1. User Mailbox Cannot Login from OWA

2. Outlook status showing disconnected

3. Re-Created the outlook profile, but failed.

The workaround, I did restart the IIS at the Exchange 2013. After that,

1. The pop-up message again appear at client outlook to restart the outlook.

2. And after that it's working fine for Outlook/ OWA & Activesync.

And I found the following article from MSKB.

https://support.microsoft.com/en-sg/kb/3097392 

Anyone please suggest me, how I can i resolve the issue without applying the workaround every-time I move the mailbox from 2010 to 2013?

Thanks & Regards,
Nay Lin 

Nay Lin Oo [ Systems Engineer ]

So here is my situation:

I have an Exchange 2007 (my main Server ) and i have recently added a new Exchange 2013 in the same forest with a plan to move my users there slowly while in co-existence. What i have done is i have installed the exchange on a new Server 2012 R2 and i now have Mailbox databases , one for the old exchange and one for the new. I can access exchange 2013 ECP , OWA and everything works fine . My dns have not been switched to the 2013 but i have created records separately for it . 

My issue seems to be with outlook anywhere . When configuring users on 2007 exchange everything works fine internally , it auto detects settings and for outside lan connections i enable http access . Now for the mailboxes on 2013 database i have some issues. While it auto detects the settings auto discover sets authentication method to anonymous resulting in popping up for password all the time (even though mailbox is actually connected and can send and receive) . 

My outlook anywhere settings for both servers are :

RunspaceId                         : 2abda2a1-9c7d-4e7d-9861-2ccc4260ff17
ServerName                         : TTSERVER
SSLOffloading                      : False
ExternalHostname                   : remote.tototheo.com.cy
InternalHostname                   : 
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic}
XropUrl                            : 
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://TTSERVER.ttgroup.local/W3SVC/3/ROOT/Rpc
Path                               : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             : TTSERVER
AdminDisplayName                   : 
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (SBS Web Applications)
DistinguishedName                  : CN=Rpc (SBS Web 
                                     Applications),CN=HTTP,CN=Protocols,CN=TTSERVER,CN=Servers,CN=Exchange 
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First 
                                     Organization,CN=Microsoft 
                                     Exchange,CN=Services,CN=Configuration,DC=ttgroup,DC=local
Identity                           : TTSERVER\Rpc (SBS Web Applications)
Guid                               : fed5e59b-9845-4aad-8cfe-230d6ba48976
ObjectCategory                     : ttgroup.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 07/10/2013 19:17:53
WhenCreated                        : 07/10/2013 19:17:53
WhenChangedUTC                     : 07/10/2013 16:17:53
WhenCreatedUTC                     : 07/10/2013 16:17:53
OrganizationId                     : 
OriginatingServer                  : TTSERVER.ttgroup.local
IsValid                            : True
ObjectState                        : Changed

RunspaceId                         : 2abda2a1-9c7d-4e7d-9861-2ccc4260ff17
ServerName                         : EXCH1
SSLOffloading                      : False
ExternalHostname                   : mail2.tototheo.com.cy
InternalHostname                   : mail2.tototheo.com.cy
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Negotiate
IISAuthenticationMethods           : {Negotiate}
XropUrl                            : 
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCH1.ttgroup.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 516.32)
Server                             : EXCH1
AdminDisplayName                   : 
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange 
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First 
                                     Organization,CN=Microsoft 
                                     Exchange,CN=Services,CN=Configuration,DC=ttgroup,DC=local
Identity                           : EXCH1\Rpc (Default Web Site)
Guid                               : 18b2bcf1-59fc-4186-8b99-bf37a103ae38
ObjectCategory                     : ttgroup.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 30/05/2016 14:50:19
WhenCreated                        : 01/04/2016 12:14:41
WhenChangedUTC                     : 30/05/2016 11:50:19
WhenCreatedUTC                     : 01/04/2016 09:14:41
OrganizationId                     : 
OriginatingServer                  : TTSERVER.ttgroup.local
IsValid                            : True
ObjectState                        : Changed

I have bolded my auth methods for both servers. Please note that i have tried several combinations of auth methods for Exchange 2013 such as Internal ntlm , External basic , IIs All 3 but still same issue . I haven't touched Exchange 2007 settings as most of my users are still there and i don't want to mess it up. Can anyone please help on what might be the issue and why is auto discover setting anonymous authentication on outlook ?

I have also checked "Test Email Autoconfiguration" on Outlook and i have noticed that on EXchange RPC protocol i get Auth Package : Anonymous while on Exchange HTTP its Negotiate meaning it gets the one i set in outlook anywhere config .

I have an issue with the migration.  I have moved a few users to a the new 2013 exchange server. I can access the mailbox on 2013 viahttps://ex2013/owa internally and send and receive emails but I cannot get outlook 2010 to connect to the mailbox on the exchange 2013 server.  Outlook 2010 gets stuck on Logon to server during autoconfig of mailbox and I get prompted with username and password for the mailbox but nothing works. I have setup exchange proxy detail within outlook manually and still no joy :( 

Ive been following this procedure

https://blogs.technet.microsoft.com/meamcs/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration/

Any help would be great!

Ben

I have to migrate Exchange 2013 mailboxes and public folders to a new Exchange 2013 server in a new forest. Due to a third party network management tool being implemented, the users have already been created in the new forest. They user accounts have not been migrated from the source forest.

I did this once before with Exchange 2007 using the Move-Mailbox cmdlet and the -append switch. This found  the new mailboxes, matched the user names and moved the contents to the new environment.

is there a similar way to move the mailboxes from the Exchange 2010 server to the Exchange 2013 server in a new forest, where the users have not been migrated from the legacy forest, instead they have been created using a third party management tool?

Thank you

SA

Alejandro | Especialista en Infraestructura Microsoft y Fortinet|

Shyam

Hello,

Yesterday i migrated a mailbox to another database in the same server. The mailbox had almost 4000 items but now its has only the emails which was received after migration. The migration was done using ECP and i dont know how to recover. Please help.

Using exchange 2013 sp1

Hello,

I would like to check regarding with the OWA Motification.

Now, I've modified the OWA login page for the my exchange 2013 Customer. It is working fine for the desktop view and all customization is effect as per configured.

But there is problem at other device view. When the user access from mobile browser to OWA, they cannot able to see their logo.

Anyone can plz advice me regarding with the following items:

1.  Can I disable the twide view and tnarrow Mode ?

• The Table view  - twide;
• The Phone view -tnarrow.

2. Is there anyway to add Logo in TNarrow View(Phone View)?

3. Can I only set desktop view for all the PC , Tablet and Mobile Devices?

Remark:  I've tried to redirect from IIS to the following url but still not working for the phone.

https://mail.domian.com/owa/?layout=tmouse

Thanks & Regards,

Nay Lin

Nay Lin Oo [ Systems Engineer ]

Just wondered if i could sanity check the plan I've come up with as part of this Cross Forest Migration

Both orgs are in and working. I'm trying to configure mail to be copied from the old org to the new org on delivery.

The way I remembered from the last time i did this, which was admittedly a long time ago:

1. add the UPN suffix of the new domain to the old as an addtional.

2. create a connector, for the new domain space, to forward to a smart host and allow all clients to connect.

3. for the user who has migrated to the new server, add a primary SMTP address with the domain of the new org, so that the connector bounces incoming mail across. 

4. in the new org, make sure the address policies are set to give the right SMTP address as default, but also include the address that is being targetted by the bounce.

I'm trying to do this because the mail is incoming from a cloud security service and once all users have been migrated that will be cutover to the new org as the endpoint. no more config will need to be done.

does this seem a sensible way of doing this? I've got it configured and its not working, so might have to rethink. but just wanted to see if anyone can actually remember doing it this way. I can't find a lot on the web about this approach, but lots of 2003 resources are being taken down. 

Hello,

We have 4 Exchange 2013 servers running Windows Server 2012 R2

I have upgraded all of the servers from Exchange 2013 CU11 to CU12 this week, and also installed the latest Windows updates.

I have found that OWA no longer works following the install of CU12 on all servers.

As per any CU install I always run the "UpdateCAS.ps1" script following the installation on all servers, and also the"UpdateConfigFiles.ps1" script. This has not fixed the problem.

I can navigate to the following URL on all servers https://localhost/owa and be presented with the OWA logon page, however once I have entered my credentials and hit enter I get the following response:

"HTTP 400 Bad Request - The webpage cannot be found"

This is the same from Windows client machines - tested with IE11, Chrome and Firefox browsers.

If I access OWA from Chrome on my android phone, I can log in to OWA without issue, and I receive the OWA "light" interface - which is normal.

Has anyone else seen this issue since upgrading to CU12?

Regards

Matt

Matt

Нelo.

I have 2forests:

1) root domain - contora.com and subdomain sub.contora.com
Exchange 2010 installed in the subdomain

2) domain contora2.com - the only domain in the forest

Exchange 2013 installed in this domain

Can I migrate forest  contora2.com to forest sub.contora.com ?
Is not the problem that version of the Exchange in target forest is lower than the version of the Exchange in source domain?
Thank you.