Hello,

I have been trying to troubleshoot why PST Capture 2.0 will not show all of the mailboxes from my Office 365 environment (Exchange Online). 

I am using a global administrator (Who is allowed for the Organization Management role)  in the connection settings and have used the following for the server settings:

smtp.office365.com

smtp.outlook.com

outlook.office365.com

pod#####.outlook.com

however when I used the pod url I was able to view all 50+ mailboxes for about 10 seconds before it only showed roughly 10 mailboxes.  However because the pod url changes it is not reliable. Is there anyway for me to force PST Capture to show all of the mailboxes that it finds? 

Hello,

Our HR department would like to have all employees' photographs available in Outlook. When creating an email message, at the bottom of the email message window there is a list of recipients where their photos can be shown. How do I upload the photos? Does it need to be uploaded to the GAL? I use Exchange 2010/Outlook2010.

Thank you.

Hi all, let me just preface by saying thank you very much all your time, help, and patience!  

So I've gone through the Exchange 2013 deployment guide, have installed all the pre-requisites, and am now trying to install Exchange 2013 CU7 on (2) 2008 R2 Enterprise SP1 servers.  Unfortunately it is failing on both of them at the Mailbox Role: Transport Service - 97% with the following error:

Error:
The following error was generated when "$error.Clear(); 
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

I've seen and heard the suggestions about enabling IPv6 on the servers as well as the Domain Controllers which I've done to no avail.  We do not have IPv6 addresses available on our network as we use IPv4 space, but I've heard just having the IPv6 adapter disabled is a lot of times the issue.  So the adapters are set to DHCP even though there's no IPv6 address for it to grab.  The 2008 R2 servers that I'm trying to install Exchange 2013 on are VMs on ESX.  Will the install fail even if it offers to pick up the installation where I left off?  Do I need to completely start from scratch?  Any help would be wonderful!

Hi Everyone,

I'm trying to migrate mailboxes from 2010 -> 2013 and I've com across an odd error.

I've put my skip limit to 5(for bad files), however this error seems to appear regardless. I'm not a Jets DB expert, but not being able to find a row seems quite serious. Any ideas?

Data migrated: 1004 MB (1,052,931,906 bytes) 
Migration rate: 0 B (0 bytes) 
Error: MigrationPermanentException: Error: MapiExceptionJetErrorPageNotInitialized: Unable to find table row. (hr=0x80004005, ec=-1019) Diagnostic context: ...... Lid: 52176 ClientVersion: 15.0.516.30 Lid: 50032 ServerVersion: 14.3.123.2 Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropGetContentsTable [5] Lid: 27962 ROP: ropSetColumns [18] Lid: 17082 ROP Error: 0xFFFFFC05 Lid: 27489 Lid: 21921 StoreEc: 0xFFFFFC05 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 8756 StoreEc: 0xFFFFFC05 Lid: 58765 StoreEc: 0xFFFFFC05 Lid: 48425 StoreEc: 0xFFFFFC05 Lid: 6995 StoreEc: 0xFFFFFC05 PropTag: 0x67B50102 Lid: 4819 StoreEc: 0xFFFFFC05 Lid: 17692 Lid: 5587 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 13300 StoreEc: 0xFFFFFC05 Lid: 21097 Lid: 39027 dwParam: 0x6BD Lid: 8756 StoreEc: 0xFFFFFC05 Lid: 58765 StoreEc: 0xFFFFFC05 Lid: 48425 StoreEc: 0xFFFFFC05 Lid: 5459 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 6483 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 59073 StoreEc: 0xFFFFFC05 Lid: 28220 Lid: 52321 StoreEc: 0xFFFFFC05 Lid: 46177 dwParam: 0xBFE629 Lid: 35937 StoreEc: 0xFFFFFC05 Lid: 44129 dwParam: 0x1183C6F Lid: 60513 StoreEc: 0xFFFFFC05 Lid: 48225 Lid: 9253 StoreEc: 0xFFFFFC05 Lid: 28104 Lid: 13861 StoreEc: 0xFFFFFC05 Lid: 27265 StoreEc: 0xFFFFFC05 Lid: 1750 ---- Remote Context End ---- Lid: 27962 ROP: ropFindRow [79] Lid: 17082 ROP Error: 0xFFFFFC05 Lid: 23649 Lid: 21921 StoreEc: 0xFFFFFC05 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropFindRow [79] Lid: 40685 StoreEc: 0xFFFFFC05 Lid: 28720 Lid: 11621 StoreEc: 0xFFFFFC05 Lid: 56781 StoreEc: 0xFFFFFC05 Lid: 21484 Lid: 23788 StoreEc: 0xFFFFFC05 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0xFFFFFC05 Lid: 29726 Lid: 18462 StoreEc: 0xFFFFFC05 

