upgrade to 7.4.5 / prerequisite software

I'll try that today, thanks Richard!

Recently I tried to install ARS 7.4.5 on *W2016* in my Lab and had issue to pass with O365/AAD prereqs. I promoted *W2019* Server and qas able to enable all O365/AAD prereqs without any problem as per the links provided in the ARS Install Wizard (EXO, Module Azure, Module Az, Teams).

Thanks for your suggestions Aidar, unfortunately I can't upgrade my server, also probably the issue is that I am not able to install the packages over the "normal" way, as this server is very restricted, no PSrepository and other connections. I've tried to install again as suggested above, but it seems azure AZ module is not listed when I check with "Get-Module -ListAvailable", so not sure... it seems something is missing, i did the same "unzipping" installation with other modules and that was working fine. 

 micha.becker 

Where the module is not packaged (so just downloadable), and therefore you need to get it via a PSProvider, the below might help.

This post by on "sqlrambling.net"

INSTALLING POWERSHELL MODULE WITHOUT INTERNET ACCESS

In essence you'd download them from the appropriate PSProvider, save them to file, transport, the import.

Hope this helps

The below is in essence the save of the powershell modules, as mentioned in the above article.

$SaveTo = "C:\Temp\Modules"
$Modules = ('ExchangeOnlineManagement','AzureAD','PartnerCenter','MicrosoftTeams')


clear-host

If(Test-Path($SaveTo))
{

    ForEach($Module in $Modules)
    {
        Write-Output "$Module"

        If(Test-Path("$($SaveTo)\$($Module).zip"))
        {
            Rename-Item -Path "$($SaveTo)\$($Module).zip" -NewName "$($Module) $(Get-date -Format "yyyymmddhhmss")-old.zip"
            Write-Output "Renamed existing ZIP File for $($Module)"
        }

        $Result = Save-Module -Name $Module -Path $SaveTo

        If(Test-Path("$($SaveTo)\$($Module)"))
        {
            Write-Output "`t$($Module) downloaded, begin zipping"
            Compress-Archive -Path "$($SaveTo)\$($Module)" -DestinationPath "$($SaveTo)\$($Module).zip"
            
            If(Test-Path("$($SaveTo)\$($Module).zip"))
            {
                Write-Output "`t$($Module).zip created, removing download folder"
                Remove-Item -Path "$($SaveTo)\$($Module)" -Recurse -Force

                If(Test-Path("$($SaveTo)\$($Module)"))
                {
                    Write-Output "`tFailed to remove $Module download folder"
                }
                Else
                {
                    Write-Output "$($Module) folder removed"
                }
            }
        }
        Else
        {
            Write-Output "Failed to download $Module"
        }

    }
}
Else
{
    Write-Output "$SaveTo does not exist"
}

Able to get past this issue?   I'm working with my team now to get 7.4.5 installed in our dev environment ... should be the easiest install of all.  nope.

we have the module folders copied into the default module location and can see the commandlets associated when we run get-command *exo*  .. *team* etc.
we are being prompted for all the modules and a SQL connector, each of which we have in place.   

If there was a be-all ending to this question ... can you share?

Hi, I went with the quiet install, I couldn't pass all requirements (install the modules offline). As I don't use the Azure parts in ARS anyway, that was working for me. 

E:\ARS_Software\Active_Roles_7.5\ActiveRoles.exe /quiet /install /IAcceptActiveRolesLicenseTerms /log "E:\ARS_Software\Active_Roles_7.5" 

Regards,
Micha

we used this method too - Micha - thanks for the reply. it allowed us to get past the install pre-req check, but that leaves me with no confidence in the post-install ability to fill the needs of all the tools we support / or will soon support that require these modules to be installed and properly configured.  we have an onsite Microsoft rep who confirmed with us that a module-is-just-a-folder-with-stuff-inside.  there are no registry keys, no magic environment variables involved.  the installer should see and accept the module found at the default location.    We're working with OneIdentity support to evaluate why - despite putting the extracted folders in place - that the pre-requisites screen still tells me 3 modules are not installed.   Where I work - We can't just d/l ... there are a number of hoops to jump, with each module requiring it's own separate set of hoops.  I don't fully understand why  - given all the 'check here to accept this and that license for 3rd party tools' already in place in the 7.5.3 installer  ... why the dev team couldn't just include the required modules in the redistributables folder, and auto-install where needed.     

We're proceeding with support, and while that plays out, testing out the new silently installed version in DEV ...  we are exporting production templates/scripts/workflows/websites to make sure our customizations still play nice in the new version.   

Thanks again for the feedback.  Helped us get on our way.

Many thanks for that answer, I too reported to oneIdentity that the modules should be part of the installation and still hoping this will be the case in a later version because I've lost too much time for this topic already in the past. The statment from microsoft is very helpful to me too, thanks!

We are reviewing the PowerShell requirements for a future release of Active Roles.

For the current releases of Active Roles, not having them installed may put customers in an unsupported configuration as this has not been officially tested.

Please refer to KB 333457 for details:

https://support.oneidentity.com/active-roles/kb/333457/active-roles-powershell-module-prerequisites

Thank you,

Daniel Bishop

One Identity

Hi Daniel, the quiet install was suggested by the OneIdentity Support as the install did not recognize the offline installed module folders. So I do not hope that this will put me in an unsupported configuration now. Unfortunately the support team wasn't able to find any other solution at this time.