Google Message Security for Google Apps Administration Guide - Manual (Page 382)

382 Message Security for Google Apps Administration Guide
When To Use Batch
Authority privileges determine which batch commands an administrator can run,
just as they determine what parts of the Administration Console an administrator
can access. Batch processing is independent of your currently viewed location
within the Administration Console, since each batch command contains details
about where to apply.
Configuration changes should be made by batch whenever:
• The number of changes is too great to effectively use the Administration
Console.
For example, you want to lower spam filter settings from level 4 to level 3 from 100
users. Configuring the Default User with the change will only affect new users.
Since changing user configuration for 100 users by Administration Console
interface would be repetitive and downright unpleasant, use the batch interface.
For detailed information about the EZCommand feature, see the Email Security
Batch Reference Guide.
Troubleshooting: Batch
Batch validation fails because a Batch command argument contains the comma
“,” character.
The comma character, is used to delimit different arguments passed to a batch
command, as described in the Email Security Batch Reference Guide.
Within a batch command argument, add quotes around the argument, so that the
comma will not be used as a delimiter.
Examples:
modifyuser [email protected], approved_senders=+"yahoo.com,+aol.com"
modifyorg "Jumbo, Inc Account", [email protected]
Batch Validation fails although command syntax is correct.
The batch validator does not take into account previous changes made within a
batch file. This implies that the following batch command sequence will cause a
validation error.
adduser [email protected]
addalias [email protected], [email protected]
If the syntax is correct, then these batch commands can be processed in this
sequence without error.