Corrected anomalies in this release
The list identifies the anomalies corrected in
FactoryTalk Policy Manager
version 6.60.00
.Use the identification information provided in the brackets
[]
to track anomalies in future releases or to request assistance from Customer Support.Changing a FactoryTalk Linx driver name causes deployment and onboarding errors
[3314099]
Deployment errors occur when you perform the following sequence:
- Add a device from theDiscoverypane to a zone with a certificate and deploy the security policy model.
- Change theFactoryTalk® Linxdriver name.
- Deploy the added device again with the driver name changed for the device.
To resolve this issue, restart
FactoryTalk System Services
after updating the FactoryTalk Linx
driver name.This anomaly corrected in version 6.60.
This anomaly first identified in version 6.40.
Devices validated for redundancy may no longer appear in Discovery pane
[3794255]
If you validate redundancy for a device, some devices may disappear from
Discovery
.
TIP:
To redisplay
devices, in 
for each EtherNet driver.
Discovery
, disable and enable
Auto browse
This anomaly corrected in version 6.60.
This anomaly first identified in version 6.50.
Proxied devices may disconnect after a security policy model deployment
[4800712]
If you deploy a security policy model with EtherNet in Cabinet devices and
CIP Security
proxy devices, a deployment error may display.To restore connections, power cycle
CIP Security
proxy devices.This anomaly corrected in version 6.60.
This anomaly first identified in version 6.51.
Provide Feedback