|
|
|
This section only applies to scanning jobs created using the FSA Job Definition wizard in the Administration console. The issues below do not apply to scanning jobs run from a command line.
Important! When a scheduled scanning job is running, it is essential that nobody logs onto the target machine using the same account as the FSA!
If a user and the FSA are logged on to the same machine, at the same time, and using the same Windows user account, this can adversely affect the scanning job. The job may terminate prematurely or it may even fail to respond to attempts to terminate it manually.
For this reason, you must be careful when choosing the Run As user for a scheduled scanning job. Specifically, if you want jobs to run as your FSA limited access user or FSA full access user, we recommend that these users are bespoke accounts created for exclusive use by the FSA. Do not choose a Run As user that corresponds to a real user account if there is any possibility that this user will be logged on to the target machine while a scheduled scanning job runs.
Avoid This Situation!
The classic mistake is when a network administrator schedules a scanning job and enters their own domain account as the Run As user (because they know that they have access to all the required scan locations). While performing an unrelated task, they subsequently log on to a target machine while the scan is in progress, so causing the scan to fail.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |