Esri / arcgis-powershell-dsc

This repository contains scripts, code and samples for automating the install and configuration of ArcGIS (Enterprise and Desktop) using Microsoft Windows PowerShell DSC (Desired State Configuration).
Apache License 2.0
110 stars 61 forks source link

ArcGIS Pro Patches not Downloaded/Installed #534

Open mikiekelly opened 2 months ago

mikiekelly commented 2 months ago

Community Note

Module Version

Affected Resource(s)

Configuration Files

{
    "AllNodes": [
        {
            "NodeName": "servername",
            "Role": [
                "Pro"
            ]
        }
    ],
    "ConfigData": {
        "DownloadSetups": true,
        "DownloadPatches": true,
        "Credentials": {
            "AGOCredential": {
                "UserName": "agolun",
                "Password": "agolpw"
            }
        },
        "ProVersion": "3.2",
        "Pro": {
            "Installer": {
                "Path": "D:\\Installers\\ArcGIS\\ArcGISPro_32_188049.exe",
                "DotnetDesktopRuntimeDownloadUrl": "https://download.visualstudio.microsoft.com/download/pr/d0849e66-227d-40f7-8f7b-c3f7dfe51f43/37f8a04ab7ff94db7f20d3c598dc4d74/windowsdesktop-runtime-6.0.29-win-x64.exe",
                "DotnetDesktopRuntimePath": "D:\\Installers\\ArcGIS\\windowsdesktop-runtime-6.0.29-win-x64.exe",
                "InstallDir": "D:\\Apps\\ArcGIS\\Pro",
                "PatchesDir": "D:\\Installers\\ArcGIS\\Pro"
            },
            "AuthorizationType": "CONCURRENT_USE",
            "LockAuthSettings": true,
            "BlockAddIns": 1,
            "SoftwareClass": "Professional",
            "PortalList": "https://myorg.maps.arcgis.com/home",
            "AllUsers": 1,
            "EsriLicenseHost": "@mylicenseserver",
            "EnableEUEI": true,
            "CheckForUpdatesAtStartup": false
        }
    }
}

Expected Behavior

ArcGIS Pro patches should be downloaded to the PatchesDir and installed

Actual Behavior

ArcGIS Pro and runtime successfully install, but no patches included

Steps to Reproduce

Run json via Invoke-ArcGISConfiguration

Important Factoids

NA

References

NA

QuadTog commented 1 month ago

What's your error? I've been mucking with a 4.2.1 enterprise install and it does work.

You should have the patches sitting in your "D:\Installers\ArcGIS\Pro" directory. I assume you can just click/run them too, like no 'perm/admin/can't install this .exe' issues? (Generally, means your domain/userID is blocked from installs).

Second thought is... (Pro 3.2 should work fine with .Net 6.0+...), but the newer Pro 3.3 says it requires 8.0x+ "ArcGIS Pro required Microsoft .NET Desktop Runtime (x64) 8.0.x. To download and install Microsoft Windows Desktop Runtime - 8.0.x (x64), visit the Microsoft website or contact your system administrator."

I noticed my auto patch pulled down the windowsdesktop-runtime-8.0.4-win-x64 version even though it was never specified/required nor used for an Enterprise setup lol.

mikiekelly commented 1 month ago

There's no error, but no patches download to the PatchesDir. A similar config with ArcGIS Enterprise downloads and installs all available patches. Did the config above download and install patches for you?

QuadTog commented 1 month ago

I haven't tested a singular Pro deployment. I don't see why it wouldn't work as they both use the same Powershell DSC modules to do it.

When you invoke your script, you get absolutely no output? That doesn't seem right, you should defs be getting some logs/info back.

cameronkroeker commented 1 month ago

Looks like ArcGIS Enterprise patches and ArcGIS Pro patches do not reside in the same repository. The module is searching for ArcGIS Pro patches in the same repository that ArcGIS Enterprise patches are hosted in, and is not finding any to download so it does not give an error.

It turns out ArcGIS Pro patches are hosted in My Esri only and the module does not contain logic to download patches from My Esri. For now this is a known limitation.

mikiekelly commented 1 month ago

Thanks for the update Cameron - that makes sense. I thought it might be something specific to ArcGIS Pro.