Nimaz, that link isn’t available to me. I’m guessing since it is a sharepoint site that only those with ifs accounts can access it.
The first link worked for me at this time.
The problem is, I think it is a moving target. That with the next update, there will be a different page to go to and finding it will be a challenge. Maybe it stays the same though. I have bookmarked it so we shall see.
In the link, Microsoft gives some recommendations how to follow the release cadence for Windows 10 considering the limited support window of only 18 month.
IFS is now following a very similar approach with an even higher cadence in IFS 10.
Above, IFS limits certain IFS 10 Updates to specific updates of Windows.
Probably this works for a vanilla IFS solution with no or very limited number of customizations.
How is this meant to work out for an enterprise customer having a more complex reality with a bigger number of customizations on the inside and on the outside?
Which tools can a customer use for quality assurance of the update process to verify and validate functionality including extentions (eg. GET), customizations and configurations accross all business processes?
Does it mean, the customer is forced to use the windows version as described in above IFS document or looses the right for support?
What should the customer do in case he has other enterprise application(s), that do not fit the IFS approved and supported platform scheme for MS Windows?