Current site has been using Automation Servers independently with no Enterprise Server; it is now required to bring the Automation Servers into the Enterprise Server. Can we rename these Automation Servers as needed?
- Renaming of the Enterprise and Automation Servers are grayed out, can we rename these Servers?
SmartStruxure Automation Server and Enterprise Server (all versions)
Problems have been found with loss of communications, such as Enterprise Server indicating that the Automation Server is offline even though the Automation Server indicates it is Online.
Communication issues between objects referenced between the Enterprise Server and various Automation Servers, including objects reference between multiple Automation Servers themselves not updating.
As such moving / renaming of the Automation Server and Enterprise Server will be disabled once you have added your first server (Automation Server) to an Enterprise Server.
The Enterprise Server’s default name is “Server1”, when starting to use the Enterprise Server; its name should always be defined first before completing any other function.
The Automation Server’s default name is “Server1”also, when working with a set of Automations Server’s independently without an Enterprise Server then you are free to name and rename the Automation Server so long as you are working with one standalone Automation Server. When you add the Automation Server to the Enterprise Server the name of Automation Server is automatically renamed at the time of adding the Server to the Enterprise Server.
If you have initiated a Project using an Enterprise Server and added Automation Servers you will notice that if you right click on the Enterprise Server or any of the Automation Server’s the Rename (F2) option will be greyed out (as shown below).
There is a current workaround that will allow you to rename the Automation Server after it has been added to the Enterprise Server, provided you follow these set rules and process.
VERY IMPORTANT: This can only be done during the initial implementation of the project. You should NOT do this if you have already started to reference objects from the Automation Server at the Enterprise Server level or started referencing object between multiple Automation Servers. These objects / functions may include the following:
- Backups / Archives
- Trend / Logs
You will cause communication problems and the references will NOT work if you proceed with these steps and you have already added or performed any of these objects / functions.
For these steps on how to rename your Automation Server we will use the simple system shown below:
With the scenario as shown above and with none of the listed objects above created, you can perform a rename as follows:
Using Workstation log into the Enterprise Server.
Now select the Automation Server you wanted to rename and select Delete – Confirm the Delete
Using our example, the screen should now only show one Automation Server
You can now add a New Server, selected the new name of the server you just deleted, in our case we have used AS#1Renamed as shown.
All functionality of the renamed AS#1 should now be available under its new name AS#1Renamed.
Once you have added all your required Automation Servers with the CORRECT NAME you can then safely start to create objects in the Enterprise Server that reference the Automation Servers as well as create objects that are referenced between each Automation Server.
If you require any additional assistance on how to perform these steps refer to the StruxureWare WebHelp site. http://help.struxureware.schneider-electric.com/