Hi, 

I am running Exchange 2013 in Coexist and Frankly hate it, nothing but problems I have been having.  I haven't been able to migrate any mailboxes over to the 2013 environment because I cant get it working.  

Here is my setup:

ExchangeFE1 - Exchange 2010 CAS

ExchangeMail - Exchange 2010 Mailbox Server

ExchangeUM - 2010 UM Role

Mail 13 - 2013 Mailbox, UM

MailExchange2 - SEcondary 2013 Mailbox Server

Exchangecas13 - 2013 CAS Server

Using OWA on the 2013 CAS server I can send/receive email perfectly fine both internal and external.  I am unable to get Outlook to work at all.  Even when I manually try typing in the server it doesn't work.  What does work for no apparent reason is if I type exchangefe1 as the server and type the user on the 2013 mailbox and click checkname it then, fills in Mail13 as the server.  However, if I manually type Mail13 it doesnt work.  Even when I get done with that it wont let me open the mailbox says I have to already open it.  

Alright so I Figure its a certificate issue.  I add the local Exchange2013 cert to my PC's trusted root certificate, doesnt work.  So then I create an SSL cert with Godaddy.  It complains because the command name is company.domain.com.  

The other issue is that Webmail Redirection doesnt work I looked at the logs it tries but never gets there.  Right now I am running two seperate SSL certs one for production through Godaddy and 1 for our 2013 environment with Godaddy.  There still might be a cert issue but this coexist is confusing me because I dont want to impact anything running.  

I run autodiscover on the 2010 environment but its not configured on the 2013 environment.  I can only have 1 SRV record so I dont want to take down the 2010 environment which is were all the mailboxes are.  

Any assistance is greatly appreciated. 

Hi Everyone

I had a problem where  my exchange shut down and i after run the eseutil /mh command i could see that

Unfortunately i could not run eseutil /p to restore within the folder as it was giving this error 1032 Jet_errFileAccessDenied

I checked the database to see if it was mouted but no joy so i copy the edb file to another location and runned the command and paste the edb back

after running again the eseutil /mh i can see that the database is not on clean shutdown but it will not mount still

can someone give me a hand 

The database is located on teh e:\exchange but exchange is localted in c:\programfile\microsoft\exchange\v15\mailboxes\

Thanks

Hi team,

In a scenario like below, how many Exchange Server 2013 Licenses are required?

• Physical Server 01 (OS Only)
• VM 01 - CAS/MBX
• VM 02 - MBX

• Physical Server 02 (OS Only)
• VM 01 - CAS/MBX
• VM 02 - MBX

Thank You.
Chris!

Can I add a second cas server without putting in cas array and make its sole purpose to do pst exports of current mailboxes. Currently have Exchange 2010 Server with CAS/HUB/Mailbox on same server. 

Christopher

Hello Everyone,

I getting error when trying to migrate mailboxes to exchange 2013

This is what i'm get:

Data migrated:
Migration rate:
Error:MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'mydomain.tv/System-Users/AD DIRAY‎'. --> Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'mydomain.tv/System-Users/AD DIRAY‎'.

Please help with this.

Thanks.

I have domain with company.local name and I’m using for public company.com. I’m going to install Exchange 2013 in my organization but I’m not able to buy ssl certificate for my internal DNS anymore from GoDaddy and as far as I know it is still required.

How deal with this? I don’t want to do any major changes in my organization like domain name change and I still want to use trusted domain authority.

I receive the following errors when installing Exchange Server 2010 :

• unable to locate schema master
• cannot find the recipient update service

I made sure the schema master is in the same domain that I'm installing Exchange server on.

We have one 2007 Exchange SP1 with all the roles in one server 100 users on it, and have Public folders as well.<o:p></o:p>

Exchange 2007 SP1 server is on one leg, my coworkers and my boss doesn't want to touch this sick poppie even though I suggested to do steps to stabilize it. The bottom line is to build new Exchange server 2013 in separate organization, migrate all mailboxes into it.<o:p></o:p>

