Latest Contributions by ChrisPedrezuela

Keen to get this available so easy to automate replica creation with register existing data option ... View more

This works now on our 10.6.1 setup. Only thing now is that this should be exposed as part of the arcpy modules rather than just using the Distribution Geodatabase toolbar ... View more

Is there anyway to automate this process? were on 10.6.1 already. Issue here is that my parent FCs are in a feature dataset on an SDE database and I want to replicate it on another SDE but without the featuredataset (just standalone fcs). I can establish the replicas using the method of "register with existing data" but its just way too slow. ... View more

I'd like to automate this process and would be good to include it as a parameter for the CreateReplica function for Arcpy. ... View more

Thanks Fay. I see from documentation that there is a "roleId" apart from "role" that can be exposed, so interesting that they don't have something like "roleLabel" or something. Anyway I guess i'll just look more to the online doc if there is a way otherwise I cannot its something I cannot add to my report that I am trying to automate. ... View more

I ran into this issue just recently. Basically once you update a mosaic dataset (previously create by a 10.3 desktop) using a 10.6 desktop, the mosaic dataset version becomes compatible only to 10.6 products or later. Once you publish it on 10.3 ArcGIS server, it wont recognize the mosaic dataset anymore and would give you logs that its an invalid image. The only resolution is get hold of a 10.3 desktop and create the mosaic dataset again and then publish. ... View more

Thanks Amnoy.  I think we need to verify the borrowing option for groups. Btw how do you check the entitlementID? Thanks Sent from Yahoo Mail on Android On Fri, 22 Mar 2019 at 6:13 AM, Amnoy Am<geonet@esri.com> wrote: #yiv0325569280 * #yiv0325569280 a #yiv0325569280 body {font-family:Helvetica, Arial, sans-serif;}#yiv0325569280 #yiv0325569280 h1, #yiv0325569280 h2, #yiv0325569280 h3, #yiv0325569280 h4, #yiv0325569280 h5, #yiv0325569280 h6, #yiv0325569280 p, #yiv0325569280 hr {}#yiv0325569280 .yiv0325569280button td {} | GeoNet | Re: Borrowing licence does not honor license OPT file reply from Amnoy Am in Admin Tools - View the full discussion GROUP A user1 user2 INCLUDE Editor GROUP A MAX 6 Editor GROUP A EXCLUDE_ENTITLEMENT EFL123456789-1010 GROUP A   GROUP B user3 user4 INCLUDE Viewer GROUP B MAX 6 Viewer GROUP B EXCLUDE_ENTITLEMENT EFL987654321-1010 GROUP B   Using your example.  I've replaced Product with actual feature name, Editor (Standard) and Viewer (Basic) licenses.    INCLUDE Editor GROUP A:  All members in group A can check out the Editor license.  Everyone else cannot.    EXCLUDE_ENTITLEMENT EFL123456789-1010 GROUP A:  Assuming the EntitlementID given is for Editor license.  All members in group A cannot borrow the Editor license but all other users can.  This is why users in GROUP B and any other users can borrow the Editor license.    This contradict what you were expecting: 1. Only the usernames in the OPT file should be able to use\borrow licences. 2. Groups will control who can use a product, INCLUDEs allow to check-out but EXCLUDE_ENTITLEMENT should prevent them from borrowing those products.   The following is probably what you want: GROUP A user1 user2 GROUP B user3 user4 INCLUDE Editor GROUP A INCLUDE Viewer GROUP B MAX 6 Editor GROUP A MAX 6 Viewer GROUP B Here you defined your two groups.  Only members in GROUP A can check out the Editor license.  Only GROUP B can check out the Viewer license.  No one else can check out either licenses.  Also a maximum of 6 licenses can be checked out by either group at the same time.    INCLUDE_ENTITLEMENT EFL123456789-1010 GROUP A INCLUDE_ENTITLEMENT EFL987654321-1010 GROUP B   Assuming: EFL123456789-1010 = Editor EFL987654321-1010 = Viewer   Using the example above, only members from GROUP A can borrow the Editor license.  Only members from GROUP B can borrow the Viewer license.  A member of GROUP A cannot borrow a Viewer license.  Of course if you want a member from GROUP A to borrow either licenses, you must add it to both parameter.    Recap:  INCLUDE:  allows ONLY members in the group to check out a feature license. INCLUDE_ENTITLEMENT:  allows ONLY members in the group to borrow a feature license.    EXCLUDE:  do not allow members from the group to check out a feature licenses but everyone else can. EXCLUDE_ENTITLEMENT:  do not all members from the group to borrow a feature license but everyone else can.   I hope this clears up any confusion.  Reply to this message by replying to this email, or go to the message on GeoNet Start a new discussion in Admin Tools by email or at GeoNet Following Re: Borrowing licence does not honor license OPT file in these streams: Inbox This email was sent by GeoNet because you are a registered user. You may unsubscribe instantly from GeoNet, or adjust email frequency in your email preferences ... View more

Thanks Amnoy. If we look at my sample again, ------------------------------------------- GROUP A user1 user2 INCLUDE Product1 GROUP A MAX 6 Product1 GROUP A EXCLUDE_ENTITLEMENT GROUP A   GROUP B user3 user4 INCLUDE Product2 GROUP B MAX 6 Product2 GROUP B EXCLUDE_ENTITLEMENT GROUP B --------------------------------------------- Our expectation is that: 1. Only the usernames in the OPT file should be able to use\borrow licences. 2. Groups will control who can use a product, INCLUDEs allow to check-out but EXCLUDE_ENTITLEMENT should prevent them from borrowing those products. Now issue is that when user1\user2 borrows, he seem to be able to borrow products of group B as well, same for user3\4 they can borrow products of groupA. ... View more

Thanks Amnoy. We will test this out. One thing we also noticed is that even if a user is NOT in our OPT file, the borrowing mechanism still works. So we are not sure if it is a bug or an issue with out OPT file. Seems as long as our users have ArcGIS installation, they can borrow even if they're usernames are not in OPT file. We are using version 10.6 of the Licence Manager. Thanks. ... View more