I am trying to migrate mail from one hosted Exchange solution to Office365.  I already have the domain set as internal relay and mail flow is working fine.

My last remaining issue is autodiscover.  How am I supposed to manage autodiscover in DNS when it needs to point to two different places?

Thanks.

All,

I want to run profile analyzer tool on our exchange 2010 Sp3 servers to collect information for OWA, MAPI, EWS,Active-SYNC and log generation

I need this for exchange 2013 deployment. Basically i want to check how much storage,Network bandwidth for log shipping, MAPI client to exchange server(if it one different WAN site), Server Hardware.

I run the available analyzer tool but not work. I cant expand the server and from the server and select the database from the console.

I think it is only for exchange 2007 and above version. 

Do anyone know about the link or any place where i can download the exchange 2010 profile analyzer tool

Thanks

Hi,

Hope someone can figure this one out...

I have this strange issue when importing PST files. I found another person having the same issue. Please see problem description below

Source :http://serverfault.com/questions/465735/export-exchange-2003-mailboxes-to-pst-and-import-to-exchange-2013-wierd-folder-n

I am trying to export mailboxes from my old Exchange 2003 SP2 that runs on a Windows Small Business Server 2003 and import them to my new Exchange 2013 that runs on a Windows Server 2012.

So far I have exported the mailboxes to *.pst -files using ExMerge.exe and imported them to Exchange 2013 using the below cmdlet:

Dir \\EXCH01\PST\*.pst | %{ New-MailboxImportRequest –Name ImportOfPst –BatchName ImportPstFiles –Mailbox $_.BaseName –FilePath $_.FullName}

After a successful import if I log on to OWA on a account I get wierd looking folder names, for exampleInbox looks like this: ÂÊÊÊÂÊ]^. I reckon this has something to do with system locale...

If I however export from Outlook to *.pst I get another problem with folder names: TheInbox folder in swedish is called "Inkorgen" on 2003 and "Inkorg" on 2013, theSent folder is called "Skickat" on 2003 and "Skickade objekt" on 2013 - and so forth. This results in new folders are created instead of putting the mails and objects in the folders created by Exchange 2013.

I hope you understand my problem. Has anyone got a working solution on migrating from Exchange 2003 to Exchange 2013?

I currently have a single E2K7 server and I am bringing in a 2013 server into the org.  The installation of 2013 is complete and I am told (http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=1839-W-DABEAgAAQACACAEAAA%7e%7e) that I need to access the the EAC with the following URL: https://<server name>/ecp?ExchClientVer=15.  When I launch that URL I am prompted for the credentials of the user I used to install Exchange 2013 with.  I enter them and then get the following message:"Sorry, Access denied. You don't have permission to open this page. If you're a new user or were recently assigned credentials, please wait 15 minutes and try again."

Help.  TIA.

Larry D.

Hi Guys

I recently tried upgrading our existing exchange 2013 CU1 in a test lab to CU2 unfortunately the installs fails on the following.

I'm not to sure where it is get held up or what the problem is. Any Suggestions or help would be greatly appreciated

Mailbox role: Mailbox Service

Error:
The following error was generated when "$error.Clear();
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }
            
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Specified cast is not valid.".

Thanks

I'm setting up Exchange 2013 CU2 in a Windows Server 2012 lab environment. Works perfectly with self-signed certificates, but I wanted to try using a private CA cert created on my domain controller. When I complete the pending CSR in the Exchange Admin Console, the certificate is listed as "Invalid". What is causing this and how do I correct it?

I followed the instructions here:  http://exchangeserverpro.com/exchange-2013-ssl-certificate-private-certificate-authority/

Details of my environment:

All internal & external virtual directory URLs set to be the same: mail.domain.com

External DNS has entries for A, MX, owa and autodiscover, all resolving to my single CAS server via NAT.

AD domain name is: internal.domain.com

Added an extra zone and DNS entries to internal DNS so that mail.domain.com, owa.domain.com, autodiscover.domain.com all resolve to the CAS server's internal IP address instead of going external.

