Redshift's Lighting is Different on Team Render Than on My Editing Machine (How to Cache Redshift GI)

Sometimes it will come to pass that your lighting will look different on another machine (such as one that is part of a Team Render farm) than it does on your main/editing machine.  This is because, even with similiar or identical hardware, there can be differences in the way one machine calculates Global Illumination compared to another machine.

This can cause blown out lighting, or lighting that is too dim, and anything in between.  It is most noticeable with bucket rendering on a still image where there will be a "tiled" look because the lighting rendered by one machine's buckets is different from the lighting of another's, which makes a strange patchwork look.

This problem, however, can be solved by simply caching your Global Illumination before you render

To do this with Redshift, you need to go to your Render Settings, then select Redshift on the left side, enable the Advanced tab, then select the Global Illumination tab:
 

Here, you'll need to expand the Irradiance Point Cloud section and, under Mode, choose "Rebuild (Prepass Only)"

This will force Redshift to render only the Global Illumination prepass instead of the whole image.

Once this is set up, the next step is to choose Render > Render to Picture Viewer* to render out the whole project's GI prepass.

*Make sure that you have your Render Settings set to render the whole animation, if applicable, and make sure you are doing a regular Render to Picture Viewer, not a Team Render to Picture Viewer, as the GI prepass needs to be rendered all on one machine.

This will create a "tex" folder in your project folder* which will have a "projectname.gi" file created in it for each frame.  This is your GI prepass.

*Note that if you did not use a File > Save Project With Assets operation to save your project file to it's own project folder, the default location of the tex folder is in your Cinema 4D Preferences (which you can view from the Preferences window in Cinema 4D by clicking "Preferences Folder...").  This tex folder is shared by all projects, so if you build a new GI prepass for a new project, this one will be lost.

Once you've saved the GI prepass, you can go back to your Redshift Render Settings and, again under Global Illumination > Irradiance Point Cloud, change the Mode to "Load"

This will cause Redshift to load a GI prepass file or files instead of calculating the Global Illumination at render time, which will both save time, and use GI information from only one machine, which will prevent there from being discrepancies in GI from one machine to another.

With this final step, you can now perform a Render > Team Render to Picture Viewer, or you can start your render job from Team Render Server, and the GI should all render as expected from your Redshift RenderView/IPR/Test Renders.