Outlook 365 Cached Mode - Need Clarification - outlook

I have a query regarding outlook 365 cached mode. Say for example a new user has a outlook mails on server for three months say JAN, FEB and MAR. Let's say we are in 1st of April, iam configuring outlook365 cached mode to 1 month. So March mails will be available offline. Let's say one month is passed, now we are in MAY. Now what happens to MAR month mail which is already downloaded offline, since cache is set to one month. Will MARCH and APRIL mails will be available offline, or only APRIL mails will be available and march gets removed locally?

By default, if Cached Exchange Mode is enabled, Outlook caches email messages only from the last N months (in your case - 1-month-old) and removes anything older from the local cache for the PC. These default settings depend on the device, with mobile devices having smaller default settings. The email messages that are removed from the local cache are still available for users to view, but they’ll need to be connected to Exchange Server to view them. Users can view messages that were removed from the local cache by scrolling to the end of a message list in a folder and clicking the message Click here to view more on Microsoft Exchange. Users can also change how much email to keep offline. The administrator can change the default age or enforce the age of email messages that are removed from the local cache.

Related

Dynamics CRM Field Service: Unable to approve time off requests

I'm looking at the Field Service module of Dynamics 365. I'm trying to block out an employee's time on the schedule board by creating a time off request.
I can create the time off request, but as soon as the object is saved, the system automatically deactivates it.
The system will reported success when Approving a time off request but I can't see any changes in the data nor any records created in the audit summary. If I try to Active a time off request, the process fails due to a Business Process Error:
Microsoft.Xrm.Sdk.InvalidPluginExecutionException: Time off request records can't be reactivated.
To the best of my knowledge, there aren't any process changes to time off requests (but I'm unsure how to confirm this). From everything that I've read, this should be a fairly straight forward process so I'm not sure where to look next.
This page from the documentation is a good example of what I'm trying to do. It's failing on step 3 of "Approve a time-off request".
I've tried creating time off requests:
in the past
for tomorrow and more than 2 weeks future
of duration lengths from 2 hours through 2 weeks
for various user accounts
The time off requests are not conflicting with booked resources.
Any advice on what I could look into to determine if someone modified any processes / workflows associated with time off requests? Or is there something that I'm not doing that I should be?
I've learned that Microsoft's documentation is not complete and there was a bug.
Additional info on how Time Off Requests are used
There are two views of Time Off Requests (TOR) available to managers: Active and Inactive.
Active TORs: Lists TORs that a manager needs to approve
Inactive TORs: Lists TORs that have already been approved (i.e., the request itself has been dealt with)
Bookable Resources have a Time Off Approval Required property. When true, TORs created for the user are Active; when false, TORs created for the users are automatically moved to Inactive.
All Inactive TORs should appear as grayed-out boxes on the Schedule Board. If you attempt to Activate an Inactive TOR, the following error will correctly be reported:
Microsoft.Xrm.Sdk.InvalidPluginExecutionException: Time off request
records can't be reactivated.
Field Service Bug
Additionally, we experienced a bug that prevented Inactive TORs from being grayed out on the Schedule Board. I'm not sure if this was a process error or a client-side style issue.
We observed the bug in Field Service 6.1.0.1462. Upgrading to 6.2.1.38 resolved the issue and allowed Inactive TORs to show up on the Schedule Board.

Exchange 2010 - Archiving emails and restricting user access

I want to implement a retention policy which looks like this:
After 1 year move messages 1 year or older to personal archive - all users can access this and it is already setup.
After 3 years - move messages 3 years or older to another database which can only be accessed for HR/Legal purposes.
Delete all messages 5 years or older.
Is there any way to remove user access to the messages moved into the legal/HR database?
You could accomplish this a couple of ways.
Set a 3 year retention on the archive mailboxes, but have backups on tape or virtual tapes for 5 years. You can restore the backups to PST when a case calls for them. (this was the old way we did it)
Use an "in place hold" instead of a retention policy. I'm not sure how to do this in Exchange 2010, (we skipped from 7 to 13), but we currently setup in place holds that only legal can see, but the user can't.
This article may help.
http://www.msexchange.org/articles-tutorials/exchange-server-2010/compliance-policies-archiving/exchange-2010-litigation-hold-part1.html

How to clear the cache which is used by AuthzGetInformationFromContext API?

I have a domain and I use AuthzGetInformationFromContext API on the client machine to retrieve sid of the groups to which a user belongs.
It works fine. However, if I add the user to some group or remove him from some group on domain controller, this API will still show old list of groups. In the case, if i will wait 10 minutes or more, it will show updated list of groups.
I tried to do this on different computers and saw that the application will show updated list of groups at a different time. So, it's not a domain controller cache.
Also, my applications exits and starts again. So, it's not application level cache either.
So, I believe there is some computer level cache for group membership (retrieved through this API).
Does anybody know how to clear this cache programmatically or change some settings to decrease this 10 minutes interval to something shorter.
Accordig to this post and Kerberos Authentication problems – Service Principal Name (SPN) issues - Part 1, You can purge the Kerberos TGT (and all your service tickets) using something like klist purge (The tool is present on Windows Seven). You have to run the tool locally on the machine the user is logged in to.
You can find the source of Klist.exe in the Windows Platform SDK (the API in us is LsaCallAuthenticationPackage)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\security\authorization\klist

Desktop application validity

I am creating a desktop application using AIR. In that application user is allowed to download some resources which have life span of 2 days. I am storing the date when the user is downloaded.
But how can i check whether the date is passed 2 days or not? Right now I am checking with the current system date.But when the user changes the system date to back, it will start to work which i dont want.
How the desktop applications say like flex builder and all having trial period.? How are they tracking the dates remaining?
~Umesh
In our application we store a license file on the client machine which stores the date the product was installed and has a counter (so only days the user actually opens the application causes a decrement). We also expire the license if the system date is tampered i.e. if the date < date the product was installed set the counter to the max days allowed. (to punish cheats :))
You could implement a similar solution or even just ignore the license and store the settings in the registry.

CRM takes 1 hour to convert an email in a queue into a history record for the contact

I'm trialling CRM 4.0 and have noticed that if one of my contacts sends an email then it sits in the queue for an hour before it is also copied into the contacts history.
Is there a job or workflow controlling this?
Can it be sped up?
Sounds like the workflow behind it isn't running quickly enough.
If you go to Administration and Workflow admin (I think thats what it's called) you can change the frequency of the workflow to a shorter interval.

Resources