Optionally, you can update to the latest version of A360 Desktop to extend the service. You can identify your A360 Desktop version by right-clicking on the icon in the system tray, and selecting “Preferences” to see the version number.
Versions starting with 7, released with 2017 products: Expire September 19th, 2017.Versions starting with 6, released with 2016 products: Expire August 22nd, 2017.Versions starting with 5, released with 2015 products: Expire July 26th, 2017.Versions starting with 4, released with 2014 products: Expire June 7th, 2017.If you are using A360 Desktop, your data will remain available online in A360 Drive, but it will no longer be synchronized with your desktop. If you are not running A360 Desktop, or syncing files with A360 Drive, then this expiration will not affect you. A360 Desktop is responsible for synchronizing data on your desktop with A360 Drive online.
Should additional assistance be required, simply reply to this post.Are you seeing this Autodesk 360 Desktop Expiration Notice?Īutodesk is discontinuing the A360 Desktop application. If so, please click the Accept Solution button. Please let me know if this issue may be considered resolved. If you want to try testing BIM 360 Document Management, see the link for the 30 day trial. In all recent cases that we have seen this message, the changes actually are made and can be seen upon refreshing the page. Since the folders that the user created were not needed, there were simply deleted.įinally, development will investigate the cause for the "heavy load" messages being returned. The second was inadvertently created by mistake and had the same name.
One was created and shared by you to the user. The folder names that appeared duplicated were actually different folder that happened to have the same name.
As discussed, I have submitted this behavior to development for further review to see if there are any potential, future improvements that could be made in this area. We resolved the issue with the outdated folder name by removing the user's access to the folder and then re-adding the user's access back to the same folder. The user was experiencing multiple issues with folder names: This is in follow-up to our conversation this week.
0 kommentar(er)
