Symantec 10744983 Administration Guide - Page 45

Replicating data to Scanners, Email addresses of users and distribution lists

Page 45 highlights

Configuring system settings 45 Replicating data to Scanners Rejected The number of directory entries from the LDAP server rejected by the synchronization server. A number of LDAP transactions can be rejected when an attempt to add a group entry fails because one or more of the group members is not yet known to the LDAP synchronization service. Generally, this can be resolved by issuing a Synchronize Changes request from the Control Center. Each time this is done, the number of rejected entries should decrease. Once all group members are propagated, the group entries are added successfully. If, after a number of LDAP synchronization attempts, you continue to see the same number of rejected entries for an LDAP Source, examine the logs at Status > Logs with Control Center: LDAP selected in the Log Type: drop-down list. Use the information on this page to determine why the entries are repeatedly rejected. Pay particular attention to the file error.log.X, where X is a number. Replicating data to Scanners After an LDAP server has been defined to the Control Center, and after the synchronization of LDAP data between the LDAP server and the Control Center has successfully completed one full cycle, LDAP data can be synchronized to all attached and enabled Scanners. LDAP data includes the following: ■ Email addresses of users and distribution lists ■ Membership information for groups and distribution lists If any policies have end user settings enabled, the following data is replicated along with the above LDAP data: ■ Allowed/Blocked Sender settings ■ Language settings For replication to work properly, you must have configured, enabled, and scheduled Scanner replication and made certain that Scanner replication is enabled for each Scanner. See "Work with the Services tab" on page 26. In this section, information is available on the following topics: ■ Starting and stopping replication ■ Replication status information ■ Troubleshooting replication

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249

The number of directory entries from the LDAP server rejected by
the synchronization server.
A number of LDAP transactions can be rejected when an attempt
to add a group entry fails because one or more of the group members
is not yet known to the LDAP synchronization service. Generally,
this can be resolved by issuing a Synchronize Changes request from
the Control Center. Each time this is done, the number of rejected
entries should decrease. Once all group members are propagated,
the group entries are added successfully. If, after a number of LDAP
synchronization attempts, you continue to see the same number of
rejected entries for an LDAP Source, examine the logs at Status >
Logs with Control Center: LDAP selected in the Log Type: drop-down
list. Use the information on this page to determine why the entries
are repeatedly rejected. Pay particular attention to the file
error.log.X
, where
X
is a number.
Rejected
Replicating data to Scanners
After an LDAP server has been defined to the Control Center, and after the
synchronization of LDAP data between the LDAP server and the Control Center
has successfully completed one full cycle, LDAP data can be synchronized to all
attached and enabled Scanners.
LDAP data includes the following:
Email addresses of users and distribution lists
Membership information for groups and distribution lists
If any policies have end user settings enabled, the following data is replicated
along with the above LDAP data:
Allowed/Blocked Sender settings
Language settings
For replication to work properly, you must have configured, enabled, and scheduled
Scanner replication and made certain that Scanner replication is enabled for each
Scanner.
See
“Work with the Services tab”
on page 26.
In this section, information is available on the following topics:
Starting and stopping replication
Replication status information
Troubleshooting replication
45
Configuring system settings
Replicating data to Scanners