Not likely - with the gamut of network, server and workstation topology, anti-virus / malware, Group Policy, firewall constraints, it would seem a daunting task.  I think the best you can do is to review the latest compatibility guide.

support.na.sage.com/.../viewContent.do

I'm not aware of any such document, but I can offer the following recommendations based on our, and other's experiences over the years. Hopefully this information will also be useful to others, or invite further discussion.

If Anti-Virus or other security software is installed on the computer where installation is taking place, it's important to disable real-time scanning of the target Programs and Shared Data directories (and their sub-directories) that are specified during installation. Scheduled scanning of these directories should be fine, but check performance during scanning and alter the scanning schedule if performance issues occur.

The user used to perform software installation should have Local Administrative permission on the computer where installation is taking place. User Account Control should not need to be altered from the default setting ("Notify me only when applications try to make changes to my computer"). Also, it's important that this user runs .\<Programs Directory>\Runtime\Regacc.exe after each installation or upgrade by Right-Clicking the executable and clicking the Run as Administrator option, to ensure that COM objects are correctly registered for non-administrative users of the computer. If the Programs or SharedData directories reside in a network location, we prefer using UNC paths over mapped drives, to avoid issues with Group Policy configurations where access to mapped drives by administrative users is disabled.

The user used to run the software should not need to be a Power User or Administrator, but they will need Read permission on the Programs and SharedData directories (and their sub-directories) that were specified during installation, and Write permission on the 'Company', 'Site' and 'User' Shared Data directories.

It's common to install Microsoft SQL Server on a different server, and in this case a firewall rule will need to be added.

Tools like Process Monitor etc. are useful for identify missing permissions etc. You could also consider inviting a security expert to audit your installation.