When changing from VideoOS.Platform.SDK.RemoteRetrievalTasks to instead use VideoOS.Platform.ConfigurationItems.Camera.RetrieveEdgeStorage. Since RemoteRetrievalTasks is to be depricated in 2025R3.
When using RetrieveEdgeStorage the requestedTime in the driver seems to be truncated and the miliseconds is removed. When using RemoteRetrievalTasks the time is correct and matches the requested time down to milisecond level.
We need the miliseconds to be able to match the correct time with the request.
Milestone Development will investigate. I will let you know here what we find…
Anny input on this. I see your new samples is updated so it can be reproduced with the new RemoteRetrievalTaskSample and adding some milliseconds to StartRetrieval utcStartTime. And in the driver “public override bool MoveTo” DateTime requestedTime is truncated. And in previous sample it is not.
In the 2024R2 SDK Discontinuation announcements
What will happen if customers upgrade to 2025R3 and we still use RemoteRetrievalTasks.
Milestone Development have been working on a fix, I think there is a fix candidate in testing. I will get back with details.
The discussion here at Milestone triggered some questions from the developers.
If the fix is in 2025R3, is a hotfix/patch for 2025R2 necessary? If we make a hotfix/patch for 2025R2 another question: Do you use this in a MIP SDK based standalone app only, or also in plugins? (Plugin for Event Server, Smart Client, Management Client, or a combination of these?)
First some questions 
So the fix is on the Milestone server side and not in the driver or SDK ?
What will happen if customers upgrade to 2025R3 and we still use RemoteRetrievalTasks using an older SDK version ?
If RemoteRetrievalTasks will keep working we can keep using it as before and change to RetrieveEdgeStorage at a later time. If not we need some way to test and verify the solution before the 2025R3 release.
I’m refering to the “Discontinuation announcements” in the SDK.
Our soluition is dependent on the milliseconds and will stop working compleatly if not available.
It is in the VideoOS.Platform.dll. So if you have an standalone app you can just use a hotfixed MIP SDK and the fix will work in any version. If you have a plugin then the fix need to be deployed in all the environments as a new VideoOS.Platform.dll. Generally Milestone has been putting it in the patches for the environments when this is the scenario.
The plan is to remove VideoOS.Platform.SDK.RemoteRetrievalTasks.dll including RetrievalTaskManager in 2025R3. At this time your solution will break if still using this.
I understand your concern about testing this, I will discuss it with the developers.
Are you using plugins, or standalone MIP SDK based applications/services (or both)?
We are currently only starting retreive jobs from a standalone service and have no current plans to use it from someware else.
I guess"2020 R1" is included in “any version”. So RetrieveEdgeStorage is available also in this old verion ? We where not aware of this API otherwise we would have used it from the start.
One more thing since we are running a standalone does " At this time your solution will break if still using this." still apply? If we use the old SDK and we include the old VideoOS.Platform.SDK.RemoteRetrievalTasks.dll.
More concerned with our current installations that does not upgrade.
For now the recommendation from Milestone Development is to use RemoteRetrievalTasks.dll for the older versions. There has been some issues fixed surrounding the ConfigurationItems.Camera.RetrieveEdgeStorage in the newer versions (even though it is available in the older versions).
A hotfixed version of the 2025R2 Platform.dll / MIP SDK is being made, and we will let you know when it is available
Ok thanks for the information.
Just to clarify for our current installations. If we use the current RemoteRetrievalTasks.dll as a standalone application using the old SDK (including the RemoteRetrievalTasks.dll ourselves. Will this stop working if customers upgrade to 2025R3 ?
No. The modifications are client side not server side, this means you can use MIP SDK 2025 R2 and it will not stop working for an XProtect VMS 2025R3.
I think this is important information and I am glad you asked again, I hope it is more clear now, but don’t hesitate to ask further questions if needed.
The MIP SDK documentation now includes a description of the fix as applied in the Bug-fix maintenance release 25.2.2 - https://doc.developer.milestonesys.com/html/index.html?base=gettingstarted/mip2025r2_intro.html&tree=tree_home.html