We attempted a exchange 2013 install in a coexistence scenerio. Getting the following error during the install process. Any ideas?

Cesar Contreras | Network Administrator | CCNA

I'm interested in peoples views on if there is a standard setup for my particular scenario or any methods you could recommend.

High level overview is a Main office and a branch office, around 30 people in each. Currently 1 exchange 2007 server at the main office and a 2003 server at the remote office - 2 different domains and namespace. Plan to bring these together under one domain with VPN links for the  2 sites.

Whats the recommendation for Exchange - 2 exchange servers with a mailbox role at the branch office or just one exchange server at the main office accessed over the VPN.

I would be interested to hear peoples opinions.

Thanks

I have installed one 2013 CAS and one 2013 MBX. (MBX01)

Today I installed a new MBX(MBX02). Then I move all mailboxes to new one(MBX02).

So I uninstall the old one(MBX01). *retain MBX02 

After that I cannot send or receive mail anymore, once I connect ti EMS on CAS Server it says
"New-PSSession : [cas.domian.com] Connecting to remote server cas.domian.com failed with the following error message : [Server=cas,RequestId=e9f66d77-e016-455c-8e08-30d69e8a9a71,TimeStamp=11/21/2013 1:05:49 PM]Cannot find Mailbox server with Version 15.0 (Build 711.24). For more information, see the about_Remote_Troubleshooting Help topic.

any idea?

Hi!

Fresh 2013 install.
Default web site is set to redirect requests to https://server/owa. 
SSL is required.
Custom error for 403.4 is redirect to https://server/owa

Opening http://server redirects fine to https://server/owa but once the user is logged in, the site redirects back to https://server (no OWA in the URL)

This causes the site to look like the attached picture, because all the file paths are wrong. https://server/14.3.123.3/themes/resources/clear1x1.gif does not exist, the OWA part is necessary.

Any ideas why it redirects out of the OWA directory and to the root after login? If I type in OWA manually the themes are OK. But for some reason everything except the themes load even without the OWA part.

I was unable to access Exchange via Exchange Management Shell.
Below is the error message:
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
.
.
.

-    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

I tried to access the Exchange using browser, https://localhost/ecp or https://192.168.1.10/ecp, i able to login. But after login the browser displays blank.

The last thing i did was re-create a self-sign certificate.

Anyone can help?

Hello. 

I want to uninstall an exchange server, but because there are mailboxes I can't. I also can't delete the mailboxes because I cannot gain access either to the ecp or managment shell. 

ecp returns a 404 error and the managment shell gives this error: 

VERBOSE: Connecting toexchange.domain.local.
New-PSSession : [exchange.domain.local] The WinRM service cannot process the request because the request needs to be sent
to a different machine. Use the redirect information to send the request to a new machine.  Redirect location reported:
 https://exchange.domain.local/owa . To automatically connect to the redirected URI, verify "MaximumConnectionRedirectionCount" property of session preference variable "PSSessionOption" and use "AllowRedirection" parameter on the cmdlet.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportRedirectException
    + FullyQualifiedErrorId : RedirectInformationRequired,PSSessionOpenFailed.

Any help would be greatly appreciated. 

I'm getting ready to create my first DAG adn see I need to create a disabled user account. Our Exchange servers reside in a child domain, but i see all the systemmailboxes reside in the forest root domain.

Should the DAG accoutn be created in the forest root, or the Exchange server domain?

Tom

Hi all,

Windows 2012, single Exchange 2013 CU2 environment, fresh install.

I have been unable to get the Exchange toolbox to load in mmc either locally on the Exchange server or from a Windows 8 system with the Exchange management tools installed. The error I get is: 

FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

Type is not resolved for member
'Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationException,Microsoft.Exchange.Configuration.ObjectModel,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exception Type:

System.Runtime.Serialization.SerializationException

I am unable to run the Exchange Management shell either.

I have found a number of forum threads here that mention this or similar error situations and have tried the advice given, but so far no luck. 