All I saw was move to a different mail store with Exchange Management console. How can I easily export mailboxes maybe with a tool to pst and then I can import it to Exchange 2013? Does Exchange 2007 SP1 has a tool built-in for mailbox exports? Any suggestions will help out.<o:p></o:p>

Thanks in advance, 

Mark.<o:p></o:p>

Technet question.

Greetings,

I am new here and only a few months of working within Exchange and Powershell. I've been adept at finding most answers, but I am short on time and have stumbled along on this one for a while.

I am trying to change some Shared mailboxes to Regular mailboxes due to the OWA not picking up subfolders on the calendar side. I was trying to use the following command, but had no luck (guessing due to Password issues)

Get-Mailbox -Identity testshare@shoop.org | Set-Mailbox -Type Regular

I tried every way I could put together in order to get this working, forcing a password, you name it. Nothing helped. Any ideas on what could hold this up?

Hi 

Today i was installing the Exchange 2013 CU1 in my LAB, but getting error while preparing Ad with command setup /preparead  /IAcceptExchangeServerLicenseTerms.

Error which was getting 

Error:
The following error was generated when "$error.Clear(); 
          install-RuleCollection -Name:"ClassificationDefinitions" -DomainController $RoleDomainController;
          New-ClassificationRuleCollection -InstallDefaultCollection
        " was run: "The specified out-of-box classification rule collection update cannot be applied because it is missing data classification(s) with the following identifier(s): 95fcd7ad-a5ba-4be4-8b75-bfb3026d7e68,d2259b5e-73a6-4dc5-a190-cbf8ae247835,ec8c384f-cec2-48e2-a349-3f35fd65a4a4,897a55ba-e5f5-49bb-8eb0-b0849f4e20c8.".

Hello,

I have the following setup:

new domain: test.local

complete new domain with new user accounts has contact with the old via trust relationship.

old domain: company.local

Has 2003 Server OS and Exchange 2003 installed on it.

Our It manager wants to setup a way that all mail is deliverd to the old and the new mail server.

The already existing mail will be imported via a tool or simply exporting via pst.

The reason they want this that they want to be able to fall backup to the old exchange if something goes wrong.

And to be able to migrate user account per account (small company) and see if anything goes otherwise wrong.

Is this possible and without downtime and other issues?

Kind regards

Jo

Basic info

Exchange 2010 SP1 on Server 2008 R2.  An Upgrade from Exchange 2007.  Auto Reply returns an error from Outlook "Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later."  When attempting to access auto reply from OWA, the user is brought back to an OWA login screen.  (which does not allow the user to log back in)  This is a different URL than the normal OWA log in URL.

I have attempted to remove and recreate the EWS directory without success. In current troubleshooting, if I attempt to remove the virtual directory, I receive an error it does not exist on the domain controller, if I try to recreate it, it tells me it already exists.  If I try to set it, it tells me it cannot be found.

PowerShell information included below...

I have tried many different methods to resolve this so far without success.  (hence posting here) I HAVE NOT yet attempted removing/reinstall the CAS role, or anything involving adsi edit.

[PS] C:\>Remove-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)"
The operation couldn't be performed because object 'Server.Domain.net\EWS (Default Web Site)' couldn't be f
ound on 'DomainController.Domain.net'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Remove-WebServicesVirtualDirectory], ManagementObjectNotFoundEx
   ception
    + FullyQualifiedErrorId : AE5EDDA2,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveWebServicesVirtual
   Directory

[PS] C:\>get-webservicesvirtualdirectory | fl identity,internalurl,externalurl
[PS] C:\>

[PS] C:\>New-WebServicesVirtualDirectory -Identity 'server\EWS (Default Web Sit
e)' -InternalUrl  https://webmail.domain.net/EWS/Exchange.asmx -basicauthentication 1 -windowsauthentication 1
The virtual directory 'EWS' already exists under 'server.domain.net/Default Web Site'.
Parameter name: VirtualDirectoryName
    + CategoryInfo          : InvalidArgument: (server\EWS (Default Web Site):ADObjectId) [New-WebServicesVirtual
   Directory], ArgumentException
    + FullyQualifiedErrorId : 775B2C6B,Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDir
   ectory