When I create the CSR, it includes SANs for mail.domain.com, owa.domain.com, autodiscover.domain.com, domain.com, CAS1.internal.domain.com

Any help getting this private CA cert working would be appreciated. Is it possible to find any more detail about why the certificate is invalid?

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.

We installed 2013, activating both the CAS and MAILBOX roles on all servers (12).

Afterwards it was decided that we wanted to separate the roles. Exchange was uninstalled on all the servers but there were issues uninstalling on the first installed mailserver. Messages indicated that the database wasn't empty and the uninstall could not continue. The installer then manually deleted the database and uninstalled Exchange.

While trouble shooting the uninstall on the initial server, the installer started installs on servers that hasa successfully performed the uninstall.

Before we could build new mailbox servers we needed to run the following powershell commands:

Set-Mailbox -arbitration "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}" -database "Mailbox Database 0025485816" -domaincontroller dc.root.com

Enable-Mailbox -Arbitration -DomainController dc.root.com -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}"

We have now successfully installed 4 CAS servers and 4 of the 8 mailbox servers. (well, it looks like we have)

I am reviewing the servers and I cannot find the system mailbox. I tried executing "get-mailbvox -arbitration", I run "get-mailboxstatistics", but I just cannot find any reference to the "SystemMailbox{bb558..." mailbox.

I also do not see any references to the systemmailboxes
 SystemMailbox{1f05a927-8f02-4520-9faa-b8f438c93240}
 SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}

So, before I start putting users on here, how can I verify I have everytrhing I need?
Do I perform the "set-mailbox -arbitration..." on the other 2 systemmailboxes?
I also see articles referencing FederatedEmail and Migration accounts. Did I lose these? or have they not gotten created yet?

 Thanks!!

Tom

I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive.  Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V.  I ran the two following commands before trying to install

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Upon trying to run the installer, I recieve the following error.

Error:
The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".

During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck.  I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin.  These four services are the critical services the errors refer to.  I have verified my execution policy is correct

PS C:\Windows\system32> Get-ExecutionPolicy -list

                                                      Scope                                             ExecutionPolicy
                                                      -----                                             ---------------
                                              MachinePolicy                                                Unrestricted
                                                 UserPolicy                                                   Undefined
                                                    Process                                                   Undefined
                                                CurrentUser                                                   Undefined
                                               LocalMachine                                                RemoteSigned

Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|set-service-startuptypeautomatic

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|Start-Service

No matter what I do, the Exchange 2013 CU2 installer seems to fail.  I'd appreciate any possible help with this.

Thanks,

Chris

To add to what I posted, I also have the following error in the event log.

[07/22/2013 13:57:01.0279] [1] Executing:
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                
[07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
[07/22/2013 13:57:01.0373] [1] 0.  ErrorRecord: AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] 0.  ErrorRecord:
System.Management.Automation.PSSecurityException: AuthorizationManager
check failed. ---> System.Runtime.InteropServices.COMException: The
service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. (Exception from HRESULT:
0x80070422)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementObject.Get()
   at System.Management.Automation.PsUtils.GetParentProcess(Process current)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
   at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
  
at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   --- End of inner exception stack trace ---
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   at
System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
context, PSHost host, CommandInfo commandInfo, CommandOrigin
commandOrigin)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
SessionStateInternal sessionState)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String
commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
  
at
System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor
pipe, CommandParameterInternal[] commandElements, CommandBaseAst
commandBaseAst, CommandRedirection[] redirections, ExecutionContext
context)
   at
