Trying to find a reasonably streamlined way of deploying and maintaining (future updates to attributes, symbology, etc) a set of feature classes to multiple different ArcGIS deployments, and wondering if the following is possible:
Open somelayers_v1.lpk in ArcMap, leaving default C:\Users\<user>\Documents\ArcGIS\Default.gdb
Share as service, publish a feature service (using the layers from v1.lpk)
...two weeks later...
Open somelayers_v2.lpk in ArcMap, where the _ONLY_ difference from v1.lpk are some changes to the symbology of some of the layers, & leaving default C:\Users\<user>\Documents\ArcGIS\Default.gdb
Share as service, overwrite existing service from step 2 (using the layers from v2.lpk, which are the same as v1.lpk)
..
Desired outcome is initial feature class is used by new service, symbology is updated and all existing data is preserved.