The reason I am particularly interested in the toolbox is that I am troubleshooting a problem for a user who is complaining about delayed mail delivery.

George

George Merriman gwm@gsi-bkln.com Gravesend Systems Inc. Brooklyn NY USA

Hi all.

I've been working on setting up Exchange 2013 in our Exchange 2007 environment.  I've managed to install it, configure it, move a handful of mailboxes, and fix several issues (2013 users being asked to login, free/busy maximum settings mismatch, Autodiscover not really updating the settings in Outlook clients...).  However, I'm stuck on getting Exchange 2013 users to access Exchange 2007 public folders.  Because the new server is very much in a development stage, I can't migrate the public folders over and won't until the mailboxes are thoroughly tested and fully migrated.

According to the public folders FAQ at http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx, it's both possible and impossible to get new users to access legacy folders.

From "Considerations:"

Exchange 2013 no longer supports public folder databases. Therefore, there’s no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

From "Migrate public folders from previous versions:"

...However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously....

I did originally start to build the master hierarchy in 2013 before finding this page, but I have since deleted the hierarchy from Exchange and from AD via ADSIEdit.

When a 2013 user tries to access a 2007 public folder, they are met with "Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems of the Exchange server is down for maintenance. (<correct info about the the legacy 2007 server's DN>)"

I've reviewed the RPC logs from the new server and am seeing what looks like a proper redirect command to the Outlook client.  But the Outlook client can't connect to the public folders.

I've tested public folders in OWA and they don't work there.  I've verified that the services are started on both the new and old servers.  And I've used the Outlook Connection Status tool to observe how Outlook seems stuck in a perpetual "connecting" state to the old mail server, even when I'm not trying to access a public folder.

So my question then, is using Exchange 2013 to access Exchange 2007 public folders actually possible or not?  If so, what else can I check to find out why I can't open legacy public folders?  We need to access some of the shared folders for collaboration, and I'm trying to avoid moving the upgraded users back into Exchange 2007.  This seems to be about the last major problem I have before I can start migrating all of the other users.

Thanks!

Alan

PS - Microsoft, please update your Exchange 2013 Public Folders FAQ to clarify if this is possible or not.  You state both in two adjacent sections.

Hi, I am having an issue with Autodiscover not passing EXPR attributes which is causing Outlook client connection issues.  My auto discover repsonse looks like this:

Autodiscover Account Settings

Basically the response isn't passing EXPR settings at all.  I have tried running Remove-OutlookProvider EXPR and then New-OutlookProvider EXPR, Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.domain.com

When I run Get-OutlookProvider everything looks normal with the EXPR settings but they are still not being passed via auto discover.  Any ideas on how to resolve this?

Hi, I couldn't find a separate forum for Exchange 2003 / 2010 so I hope it's OK to ask here.

We have several sites that have single servers that are both Domain Controllers (2003 Server) and Exchange Servers (Exchange 2003).  I am involved in migrating these to separate virtual Windows 2008 R2 servers in Hyper-V.  The DC roles get transferred to one virtual 2008R2 server, and Exchange 2003 gets migrated to Exchange 2010 running on the other virtual 2008R2 server.

What's the correct way to do this ?  We've tried a couple of different ways but everything we've done so far seems to break Exchange once AD is transferred to the new DC.  The last time we migrated Exchange over fine, then made the new DC virtual machine into an additional DC, transferred roles then demoted the original physical DC and Exchange 2010 broke (presumeably something to do with the DC name changing, even though the domain is unchanged).

Any tips or pointers would be great !

Thanks !

Hi, 

I installed exchange 2013. The installation went bad I had to uninstall it manually from ADSI edit, then deleted the VM. I installed exchange 2013 once again. I log into ecp, I find under recipients the old mailboxes created with the old exchange server. when I try to delete them or move them, the following error shows: 

The object domain/Users/someuser has been corrupted, and it's in an inconsistent state. The following validation errors happened:
Database is mandatory on UserMailbox.

digging around on the net, I followed this link: http://support.microsoft.com/kb/2702446?wa=wsignin1.0

