LCSError allows you to translate error codes into a description of the error;
it also may provide additional details regarding possible error causes and
solutions. This tool can be useful when log fi les list only error codes and no
descriptive text.
You can use both of these tools on machines that are not running OCS,
allowing them to be used by support teams and analysts.
Ensuring Compliance
With OCS archiving you have the ability to archive all meetings and IMs. This is referred to
as Critical Mode archiving. When archiving is running in this mode and a front-end server is
unable to archive messages, it will shut down, ensuring that no further messages can be
passed and compliancy requirements are maintained.
Configuring Archiving ??? Chapter 7 225
An additional aspect of the archiving capabilities in OCS allows the messages to be
encrypted between the front-end server and the Archiving and CDR Server, which may be
part of your compliancy requirements. If your setup includes use of a database on a remote
server, you will need to use SQL SSL encryption to secure the traffi c between the Archiving
and CDR Server and the database server; as an alternative, you can use Windows IP Security
(IPSec) encryption.
Handling Failure
Archiving can fail in OCS in a number of ways, and all of these failures are handled in the
same way if you are running in Critical Mode. In such a scenario, an error is written to the
Windows Event Log and the Front-End Service is shut down.
Pages:
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259