This took me some time to work out from different sources and my own fiddling, so I thought I would put as much as I could into a good old tech doc.  This will silently uninstall all the Adobe CC products.
note - the packaging tool is called CCPLauncher.exe but I also refer to the interface the user receives the Adobe Creative Cloud (launcher), so I will refer to them as I just have in full during my following information.

First off, this is the configuration we have here
- The Creative Cloud (launcher) is deployed by SCCM, the user can then install anything they are licensed for with the "elevated permissions" tick box during packaging with CCPLauncher.exe. 
- Only the Creative Cloud (launcher) was packaged to save creating multiple packs or one large 24Gb package, where they need updating every few months
- We have an Adobe software Server to deliver the CC licensed software to the user.
- During deployment, to turn off the auto updates, I found the file com.adobe.acc.container.default.prefs under [username]\Adobe\OOBE.  it contains the line  <prefs><property key="keepAppAlwaysUpToDate">ON</property></prefs>.  Change this to OFF.  The website doesn't work.  The AdobeUpdaterPrefs.dat also removes the elevated permissions flag when it is put in externally.
Packaging has been covered by many others before me, so this is more about uninstalling the complete Adobe Creative Cloud (launcher) and Suite when the user no longer wants to use it, or Software Management wants it off.  These are the steps I took to build the uninstaller

- Run CCPLauncher.exe and select to create an uninstall package, this creates AdobeCCUninstaller.exe and AdobeCCUinstallerConfig.xml.
- Install the Adobe Creative Cloud (launcher) on a VM and install Flash Builder Premium.  Using the registry uninstall command (found in Wow6432Node on a 64bit install), run the uninstaller for Flash Builder and look in the {adminuser}\Temp\{GUID} directory for a file deploy.xml.  Take a copy of this file while it's uninstalling. Change its name to something like uninstallFlashBuilder.xml (so you know what the file is used for later).

Here are the uninstall commands without the GUIDs as they might be different for different versions.  I have a VBscript I use to uninstall any MSI from the registry DisplayName, so I used that here.  I went overboard with the tasks I killed as I had already spent too much time researching the uninstall methods for all this.  I might have killed more services than needed, but a reboot or if the service is "required" will restart the stopped service.  I found this to be the best order of steps, as some services restart within seconds, or crash and error message.

AdobeCCUinstaller.exe (no switches or anything required here if both files are in the same directory, this will uninstall most of the Adobe Stuff)
Adobe Acrobat (MSIEXEC /x {GUID})
Adobe Gaming (MSIEXEC /x {GUID})
Adobe Scout (MSIEXEC /x {GUID})
Adobe Creative Cloud (launcher) (MSIEXEC /x {GUID}) - this doesn't uninstall the launcher, just the MSI header, so now you won't find it in ARP or registry, the rest is removed during the cleaner tool operation
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\DWA\Setup.exe --deploymentFile={path}uninstallFlashBuilder.xml"
taskkill "Adobe CEF Helper.exe"
taskkill "creative cloud.exe"
taskkill "coresync.exe"
taskkill "armsvc" - Service AdobeARMService
taskkill "AGSService" - Service Adobe Genuine software integrity
taskkill "AdobeUpdateService" - Service
taskkill "Adobe Desktop Service" - Service
taskkill "Adobe Installer"
taskkill "cclibrary"
taskkill "CCXProcess"
taskkill "CoreSync"
taskkill "node"
taskkill "AdobeIPCBroker"
AdobeCreativeCloudCleanerTool.exe --removeAll=CREATIVECLOUDCS6PRODUCTS

EDIT: If the user uninstalls then reinstalls, the file {localappdata}\Adobe\AAMUpdater\1.0\AdobeUpdaterPrefs.dat needs to be deleted if "elevated permissions" was selected in the packaging options.  Adobe Creative Cloud (launcher) can be running when deleting the file.  It looks like it dynamically checks the file.

I hope this helps anybody trying to do the same.

my main resources came from here, the rest was bash and test - 10/12/2015 by: apptopack