Latest Contributions by JeffTimm

Get Creator Users per group · ‎04-16-2020

I am struggling with getting all of the creators in a certain group in my Enterprise portal environment. I am using Enterprise Notebook. group = gis.groups.get("6bde3136acbb48bcba1edc2eca61eac6") response = group.get_members() for user in response['users'] : print(user) will list all the users in specified group, but how do I limit it further to only Creators?

‎04-16-2020

Forgive my ignorance but where in the world would print(os.path.abspath(fname)) be if I ran this on and Enterprise Notebook? I ran this with no errors and it said: =================== The CSV file can be found here: /arcgis/AGOL_Group_Membership20200416.csv =================== But I cannot find this file

‎02-28-2020

We had a Chef rep reach out to us and we had a webinar. Currently we have an on site linux server for Chef Manage with over 20 nodes bootstrapped. Their new business model from my understanding from that meeting is this. Their hosted environment with less than 20 nodes would remain free but more that 20 would cost per node. We can keep our current on prem chef server but would not be able to update without licensing cost. This is not an option for us as governance requires updated software to mitigate risks. The multiple Admin issue is a non issue because in our original setup we used the same Admin between Portal and servers. I am sure I can figure out the new json if I have access to the right examples. My question is will there be an issue running the correct powershell-dsc scripts to upgrade after having used chef up to this point? Would I be better off doing a backup of the Enterprise then uninstalling and then reinstalling using Powershell or will I be ok just upgrading as is.

‎02-27-2020

Chef is changing their business model. We can no longer have an on site Chef Manage solution if we want it supported without a significant cost. We have been deploying our multi server environments with Chef since 10.6. My question is can I switch to using Powershell-dsc for upgrades or are there steps I need to do to migrate deployment solutions?

‎01-06-2020

Right, that is what I am doing but with this process I get the above error. It is causing the ports all to be used. If I restart the server I then can run the webgisdr again. This error is causing all network shares (even local folders shared as a network share) to be unreachable. Is there a setting somewhere to prevent this?

‎01-02-2020

I have found that unpacking a zipped backup file off of the network takes forever and sometimes times out. How I got around that is I have shared a file off of my secondary portal server. \\gispt2\SHARED. This is also known as D:\SHARED. The webgisdr tool does not seem to allow storage on a local drive thus the trickory. The error is happening on the restore.

‎01-02-2020

Here is a new error for the Webgisdr tool. In my process the original portal creates the backup then a script moves this backup file to the secondary portal where the restore process is then ran. This morning I came in and my server could not reach any file shares. I discovered why (attached screenshot) and restarted the server restoring file share access. Has anyone seen this before?

‎11-14-2019

That worked! Thanks

‎11-12-2019

the api has been updated and cloning is much easier. It is that simple. One caveat, I am using enterprise notebook so I did not have to enter source information.

‎11-12-2019

I was hoping to demo this on GIS day! Tomorrow

‎11-12-2019

I am going through the example notebook Content Management: Check for broken URLs and it works fine other than the email output. The assembly code says this: # Asemble the message and return it return f"Webmap ID '{webmap_item.id}' contains unreachable URLs."\ f"You can view the webmap here: {webmap_item.homepage}\n"\ f"\n"\ f"Reachable Layers\n"\ f"----------------->\n"\ f"{reachable_str}\n"\ f"\n"\ f"Unreachable Layers\n"\ f"------------------->\n"\ f"{unreachable_str}" but the email sent has this in the email body: Reachable Layers -----------------> * World_Hillshade_3805 Unreachable Layers -------------------> * plsstest_655 * CityCountyState_5586 Where is the first part and why does it not include that in the email? Any ideas?

‎10-15-2019

To verify if I recreate the registered data connection with the new standardized name I should be able to delete the old registered connection without affecting the rest services.

‎10-11-2019

Is there a way to rename registered data connections to arcgis server? I need to standardize between environments and currently they are all over the place. If I cannot rename what ramifications are there to deleting and recreating the same connection with a standard naming convention?

‎10-01-2019

Will this referenced bug be extended to 10.7 to 10.7.1?

‎09-24-2019

Why is that the first time anyone has said that to me? I will give this a shot. As far as the task scheduler, I will try that again as well. I had other issues with it that were unrelated to this. I will let you know how this turns out.

Online Status	Online
Date Last Visited	4 hours ago

My Ideas

Latest Contributions by JeffTimm

Get Creator Users per group

Re: A quick overview of group membership in your AGOL organization

Re: Deployment software change - Chef to Powershell-dsc

Deployment software change - Chef to Powershell-dsc

Re: Webgisdr failed. Cannot connect to share.

Re: Webgisdr failed. Cannot connect to share.

Webgisdr failed. Cannot connect to share.

Re: notebook example does not work

Re: Error when cloning items from one portal to another

Re: notebook example does not work

notebook example does not work

Re: Rename registered data connections

Rename registered data connections

Re: ArcGIS Enterprise Portal Upgrade Error 10.7.1

Re: WebGISDR failing for Full recovery

How to search for field name in feature services u...

Re: The kernel appears to have died. It will resta...

Allow Feature service edits in Read Only mode

Re: ArcGIS Enterprise Portal Upgrade Error 10.7.1

Re: ArcGIS Enterprise Portal Upgrade Error 10.7.1