Hello, could you provide me KB 2908387 for Windows Server 2012 R2. It is prerequisite for MAPI over HTTP.
Thank you.
Hello, could you provide me KB 2908387 for Windows Server 2012 R2. It is prerequisite for MAPI over HTTP.
Thank you.
On my one computer, when I use some older docs from excel and word, they save in that computer, but not on my new computer.
My newer docs seem to save without issue on the new computer. I am guessing that if I can update all my files within my server, that would fix the issues. If that is correct, what might be the steps to do that.
Currently I am updating each doc as I am using it, but I think that is not a sure way to fix the problem and is time consuming. Thanks for your help. JAF
Hello,
we are planning migration from Kerio to Exchange 2013. Clients are now running on IMAP.
My concern is simple - Can I install Exchange 2013 (Mailbox and CAS) on same domain with currently running Kerio without affecting clients (MS Outlook) in any way, before we start migrating data ?
Thank you for answers.
How to give access to book mailroom to users in different Exchange organization?
The company A and company B have been merged in one company but each company has still their own Exchange server. Now users in company B want to be able to see and book mailbox room of company A. What is required to make this work?
Thanks
Ok it time to renew SSL for my Exchange 2013 in a few days
I'm using Godaddy UC
is there a step-by-step specific to Exchange 2013 ?
(even on Godaddy site the info relates to 2010 not 2013 - I know its similar but...)
I found posts for Exchange 2007 & 2010 but nothing for Exchange 2013!!
Whilst I think I have a general idea... I really don't want to mess this up !!
JK
Hello
I found annoying issue with CU6 setup. When you try to use GUI setup using setup.exe everything goes fine until it reaches prerequisites analysis. It goes to 100% and display "back" and "install" buton but they are not working. You cant't also finish Setup using close button. I try few times reboot and resetup again without success.
Then I try to make Schema and AD prepare using setup.exe from command line.
Then I got this error:
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy 'Default Policy'. Setup can't continue. For more information, visit (...)
It's strange because this error should be reported in GUI setup windows instead of freezing it.
When I removed SMTP Recipient address from 'Default policy', evrything goes just fine. Maybe this will help some of you.
Cheers Pacek.
I have used two mail server (Exchange 2013 and Linux sendmail) for mailing in the same domain like abc.com.
I have converted authoritative domain in to internal relay for sending mail in Linux mail user, and create a send connector point to Linux mail system as a smart host. in that case my exchange user send mail to Linux user and internet via Linux smart host,
then I create a receive connector in exchange server for receiving mail from Linux mail system as edge transport custom connector & permission set to anonymous, when Linux user send mail to my exchange user it queued in my exchange message queue and the error is:
Last Error:A local loop was detected.
What's the problem?
Hey Team,
I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
1) All servers in the same ad site
2) mail. autodiscover, pointed to the 2013 server
3) 2013 server is internet connected.
Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
Thanks,
Robert
Robert
Hello,
We are using Exchange server 2003 on Windows Server 2003 SBS. We have decided to migrate to cloud and use codetwo office 365 tool for migration due to its public folders support.
The migration tool requires SP2 on the server 2003 and due to some reasons which can not be fixed without a repair installation (we do not want to mess with it or stop it), we can not update the windows.
We decided to try a scenario that includes setting up a windows server 2003 on a virtualbox and installing exchange 2003 with the same server name.
We use ntbackup to backup the data and I used this backup to restore the mailbox store and public folder store (with and without Log Files). I followed the instructions in http://www.ciaops.com/storage/tech-docs/NTbackup%20exchange%20recovery.pdf. The problem
occurred when I tried to mount the either mailboxes or the public folders at the last step (error id:c1041724). I have tried solving it with the Microsoft support information but I have neither the issues of free space on harddisk nor runningeseutil /p command on the system.
I would like to get some help about how I can do this migration successfully.
Recently I built two Exchange 2013 servers, CAS & mailbox and added them to my existing 2010 organization. Now, people who HAVE NOT been migrated to the 2013 mailbox server are not getting an updated OAB. Those on 2013 are getting an updated OAB.
Besides the obvious answer to hasten the migration to 2013, why aren't the 2010 mailbox users not getting an updated OAB?
Thank you,
Chris
Hi,
We are currently in a coexistence between Exchange 2010 and Exchange 2013.
We have migrated around 20 pilots and have a question regarding outlook provider.
EXCH is still mapi.company.com (used in legacy environment, CASArray was mapi.company.com)
EXPR is set to msstd:mail.company.com (mail.company.com is our new proxy server bound to a HLB)
Shall we clear everything or just EXCH used for legacy MAPI/RPC?
I have successfully performed a staged migration for a few users. However, they have each been plagued with different issues along the way. Currently, I am attempting to complete the migration of two users to Exchange 365 and have gotten to the last step, which is executing the PowerShell script Exchange2007MBtoMEU.ps1. This script fails at the first step, which is Disable-Mailbox. The error message I receive is:<o:p></o:p>
Disabling Mailbox<o:p></o:p>
A positional parameter cannot be found that accepts argument '-DomainController'.<o:p></o:p>
+ CategoryInfo : InvalidArgument: (:) [Disable-Mailbox], ParameterBindingException<o:p></o:p>
+ FullyQualifiedErrorId : PositionalParameterNotFound,Disable-Mailbox<o:p></o:p>
I have added the -DomainController parameter in just about every conceivable fashion, but have gotten this message every time. In turn, this causes the remainder of the script to fail.<o:p></o:p>
I really need to get this migration completed, as having an on-premise server and Exchange 365 is proving to be difficult.<o:p></o:p>
Thanks so much,<o:p></o:p>
Randy<o:p></o:p>
Hi All,
I have an exchange 2007 organization with 2 exchange sites. Below is a diagram of my current infrastructure.
From the above setup:
Going forward, I want to upgrade this infrastructure from exchange 2007 to exchange 2013. This is what I intend to achieve after the up;
I have had to upgrade from exch 2007 to 2013 for a single exchange site. I however am not sure how to upgrade in the case of different exchange sites.
I will appreciate a step by step guide or pointers on the options I have + how to proceed. So far MS has not been forthcoming with any online doc or resource for this type of upgrade.
I assume this will be a lengthy discussion .. :)
Regards,
Richard
..forever is just a minute away*
Anyone know if the SMTP checkbox is required on the Certificate configuration in 2013?
Hello,
This is probably something very simple that I'm overlooking. We recently let our primary System Admin go and he was the one that did the majority of the work setting up our new Exchange 2013 server so I'm uncertain of what for sure has been done but I'm hoping someone here can help out.
Here's the situation:
Brand new domain (Call it DomainX) with a Brand new Exchange Server (ExchangeX) running both the mailboxes and Client Access roles.
Old Domain (Domain Y) with Exchange 2003 (ExchangeY).
Two different IP Ranges as well. Range 10.x and Range 192.x. DomainX has all servers on Range 10.x while all servers and clients on DomainY are on 192.x.
PCs on DomainX and Range 10.x can see and connect to ExchangeX immediately and flawlessly.
PCs on DomainX and Range 192.x can connect to ExchangeX by using the Outlook Anywhere setup.
PCs on DomainY and either Range get the error that ExchangeX is offline or not available.
PCs on both Domains can connect to ExchangeY with no issue.
PCs on both domain are able to ping ExchangeX by name and IP address successfully.
So what am I overlooking? How do I get PCs on DomainY to connect to ExchangeX?
Hey there,
Can somebody please explain to me why I need to set Outlook-Anywhere on my legacy (2010) servers if I'm not using Outlook Anywhere externally in the org and don't intend to? Keep reading that it's a must so that 2013 can proxy requests, but not really sure why it would need to proxy requests if I didn't want to allow OA externally (and going through 2013 CAS).
I'll also add that the only namespace I've cutover is Autodiscover. I have around 2000 mailboxes migrated over from 2010 on to 2013 and I don't really see any problems (still a good thousand on 2010). Not sure if I was supposed to point rpcclientaccessarray records at my 2013 cas, or what advantage that would give. 2010 Exchange mailbox users can connect to 2013 mailboxes when given access (presumably due to Autodiscover). Everything just seems to work.
So please, if someone could tell me the error of my ways or reaffirm that everything's going according to plan I'd really appreciate it. Apologies if my questions are a little diffuse!
Joe
I'm fairly sure the issue is related to the fact that I had installed Exchange server 2013 CU1 on a Windows server 2012 box, and then uninstalled it. I then installed Exchange Server 2013 SP1 after rebuilding the servers to 2012 R2.
When I try to install a Mail App I get the error "Exchange Server doesn't support the requested version.". I don't see any correlated errors in the event logs to figure out what exactly is going on. If I use the powershell commandlet get-app to see what apps are available for a user I get the same thing.
I do have Exchange Server 2010 SP3 servers in my domain that I will eventually be migrating off of. If anyone can give me some pointers of where to look for what might be broken I'd really appreciate it.
Hello,
We are receiving the below error while trying to install Exchange 2013 CU5 or CU6 on our Exchange Server running on Exchange 2013 SP1 on W2012R2
Thanks.
[10/14/2014 10:05:33.0978] [0] RootDataHandler has 1 DataHandlersHello,
When I am using the command c:\Exchange2013\>Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms on my domain controller I am receiving the error below:
Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis COMPLETED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareA
D'. No Exchange 2007 server roles have been detected in this topology. After thi
s operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms
.exch.setupreadiness.NoE12ServerWarning.aspx
Configuring Microsoft Exchange Server
Organization Preparation FAILED
The following error was generated when "$error.Clear();
initialize-ExchangeConfigurationPermissions -DomainController $RoleDomai
nController
" was run: "Active Directory operation failed on domain.com
. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF
_ACCESS_RIGHTS), data 0
".
I am using an admin account with full rights. Could you give me any advice what might that be?
Thank you in advance
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 ?
Regards
S.Nithyanandham