CentralCommand v2.0 Impacts on IT
Below is a list of IT environmental impacts in the CentralCommand v2.0 installation. | | | | | IIS must now be run | | IIS is necessary for: Web services Report notifications Help files | The IIS server will require ASP.Net enabled | | | .NET Framework 1.1 must be installed on workstations and Citrix servers. | | | | Changes to the security configuration to allow the trusting of AGRESSO components | | To use the new AGRESSO Smart Client in a central configured environment, the client computer needs to trust the AGRESSO assemblies. To achieve this, modifications must be done to the .NET configuration files on the client computer. | | Uninstall and reinstall VBA and Report Engine | | VBA will be new as well as Report Engine so that components (and Common Files, etc) will need to be uninstalled / reinstalled on workstations (and Citrix servers) running Central Configuration. | | Deployment of central config clients | | When you have 5.5 and 5.4 living in the same "environment", once you've run the 5.5 central config client on a workstation, then the 5.5 versions of Agresso Common and Agresso VBA that get auto-installed on that workstation must be manually uninstalled before the 5.4 central config client can be re-run on the same workstation. This is because the 5.5 versions of Common and VBA are not compatible with the 5.4 CentralCommand client. Note: One possible approach is to switch off the auto install of VBA/Common during testing and manually install them only as needed. |
Return to CentralCommand 2.0
|