Microsoft Exchange 2013 In Place feature

I set up a DC/Client Access/Mailbox for Mailbox database and another Server foe archive database. I enable archive all mailbox user and set retention policy 7 day for archiving. Next i increase time in client access server 7 days but mail not automatic archive.
User use outlook web log in cannot see any mail in archive folder.
I try start-managefolderassistant on client acces server but exchange shell result "Archive Mialbox is offline" and nothing in archive mailbox
Please help me how to make mail from inbox automatic archive.

Hi,
Do you install Exchange server on DC?
It is not recommended to install Exchange server on DC.
Please run the following command to check result.
Get-Mailbox –Identity | fl *arch*
You mentioned you placed archive mailbox database on another server. If possible, please create a new mailbox
and enable a local archive mailbox, then apply retention policy to this mailbox to check result.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

2012 r2 -Microsoft Exchange 2013 DNS timed out

I just installed Microsoft Exchange 2013 on my 2012 r2 server. I just installed all of the Roles &features, then I went to my fire walls and then I disabled them (temporarily). I configuring my IP addressing, DNS Ip address and a dns suffix. Now I
can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address. I can ping my IP address though. If anyone has any suggestions that would help then let me know. Thank you for any responses!

Hi Dallen,
>>Now I can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address.
It is not a hyper-v issue , it's more like a network problem .
First , I would suggest you to disable firewall in DNS server for troubleshotting .
If firewall is truned off then you still can not ping the DNS server , you may check if the exchange server can ping other IP address in your LAN to check network conectivity .
If they are in different subnet ,you may try to check the configuration of the router .
Any further information please feel free to let us know .
BestRegards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Chat feature for Microsoft Exchange 2013

Hi Good day,
is there any way to have a simple chat feature service for exchange 2013? im looking for some solutions but only Exchange 2000 has this common feature. I just need to have a simple chat service for our internal and branch offices

Hi,
There is no feature in Exchange server 2013 to meet your requirement. But we can use Microsoft Lync to chat with your domain environment. Microsoft Lync is an enterprise-ready unified communications platform.
By integrating Lync Server and Exchange Server, we can also chat directly in OWA. For more information about it, we can refer to:
http://office.microsoft.com/en-001/lync/lync-server-2013-features-video-conferencing-and-instant-messaging-FX103789592.aspx
If you don’t want to deploy a Lync server in your environment, we can also use
Skype with a Microsoft account or Skype account to chat with others.
Thanks,
Winnie Liang
TechNet Community Support

Microsoft Exchange 2013 eDiscovery - specific search query: looking for specific hyperlinks within e-mails content/body