[PS] C:\>Set-WebServicesVirtualDirectory -Identity "server\EWS (Default Web Site)" -InternalUrl  https://webmail.domain.net/EWS/Exchange.asmx
The operation couldn't be performed because object 'server\EWS (Default Web Site)' couldn't be found on 'DomainController.Domain.net'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-WebServicesVirtualDirectory], ManagementObjectNotFoundExcep
   tion
    + FullyQualifiedErrorId : D6F18491,Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebServicesVirtualDir
   ectory

[PS] C:\>get-webservicesvirtualdirectory | fl identity,internalurl,externalurl
[PS] C:\>

I am attempting to load MS Exchange 2013 standard onto Windows Server 2008 R2 SP1. This is a new installation, no previous version of Exchange exists on the server.  This is being loaded on a Dell R320 PowerEdge with 64Mb RAM on a Xeon E5-2450, 8 core cpu.

I pulled/burned the ISO successfully.  On the server when I executed D:\setup.exe, I was given a message box "Exchange Server 2013 requires Windows Management Framework 3.0.You can download Windows Management Framework 3.0 from http://go.microsoft.com/fwlink/?LinkId=260992."

I attempted to install Windows6.0-KB2506146-x64, but was given the error message of "This update is not applicable to  your computer".

I attempted to install SP2 for 2008 server (Windows6.0-KB948465-X64), but was given the error of "This service pack does not apply to the version of Windows running on this computer"

When I attempt to run the MS Updates, I am blocked.  Can anyone tell me if the lack of updates are the cause of my Exchange installation failure?

I started a coexistence upgrade from 2010 to 2013 a couple weeks ago, had 2013 CAS in front proxying OWA and web requests to 2010 and 2013 users alike, all running properly. Then "something" happened, not sure what, and suddenly all Exchange 2013 web requests to login to OWA or to ECP generate a 500 error on the server, no matter if I use localhost, IP address, or FQDN for the internal or external URLs.

