Latest updates
6.24.06
Improved gam user user@domain.com print filecounts select teamdriveid "<DriveFileID>" summary only
to display the Shared Drive ID and name on the summary line.
6.24.05
Updated option orderby completed|due|updated to gam <UserTypeEntity> print|show tasks to
display tasks in date order regardless of the hierarchy.
Fixed bug in 6.24.03 bug fix in gam <UserTypeEntity> transfer drive <UserItem> ... targetfolderid root ....
6.24.04
Updated gam update chromepolicy to allow zero-length values for TYPE_STRING policy values;
this is required to be able to clear a value from such a policy.
6.24.03
Fixed bug in gam <UserTypeEntity> transfer drive <UserItem> ... targetfolderid root ... that
transferred data to the source user's root folder, not the target user's root folder.
6.24.02
Fixed bug in gam print crostelemetry that included a spurious column header, devicdId, in the output.
6.24.01
Updated gam <UserTypeEntity> print|show tasks to display tasks in hierarchical order.
Added option orderby completed|due|updated to gam <UserTypeEntity> print|show tasks to
display tasks in date order within the hierarchy.
6.24.00
Added commands to manage and display Google Tasks.
6.23.01
Updated gam <UserTypeEntity> create|update|show|print form to give a better error message when the Forms API is not enabled.
ERROR: 403: permissionDenied - Google Forms API has not been used in project XXXXXXX before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/forms.googleapis.com/overview?project=XXXXXXX then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our sys\
tems and retry.
is replaced with
ERROR: Forms API not enabled. Please run "gam update project" and "gam user user@domain.com check serviceaccount"
6.23.00
Updated gam <UserTypeEntity> copy|move drivefile to produce more
informative progress messages. The source file name(ID) are shown
as well as the target parent folder name(ID) and target file/folder name(ID).
Deleted options copytopfileparents, copytopfolderparents copysubfileparents and copysubfolderparents
from gam <UserTypeEntity> copy drivefile as multi-parent file/folders can not be copied with multiple parents.
Updated gam <UserTypeEntity> copy drivefile to use shortcuts when the same file appears more that once in the copy.
The first time the file is processed, it is copied; if it is processed again (because of multiple parents within the source
folder structure), a shortcut is created that points to the first copy.
Added option copiedshortcutspointtocopiedfiles [<Boolean>] to gam <UserTypeEntity> copy drivefile.
In previous versions, copying shortcuts caused an error because shortcuts can't be copied, they must be re-created.
If a shortcut in the source structure points to a file/folder that is not in the source structure:
- The shortcut is re-created to point to the original file/folder.
If a shortcut in the source structure points to a file/folder that is in the source structure: copiedshortcutspointtocopiedfilesomitted orcopiedshortcutspointtocopiedfiles true- The shortcut is re-created to point to the copied file/folder.copiedshortcutspointtocopiedfiles false- The shortcut is re-created to point to the original file/folder.
Deleted options copysubfileparents and copysubfolderparents
from gam <UserTypeEntity> move drivefile as multi-parent file/folders can not be moved with multiple parents.
Added option createshortcutsfornonmovablefiles [<Boolean>] to gam <UserTypeEntity> move drivefile
to control processing of non-movable files; for example, files owned by users outside of your domain.
It causes GAM to create a shortcut in the target folders for files in the source folders that are not movable.
createshortcutsfornonmovablefilesomitted orcreateshortcutsfornonmovablefiles false- No shortcuts
are created and an error message is given explaining why the file can't be moved.createshortcutsfornonmovablefiles true- A shortcut is created that points to the non-movable file.
6.22.22
Fixed bug in gam <UserTypeEntity> create|update contact where the relation property was not properly processed.
6.22.21
Fixed bug where redirected stderr output from Gam main process was written
after GAM sub processes redirected stderr output.
6.22.20
The following update applies to one or two GAM users, if you're not one of them, stop reading.
When GAM is processing commands with data from a CSV file, csv_input_row_drop_filter and
csv_input_row_filter are evaluated and utilized by the GAM main process and are not
evaluated or processed by the GAM sub processes.
When GAM is processing commands with data from a CSV file, csv_output_header_drop_filter,
csv_output_header_filter, csv_output_row_drop_filter and csv_output_row_filter are
evaluated by the GAM main process and utilized by the GAM sub processes.
Evaluating the row filters once in the GAM main process means that <RowValueFilter>
forms data:<DataSelector> and notdata:<DataSelector> only read the data from <DataSelector> once.
6.22.19
Updated code to handle OUs with a % in their name. OUs with a + in their name
are still handled incorrectly by the API when accessed directly.
6.22.18
Added option oneitemperrow to gam print vaultexports|exports to have each of an
exports cloudStorageSink files displayed on a separate row.
Added options bucketmatchpattern <RegularExpression> and objectmatchpattern <RegularExpression>
to gam download vaultexport|export to allow selective downloading of export files.
6.22.17
Added quick_cros_move variable to gam.cfg that is used to provide the default value for quickcrosmove [<Boolean>] in:
gam update cros <CrOSEntity> <CrOSAttribute>+ [quickcrosmove [<Boolean>]] [nobatchupdate]
gam <CrOSTypeEntity> update <CrOSAttribute>+ [quickcrosmove [<Boolean>]] [nobatchupdate]
gam update org|ou <OrgUnitItem> add|move <CrOSTypeEntity> [quickcrosmove [<Boolean>]]
gam update org|ou <OrgUnitItem> sync <CrOSTypeEntity> [removetoou <OrgUnitItem>] [quickcrosmove [<Boolean>]]
Added use_projectid_as_name variable to gam.cfg that modifies gam create project to set
the default project name to the project ID instead of 'GAM Project' and to set the
default app name to the project ID instead of 'GAM'.
Improved error handling for the following error that occurs when the Customer ID is invalid.
ERROR: 400: invalidInput - Invalid Input
Installation
If you are a first time Gam user:
If you are upgrading from standard Gam
If you are upgrading from GAMADV-X or GAMADV-XTD