Dear all:
I am currently using the MS Exchange 2013 eDiscovery feature with the objective to identify which of my users have received emails containing specific hyperlinks (e.g. http://website1/webroot/file.zip, http://website2/webroot/file.zip, etc.) from an unknown
sender.
To this end, I have been creating an eDiscovery on-hold case looking for a specific search criteria in all mailboxes.
As the search criteria, I have tried many options but was unable to obtain satisfying results: I know I am missing some e-mails from this specific search (I checked manually). I have notably tried the following search queries (with and without the body:
search operator, with and without double quotes, etc.)
body:http://website1/* OR body:http://website2/*
body:"http://website1/*" OR body:"http://website2/*"
body:"website1*" OR body:"website2*"
body:"*website1*" OR body:"*website2*"
When replaying these queries on my local Outlook client, everything works fine and I get results as expected.
However, when going through the ECP eDiscovery feature, I am missing some results.
Therefore, I am looking for any advice on what Exchange eDiscovery KQL query I should use to identify all emails containing, in their message body, a list of specific hyperlinks/URLs.
Many thanks in advance for your help.
S.

Alas I do not know the answer to resolution via ECP and like you I have found it to be a bit maddening to use ECP for discovery tests Ive done when comparing results with our DigiScope product. I know we can accomplish what your looking to do via Regular
Expression but again that's with a 3rd party tool.
One thought is I suppose it could be an indexing issue with the DB, so perhaps rebuilding the index would help?
If you do get it working I would love to know the resolution since many of my tests with ECP have left me yelling at the screen. When its works its cool when not well...
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Slow PowerShell execution of Microsoft Exchange 2013 commands from c#

I have the following code that executes an exchange cmdlet. It works fast with command that return some output but work slow if command has no output.
for example
Invoke("Get-Mailbox")
prints following output:
Begin execution at 11:44:43
Finish execution at 11:44:51
Output :
Administrator
Discovery Search Mailbox
Artem Romanchik
Execution time was about 8 second(6 second for loading exchange snappin + 2 seconds for command execution)
Slow example is
Invoke("Set-Mailbox -identity tema -MaxSendSize 10MB")
Begin execution at 11:53:34
Finish execution at 11:54:36
Output :
Now it was 62 seconds(2 seconds for command and 60 seconds of waiting for something)
How can I reduce execution time of second example?
Invoke method code:
public void Invoke(string command)
var config = RunspaceConfiguration.Create();
PSSnapInException warning;
config.AddPSSnapIn("Microsoft.Exchange.Management.PowerShell.Snapin", out warning);
using(var runspace = RunspaceFactory.CreateRunspace(config))
runspace.Open();
using(var _psInstance = new RunspaceInvoke(runspace))
var psCommand = new PSCommand();
Console.WriteLine(String.Format("Begin execution at {0}", DateTime.Now.ToLongTimeString()));
var result = _psInstance.Invoke(command);
Console.WriteLine(String.Format("Finish execution at {0}", DateTime.Now.ToLongTimeString()));
var output = "";
foreach (var line in result)
if (line == null)
continue;
output += "\n" + line.BaseObject.ToString();
Console.WriteLine(String.Format("Output: {0}", output));
runspace.Close();

On 2010 and 2013 Powershell is throttled
http://technet.microsoft.com/en-us/library/dd298094(v=exchg.150).aspxyou might want to do some testing with a user that has throttling policy disabled. Also you might want to check the logs on the CAS server the request are going through eg \Microsoft\Exchange
Server\V15\Logging\CmdletInfra you should be able to determine from these if your being throttled.
Cheers
Glen

Livecycle ES4 and Microsoft Exchange 2013

Hi,
My customer inquired me of configuring LiveCycle ES4 with Microsoft Exhange 2013 but supported documentation says that LiveCycle only supports Microsoft Exhange 2010 and earlier. ¿Could be posible LiveCycle ES4 SP1 either supports Microsoft Exhange 2013 or configure an account in Microsoft Exhange 2013 for configuring in Livecycle without getting on troubles?
Thanks in advance.

MS Office 2013 is also not supported with ES4 SP1.
Here is the link to updated documentation - http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html#Software support for PDF Generator
Regards,
Varun

Changing AD Domain name with Microsoft Exchange 2013

Hello everyone,
we need to change our Active Directory Domain name from .local to another naming convention.
We are running a Windows Server 2012 R2 environment with Exchange 2013.
- Domain Controller
- File Server
- Exchange 2013
Running on a VMware ESX Host.
What is the applied way to change the Domain name? Or is there no way to change in the running Forest and we have to re-setup everything?
Thank you for your answers.
Regards,
Sebastian

Hello,
You need install new Exchange server in your new enviroment (forest).
Please read this link:
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
Other nice article:
Moving to a new forest and retaining the same SMTP domain ( with native scripts ) -
Part I
Regards

Exchange 2013 In Place Hold with In Place Archiving

I'd like to use in place hold to ensure all data is kept for 5 years rolling but still use in place archiving for all data over 1 year old.
Is this possible without all data between 1 and 5 years old being held both in the recoverable items folder of the primary mailbox as well as in the archive mailbox?

Hi,
Based on your description, you want to use In-Place Hold to keep data for 5 years and use retention policy to move messages older than 1 year to archive mailbox.
If you have mails older than 1 year, then they will be moved to archive mailbox and In-Place Hold will not prevent the items being moved from the primary mailbox to archive mailbox. These won't go to the recoverable items folder in the primary mailbox.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

Fresh installation of Exchange Server 2013 on Windows Server 2012.
Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
your folders with your Outlook data file (.ost)" is displayed.
If I turn off cached Exchange mode, setting the email account to not
cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
time.
I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
Microsoft Exchange RPC Client Access service is running.
No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
like OutlookAnywhere - which I might add had their place under that scenario.
In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
users.
Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
certificate.
See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
there is a 3rd - I forgot, but you get the idea).
Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
Open Outlook - BOOM! It works... Was it as good for you as it was for me?
You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
Frustrating beyond reason - that should be Exchange's new slogan...
Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
PS
ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

I have an new install of Exchange 2013 with all updates.
When I setup an inbox rule to redirect messages to another contact it is not working.
When I used Outlook 2010 and ran the rule manually I received this error:
"the redirect action is not currently supported with run rules now"
It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