Because this is production, I moved back to the 2010 CAS array as the primary and tried to tinker with 2013. Nothing would work, nothing would allow me to access mailboxes hosted on 2013, so I had to disable the mailboxes and re-enable them on 2010 (migration commands wouldn't even work to move them back to 2010). In the end I uninstalled all 2013 servers from my organization and checked ADSI Edit to ensure there weren't any pointers to the 2013 servers I installed.

Fast forward to this week, I wanted to try again, see if the uninstall of the servers fixed the issues. I built two new Windows Server 2012 servers (one CAS and one MBX) and accepted all default settings coming off of the CU2 installer (except one I chose the CAS role and one I chose the MBX role). Fresh install, no users running, I cannot get to the ECP or OWA once again, 500 error no matter what URL I use to access the servers. And proxying to a 2010 mailbox still fails as well.

I've checked out everything I can online, I've removed and re-added the Windows Identity Framework, I've recreated the OWA and ECP directories on CAS and MBX server, and I've run the get-serverhealth command against both servers for the OWA and ECP health sets without errors. Any ideas?

Environment: two Windows servers running AD services and the Hyper-V role, one Windows 2008 R2 SP1 with two virtual guests running Windows 2008 R2 SP1 servers with Exchange 2010 SP3 RU2 and one Windows 2012 with two virtual guests running Windows 2012 servers with Exchange 2013 CU2. Image

Our setup before we applied Rollup 7:

Exchange 2010, SP2 Update Rollup 6 running on all servers.

2 Mailbox servers w/ DAG

3 CAS/HUB Servers using a hardware load balancer

No problems prior to the Rollup 7 installation.

The Rollup went fine on 4 out of the 5 Exchange Servers. On the 5th server, however, there are problems. The first time I tried to install RU7 it was about 5 hours in when I cancelled it. So I tried again and the install has been running for 13 hours and it appears to be only about 40% complete. The progress bar has been stuck in the same spot for nearly all of that time. Per an article I found on Susan Bradley site (SBS Diva) I had verified that "Check for publisher's certificate revocation" was disabled in IE prior to the start of the install.

I have seen Service Packs take a long time in the past and I have Rollup Updates take a long time too, but this is taking a very long time.

Anyone else  observing this issue with this latest Update Rollup for Exch10, SP2?

Thanks.

Upgraded a server from Exchange 2007 RTM to Exchange 2007 SP3Ru11 in preparation to upgrade the Org to Exchange 2010. After doing so, the Out of Office assistant within Outlook now doesn't work for any of the Exchange 2007 Outlook client users. All the users get a message "Your Out of Office Settings cannot be displayed, because the server is unavailable."

However, OOF works fine in OWA. OOF also works on mobile devices like iPhone. In addition both the www.testexcahngeconnectivity.com tests work fine and the internal Outlook client test configurations and such all show connected and working. I simply don't see any errors in order to troubleshoot.

What am I missing? Is there something about applying SP3RU11 that breaks OOF for Outlook 2010 clients? How can I fix this?

Thank you.

Hi

While trying to install the CU2 on an Exchange 2013 i got the following errormessage(s). The error shows up while the setup is trying to install the client access service.

The following 1 error(s) occurred during task execution:
[1] 0.  ErrorRecord: Das Argument kann nicht an den Parameter "WindowsAuthentication" gebunden werden, da es NULL ist.
[1] 0.  ErrorRecord: System.Management.Automation.ParameterBindingException: Das Argument kann nicht an den Parameter "WindowsAuthentication" gebunden werden, da es NULL ist.
   bei System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   bei System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   bei System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   bei System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[08.21.2013 08:07:05.0077] [1] [ERROR] The following error was generated when "$error.Clear(); 
          update-WebServicesVirtualDirectoryVersion -DomainController $RoleDomainController;
          $BEVdirIdentity = $RoleNetBIOSName + "\EWS (Exchange Back End)";
          $be = get-WebServicesVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          {
            $BackEndPort=":444";
            $urlToUse = "https://" + $RoleFqdnOrName + $BackEndPort + "/ews/exchange.asmx";
            new-WebServicesVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -windowsAuthentication:$true -WSSecurityAuthentication:$true -OAuthAuthentication:$false -BasicAuthentication:$false -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
          }
          else
          {
            $be | set-WebServicesVirtualDirectory -windowsAuthentication:$be.WindowsAuthentication -WSSecurityAuthentication:$be.WSSecurityAuthentication -OAuthAuthentication:$be.OAuthAuthentication -BasicAuthentication:$be.BasicAuthentication
          }
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeServicesAppPool" -Version:"v4.0";
        " was run: "Das Argument kann nicht an den Parameter "WindowsAuthentication" gebunden werden, da es NULL ist.".
[1] [ERROR] Das Argument kann nicht an den Parameter "WindowsAuthentication" gebunden werden, da es NULL ist.
[1] [ERROR-REFERENCE] Id=ServicesComponent___ca981854eaa74c1ca684178d9ea52fff Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[1] Setup is stopping now because of one or more critical errors.
[1] Finished executing component tasks.
[1] Ending processing Install-ClientAccessRole

I tried to install the CU with the command line setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms and also with the GUI setup. But the same error by both ways.

Also I prepared the AD and the schema before I tried to install the CU2.

I'm very thankfull to every answer that will help me to continue the Installation.

Kind regards

Hi All,

Getting extremely frustrated now with a new Exchange 2013 installation on a Windows Server 2012 VM...

After having a lot of problems with the installation (didn't uninstall visual c++ which caused failure, then needed to delete the AD Microsoft Exchange System Objects group due to permission failures, etc) I've now got a fully installed Exchange server. Still, now I cannot figure out how to fix my next problem - Accessing the EAC/ECP.

I've searched every possible web guide/forum thread and the only one which is the same issue I'm having is this one: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/89c42771-78c9-4d94-88e5-557320eccc71 

Unfortunately, as you can see in that thread, it is still unresolved. 

Current Issue: trying to access https://localhost/ecp (or any other variation) returns a 404 Not Found.

The error page points the physical path to c:\inetpub\wwwroot\ecp however that folder does not exist. I have tried manually changing the IIS site (Exchange Back End) to point its physical path to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp which seems to be valid, however it doesn't work...

Not sure what else to do... HELP!

Oli