Questions on Enable-D365MaintenanceMode

[FH-Inway]

Today I had the rare opportunity to enable the maintenance mode on a cloud hosted environment (demo topology). I was thinking about using the Enable-D365MaintenanceMode cmdlet, but ended up doing it the documented way.

The cmdlets documentation states that the Microsoft.Dynamics.AX.Deployment.Setup.exe is used to enable the maintenance mode. Since the documentation suggests this should only be done on VHD-based environments, I'm wondering if using Microsoft.Dynamics.AX.Deployment.Setup.exe on a CHE is fine, too.

I also noticed that the cmdlet references the disable-maintenancemode.sql script. I haven't got a chance to test this, but it looks like a copy&paste error. I think the enable-maintenancemode.sql script should be referenced instead.

[Splaxi]

You are totally right !

We should refactor both cmdlet to offer a mandatory parameter where you can select one onebox or che mode.

[FH-Inway]

Sounds good, I will give it a shot. Are there other cmdlets that have something similar? Or maybe some way of detecting if the tools are running on a CHE or VHD environment? This way, a mandatory parameter could be avoided.

[Splaxi]

Not really.

Back in the days we tested for elevated privileges - that indicated one onebox.

But thinking about it, the sql password could be an indication we could trust. The same goes for the package directory - if on c drive, it will most likely be a onebox 🤞

[Splaxi]

Or the certificates on the iis might be even better 🤘

[FH-Inway]

What about the $Script:IsOnebox variable? Several cmdlets make use of it and the tools use one of the application dlls to set it (see Get-ApplicationEnvironment)

[Splaxi]

IsOneboxEnvironment is the internal property that we depend on for that variable.

But if I remember correctly, both che and onebox (vhd) thinks of themselves as IsOneboxEnvironment = $true

[FH-Inway]

Will test this. If it is true for both environment types, there is also $Script:EnvironmentType which gets set in variables.ps1 based on the URL of the environment.

[Splaxi]

True and I would trust that one even more after looking at the code

[FH-Inway]

Seems we have a winner. I created issue #586 for further work on this.
I think I also found another issue with the enable script. It starts by stopping all services, but in the end, only the Aos service is started again.

[Splaxi]

That is on purpose, as you really only want the aos to be running while in maintenance mode.

😉

[FH-Inway]

Ah, yes, of course, that makes sense.