Hi,
From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
Get-Mailbox <identity> | fl DeliverToMailboxandForward
If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

I can receive email on my 5s but can't send. Hosted Exchange 2013, 5s running 8.0

We just moved email providers from in house (Exchange knock-off called 'Kerio' on a server) to hosted Microsoft Exchange 2013. My iPhone 4 (7.x) is able to connect to the new email server and send/receive emails. I've tried connecting my 5s (8.0) and a 5c (7.1.2) but I'm only able to receive email, not send. The 5c/5s were setup using 'Exchange' in the mail app. Any advice?

Hello daveyellis
Check the article below to go over some troubleshooting options to resolve issues with send emails from the Mail app. I would look at the settings and look at the outgoing mail server to make sure it is correct. If that does fix it, I would then remove the account and reset it up.
iOS: Troubleshooting Mail
http://support.apple.com/kb/TS3899
Regards,
-Norm G.

Outlook keep connecting and disconnecting from exchange 2013

hi, currently im having microsoft exchange 2013 in server 2012 standard. when i running my outlook 2007/2010/2013 , it will keep showing connecting and disconnected. once i restart microsoft exchange rpc client access and it will be working fine for temporary,
around 10 min later and it will happend again, can advise?

Hi,
You can raise it via Regedit:
http://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx
Thanks,
Simon Wu
TechNet Community Support

Android & WM6.5 devices can't use ActiveSync with Exchange 2013, ADFS and WAP.

Bit of a long winded title but I was trying to sum up the issue.
Newly installed Exchange 2013 environment; we've setup external access for OA and ActiveSync. We've used ADFS with WAP to publish the necessary paths etc. We've setup DNS and firewall rules etc.
OA is perfect and can be accessed by anything with a browser. ActiveSync is perfect for any new Windows Mobile device and any iOS device. When we've tried to sync older WM6.5 or any Android device, it just doesn't seem to want to work.
We've checked logs on both devices; the WM6.5 complains about a cert issue however we've took every step from installing the CA, RA and actual cert on the device to no avail. Some android device complain about using the port 443 but no matter what
we change this to it still won't sync.
Unfortunately my suggestion of 'just give everyone a new phone' went down as well as...well lets just say not good :)
I appreciate this might be an ADFS\WAP issue but thought I'd rule Exchange out first so any advice is much appreciated.

We are having issues on connecting ActivySync on Microsoft Exchange 2013.
OWA,OutlookAnywhere is working
ActiveSync is not working.
can you help us or share the configuration.
We have Used MS UAG2010 SP4 to publish Exchange 2013 SP1 (On premises).
Regards,
Furqan

Exchange 2013 / Eudora POP-account not working

I have a MAC (version 9) user who has Eudora (6.2.4). User tries to connect to Exchange 2013 server with POP-account but is unable to get this to work.
I tried to search the web for this answer but couldn't.
I would be happy to know if this is even possible to set up before I spend my time and customer's money on this.
I got Eudora 7.1 working with IMAP on my XP Virtual machine, but I have no way of testing it with MAC-computer.
Edit: I also got POP account working on my XP Virtual machine.

Thanks for your reply. I do not know the specific error message as this happens to one of our end-customer and he has not provided detailed information about this.
User can't update Eudora, because he is using older version of MAC.
I would just like to know if it is even possible to connect Eudora 6.2.4 to Microsoft Exchange 2013.

Exchange 2013 archiving

Hello,
i have a problem with exchange 2013 in-place archiving.
Archive mailbox is in different database that mailbox database.
Yesterdey i have activated archiving for a first mailbox; when i activated archive many "Not read" message were sent.
Seem that when archive is active message sent to user that have request of read but that have not answer like "read" for the user when they are stored in archive mailbox send out reply to sender with "Not read: " in the subject.
I have checked "retention policy" and "retention tags" properties via exchange management shell but i did not find any field to disable unread in archive or something like.
Please can i have support for this problem?
Thanks in advance.

Hi,
Before going further, I’d like to confirm how many senders are affected by the issue.
Please check if there is any Outlook rule about the unread message notification.
And we can also check if the sender select the option “always send read receipt”:
File>options>mail>tracking
Best regards,
Angela Shi
TechNet Community Support

Microsoft Exchange 2013 In Place feature

Similar Messages

Maybe you are looking for