Hello

After install exchange 2013 cu6 server to root domain in multiple domain environment I cant move mailbox from exchange 2007 to new server because migration batch search mailbox only root domain controller. 
ADTopology list all child domain dc without error.

setup /ps and /pad run without error.

but new-moverequest working.

please help.

Udvozlettel:Sneff Gabor

Hello,

I have a very interesting problem Exchange 2013 installation step on Hyper-V.

I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.

I created virtual machine for first server and this virtual machine domain controller.

And then I created virtual machine for second server and this virtual machine Exchange 2013.

I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.

And then I removed hyper-v role and installed vmware v11. and installed same applications like above.

Very interesting finished installation and opened ecp console. eveythink seen to good.!

Actualy I find problem. 

There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"

I must uninstall this programs before install unified communication api 4.0.

I cannot see on hyper-v when running this feature.

But I can see on vmware this features on programs and feature.

This is very absurt.

Anybody have an idea for this 

Thank you for your clarify.

Hi All,

I recently inherited an environment that's had a handful of admins working on it, all of whom had varying competency levels and poor documentation habits (this story is pretty much a cliche by now, isn't it?). Personally, I have a few years of experience administering AD and Exchange in a DFL of 2008R2, but things were mostly set up correctly in that environment and I typically didn't have to dig in too deeply.  I'm working on some training to improve my knowledge, but at the moment I'm definitely still lacking in many areas.  I've been asked to install some shiny new 2012 servers, retired the old 2003 DC and 2008 DC, raise the domain functional level, and in general get our environment at my new employer up to date.

In the past, this environment was migrated from a 2003 Exchange server, possibly to a 2007 at some point, and now is running on a 2010SP3. One or both of the previous iterations of Exchange was running on the 2003 domain controller that until a week ago was the holder for all FSMO roles in the domain. I have the new DCs spun up, joined, and replicating.  I'm ready to remove the old 2003 DC. I decided to simply shut it down for a few days before doing anything more difficult to undo. When I shut it down to make sure things still work without it, Exchange breaks. I can fire it back up again and Exchange works. 

I have been told by other people in the organization that they remember a previous admin saying something about needing to keep some service routing through the old exchange server (the 2003 DC) to make it work, and if I run an organizational health report in the EMC, it comes up with 2 servers. The problem is that in server management, I only see the 2010 exchange server present, so I don't know what's relying on the 2003 machine. It sounds like the previous people also did a lot of messing with DNS that they didn't quite understand too, so it's possible this isn't even directly an Exchange issue. Since I'm seeing 2 servers reported when there should only be one however, that seems like a really good place to start.

Anyone have any ideas?

Hi I am installing Exchange 2013 SP1 in a test environment. This server will coexist with an Exchange 2007 server.

Both the Exchange 2013 server and the 2007 server are standalone servers with all roles installed.  I understand that the mail flow has changed some in 2013.

On my current Exchange 2007 server, the Client and Default Connectors are disabled.  I then have two additional connectors that were created, the 1st receives incoming internet mail from our spam gateway, and the 2nd receives mail from a few select internal clients that send via SMTP (example: printers and copiers, server application alerts)

