Changing symbology to a pre-existing layer:
For your GO! Sync project if you are changing the symbology to a pre-existing layer, you will need to make the symbology change in ArcMap and then save your changes. The MXD’s being used by your project can be found in the $serverdata\MobileDownloads\Default\MXD folder location, where $serverdata is the server root directory and “Default” is the particular device group. If you have no device groups configured you will automatically be using the Default device group. The next time you run a sync from one of your client machine’s with GO! Sync installed you will see those changes you made.
How do I know which MXD to use?
If you only have 1 MXD you will be using the default MXD which can be found in this location: $ServerData\MobileDownloads\Default\MXD folder
I have multiple MXD’s for my project. How do I know which one is my default?
If your GO! Sync project is configured to use multiple MXD’s and you want to identify the default MXD being used, navigate to the $serverdata\MobileDownloads\Default\MobileConfiguration and open the file called GoSyncMobileConfiguration.xml. Once open, search for the following tag:
<StartUpMXD></StartUpMXD>
Please note: If multiple MXD’s are being used, Mapbook automatically remembers the last MXD used in the application.
We created a new feature class – how can I add this to my GO! Sync project?
If your new layer was added to ArcSDE:
You will need to first navigate to your GO! Sync server and open the GO! Sync Extractor. This can be located by navigating to the Start menu and finding the GO! Sync folder.
Once open, click the Open Extract Configuration button 
and navigate to your extractor configuration file (.xconf file) which is usually found in this location: $serverdata\ServerConfiguration\Extractor folder. If there is no .xconf file visible you can run a search in Windows explorer for $serverdata for “.xconf”.
What is the purpose of the .xconf file?
The .xconf file is used to store configuration information for extractor. This file, once opened with the extractor populates any existing destination or source geodatabases; its specific feature classes, auxiliary processes, and any additional output options applicable to destination geodatabases.
If your .xconf file(s) have already been created for you the best approach would be to utilize an existing .xconf file. Doing so avoids having to create a new .xconf file, and a corresponding scheduled task to run the extractor that uses the .xconf file.
Adding your new layer to the .xconf file:
In the extractor, if your new layer is visible but unchecked then this means you need to update your .xconf file by placing a check beside the layer and then saving your changes.
If this is a new layer then most likely there won’t be a check by the layer. If you cannot see your new layer among your other feature classes then your feature class does not exist in the source geodatabase specified.
*Please note that .xconf files can store multiple destination geodatabases and different corresponding source connection files in their respective drop down menus. It is recommended to verify you are using the proper connection information when location your new layer.
How do I change the symbology if my layer was added to a personal or file geodatabase?
If your new layer was added in a separate geodatabase:
1) Locate the Destination Geodatabase drop down in your .xconf file and add a new destination geodatabase. Ensure this geodatabase is different from the previous destination geodatabase. 
2) Select the corresponding location of the Source Geodatabase for the new layer
3) Save the .xconf file 
Adding the layer to the .xconf file only has to be done once as these setting are saved in your .xconf file. By adding the new layer in the .xconf file you are adding a layer to your other existing feature classes that are part of the FTP syncing process that occurs daily to each of your client machine’s. As long as the information is saved in the .xconf file the layer is permanently added to your GO! Sync project (permanent until you delete or remove).
Checking your project for your new layer:
To check for the new layer run a sync on the client machine and open Mapbook. If a client machine is not available, there is an option in the extractor to create an unzipped geodatabase which helps confirm if your feature class was added to your .xconf file successfully.
