We have a situation where we have an assembly that we need to make a copy design of an old revision of.

Without jumping through a ton of hoops this would make a nice enhancement for this software.

Please, add an ability to use several Vault license types at one server. For example, using combination of Vault Collaboration and Vault Professional.

Because not all users need the top functionality, but read-only from web-client is not enough for them - so why pay more? Customers really need this feature.

One of discussions: at Vault forum.

We're using full SQL replication and as far as I know, the document numbering schemes are having no issues with being used across multi-sites so on face value, I can't see why the Item numbering schemes should.

Technically speaking again, I get the 'if a workgroup goes down' theory but to be honest if a business is large enough to justify having multi-site replication, it'll be sitting on a pretty good IT infrastructure so although you can never say never, it's a rare occurence for a site to compeletely go down.  However, item's being created is an event that occurs multiple times, hundreds of times per day.  

In addition to that, I worked in the reseller channel for nearly a decade and this was never publicised by Autodesk, I had no idea that we needed to consider this when building multi-site implementations.  A Google search for "autodesk vault item number replication" returns zero information on this and confirms that I haven't missed an technical publications on this story.

The concept of having a numbering scheme per site isn't a practical one, if you allowed the option of defaulting a specific numbering scheme to a specific site then it would be close to being a considerable option.  If it was up to me, I'd consider altering product behaviour to either:

1) Provide an administrative option whereby if a workgroup goes down, prevent any Items being generated.  Then it's up to me, if a site goes down I can simply stop Items being made until things come back online.

2) Keep the current existing workflow, but in the event of a disconnection between publisher and subscriber, when the failed site comes back online, Vault creates an ADMS task to automatically renumber any Items created during that time with the [@WORKGROUP suffix], giving them the next available number.  Warn all users with an in-client prompt that the Items they're creating may be automatically renumered when the system fault is resolved.

3) Most if not all everyday Vault users are not going to have a clue about what we're talking about here, so when this numbering conflict occurs through standard workflow, at least give them an in-client prompt or warning explaining why their Item number isn't now what they first thought it was.

4) Make the Item numbering schemes work the same way as the document numbering schemes!

I can think of many more options, most of which including the above are all much more favorable than what we have now which is Vault modifying production data at will without any warning to the user.

** Pulled from newsgroup post: http://forums.autodesk.com/t5/Autodesk-Vault/Item-Numbers-Vault-hacking-them-up/m-p/3766632#M46267

Consider this Scenario

(VP2013) Connected Workgroup

Workgroup A (Admin Ownership)

   Vault SiteServer 1

Workgroup B

   Vault Site Server 2

If you log into "Vault Site Server 1" and initiate a "Replicate Now" on a database on "Vault Site Server 2".

This message is written into the ADMS Console log on "Vault Site Server 1"

15/02/2013 9:30:18 PM Replication has been initiated.

The Wish is to give more information on this and similar commands. It would be useful if the log file said

15/02/2013 9:30:18 PM Filestore Replication has been initiated for <database x> on <Vault Site Server>. Refer to the log files on <Vault Site Server> for more information.

Once a file\folder is replicated from one site to another, the challenge is to unreplicate.

Currently there appears to be 2 options to unreplicate a file.

1) In the ADMS Console, edit the "Replicated Folder" and untick the folder that you want to unreplicate, then delete the file(s) from the vault, re-add it to the "unreplicated" folder. This will prevent the file from being replicated in future

2) Disable the Vault on the site, delete the local filestore, Enable it. This can be dangerous if the file is not present on at least one other site. Its OK if you know all files are replicated to at least one site.

The wish is to untick a folder in the "Replicated Folder" dialogue for that site and for the ADMS Console to check to see if that file appears on another site before allowing the Admin to unreplicate the folder. Once the check is completed, the files in the selected folder are removed from that sites filestore.

If you think this would be a useful enhancement, add a comment to this thread...

establish a system, where known issue go directly to the customer (especially platinum users)

e.g. WorkgroupReplication.xml issues and things where we can easily improve our system like web.config tweaks.

A customer who must plan for disaster recovery scenarios would like the ability to restore the primary Vault Database and Filestore from a replicated Database and Filestore. If it is not possible to do this now might the capability be added in a future release?

SAMIAM