(imported topic written by mholder91)
When we first deployed our BES environment, it was configured with a remote database. A couple years later, the database was migrated to the local BES server. I wasn’t really involved with either of these procedures, but the migration was successful and everything has been functioning fine for years. However, there is one small quirk – only the MANUAL upgrade fixlets are relevant for our BES server. In other words, there is something still configured for a remote database that is causing these manual fixlets to be relevant even though our database is indeed local. I seem to recall that this was true for the last couple of upgrades, so it’s not isolated to just this last 8.1.617.0 upgrade. I believe we just followed the manual instructions for upgrading the last couple of times we upgraded even though the database is local and I’m sure I can probably stumble through the manual upgrade process again, but I’d love to make it easy by just running the upgrade fixlets. Is there a checklist of items I can review for how things should be configured for a local database as opposed to a remote database? After briefly reviewing the relevance for the manual upgrade fixlet, I believe the fixlets are relevant because the FillDB and GatherDB services are NOT set up to use the localsystem account. Can I just change these services back to running under the local system account or are there other things that I need to check? Any guidance is much appreciated. Thanks.