Introduction

When you try to install a new Exchange Server or if make an attempt to recover a failed server, you might run into the following error:

This error occurs because the Scripting Agents CmdLetExtentionAgent is enabled but during installation the ScriptingAgentConfig.xml is not found. By default, the file is called ScriptingAgentmConfig.xml.sample (and that is also how it is copied from the installation source).

I find it very unfortunate that the installer doesn’t take into account that if the Scripting Agent is installed it should change the filename, therefore avoiding this error. However; I understand that this might not be an easy thing to do. So let me show you how you can avoid this error.

Solution(s)

The first solution:

Copy the ScriptingAgentConfig.xml from another server (or a backup) to “C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtentionAgents” before running the installer. This way, the installer will find the file and will not throw an error. Just make sure that you create the folders exactly as written, because the folder path is case sensitive.:

The second solution: Disable the Scripting-Agent before you run the install/recovery and re-enable it afterwards.

1. Run the following cmdlet from another Exchange Server: Disable-CmdletExtensionAgent –Identity “Scripting Agent” and confirm:
   
   
    
   
2. (Re)Run setup:
   
   
    
   
3. Re-enable the scripting agent running Enable-CmdletExtensionAgent –Identity “Scripting Agent”: