As is the sa password of AutodeskVault. both are pretty risky data security /integrity issues, along with voiding the domain password policy (See same TS#). AFAIK – given physical network access, not even login, any Vault installation can be corrupted/ hacked/ edited with impunity. Vault does not respect or understand domain security or privileges. Yet, it is completely dependent on MS SQL Server….. which does have a built-in understanding of domain security. somehow that makes little sense.

Speaking of SQL Server…. The Autodesk DataManagement Server, ADMS, is middleware. There’s no logical reason that it should be totally dependent on MS SQL Server. The whole point of any data manament server layer is to communicate with the database server! Good programming practice would entail designing your Data Management Server to work with multiple SQL-based DB Servers, cleanly separating the DataManagement from the DataStore. Failing to do so indicates problems with either the requirements for, or the implementation of, the DMS. I could understand a small developer with a two man shop cutting corners that way, coding DB-specific calls, and not doing a quality job of DataManagement, but that’s not who’s developing Vault.

Presuming my infrastructure is built heavily on either Oracle, MySQL, PostgreSQL, or a different enterprise-class scalable DB, Vault still requires that I license, install, support, & maintain the MS DB product, and purchase CALS for every person who will be accessing it. The cost of Vault just became very large, simply to duplicate an already existing PostgreSQL infrastructure. We could discuss the merits and (dis)advantages of various enterprise DB packages all day, but the essential point is that Auodesk has prevented the Vault administrator from using his tool of choice, and locked him into an expensive path. And that was not necessary to accomplish the job of the ADMS.

Migration — it’s my understanding that Vault 4 does not have a clean or simple migration to Vault 5. I’m hearing that secondhand, never having installed Vault 4, so it’s possible I’m incorrect. The reports i have heard however, describe much conflict, wailinng, and hairpulling.

There _are_ enterprise level EDMS solutions out there (which work somewhat with AutoCAD, and have no ability at all to handle C3D dependencies). Documentum is one of the largest players in that space. I’ve yet to see any information or planning on how to incorparate a project from Vault to Documentum. Even Projectwise from the Bentley folks has that ability, and a moderate ability to deal with AutoCAD design drawings. Migration between Vault and a real enterprise EDMS is a mandatory requirement. Pretending that Vault is a sufficient answer, or ought to be a black hole that consume data but can’t share it, is not realy a good thing for customers.

Security — Ok, to be fair securty is something that cannot be judged until the product has been worked on and attacked. But given the issues identified earlier, I cannot be optimistic that Autodesk managers have any basic understanding of database security. The default installation that tags everyone as a single SQL user indicates to me fairly well that auditing, edit history, etc were not on the list of important items, at least not in relation to easier installations. Since ADMS is hardwired to use MS SQL Server, any security flaws in SQL Server will automatically apply to _every_ Vault installation and user. If that doesn’t concern you, it probably should.

Any and all of these issues can be fixed. Most of them are design flaws rather than bug. But is there any interest in Autodesk’s part to do so?

http://i90.photobucket.com/albums/k246/tygati/worlds_finest/wf311_1.jpg

But other than that, I don’t have much to share. Enlighten us instead of throwing out challenges. The idea is to share knowledge.

Vault is interesting, and to someone who has not invested any time or money into enterprise EDMS packages, it may look interesting. But, if an individual has, then exercising due diligence on Vault will point out a huge number of issues, from security, to migration, to infrastructure. Conceptually Vault has potential, but the implementation is of great concern. As an exercise to a vault proponent, explain ’superman’ and why that would be an item of concern.

I’ve spoken to sources inside Adesk and Vault is on the product roadmap for C3D for every version that’s been penciled in.

Anonymity doesn’t fly at civil3d.com. Own your opinion, or keep it to yourself.
JW

Frequently that does not seem to be recognized by Autodesk the corporation. Occasionally, as in the return of 3dsOut, it is. But, as a user of Autodesk software, and a paying customer of Autodesk, I do not often see that the customer/user really counts. Judging from your comments it’s a point you do not see as relevant. I would hope that you consider your own customer’s interests a priority in your business even if the mega-corporations do not.

MyFeedback is marginally useful in helping the developers locate specific issues, but the design decisions and architectural flaws in the software are predicated on decisions made within Autodesk’s ivory towers with little apparent regard for the customer.
Many seem driven by internal corporate politics rather than being customer driven.

Just call me a curmudgeon, but I really do expect a better product and better service for my hard earned dollars.