Copy link to clipboard
Copied
Dear anyone doing this in 2019 or recently,
I am performing a fresh sync following the instructions on Adobe helpx for AUSST setup -- https://helpx.adobe.com/enterprise/package/help/update-server-setup-tool.html#SetupAUSSTserver
Folder path after the <serverroot> is not created like it is shown in the documentation example.
Performing an incremental sync after manually creating the "serverroot\updates\Adobe\CC" folder structure, the sync just starts recreating the same folder structures like in "serverroot\ACC" AND "serverroot\updates" AND "serverroot\webfeed" one level down in the manual folder structure.
What is the correct folder structure and why does the "serverroot\updates\Adobe\CC" not exist when the --fresh syn is started?
Thanks,
Hello,
there is no "serverroot\updates\Adobe\CC" directory on a correctly sync'ed AUSST server. I assume you're referring to the example given for the address of the server in the documentation under Set up AUSST server -> Set up Internal Update Server where it says to specify the root path and gives the following exmaple:
--root="/serverroot/updates/Adobe/CC"
I accept that this is slightly misleading, and will ask the documentation team to provide a clearer example.
If your server is not synchronis
Copy link to clipboard
Copied
Hello,
there is no "serverroot\updates\Adobe\CC" directory on a correctly sync'ed AUSST server. I assume you're referring to the example given for the address of the server in the documentation under Set up AUSST server -> Set up Internal Update Server where it says to specify the root path and gives the following exmaple:
--root="/serverroot/updates/Adobe/CC"
I accept that this is slightly misleading, and will ask the documentation team to provide a clearer example.
If your server is not synchronising properly, then there might be a network issue somewhere between your server and Adobe's. I would suggest checking the DLM log unter %TEMP%\CreativeCloud\ACC\AdobeDownload (assuming you're running it on Windows Server). If the reason is not clear, please open a support case via your Admin Console so we can investigate further.
Dominic