Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

(0) Share

Report

Posted on by jt1024

452

Hello knowledgeable gurus of the D365 Finance forum,

I have yet another new administrator silly question! haha!

I'm scheduling a Software Deployable Package installation on our MS LCS Hosted Production system for tonight. My Dev and Test tier 1 cloud hosted machines currently match my production environment

The SDP that is marked as a release candidate is on on of our LCS Hosted environments. That environment has had a Proactive Quality Update.

So now I have this:

Production is at Version: 10.0.31 (10.0.1406.128)
PreProd (hosting the release candidate SDP) is at 10.0.31 (10.0.1406.139).

When I apply the update tonight, this will bring the Application Version on Production from: 10.0.31 (10.0.1406.128) up to 10.0.31 (10.0.1406.139).

Now here's my question: My Tier 1 build environment and my Tier 1 development branch mapped environment are both at Application Version 10.0.31 (10.0.1406.128) to mach the current production application version. But after the Production is upgraded by the SDP tonight, these environments will no longer match Production.

How do I update my Build and my Development environments to match the application release of Production after the Production system is upgraded? I.e. how do I get the tier 1 cloud hosted environments to 10.0.1406.139?

Thanks again everyone!

- Jim

All responses (5)

Answers (1)

André Arnaud de Cal... 291,391 Super User 2024 Season 2 on at

Like (1)

Report

RE: Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

Hi Jim,

If the answer from Komi helped you, would you mind marking his answer as verified?
Suggested answer

jt1024 452 on at

Like (1)

Report

RE: Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

Komi!

You. Are. A. Genius! Or at the very least a fantastic encyclopedic link provider!

Thanks a ton, that worked!

- Jim
Verified answer

Komi Siabi 12,711 Most Valuable Professional on at

Like (0)

Report

RE: Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

Hello Jim,

Regarding the error you got,

check this.

https://msdyn365fo.wordpress.com/2022/09/08/step-globalupdate-script-for-service-model-retailserver-on-machine-dev-vm-is-failing-during-msdyn365fo-package-deployment/
jt1024 452 on at

Like (0)

Report

RE: Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

Actually.... update on this. The attempt to apply the proactive quality update failed. I wonder if it was because I already had my SDP that was made sometime after the proactive quality update? But the environment it came from didn't have a newer updates that I would think would conflict with this proactive quality update. More to learn here I guess. I downloaded the logs, and the files containing the word 'error' in their name were not useful as far as I could see.

The environment change history shows it failet at step 57: GlobalUpdate script for service model: RetailServer on machine: <machine name>.
jt1024 452 on at

Like (0)

Report

RE: Update a Cloud-Hosted environment to match the Application Version of the Production environment. (See detail for nuance, it's not so simple. Edited.)

I think I found the answer to my own question! Tada!

When I look at the Environment change history on PreProd (Which as I describe above is holding my release candidate SDP) I see the change Microsoft made with the ProActive Quality update.

AND.... when I look at my asset library, that SDP for that ProActive Quality Update is there:

which.... (If I spend all my time reading MS documentation... which I don't outside of work and study hours..) I would have inferred had I read: "Can customers still manually apply hotfix updates from Lifecycle Services?"

So I think I've answered my own question. Now I have to go update my own process notes!