Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

After Migration Queries - 2013 Sp3 to 2013 CU3

$
0
0

dear friends,

its been few days completed migration and few doubts which are in my mind wanted to share with you if some one can please guide on the same.

1. During the migration i added 2013 and started moving mailboxes. The observation was that till the time the mail box was on 2010 all is good and once mailbox gets transferred it stops. as i havent had any connector configured on 2013. The article i followed guided to configure the connector once all mailbox moves.. not sure if this is correct as this will be a good time and dont knw when all will finish so we can have downtime.  - What is the recommended way.

2. Can this be fully transparent to user.

3. It took almost 2days 2 night to transfer - 100Gb data... is it normal ... Is there any other fast and reliable way

4. i didnt migrated the SSL from source instead i applied a new SSL reason being my source SSL was about to expire. But then all the users started getting the SSL proxy error... - Not sure why, i was expecting this to work without issues

5. Password prompt : Not sure why my half of the users started getting password prompt continuous from outlook,.

6. Any suggestions for anti-Spam as forefront is no more there and i am getting loads spam, i knw about third party .. - SUGGESTIONS

These were my observations .. and i hope i am able to put all... please share your views on above.



Thanks
Happiness Always
Jatin



New-PublicFolderMigrationRequest - Couldnt connect to the source mailbox

$
0
0

Hi All,

When performing the new-publicfoldermigrationrequest command on exchange 2013 server I receive the following error:

Couldn't connect to the source mailbox.
    + CategoryInfo          : NotSpecified: (:) [New-PublicFolderMigrationRequest], RemoteTransientException
    + FullyQualifiedErrorId : 19495301,Microsoft.Exchange.Management.RecipientTasks.NewPublicFolderMigrationRequest
    + PSComputerName        : svr12365.bcb.local

I am copying from Exchange 2007 on sbs2008 server. if I run get-publicfolderdatabase from exchange 2013 powershell it returns with the correct database name and server.

any ideas?

Many Thanks

Exchange 2013 Cu3 Unable to get ECP or OWA working.

$
0
0

Hello, 

I'm expirencing difficulties with exchange 2013 CU3, I installed two exchange 2013 servers one for the mailbox role and the other for CAS. After that I upgraded to CU3 and with the default configuration I cannot access the ECP or OWA. 

I can access the Exchange managment shell.

I get a blank page with the url: https://CAS.Domain.local/ecp/login.aspx?ReturnUrl=%2fecp

Edit: 

After setting the authentication parametres in IIS to the default values I am instead redirected to a blank page with the following url: https://CAS.Domain.local/owa/languageselection.aspx?url=%2fecp%2fdefault.aspx


Relay

$
0
0

Hi,

We have some website's that our customers own that need to send mail through our exchange 2013 server, we want to create a specific user to handle this but it seems we can't give the user permission to relay mail to anyone outside of our exchange environment. Is there a guide on how to achieve this ?

Exchange 2013 on 2012 Server Cumulative Update 3 Install Error "No Suitable Directory Servers Found" Answered

$
0
0

Exchange 2013 on 2012 Server Cumulative Update 3 Install Error "No Suitable Directory Servers Found" Answered

Topology: 1 2k12 host and 12 2k12 virtual servers. 2 Active Directory Domain Controllers both GC. - DC1 and DC2 respectively.

While installing exchange 2013 cumulative update 3, I received an error indicating that the update was not able to contact an Active Directory Server.

I bought a golden ticket and the tech entered: C:\ExchUPDCumulative3>setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms /domaincontroller:DOMAIN.DC2 into the elevated command prompt.

This solved the problem...  Subsequently, I re-ran the update using /domaincontroller:DOMAIN.DC1 to see if the problem was with my DC1 but the update ran fine. So it doesn't seem to have ever had a problem with seeing the Domain Controllers but whatever the GUI is doing to detect the Domain Controller is not working. So if you run into this problem, the command line above is the answer. Below is the error text.

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: "Unable to set shared config DC.".

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3132) Forest DOMAIN.LOCAL. Topology discovery failed, error details

No Suitable Directory Servers Found in Forest DOMAIN.LOCAL Site Default-First-Site-Name..

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3132). The Exchange computer DOMAINDC1.DOMAIN.LOCAL does not have Audit Security Privilege on the domain controller DOMAINDC1.DOMAIN.LOCAL. This domain controller will not be used by Exchange Active Directory Provider.

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3132). The Exchange computer DOMAIN.DC2.DOMAIN.LOCAL does not have Audit Security Privilege on the domain controller DOMAIN.DC2.DOMAIN.LOCAL. This domain controller will not be used by Exchange Active Directory Provider

Process MSExchangeFrontendTransport.exe (PID=5396). WCF request (Get Servers for DOMAIN.LOCAL) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details

 No Suitable Directory Servers Found in Forest DOMAIN.LOCAL Site Default-First-Site-Name.

   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()

   at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)

   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)

   at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()

   at System.Threading.Tasks.Task.Execute()

   at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)

   at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)

   at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()

   at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action

Slow Exchange Migration

$
0
0

I am currently on exchange 2007 SP3 RU11

i want to install exchange 2013, but i'm wondering if I can do the install and slowly test things and migrate

if i run the exchange 2013 install, can i have it coexist on the side but keep everything pointed to my exchange 2007 environment till i'm ready to move over?

currently use

outlook 2013 MAPI clients

outlook 2011 EWS os x clients

active sync clients

no OWA

thanks, couldn't find a lot of info on this.

Name spaces

$
0
0

Hi!

Today we have two Exchange sites running Exchange 2010 sp3. Both sites are internet facing and have a DAG deployed.

Currently we have two names for webmail.

for site europe.

internalurl:webmail-eu.company.xx

externalurl:webmail-eu.company.xx

For site US it's

internalurl:webmail-us.company.xx

externalurl:webmail-us.company.xx

If a user access the VIP for webmaileu and the mailbox is located in US, the connections is sliently redirected. Works perfect both ways in our current setup.

Now we want to deploy Exchange 2013 in both sites. Once deployed and all the certificates are in place, can we point the webmail url's to point to Exchange 2013?

And what about outlook anywhere, can we configure the internalUrl for OA to be the same as webmail for each of the sites. I'm guessing that we can control what url is handed out to our Outlook clients by scoping autodiscover.

Any suggestion on how to configure this?

Best regards,

UC


Unresolved ObjectType on all newly created or migrated 2013 Mailboxes

$
0
0

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.


Exchange 2013 CU3 failed; multiple errors

$
0
0

Upgraded to CU3 last night.  5 out of 6 were successful.

Error:

The following error was generated when "$error.Clear();           

                  $RoleDomainController = $RoleDomainController                 

                  $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "The virtual directory 'PowerShell' already exists under '$RoleFqdnOrName/Exchange Back End'.

Parameter name: VirtualDirectoryName".

I successfully manually ran the cmdlet to remove the Powershell Virtual Directory and got a bit further:

get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController

Then came this error:

Error:

The following error was generated when "$error.Clear();

        Get-PushNotificationsVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | Remove-PushNotificationsVirtualDirectory -DomainController $RoleDomainController;

        New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;

      " was run: "The virtual directory 'PushNotifications' already exists under $RoleFqdnOrName/Exchange Back End'.

Parameter name: VirtualDirectoryName".

I manually deleted the PushNotifications virtual directory and got a little further.  Next came this error and I'm stuck:

Error:

The following error was generated when "$error.Clear();

          Update-OwaVirtualDirectory -DomainController $RoleDomainController;

          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";

          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;

          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeOWAAppPool" -Version:"v4.0";

          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeOWACalendarAppPool" -Version:"v4.0";

        " was run: "An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.

. HResult = -2147024893".

I've verified the path and file exist for $RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" and the MSExchangeOWAAppPool, MSExchangeOWACalendarAppPool pools exist.

At this point I can't get the CU3 to complete and I don't know how to uninstall Exchange and start over.  I've tried .\setup.exe /m:uninstall /IAcceptExchangeServerLicenseTerms and it just resumes the failed install.

I'm tempted to blow the server away and manually remove the server with ADSIEdit, but I'd like to find the fix if possible.


Ambers


cross forest users send on behalf access

$
0
0
Hi Guys, been searching around google for information on how to grant send on behalf of access to a mailbox for a user located in a separate exchange forest but getting no where fast.  Background to why I want to do this is I have created a new active directory forest and installed exchange 2013 with a view to migrating all users/computers etc from out existing forest that is currently hosting our exchange 2010 organization.  Both these forests are on the same physical LAN and are shaing the same subnet and smtp namespace.  I want to be able to migrate the users in stages so during the migration period I need to be able to allow users in the target forest to be able to send on behalf of users in the source forest.  Is this possible or am I wasting my time?  Any help greatly appreciated :-)

Exchange 2013 CU2 upgrade to CU3 Failed at Front End Transport Service

$
0
0

Error:

The following error was generated when "$error.Clear();

         $feVdirName = "PowerShell (Default Web Site)";

         $beVdirName = "PowerShell (Exchange Back End)";

         $vdirName = "PowerShell";

         $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

         get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

         new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

         new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

       " was run: "The virtual directory 'PowerShell' already exists under 'server01.XXXXX.local/Exchange Back End'.

Parameter name: VirtualDirectoryName".

Thanks


Exchange login error

$
0
0

Hi 

when i login exchange 2013 iam getting the errors.

1. There is a problem with this website's security certificate and then i click continue this website and it asks for username and password

2. i have given domainname\administrator to get login

3. then i asks for timezone and language and then i clicked save 

and iam getting error message

4. server error in /owa application the active directory user wasn't found.

Please help me in regarding this

Regards

B.Ashok

2010 -> 2013 Public Folder migration failed - Property Expression isn't valid

$
0
0

We just migrated from 2003 to 2010, and now on to 2013.  I have Exchange 2013 CU3 installed, and all mailboxes moved.  When trying to move the public folders, I'm getting an error about DataValidationException.  Property expression <PF Name with spaces> isn't valid......

Many articles refer to a mail-enabled public folder with spaces can't have spaces in the alias.  This is NOT a mail-enabled public folder, so there isn't an alias that I can find.

Any ideas?

Thanks!

--Kent

OWA and ECP not working anymore

$
0
0

When I try to access https://myserver/ecp, I get a login prompt, enter my credentials, then I hit this error

:-(

something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
Want to be able to use your email when you're offline?

Next time you are connected:
1. At the top of Outlook Web App, next to your name, click Settings
2. Click Offline settings and turn on offline access
3. That's it! You'll never see this message again.

Same thing for owa.

I tried the remove-owavirtualdirectory and remove-ecpvirtualdirectory cmdlets, then re-create them. Same issue.

Also cleared the browser's cache several times.

Thanks for any help you could provide

Martin

Autodiscover not setting outlook anywhere accordingly

$
0
0

We have installed 2013 Mailbox and CAS Server on separate boxes into our 2010 environment.  We have migrated a few users and it seems autodiscover does not configure Outlook anywhere on the Outlook 2010 client.  If we configure this manually the user can connect and view mail.  Outlook web access is fine, certificates appear to be working as we can manually configure Outlook and it is ready mail very well.  We are running Exchange 2013 CU3, and have installed the certificate on the CAS.  the autodiscover dns entry has been changed to point to the 2013 CAS.

Is this a common problem and what can we try to do to resolve this issue ?

I've read a few different posts and looked at authentication of virtual folders (still default setup), certificates (added new certificate from company CA).  Any ideas ? 


Exchange 2013 Install - Setup can't verify that the 'Host' (A) record for this computer exists

$
0
0

"Warning:

Setup can't verify that the 'Host' (A) record for this computer exists within the DNS database on server 192.168.x.x.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.HostRecordMissing.aspx"

This is the warning message that I get during install of Exchange 2013. The DNS is working totally fine without any errors so I looked this problem.

To get rid of this warning message, all you have to do is make sure the IPv4 DNS is set to 127.0.0.1 on your network interface and not to the IP address of the IPv4 interface. The warning message doesn't look at the IPv6 interface so you can leave the IPv6 interface as is. I ignored the warning message and left the DNS set to the IP of the IPv4 interface and Exchange 2013 installed without any errors.

Microsoft should really fix this warning message. If I set the DNS IP to be the same as the IPv4 interface IP, I shouldn't get this warning message at all.

Problem migrating Public folders from 2007 to 2013

$
0
0
Hi.

We are migrating from Exchange 2007 to 2013.

I am currently trying to migrate our public folders to the new server, but it is going very slowly, and it fails after working for some time.

In my report for the migration I keep getting these errors:

1/17/2014 9:42:27 AM [WINSRV01] Transient error ResourceUnhealthyException has occurred. The system will retry (14/60).

1/17/2014 9:42:35 AM [WINSRV01] The move is currently stalled due to 'Remote Resource' lagging behind on resource 'Resource 'CiRetryQueueSize(New Mailbox Database)' is unhealthy and shouldn't be accessed.'.

My contentindexretryqueuesize is currently about 7000.

What is causing this, and how do I fix it :)

Regards

Jens Hyllegaard

Exchange server 2013 roles error

$
0
0

Hello,

After successfully installed Microsoft Exchange 2013 coexistence with Exchange 2007, I run into many problems. I am getting event ID 1023:Microsoft-Windows-Perflib: Windows cannot load the extensible counter DLL MSExchangeIS. The first four bytes (DWORD) of the Data section contains the windows error code.

Event ID 6003: MSExchange Common: ConnectitityLog: Failed to create log directory: Access is denied to path. What kind of access permission do I give to the file directory?

Jimmy


Jimmy

Alternate ways to transfer a single Public Folder?

$
0
0

Hi,

I've been troubleshooting a single public folder migration issue for a couple of days now.  The post is here: 2010 -> 2013 Public Folder migration failed - Property Expression isn't valid

If I can't get it transfered from Exchange 2010, isn't there a way to export it via Outlook to a PST file and then re-import it into Exchange 2013 and re-set permissions?  I would rather do it the recommended way, but I haven't been able to get any help with the transfer.

Any recommendations would be appreciated!

Thanks in advance!

--Kent

A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.

$
0
0

Outlook anywhere not working , all testing ok except below:

Attempting to ping RPC proxy mail.abc.com.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: 35d8bc5e-0a93-444c-a25f-ad0e991fd5b8
X-CasErrorCode: EndpointNotFound
Persistent-Auth: true
X-FEServer: E2013HT
Content-Length: 0
Cache-Control: private
Date: Fri, 12 Jul 2013 12:34:26 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>