Can't find OABGeneratorWorkcycle in Exchange 2013

Dear All,
I want to use OABGeneratorWorkcycle to set generation cycle in Exchange 2013, but when i entry the following cmdlet and get an error, "not found the parameter OABGeneratorWorkcycle ", any idea? Thanks.
Set-MailboxServer <SERVERNAME> -OABGeneratorWorkcycle 00.05:00:00
Set-MailboxServer <SERVERNAME> -OABGeneratorWorkCycleCheckpoint 01:00:00

You have to follow this excellent writeup by Clintboessen -
http://clintboessen.blogspot.ae/2014/03/how-oab-distribution-works-in-exchange.html
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Similar Messages

Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

Hi,
the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
purchase a third party certificate or get one from a internal CA.
Anyone can answer this question with no doubt?
Thanks in advance!
jspt

Hi Abhi,
I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
Anyway thanks for your answer.
jspt

Can't access site mailbox- Exchange 2013

Hi
Please I have been refered to the Exchange 2013 forum Support team by the SharePoint Team to resolve a complex issue that is unfortunately taking quite some time to resolve. I currently manage a Sharepoint 2013 environment. I have a requirement
to configure and enable the creation of site mailboxes.
So, I have Sharepoint 2013 installed on A.contoso.com which has all the user accounts( Account Forest). As a means of using the Sharepoint 2013 site mailbox feature, another domain( resource domain) called B.contoso.com has been created. Exchange 2013 has
been setup on B.contoso.com. All the lengthy services on Sharepoint and Exchange 2013 have been configured. A two way trust has been established between both domains. I am able to access resources both ways. On the other hand, when ever I or a user tries to
access a site mailbox it prompts that a mailbox has been created and then takes you to the OWA page of which login credentials don't work. I'm having to now create a linked mailbox and specify the users account in the accounts domain in order to enable a user
login to the created site mailbox. Furthermore, When, I access Exchange management Center I don't see the site mailboxes listed. I only see the linked mailboxes for the account holders. I am only able to view the site mailboxes through powershell.
Please, I would appreciate it if anyone can help.
Dominic

looks as if there are not many exhange 2013 experts around. Please could you someone look into my question.

How can i publish owa on exchange 2013 without ssl?

hi
i need connect to owa on exchange 2013 without ssl.
but when i change config from https to http. my iis return internal error.
can anybody tell me switch from https to https step by step on exchange 2013?
regards

Check out http://technet.microsoft.com/en-us/library/dn635115(v=exchg.150).aspx#OWA
Bharat Suneja
Exchangepedia.com | bsuneja
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup purposes only.

Can't find FP read in 2013

Can not find these tools in LabVIEW 2013
Solved!
Go to Solution.

Did you install Fieldpoint from a disk or download? It is not part of the labVIEW install.
I believe the correct version for 2013 is 6.1 and can be downloaded from NI's site.
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Outlook 2013 client, not in domain, can't connect to the Exchange 2013 server.

Hello everyone,
A colleague and me are in the process of rebuilding our Hosted Exchange servers. Everything is working perfectly except for the local Outlook 2013 clients. They are not in the domain but in the same network (through VLANs) as our Exchange server, and still
they can't connect to Exchange without the use of Outlook anywhere. If we use Outlook Anywhere, it connects perfectly. If I ping the Exchange servers (1 CAS, 2 MBX servers) I get response with the right IP addresses.
We've tried to create a new profile, this goes without problems. We enter the FQDN (or IP address) of CAS server and the required usersname, and the FQDN gets resolved to the correct MBX server where the mailbox resides on. We complete the whole wizard and
then start Outlook. We then get the error that Outlook can't logon to the Exchange server.
Is this an authentication setting that is wrong or do we need to use Outlook Anywhere if the PC is not in the same domain as the Exchange server?
Thanks in advance!

Hi,
Agree with Martina, all Outlook clients use RPC over HTTP to connect to Exchange 2013. if the server version is Exchange 2013 SP1, only Outlook 2013 SP1 use MAPI over HTTP to connect to server after we enable the protocol MAPI over HTTP.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
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

HT3042 I can't find any file exchange icon in the utilities folder

I can't find the Bluetooth File Transfer icon in the utilities folder on my iPhone

It's not supposed to be on your iPhone. That application is for Macs.
iPhone's do not support file transfers over Bluetooth. There are some apps in the AppStore that can do it to the same app running on another iOS device, but not to non-iOS devices.

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.

Can't Find Mail for Exchange e-mail folder on E71

Hi Guys,
I've installed MfE 2.09 (158) and its syncing correctly. I can view my meetings in calendar.
But i'm not able to find the Mail for Exchange folder in Messaging folder.
Has anyone else faced this issue? Can you please advise on what can I do to view that folder.
Cheers
Solved!
Go to Solution.

After playing around for a while, I'm now able to get my exchange mails working.
The issue was:
I installed MfE by using my phone browser which was working synced but didn't give me the icon to check my mails.
Solution to this particular issue is:
Un installed the MfE which i previously downloaded.
I downloaded MfE from Nokia web site and used Nokia PC Suite to install in on my phone.
Re created the profile
Synced it.
and I was able to see the Mail for exchange icon to check my mails.

IPhone 7 & 8 can't connect to Exchange 2013 CU5

I am getting call from users with iPhone and iPads that can't connect to our Exchange 2013 server. They get a error that the server can't be found. I can take the same account and run Microsoft online connectivity test and it passes. They don't have problem
with Outlook. Just the iPhone and iPads.
Matt Stehouwer Michigan State University

The error message I get is Exchange Account “Unable to verify account information”. This appears after the first screen that I guess you would call the autodiscovery screen if I click on that I am left on the auto discovery screen until I click cancel
I don’t advance to a screen that allows me to type the server or anything. I did the first time or two get the advanced setup screen that allowed me to type in a server but after that It wouldn’t take me to that screen again.
Looking at the cert idea.
Matt Stehouwer Michigan State University

Exchange 2013 SP1 - Edge Tranport Role

Hi.
When Exchange 2013 was released only CAS & Mailbox roles where available. Hub & Edge Transport server roles were discontinued.
Now with Exchange 2013 SP1, the edge transport role has came back.
Question:
1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
2. will there any be problems without an Edge Transport ?
Thanks,
Paul

Hi ,
Please find the below mentioned points .
1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
Answer :
Just ensure that the product is having all the features as you need on your side .There is not necessary to have a an edge server in all the exchange environment's. Moreover Gateway and anti spam products will differ as per the company requirements.
2. will there any be problems without an Edge Transport ?
Answer :
If you are having any one the anti spamming solution to have all the emails scanned before it reaches the exchange server then it will be good .
Just ensure that the anti spamming product what you are going to use is mainly doing the reverse dns lookup
and spf look up .With the help of that we can able to avoid large no of forged emails.
Regards
S.Nithyanandham

Exchange 2013 category view always in "expand all" mode

Hi all,
having issues with mailboxes that have been migrated to Exchange 2013.If in category view and choose collapse all,then expand just a few,go to another folder/inbox then back all categories are expanded.Seems like Outlook (2010 and 2013) doesnt remember it.
Checked in view settings - group by - expand/collapse default is set to As last viewed.
This happens to all mailboxes exept those mailboxes that are on Exchange 2010.
Exchange 2010 sp3 cu6 had an update that fixes categoryview not updated,but cant find any for Exchange 2013.
Since the update is on server,i guess this can be changed on serverside settings in Exchange 2013?
Our workaround atm is to ask users to open additional mailbox in new window,but this doesnt work well for users with 1 screen.
Are there any fix for this?
Thanks.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
There is no related category view settings in Exchange server side. I also have tested in my Outlook 2010 and Outlook 2013 with two test accounts: one for Exchange 2010 SP3 account and one for Exchange 2013 CU1 account.
Both these two accouns are working fine in . I set my Inbox folder in category view and collapse all colors except one expanded. I go to other folders(Deleted Items folder and Drafts) then go back to Inbox folder, the view is the same as last viewed without
expanding all colors. However, if I restart Outlook, the colors would be all expanded in Inbox folder.
Please make sure your Outlook is the latest version and start Outlook by running Outlook /cleanviews to restore default Outlook view to have a try.
Regards,
Winnie Liang
TechNet Community Support

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

Hi Guys,
I was hoping to get some opinions/ advices regarding the case explained below.
The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
every mailbox server in the environment. All users are using Outlook 2010/2013.
There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
To work around this issue while still performing the migration I am considering the following scenario:
Deploy Exchange 2013 servers in the organization
Migrate all mailboxes to Exchange 2013 servers
Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
What do you think of this setup? Do you see any issues with such long-term coexistence?
Thanks.

Hi,
You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Can't find OABGeneratorWorkcycle in Exchange 2013

Similar Messages

Maybe you are looking for