My question is regarding the setup of receive connectors on the new 2013 servers. I have already duplicated the 2 connectors that are on 2007. Which of the default receive connectorscan I disable on Exchange 2013?  thanks

Hi

Can any budy share me the best deployment guide of Exchange server 2013 with DAG implementation on Hyper 2012

Also the sizing of mailbox database..

i got this error after  any idea ?

Get-MailUser "usertest" |New-MoveRequest -RemoteLegacy -TargetDatabase "test01" -baditemlimit 10 -RemoteGlobalCatalog $remoteGC -RemoteCredential $remoteCredentials -TargetDeliveryDomain $domainTarget

MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    ......
    Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[2]: Pointer val: 0x51C8A8C000000000
    Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 19796
    Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2015-01-14 20:21:54:210
    Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 0
    Lid: 45169   StoreEc: 0x977
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52209   StoreEc: 0x977
    Lid: 56583
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : FBB4FBA6,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hello,
I am having issues receiving any push notification on OWA Apps for Devices. My Exchange server is running 2013 CU7.

Here is what I have done:
- I created an Office 365 Account
- Verified My Domain but did not change any DNS records other than adding the TXT record required
- Followed this guide:
http://technet.microsoft.com/en-us/library/dn511017(v=exchg.150).aspx
Everything worked except when getting to the line:
New-MsolServicePrincipalCredential -AppPrincipalId $p.AppPrincipalId -Type asymmetric -Usage Verify -Value $credValue -StartDate $cer.GetEffectiveDateString() -EndDate $cer.GetExpirationDateString()
I got the error:

New-MsolServicePrincipalCredential : Invalid value for parameter.  Parameter name: Credential.EndDate.
At line:1 char:1
+ New-MsolServicePrincipalCredential -AppPrincipalId $p.AppPrincipalId -Type asymm ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [New-MsolServicePrincipalCredential], MicrosoftOnlineException
    + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.PropertyValidationException,Microsoft.Online.
   Administration.Automation.NewServicePrincipalCredential

I then removed the last two parameters of StartDate and EndDate, and reran the script and it worked. I don't know if this is the cause of the issue.

- I then tested push notifications in PowerShell with the following:
Invoke-MonitoringProbe PushNotifications.Proxy\PushNotificationsEnterpriseConnectivityProbe -Server:$s.Fqdn | fl ResultType, Error, Exception
I got the result of Succeeded.
- I then tried seeing if I'd get any notifications on my phone when receiving new mail, and I couldn't.

Note:
When I reran the Invoke-MinitoringProbe command and just got all of the parameters, I noticed the following:

ExecutionStartTime : 1/14/2015 6:05:53 PM
ExecutionEndTime   : 1/14/2015 6:05:53 PM

That time is 5 hours past the timezone we are in. Could this be an issue?

Thank you for your time.

Hello,

In our environment, we used to have exchange 2003 but the server is crashed and not turning on. Also, we are not concerned about restoring its data.

I want to install Exchange 2013 but am not able to do so as the AD is still recognizing that there was an exchange 2003 version installed.

What is the best way to clean the active directory so that I can proceed with installing the exchange 2013? My current environment is based on Windows 2012.

Thank you

Goldenberg

Hi all!

I install Exchange Server 2013,but for some reasons I copy the installation files to a folder in my server, but spanish language not copy with that, after installation I try to select spanish language in my ECP an OWA but cant do that because spanish not exist in options...

please need help!!!

Hi all. I implemented Exchange 2013 in my current Exchnage 2010 environment, update this server to version 15.0 build 847.32. Build Exch2010 - 14.3 (build 123.4). Then i move mailbox from exch2010 to exch2013 this request all time "queued" and not migrate to exch2013:

PS C:\Windows\system32> Get-MoveRequestStatistics Scom

DisplayName                         StatusDetail              TotalMailboxSize                   TotalArchiveSize                  PercentComplete 
-----------                         ------------              ----------------                   ----------------                  --------------- 
scom                                Queued                    575.3 KB (589,056 bytes)                                             0

