D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

Lessons Learned moving from 10.0.6 to 10.0.8

  • 1.  Lessons Learned moving from 10.0.6 to 10.0.8

    Posted Jan 23, 2020 09:18 AM
    We've recently moved from 7.3 D365 F&O to 10.0.6 D365 F&O - which was a very challenging exercise and a considerable amount of work.  We use 3rd party partners to assist us in setting up environments, etc. but the bulk of the testing is done by us - and manually until we can get RSAT up and running.

    We're now embarking on the update to 10.0.8.  Does anyone have any "lessons learned" on moving from one 10.0.x to another 10.0.y version?  I'm hoping this will be a much smoother update given we are only moving up by 2 "minor versions" but would appreciate any guidance or advice this community can offer.

    #FinanceandOperations
    #UpgradesandUpdates​​​​

    ------------------------------
    Stacey Noah
    The Conference Board of Canada
    Ottawa ON
    ------------------------------


  • 2.  RE: Lessons Learned moving from 10.0.6 to 10.0.8

    Posted Jan 24, 2020 01:53 AM
    Hi Stacy,
    We entered 365 on 10.0.0. Since then we have followed the releases and for the moment we are on 10.0.7.
    We have had one problem, think it was from 10.0.3.-10.0.4, and a miss from our side in the integration framework.
    Otherwise it have worked very smooth for us. As long as you read the release notes and testing accordingly.
    For the moment we are setting up rsat to get help with test, I think that will help us a lot and save time of course.

    ------------------------------
    Tobias Hultbäck
    Service Manager
    PostNord
    LJUNGBY
    ------------------------------



  • 3.  RE: Lessons Learned moving from 10.0.6 to 10.0.8

    TOP CONTRIBUTOR
    Posted Jan 24, 2020 09:25 AM
    We are currently working on upgrading from 10.0.5 to 10.0.8.  We have been on 10.0.x since March of 2019 and have taken 2 upgrades since.  Here is our biggest lesson learned:  after upgrade immediately apply whatever quality update is available for the upgrade.  The quality update is for any hotfixes for the release.  We applied a hotfix for 10.0.3 to resolve a bug that was introduced by the release.  When we upgraded to 10.0.4, we assumed that the hotfix for 10.0.3 was rolled up into the 10.0.4 release.  It was not.  Microsoft could not explain this to us.  Long and short, taking the quality update protects you from Microsoft not applying previous hotfixes to the release.

    The other tip is Microsoft's default is to automatically deploy the upgrades to test and then to production a week later.  This gives you a very small window to do any regression testing.  Since we have been burned several times by the upgrades, we simply can't short change the regression testing.  Turn off the auto deployment in LCS.

    Good luck.

    ------------------------------
    Mark Schurmann
    Accounting Systems Manager
    Automobile Protection Corp
    Norcross GA
    ------------------------------



  • 4.  RE: Lessons Learned moving from 10.0.6 to 10.0.8

    SILVER CONTRIBUTOR
    Posted Jan 27, 2020 04:33 PM
    Hey Stacy;

    First, I would same as it pertains to D365 F&O  'Minor vs Major'; software releases require planning and test execution.  Don't underestimate or take from granted the testing that is required for each release/build.  Microsoft has a built in '1 week push' schedules between Sandbox (test) and Production that, as Mark states, "...gives you a very small window to do any regression testing..."  We test in iterations, initially IT Testing as a precursor, IT RSAT execution, IT 'smoke test' in the Sandbox (UAT) environment  and finally IT sponsored Business UAT.  In general, we run a test cycle of ~4-6 weeks per release, which Microsoft told us in an audit is "...too much time on release testing..."  Microsoft will indicate that you should rely on their delivery and the quality of their releases; what I would say to that is that we've been surprised by the number of 'P1 / SEV-A' tickets that are not back-revved and are not noted until they become issues 'P1 / SEV-A' tickets in our environment.  Again, don't underestimate the effort...

    Second, items to be aware of, introduction of 'new' D365 flags, support of 3rd Party plug-ins, custom Payment connectors, common Data Entity import/export processes (for BYODB) , D365 batch processing, external integrations and post-deployment IIS service restarts; we've been impacted by all...

    Lastly, planning, we use a detailed Hour by Hour (HbH) deployment guide that acts as a check list and a validation for the day of cut-over which include a multi-person 'smoke test' to ensure that we've hit on all issue, especially with respect to those issues that we've been impacted from prior releases...  As a course of action, we deploy on Thursday evening/Friday morning, we notify the business users of the release schedule in advance and advise on the potential for business interruption, this deployment model minimizes business outages and allows IT an extended remediation window across the weekend (should it become necessary)...

    My office 'white board' has a saved corner that I add to with each release as a gentle reminder of the 'gotchas' that we need to hit on during the release testing and the planning for the cut-over...  We just last week (1/23) upgraded from 10.0.4 to 10.0.7, our testing and planning enabled us to be up and running with no impact to the business on the day of cut-over...  We only had a single 'SEV-A' on a Data Entity which impacted our internal reporting dashboard and external integrations across the weekend...

    Hope this helps-
    Joe


    ------------------------------
    Joe MacPherson
    Coldwater Creek
    Hingham MA
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role