Skip navigation
All People > Chad_Kopplin > Chad Kopplin's Blog

We recently upgraded our SQL Server and Windows Server on our production server from Windows Server 2008R2 and SQL server 2008R2 to Windows Server 2016 and SQL 17.  I will qualify this by saying that I do not recommend waiting this long to perform these upgrades.   However, this was a very stable environment for us for years, given that I am the only person in our agency managing our GIS environment.  I just wanted to let the community know how this upgrade went.  The SQL upgrade was performed first, and it went seamlessly.  The test and cut over was very smooth.  I had to contact our personnel to change the SQL instance to the new database, and then there were some minor items working with our enterprise SQL person.  

Next came the OS upgrade, this was a little more involved, because we chose to upgrade our ArcGIS Enterprise software to 10.7.1 as well.  The challenge came from having to set up a new server so that we could keep our old prod server running at the same time and to add to the challenge, we have about 60 to 70 web services that we were serving as well.  So, I worked with Esri support to try a few things hoping to recreate the map services on the new server without creating them manually.  

Esri has a backup tool for the server, that would work great if I was shutting down the old server, updating the OS on a new server, and then restoring the server to the new server keeping the original server's name.  So, this was not an option.  I also tried the Enterprise builder option, because this was a new server; however, I ran into some configuration issues and ended up uninstalling and reinstalling some of the components.  

So, what worked the best for me was following the ArcGIS 10.7 deployment instructions

ArcGIS Enterprise 10.7.1 quick start guide—Quick Start Guides | ArcGIS Desktop 

Steps to get ArcGIS Server up and running—ArcGIS Server (Windows) Installation Guide | ArcGIS Enterprise 

I was able to use the saved configuration files from earlier deployments, and this worked the best for my setup.  

One of the projects that I am working on is developing a Nitrate Vulnerability model for Laramie County in SE Wyoming.  We are using a modified version of the EPA's DRASTIC model, which takes into account Land Use, in the model.  If anyone has every done this please let me know parameters that you used and any issues that you may have run into.

Over this past year at WY DEQ we have federated our portal and ArcGIS Server Manager, for the most part this has worked out very well, but we had a few issues to work through during the implementation.  With this post I want to let you know what we ran into with our implementation.  Since, I had never done it before, I was trusting the consultants analyst who performed the federation on their server.  We managed everything in server manager before the federation. After we federated, the users and roles  are overwritten with users/roles in portal.  I should have first taken a screen shot of my users in ArcGIS Server, then I could have quickly added them to portal first.  The second item that I ran into was my Secure connection for our map services needed to have the SSL certificate set up in IIS, in ArcGIS Server Manager, and in Portal.  Once these were all in place the system started to play nicely again.  We only noticed the certificate problems when one of our applications was trying to use a portal generate process.  I hope that this helps others with this issue.

As I help and am helped myself, it never ceases to amaze me how close the GIS community is.  I value you all as friends and colleagues, and you all are so willing to share your knowledge to spread the use of GIS.  When I first started using GIS in the early 90's I asked one of the graduate students that I was working with if he liked GIS, and all he would say is, "It is a tool that I can use."  I am passionate about using it, I try to figure out the questions, rather than let the questions get the best of me.  As a result I have made a carrier of it.  I have seen that people either love it or they hate it, there does not seem to be much of an in between.  I am proud to count myself among those that love it. 

Over the weekend I watched a documentary called The Last Heroes of D-Day, and in episode one they discuss flying the complete coast line of France taking photography from 30,000 feet.  They were able to see everything that the German military was doing to fortify the coast, and see where the best places to land would be.  Then they used stereo photography techniques to get a 3-D picture of the complete coast line in order to see how high cliffs were and looking a circles they could see that they were actually smoke stacks for industrial plants.  They were able to see the lay of the country side down to the tree and hedge row in order to plan movements and see swampy areas in the planning.  It was really well done by the BBC.  It was amazing the remote sensing that was done.

Yesterday I ran into an issue plotting well sites across the state.  When I zoomed to the full extent of the shapefile that I created from a txt file, I noticed many of the locations showing up in Asia, this is very common, these records were missing the negative in front of the Longitude values to place them in my state.  I thought no problem, I will add a new field and calculate it equal to a negative and the old field.  This worked beautifully just like I expected.  I re added the txt document to my map and still saw the sites in Asia.  When I identified the sites, what did I see, my new values were positives, because when I performed the calculation all of my correct records that all ready had a negative changed to a positive with my new negative that I added.  So, my daughter has been working on integers lately in math, and she will get a kick out of this when I tell her the I messed up my locations, because I did not pay attention to the signs.  I hope I gave you a good laugh or at least a chuckle.  Have a great day.

With the way our state is serving GIS data through our GEOHUB, we can load the metadata to the site in either FGDC or ISO formats.  I have been having a problem exporting the metadata for the map services that we needed to upload.  I have found where the metadata is stored on the server for the map service.  The best part of this is if you set the metadata to the FGDC standard then this is the stored version in the metadata location on the server.  the user can give their system administrator the following path (with key items changed to your server), and then copy the xml to a location of your choosing.  The user can then change the name to a name that makes sense to them.  Here is the path:




The cool thing is there is no need to export, at this point because this file is in the format that you choose all ready.  I hope this helps people who may be new to setting up metadata for a map service.