I restart services Microsoft Exchange Replication, Microsoft Exchange Search, Microsoft Exchange Search Host Controller, but no result(

Hi there,

Currently we have Exchange 2010 environment 3 MBX with CAS role and 1 CAS dedicated for External Client request. Also OutlookAnywhere is already enabled on Exchange 2010 CAS box's.

We are planning to install Exchange 2013 server in our environment and our plan is to have 3 MBX and 2 CAS dedicated.

Both the Exchange 2013 CAS will be also be responsible for internal Client and external Client request.

I plan to install 2013 MBX boxes in the environment and then both CAS 2013.

Now my question is how can i ensure that the client request internally and Externally are configured to received on Exchange 2013 CAS server. 

Where all should i make changes on CAS 2013 to achieve the same so that Mailbox which are on Exchange 2010 still connects through Exchange 2013 till i completely migrate the mailboxs form exchange 2010 to exchange 2013 box.

Hope i got my point clear what i am expecting :)

BR/Deepak

Hi all,

I would need to setup an exchange 2013 in new data center and coexist with exchange 2010 (server room).

Hoping you guys can shed some lights on this. below is the existing exchange 2010 info

AD single forest Domain : ABC.local
Email STMP address : @temp.com
1 x Exchange 2010 server (CAS/HUB/Mailbox), 1 x Third Party Mail Gateway/SPAM (Data center)

Public DNS record
MX record : temp.com (using godaddy)
A record - mobile.silver.com (OWA/EAS) -using netregistry.net
A record - oa.silver.com (outlook anywhere) using netregistry.net

Internal DNS record

-A record for exchange server only

Virtual Direcotory (Exchange 2010)
Internal URL : server1.abc.local/owa
                     server1.abc.local/activesync
                     server1.abc.local/oab
                     server1.abc.local/EWS
                     server1.abc.local/Microsoft-Server-ActiveSync

External URL : mobile.silver.com/owa
                      mobile.silver.com/activesync
                      mobile.silver.com/oab
                      mobile.silver.com/EWS
                      mobile.silver.com/Microsoft-Server-ActiveSync

Outlook Anywhere
ExternalHostname : oa.silver.com
ClientAuthenticationMethod : Basic

Public SSL
Subject Alternative Name
-DNS Name=oa.silver.com
-DNS Name=abc.local
-DNS Name=mobile.silver.com

What I am planning to do on Exchange 2013 (new AD site)

1. Upgrade Exchange 2010 to SP3 with latest roll u

2. Install Exchange 2013(multi role) with SP1 and latest roll up (Install pre-requisites, Prepare schema/AD)

3. Obtain Public SSL (SAN- mail.temp.com, autodisover.temp.com),

4. Configure pinpoint DNS (mail.temp.com, autodiscover.temp.com)

5. Change all Internal & External Vdir to https://mail.temp.com/<owa,etc>

6. Import & configure public SSL on Exchange 2013

7. Configure autodiscover URI (SCP) to https://autodiscover.cscms.com/autodiscover/autodiscover.xml

8. Create internal DNS record mail.temp.com, autodiscover.temp.com pointing to new Exchange 2013

9. Create A record, CNAME for mail.temp.com, autodiscover.temp.com on public domain temp.com that pointing to new public IP address by new ISP

10. Migrating mailbox, external mail will flow to exchange 2010 to exchange 2013

11. Mail flow cutover

Please can help to review the 11 steps? maybe something important things are missing?

To coexist with 2010, question is

1. I would like to remain two different namespace (silver.com & mail.temp.com) for Exchange 2010 & 2013.

    Will the Proxy redirection works? Since they are in different site and different namespace

2. Remain -autodiscoverServiceInternalURI with no change on Exchange 2010? since no internal or external DNS record

3. Do I need to add/change any configurations on receive/send connector in order to send email between Exchange user

    2010 & 2013?

4. As you can see the above point no.9, new public ip address for exchange 2013 mail.temp.com and existing public IP address.

    Meaning Exchange users 2010 will connect to mobile.silver.com while exchange users 2013 will connect to mail.temp.com. they will run independently?

5. For external mail flow, when to cutover after moving all user to exchange 2013?

 6. During the coexistence, The external mail flow (inbound) go through Exchange 2010 then 2013?

     If yes, anything need to be changed on the connector?

Thanks in advance :)

I am having an issue trying to move over my public folders from my 2010 server to my 2013 server.  It keeps on failing or not even starting the move. I am petty sure this coming down to1 folder I have called 'Helpful Websites' from previous versions of Exchange that has been moved over a few times. I can't delete the folder no matter what I try. I have owner access to the folder. This is the error I get trying to delete it. I don't need it and nothing is in the folder anymore.

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Action 'Remove' could not be performed on object 'HelpfulWebsites'.

HelpfulWebsites
Failed
Error:
Cannot delete the object '\XXXXXXXXXCorporateForms\HelpfulWebsites'. Please make sure that you specified the correct identity and that you have the correct permissions to delete it.

MapiExceptionPartialCompletion: Unable to delete folder. (hr=0x40680, ec=0)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=61]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=173][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropDeleteFolder [29]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 19297  
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropDeleteFolder [29]
    Lid: 4887    StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849  
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 24721  
    Lid: 20625   StoreEc: 0x80070005




--------------------------------------------------------
OK
--------------------------------------------------------

I can remove other folders without issue but I think if this one is gone I can migrate them over with no issue. My Public Folders are very small like 200MB is all.

Good day all.  We have installed Exchange 2013 into our single server 2010 environment.  After a successful install I am not able to log onto the 2013 EAC.  I know that since my mailbox is still on 2010 that I should not see EAC unless I use the

https://server/ecp/?ExchClientVer=15 but this does not work either.

I opened a case with MS on this and got a response but I am confused as to one part of the instructions.  I replied to the engineer but she is offline for a few hours and I wanted to drop the instructions here and see if you know what it is that she is stating. 

Question that I need answered:  Below, at step 4 she left a note "Please run above command with your production install directory script". What you think this line means?  Run this script from the provided scripts that came with 2010?  Grab the script from 2013 files and run it on the 2010 server?  or run this script on the 2013 server?

Thanks in advance!

Action Plan
=========
1.    Recreate the ECP virtual directories on exchange 2013 server with the following commands (Run as Administrator) on EMS:

Remove-EcpVirtualDirectory -Identity "Server2013\ecp (Default Web Site)”

New-EcpVirtualDirectory -Server Server2013 -InternalURL https://Server2013.domain.com/ecp

Set-ECPVirtualDirectory -Identity "Server2013\ecp (Default Web Site)” -AdminEnabled $True

2.    Recycle MSExchangeOwaAppPool under IIS, Application Pools.

3.    Ran "iisreset" on EMS.

4.    Ran the "UpdateCAS.ps1" powershell script from the Exchange install directory scripts subfolder. The command example is as follows:

C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateCas.ps1

Note: Please run above command with your production install directory script.

5.    Open the IIS manager, find the Exchange Back End site, double-click Authentication on the right “/ecp Home” page. Point to Windows Authentication after launching Authentication windows. Right-click windows authentication, point to Providers. Make sure Negotiate and NTLM under Enabled Providers. You can refer to the related screenshot from my test environment as below:

6.    Then re-run "iisreset" EMS.
=========

Hi,

For some reason, my Exchange servers are no longer updating. Im getting error code 80072EFD.

I have googled this and found a few articles suggesting Time mismatch and a root certificate missing. This is not the case as I have checked both...

Any other ideas? This seems to have happened after I have applied CU5 on one of the servers.

Thanks in advance.

Hi All ,

How to configure Exchange 2013 OWA with Single Sign On ?

Thanks .