System.Management.Automation.PipelineOps.InvokePipeline(Object input,
Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".
[07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] [ERROR] The service cannot be started, either
because it is disabled or because it has no enabled devices associated
with it. (Exception from HRESULT: 0x80070422)
[07/22/2013
13:57:01.0388] [1] [ERROR-REFERENCE]
Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
[07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
[07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
[07/22/2013 13:58:09.0121] [0] End of Setup
[07/22/2013 13:58:09.0121] [0] **********************************************

I also have these two errors in event viewer that keep occuring. 

Event 2280, IIS-W3SVC-WP

The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load.  The data is the error.

Event 2300, IIS-W3SVC-WP

The
worker process cannot access the CLR configuration file at 'C:\Program
Files\Microsoft\Exchange
Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'. 
Verify that the file exists and that the worker process has read access
to the file.

Dear All,

I am going an Exchange 2010 to Exchange 2013 migration project, with Exchange 2010 SP3, and Exchange 2013 Cumulative Update 2 installed on one Exchange Organization. (Single forest-single domain)

Exchange 2010 environment consists of two servers, with one on each AD-site (No DAG). Each Exchange 2010 server hosting Mailbox, Transport, and CAS role. Public Folder is configured by using replication between two servers.

Exchange 2013 environment consists of eight servers, with four on each AD-site (DAG is planned, but still not configured). Four servers on each site consist of two mailbox (backend) servers and two CAS servers. Windows NLB is configured between two CAS servers. Autodiscover DNS record is using NLB's IP address. Public Folder is residing on Exchange 2010. It is still not configured and not migrated to Exchange 2013 Public Folder.

Most users is still on Exchange 2010 mailboxes. We did migration on five Exchange 2010 users to Exchange 2013 mailboxes. All migrated mailboxes are still cannot open Public Folder.

On Outlook client residing Exchange 2013 mailboxes, display message window "Cannot expand the folder. Microsoft exchange is not available. Either there are network problems or the exchange server is down for maintenance. (/o=...)".

Some outlook client prompts credential for connecting to Public Folder at most of the time. Users still could send and receive messages, though. I am sure all Outlook versions have complied with Exchange 2013 System Requirements, i.e Outlook 2013, Outlook 2010 Service Pack 2.

I also have done resolution from http://support.microsoft.com/kb/2834139 , using the same setting, but accessing public folder by Exchange 2013 users is still not working at all. 

Any advices for resolution to this case are appreciated. Thanks a lot.

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. 

Hello Everyone,

I am trying to do a new install of Exchange 2013 on a VM with SRV 2008 R2 SP1.

I am running the Setup wizard and getting the following error after the readiness check -

Active Directory must be prepared with 'Setup /PrepareAD' before domains can be prepared for Exchange 2010.

My AD and DNS seem to be all ok. I am using AD Ent credential. I looked at the Exchnagesetup log file and looks like PrepareaAD went through ok. It syas "PrepareAD has been run and replicated to this domain..".

Where it stopped is -

Failed [Rule:DomainPrepWithoutADUpdate] [Message:Active Directory must be prepared with 'Setup /PrepareAD' before domains can be prepared for Exchange 2010.

Anyone can suggest anything?

Also I must say I am relatively new  to MS environment.

Thanks.

Hi everyone,

I've just installed a fresh Windows Small Business Server 2008 Premium Edition on a new server machine, and I was wondering if I can remove / uninstall completely the Exchange Server that comes pre-installed within the WinSBS 2008?

Thanks for the help, appreciate it.

Dhow here.

I have 2 domains registered on Internet are abc.org.vn and abc.vn. They are used for old mail system (Mdaemon). Now I need to migrate to Exchange system.

My Active Directory Server host domain abc.net ( it’s not registered on Internet).

For some reason, I need to setup a mail Exchange System 2013 with required:

Users can use user@abc.org.vn& user@abc.vn for send and receive emails at the same time. And users out of organization ( gmail, yahoo or so on …)  will see “From” field are abc.org.vn or abc.vn, not abc.net on received mails.

In my oponien, i need to configure Accepted Domains abc.org.vn and abc.vn, and then, add Aliasuser@abc.org.vn& user@abc.vn to actual mail address user@abc.net

So, can you confirm my steps? Or can you give me a solution is as detailed as possible ?

Hello,

We have a newly installed Exchange server 2013 on a 2008 server and we published it in ISA server 2006. We can send out emails but we cannot receive emails from external networks. Could it be an ISA 2006 related issue?

the error says: #550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Thank you

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh