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

decomissioning Exchange 2003

November 7, 2014, 8:43 am
$
0
0

Hello,

My current environment consists of Exchange 2003 version 6.5 (Build 7638.2:Service Pack2) server and Exchange 2010 version 14.2 (Build 247.5). All the Outlook clients point to Exchange 2010 and there is no need to keep the Exchange 2003 server anymore. How do I proceed with removing this server? Should I go to Add/Remove Programs in Control Panel and uninstall it from there? If it fails, where do I remove all links to it from Exchange 2010 server? After that I would simply shut down the Exchange 2003. Please advise. Thank you.

↧
Search

unable to get mail in outlook 2013

November 8, 2014, 8:25 am
$
0
0

i have an exchange server running microsoft exchange 2013 on windows server 2012 r2 with iis8

i can access my emails via my ipad, iphone and outlook web app but its not letting me connect to my email account via outlook 2013 and i cannot find a reason for it not to be working.

how do i get the account to work in outlook 2013?

↧
↧

Mail Flow Problem During Migration from Exchange 2010 to Exchange 2013

November 8, 2014, 2:07 am
$
0
0

Hi,

I am currently migrating existing Exchange 2010 to Exchange 2013. So far, I have successfully installed Exchange 2013. I can also migrate users to and from exchange 2013. But the problem is, User on Exchange 2013 can received emails from Exchange 2010, however, emails sent from Exchange 2013 are stuck in queue and not delivering to Exchange 2010 users.

This could be worth mentioning that I have a multiple AD sites. Exchange 2010 was deployed in site ABC whereas, I deployed Exchange 2013 in Site XYZ which was a requirement. The same can be seen in the screenshot below:-

What could be the problem with mail flow as I mentioned earlier? Can it be the problem due to different site?

Thanks.


↧

Cannot install Exchange 2013 CU6 due to prerequisite failure, but they are already installed

November 9, 2014, 12:14 am
$
0
0

I have Exchange 2013 installed on Windows Server 2012 (not R2). I'm trying to install the Exchange 2013 CU6 upgrade and it fails every time with the below errors that certain prerequisites are not installed. However, according to the server manager they are all already installed.

Rebooting didn't help and running powershell as admin and then running the CU6 upgrade via the command line didn't help either. Thanks in advance for any help.

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                                                         COMPLETED
    Prerequisite Analysis                                                                             FAILED
     The 'IIS 7 Dynamic Content Compression' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7Htt
pCompressionDynamicNotInstalled.aspx

     The 'IIS 7 Static Content Compression' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7Htt
pCompressionStaticNotInstalled.aspx

     The 'Directory Browsing' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornDirecto
ryBrowse.aspx

     The 'Tracing' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpTra
cing.aspx

     The 'Static Content' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornStaticC
ontent.aspx

     The 'Web-Mgmt-Service' component is required. Install the component via Server Manager.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ManagementServi
ceInstalled.aspx

↧

Event 2193, MSExchange ADAccess

November 4, 2014, 2:18 am
$
0
0

Hi,

After updating our Exchange 2013 SP1 servers to CU6 we get a lot of these errors in the Application log on them. All our DCs except two that is on the same site as the Exchange servers, is in the error messages. It is a bit random in time but each DC gives an error about every 25 minutes on both Exchange servers. Any idea?

Event Id: 2193

Source: MSExchange ADAccess

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3576). Suitability check failed for server xxxxxx.domain.local with an exception. Error: System.InvalidOperationException: GetDomainControllerInfo() called on an invalid handle.

   at Microsoft.Exchange.Win32.SafeDomainControllerInfoHandle.GetDomainControllerInfo()

   at Microsoft.Exchange.Data.Directory.TopologyDiscovery.SuitabilityVerifier.CheckNetLogon(SuitabilityCheckContext context) (in CheckNetLogon).

↧
↧

Can't connect Outlook to Exchange 2013 during migration

November 9, 2014, 6:03 pm
$
0
0
I'm in the middle of a migration from Exchange 2007 to Exchange 2013 and have hit a snag that's baffling me. I've been using the excellent instructions at http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html as a template, and they've worked fine for our small organization up until I tried to connect Outlook 2013 to a test mailbox on the new Exchange 2013 server (page 13 of the above article). No matter what I do, it won't connect.

This is a small environment with only a single Exchange server under normal circumstances. Now we have the old 2007 server and the new 2013 server coexisting until the migration is done. Mail flow between the two servers seems to be fine, and I can send and receive mail on the test mailbox using OWA on the 2013 server. I just can't connect Outlook to it.

When I try to create a new Outlook profile for the 2013 mailbox, something odd happens. If I use "EX2013" as the server name, it doesn't find the server or mailbox. (DNS has no problem resolving the server name correctly.) If I type "EX2007" (the old server name) it [i]does[/i] resolve... but it fills in the server name of EX2013.internal-domain.org. It's supposed to fill in a server name of <mailbox GUID>@email-domain.com, but it doesn't. I then get this message: "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed."

If I run test-OutlookWebServices on EX2013, I get failure on the autodiscover test and "skipped" on the remaining ones. Specifically, I get this error:

System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

If I run test-OutlookWebServices on EX2007, I would get the same result until I disabled loopback check (as a test) per the article athttp://support2.microsoft.com/default.aspx?id=896861. With the loopback check disabled on EX2007 I get further, but then there's an error 1013 that says, "[EXPR]-Error when connecting to https://mail.maildomain.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine". This is followed by an error 1017 about contacting the RPC/HTTP service at the same address.

I've disabled IPv6 on the EX2007 server since it has been suggested as a possible culprit in this kind of scenario (seehttps://support.microsoft.com/kb/2794253?wa=wsignin1.0).

I've also tried modifying the hosts file on both the client and EX2013 in an effort to connect to it directly (autodiscover and all internal mail server names pointing to EX2013, bypassing EX2007 altogether), but I get the same result.

Domain names are as follows (modified to protect my client):

Old server: EX2007.internal-domain.org
New server: EX2013.internal-domain.org
E-mail addresses: <user>@email-domain.com
External: mail.external-domain.com

SCP (both servers): https://autodiscover.email-domain.com/autodiscover/autodiscover.xml

Yes, that's three different domain names we're dealing with. It's not my choice to do it that way, but it's what we've got in place. Outlook Anywhere is not being used externally, though, so that simplifies things somewhat.

The following is in the SSL certificate:

mail.external-domain.com (and this is the certificate name)
EX2007.internal-domain.org
EX2013.internal-domain.org
autodiscover.email-domain.com

Internally I have split DNS to point mail.external-domain.com to the EX2007 server. The autodiscover.email-domain.com address points to the EX2007 server, but as I said above, I tried pointing that name to EX2013, and it made no difference I could see.

I figure I must be missing a permissions issue or a domain name mixup somewhere, but nothing I've tried has fixed it, and I've hit a dead end on knowledge base articles and existing answers I've found in support forums. Anybody have any ideas?
↧

Ex2013 - "This user does not have an Exchange mailbox.”

October 24, 2014, 10:49 am
$
0
0

I've been researching this and I think I found a solution, but need a sanity check.

I'm upgrading from Exchange 2007 to 2013 (co-existence migration), and when I try to migrate a couple test mailboxes I get an Error: “This user does not have an Exchange mailbox.”

https://social.technet.microsoft.com/Forums/exchange/en-US/d0c96836-3ad5-49c8-bd85-2df52f481b0c/exchange-2013-migration-says-the-user-does-not-have-an-exchange-mailbox?forum=exchangesvrdeploy

http://support.microsoft.com/kb/2812509/en-us

The “get-mailbox –arbitration” and “get-mailbox –arbitration |fl name,alias” commands show corrupted several corrupted mailboxes on the 2013 server:

SystemMailbox{1f05a927-ac1a-45fa-9abc-338f309be380}

SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}

Migration.8f3e7716-2011-43e4-96b1-aba62d229136

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042

The remaining mailbox (SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}) is not corrupted.

Running the command to enable the migration mailbox fails.  Error: “This task does not support recipients of this type.  The specified recipient “Migration.{GUID}” is of type UserMailbox.

This thread suggests deleting them from ADUC and then running ADprep again to recreate them.  

https://social.technet.microsoft.com/Forums/en-US/bba16b29-0d1f-4f2b-943c-e2110ae0d8b6/fixing-corrupted-mailboxes-after-migration

Is it safe to delete all of the arbitration mailboxes (including the non-corrupted system mailbox) and then recreate them?

↧

mailbox migration failing after Upgrading CU5 -> CU6

November 10, 2014, 3:56 am
$
0
0

hello fellow readers,

we have an Exchange 2007 (latest needed Patchlevel) / Exchange 2013 CU6 Environment and are now having trouble migrating user mailboxes from the Ex2007 mailbox server to the new Ex2013 server.

migration of the first boxes before applying CU6 went fine and smooth, but now all mailbox moves are stuck with the status "Qeued".

a ps command "get-moverequeststatistics karl.treiber" brings the following

Postfach 'Karl Treiber' wird zurzeit nicht verschoben.    + CategoryInfo          : InvalidArgument: (karl.treiber:MoveRequestIdParameter) [Get-MoveRequestStatistics], Mana   gementObjectNotFoundException    + FullyQualifiedErrorId : [Server=SERVERNAME,RequestId=bf51511d-c7b8-4b39-ad60-caa71015cc6c,TimeStamp=10.11.2014 11   :27:29] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 9B1AC428,Microsoft.Exchange.Management.Recipien  tTasks.GetMoveRequestStatistics    + PSComputerName        : SERVERNAME.DOMAIN.local

i'm guessing that this is correct, as the migration hasn't started yet. in somehow similar threads people suggest putting the BadItemLimit higher, so i tried running ps command "set-moverequest karl.treiber -baditemlimit 9999" bringing the following

ARNUNG: Wenn ein Element nicht aus der Quelldatenbank gelesen oder in die Zieldatenbank geschrieben werden kann, wird
es als beschädigt betrachtet. Wenn Sie für 'BadItemLimit' einen anderen Wert als Null angeben, fordern Sie an, dass
Exchange diese Elemente nicht in das Zielpostfach kopiert. Nach Abschluss der Verschiebung sind diese beschädigten
Elemente nicht im Zielpostfach verfügbar.
Der Vorgang konnte nicht ausgeführt werden, weil keine Objekte des Typs
'Microsoft.Exchange.MailboxReplicationService.TransactionalRequestJob' auf 'DC.DOMAIN.local' gefunden wurden.
    + CategoryInfo          : NotSpecified: (:) [Set-MoveRequest], ManagementObjectNotFoundException+ FullyQualifiedErrorId : [Server=SERVERNAME,RequestId=ab82c24b-7914-4382-8de2-34462d4993b3,TimeStamp=10.11.2014 11
   :38:01] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 285DB966,Microsoft.Exchange.Management.Recipien
  tTasks.SetMoveRequest+ PSComputerName        : SERVERNAME.DOMAIN.local

my guess is, that something is missing in AD - but what? DC replication is checked and working as normal. i looked up the AD object of the user, searchung for Exchange values, finding some connecting to mailbox moves, but none similar to "Microsoft.Exchange.MailboxReplicationService.TransactionalRequestJob".

everything worked in CU5 -> after updating to CU6 we had serious issues with mailbox databases in dirty shutdown and called MS or help. as mentioned here this was a known error and they gave us the hotfix for that. the hotfix seemed to be so "hot" that it fixed the database problem but brought new ones, as the fix seems to not check Exchange installation path, assuming its always c:\Program Files\... (which it is not in our case).

here they suggest to run "setup /preparedomain" again, but i am worried about possible new problems.

has anyone suggestions what to check?


↧
Search

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

October 25, 2014, 5:03 am
$
0
0

hi,

I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot. 

I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?

Thanks

↧
↧

ECP Log In loops back to log in page

November 10, 2014, 7:43 am
$
0
0

Hi,

I recently installed two exchange 2013 server and migrated from exchange 2010. Up until today i have been able to access the ECP no problem. But now i get the login page, i fill in my details and it goes right back to the login page again. If i put in the incorrect details, it will tell me that they are incorrect.

Can anyone help please?

I think it may have started happening since i restored a Hyper-V Checkpoint of it.

Thanks

↧

Configure service connection point question

November 10, 2014, 1:04 pm
$
0
0

I am upgrading from Exchange 2007 to 2013 using the Exchange Server Deployment Assistant. I am at theConfigure service connection section.

My environment has three domains - a.com, b.com and c.com.

The exchange environment serves two related organizations with different domains - b.com and c.com.

a.com is *not* used for email addresses - just a domain name for accessing OWA.  When a user in b.com or c.com access OWA they go to https://owa.a.com/owa.

When setting up the service connection point, what is the autodiscover host name?  The Exchange Server Deployment Assistant asks me to set a variable like this.

$AutodiscoverHostName = "autodiscover.contoso.com"

For my case would I use a.com?  Or should I run through the steps twice - once for b.com and once for c.com?

Thanks

 Jon

↧

Setting RpcClientAccessServer on Mailbox Database

October 29, 2014, 6:03 am
$
0
0