but I noticed that my homeMDB is not set. 

also following this link: http://technet.microsoft.com/en-us/library/dd535374(EXCHG.80).aspx

I noticed that I dont have anything under this location in adsi edit, while it states that there are some child objects

config...\config...domain\services\microsoft exchange\org-name\administrative groups\ex...admin..groups id\servers\mailbox\informationstore

Should I have ran setup /prepschema and setup /prepad, i didn't because in MS documentation it stated that if the account is a member of enterprise admin and schema admins the schema and AD and Domain preparation would be done by the wizard.

If its partially prepared, can I run them commands again without causing problems?

I can create new users just fine, all I want is to delete these recipients and create a new working ones. also I want to know is my exchange setup right, because I don't want to face major problems when we go live.

its been 3 weeks hitting my head against the wall, help please.

I'm getting an error when trying to upgrade EMC on my managment workstation.  this is from the exchange setup log.  It is thrown in the stopping services phase.  This is stange as the admintools roles has no services to stop afaik.  I also tried uninstalling and get a different error.

[11/21/2013 16:18:25.0501] [1] [ERROR] The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "Exception calling "GetFolder" with "1" argument(s): "This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)"".
[11/21/2013 16:18:25.0501] [1] [ERROR] Exception calling "GetFolder" with "1" argument(s): "This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)"
[11/21/2013 16:18:25.0501] [1] [ERROR] Exception has been thrown by the target of an invocation.
[11/21/2013 16:18:25.0501] [1] [ERROR] This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)
[11/21/2013 16:18:25.0502] [1] [ERROR-REFERENCE] Id=AllRolesPreFileCopyComponent___2f7e3804a2b340c69e930798211fb8fd Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

Hi all,

I've setup new Exchange 2013 but having issues with the DNS records. My AD domain name is company.uni.edu.au however the email is being accepted on company.com.au domain.

I installed SSL certificate for Exchange required domains (exchange.company.com.au, discover.company.com.au) and it works fine.

The only issue is when I connect with Outlook, there's a Security alert, alerting me that the certificate been issued only for company.com.au and not company.uni.edu.au

How to resolve this issue? Do I need to get another SSL certificate or just change some DNS settings?

PS: DNS resolves the IP address correctly to exchange.copmany.com.au (which is what I want)

Thanks.

I'm setting up Exchange 2013 for the first time.

I can send emails to the outside network but I can't receive them. I get the following error:

Received: from smtp-s2.menara.ma (196.217.246.128) by MTVHUB01.mymenara.ma
 (172.28.1.69) with Microsoft SMTP Server id 14.2.318.1; Mon, 25 Nov 2013
 10:28:15 +0000
X-AuditID: c0a80a1c-b7cb0ae000003b82-3f-529334c67e5b
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com
 [209.85.192.173])	by smtp-s2.menara.ma (Symantec Mail Security) with SMTP id
 FC.60.15234.6C433925; Mon, 25 Nov 2013 11:30:30 +0000 (WET)
Received: by mail-pd0-f173.google.com with SMTP id p10so5209862pdj.18
        for <h.elyazidi@aua.ma>; Mon, 25 Nov 2013 02:34:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=+6wk/wvKWV1OeeNnuCpHOjLUvccq5uirpnu+9udBVaQ=;
        b=WLq6f+NDc8Ip+kTD5oCKzgcRzrFwOJ1yUk8wCKfMrwJ51YkaheJixqY2ykWMfB3w4W
         CNoSbghIz8ebWJ8/rGuseDGNPM7B9CljeFisJkoDoI3QDXZ0kOPqSHI7b8VoagqLxiET
         SeaUg2QHq6XQQehuDpKmZ4b57PLaIW9LxaJGsVfNY3XeiWvDQh4yAHZoLrhMbB8wLGHW
         NCwydSNja5t04oMMy49YGNQ0afZm0N58AJEy5VusqwjyO7vxr1MdnQXJQ9os5R+wB2rK
         gebLorDSmR6HzGQh7gxCvc775w12wVGZ6WWGZIo9LVxV97mBFDyT20tKGA3wJYo+YlAM
         4mZQ==
