« Job Server Troubleshooting Checklist | Main | Navisworks 2012 Vault Addin Is Not Displayed »

May 17, 2011

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a01156eaaf373970c014e887cc335970d

Listed below are links to weblogs that reference File Locked! When Releasing A File:

Comments

Scott Moyse

So does this mean its not necessary to do this setup in 2012 and that any user logged into the job processor can update view?

Scott Moyse

Now all you need to do is Allow windows authentication on the job processor. Then i can have my users use the same license for their client, Add-in and the Job processor, instead of it unnecessarily using up another license.

I paid for the full version of Vault, Professional but still feel like i'm being shafted on the licensing by Autodesk just to take full advantage of the features in Vault Pro. Why isn't the job processor just integrated into Vault in the first place?

Scott Moyse

I just thought I should post this so its a bit more balanced and to thank you for sorting out this behavior between 2011 & 2012.

I'm happy you guys have allowed the update view using job processor to work without that user needing to have the security rights to make the modifications to a file in the released state. At least with a non windows authenticated user logged into the addin/client and now the Job processor allowing this behaviour it only takes up one license.

Using windows authentication here would be a lot tidier though.

The comments to this entry are closed.

RSS Feed

  • Subscribe
Bookmark and Share

September 2014

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30