Hello

In a brand new exchange 2013, i would like to change the RpcClientAccessServer as done on exchange 2010.

Ok, i know, Exchange 2013 does not use it... but hold on ;)

Why i want to change it? Lets see:

I have a CAS server and a MBX server.

When configuring outlook, manually, not with autodiscover, it asks for a server and a username. Even after  configuring the https over rpc, you need to specify manually the server name

On exchange 2010, changing the RpcClientAccessServer on the database, i can specify with server to point, but in Exchange 2013 i cant.. and i have to type the MBX server fqdn. In 2010 i used to configure it with the webmail url, easier to remember than the server fqdn.

Is there a way to do the same on 2013?

Thanks!!!!

↧

Database Script

October 13, 2014, 11:19 am
$
0
0

Hi,

I'm trying to create the database volumes via the exported scripts from the Exchange 2013 calculator, to try and simulate a deployment. I've scaled back for the home lab, but basically I want to use the script to create the volumes and mountpoints etc.

The spreadsheet has 4 DB's per volume and I've setup 8 DB's so it should create 2 volumes...

I run the script, it creates the first volume and first 4 DB's without any issues, then it won't create the second volume so it creates the folders in the mountpoint folder (Just not mounted...)

The VM I've setup is very basic for home testing before scaling up for clients, but has the following disk

Disk 0 = OS\Exchange etc.
Disk 1 = Offline
Disk 2 = Offline

It does the first part correctly, so what am I doing wrong?

Any help/advice would be appreciated

Michael 

↧
↧

Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013

October 21, 2014, 2:55 am
$
0
0

Hi ,

Please correct me if i am wrong and also all of you tell me your valuable suggestions.

Like as said in the below article we are having an exchange 2010 ambiguous url's in place.

Referred article : 

http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx

As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .

Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010 environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?

Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.

Regards

S.Nithyanandham

↧

X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException can't access 2007 mailbox from 2013 server

July 7, 2014, 5:59 pm
$
0
0

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

 
↧
Search

Removing IIS 7.5 unwanted headers e

November 11, 2014, 3:48 am
$
0
0

Team,

it has been reported that the owa webpage displays the type ofserver  (Microsoft IIS 8.5) . Our security team has suggested to hide this information. We need to know if this can be done without impacting any services. How we can hide what necessary steps need to be done on server


↧

thin provisioning?

November 11, 2014, 4:15 am
$
0
0

Hi All,

I am working on a deployment project Exchange 2013, We have planned to deploy exchange 2013 on VMware platform. Could some one share your experience Exchange 2013 with VMware . I have already gone trough the VMware recommendations but i am looking for some one with practical experience that would be really help full for me to accomplish this task successfully. 

First Question : Can we use thin provisioning for Database and logs?

Second Question : what type of disk we need to use for DB & Logs (RDM or VMFS)? I am beginner to vmware sorry if i have asked any wrong question here :-)

Third Question : How to Size the processor for exchange 2013 with MSCalc? I have followed the below article for MScalc still have some doubts on Processor calculation. :-)

http://blogs.technet.com/b/exchange/archive/2009/11/09/3408737.aspx 

Here is the server details, could some one help me with the Processor part, I appreciate your response.

Phycial 4 sockets, 32 cores in total, 256 GB of RAM
SPECint®_rate2006 = 1130

Regards, Balgates

↧
↧

Exchange Server 2010: Convert Mailbox to MailUser

November 11, 2014, 6:51 am
$
0
0

Dear All,

I plan to cutover migration exchange on-premises to exchange online with single-sign-on.

http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx

In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.

Could you guide what is the best solution to convert mailbox in exchange server 2010?

BR,

Khemarin

Khemarin333@hotmail.com

↧

prevent user from changing calendar permission

November 11, 2014, 2:46 am
$
0
0

Hi team,

How to prevent users from changing calendar permission in outlook. When user open calendar option in Outlook he should either he should able to view the calendar sharing tab or he should not able to make modification in calendar permission by assigning permission to others.

↧

Microsoft Exchange Migration Workflow service terminated unexpectedly

November 11, 2014, 8:27 am
$
0
0

I started getting the following message after a reboot last night.  I again rebooted the server and continue to get the message about once a minute. I see the service starting and stopping.  I am actively migrating mailboxes, but this is appearing on the passive DAG database node. Thoughts?

Event 7031

The Microsoft Exchange Migration Workflow service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

↧
Viewing all 7008 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>