MIME-Version: 1.0
X-Received: by 10.68.176.228 with SMTP id cl4mr342155pbc.196.1385375691288;
 Mon, 25 Nov 2013 02:34:51 -0800 (PST)
Received: by 10.68.16.168 with HTTP; Mon, 25 Nov 2013 02:34:51 -0800 (PST)
Date: Mon, 25 Nov 2013 10:34:51 +0000
Message-ID: <CAKi21aAhXZpdejcgH+cwqHjgvaQaxExOVsruRZOYf_HBjOiK5Q@mail.gmail.com>

Any idea what's happening?

  Hi,

  I am running Exchange 2010 and Exchange 2013 on sama domain. I need some answers before I continue.

 1) Can I  move mailboxes gradually to Exchange 2013 without problem? Is there any thing I shuld be aware of regarding that?

 2) Can I use the same network for DAG on Exchange 2013 as I am using on Exchange 2010, I am using whole Cnet fore this purpose. Having poblem creating a  new DAG group on 2013. Maybe it will be solved by installing Exchange 2013 CU2??

 3)  Can I use ECP for administering both Ex 2010 and Ex, like creating users and all administration regarding that.

 4) Should I get new certificate for CAS service now og can I pospone it?

 thanks.

Erró

Hi all,

We are in progress to upgrade our exchange server to 2013. But there are issues that we feel like it's still unstable.

Here is the case:

- We did local mailbox request (i.e. from mailbox database 100MB to 1GB), via GUI, after sometimes, the request COMPLETED but the other column shows 0 including Finalized column, the mailbox is not migrated at all

- Then we tried to do the move request via exchange powershell, it prompted error and apparently there were still unclear previous move request (Get-MoveRequest and we get the result).

We delete the previous move request and rerun the command, and it works.

Via ECP, the Recipient list shows the database are still on old mailbox database. We need to edit the mailbox detail, and go to more option, to totally sure that it has been moved.

Anyone has experienced this before? Kindly advise.

Thanks.

Hello,

i can't install Exchange 2013. Setup failed at Step Mailbox role: Transport Service.

The error message is:

Error:
The following error was generated when "$error.Clear();
            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
            Write-ExchangeSetupLog -Info "Loading FipFs snapin";
            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install
            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
            if(! $MicrosoftEngineExists)
            {
              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
            }
          " was run: "Retrieving the COM class factory for component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).".

Error:
The following error was generated when "$error.Clear();
            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
            Write-ExchangeSetupLog -Info "Loading FipFs snapin";
            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install
            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
            if(! $MicrosoftEngineExists)
            {
              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
            }
          " was run: "Retrieving the COM class factory for component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).".

This is a fresh/clean installation of both Server 2008 R2 and Exchange 2007 SP3, about as vanilla as it can get.

On the default web site (the one that shows the IIS7 logo screen) and in fact any directory under that one, after installing Exchange the root site and all the sub-directories all 'fail' with 403 "Forbidden" errors whereas they were all working fine prior to installing Exchange.  

Other root sites on the same IIS server still work fine. It's just the 'default' site (the one where the Exchange installation added all of its stuff, where the CA lives, etc) that is having the problem.'

What's up with this?

Thanks.

When migrating or adding a new user to Exchange 2013, I get the following error when going into the Mailbox Delegation section in the Exchange Admin Center.

The object <Object CN> has been corrupted, and it's in an inconsistent state. The following validation errors happened:

The access control entry defines the ObjectType 'Object GUID' that can't be resolved.

I have done the following to try and resolve the GUID

Searched via LDP, ADSI, ADUC, Repadmin, with nothing found. I've converted the GUID from string to hex and searched with still no luck.

I get the identical error when running a Get-ADPermissions on the object as well.

There are no inheritance blocks on the object or OUs.

I've opened a Premier case, but wanted to ask the community if they have seen this or had any suggestions. As of right now, Exchange 2013 is the only app that can see this orphaned object.