Apr 08, 2019 11:35 AM
A few other points to consider in addition to @steven_donovan1's comments about running the Config.ps1 script (and more) are:
EXEC dbo.GrantCurrentOperatorFullAccess
Apr 08, 2019 08:40 PM - edited May 06, 2019 06:40 PM
Craig,
Make sure you back up the FNMSCompliance, FNMSInventory, FNMSDataWarehouse databases from your production. Restore to your Dev SQL server.
Populate your server information in this script. Run the .\config.ps1 "config\FNMS Windows Authentication" forceupdateconfig script that came with your install files.
After that double check your Registry on the App server that has the batch processor. See if this has your Dev server information. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Reporter\CurrentVersion
Apr 08, 2019 12:15 PM
I have personally used the exact document @steven_donovan1 has attached in his reply to do just that. The same process can also be applied if you're migrating your FNMS Production system to a completely new environment / servers with different hostnames.
Apr 08, 2019 01:01 PM
A few other points to consider in addition to @steven_donovan1's comments about running the Config.ps1 script (and more) are:
EXEC dbo.GrantCurrentOperatorFullAccess
Apr 08, 2019 08:40 PM - edited May 06, 2019 06:40 PM
Apr 09, 2019 08:31 AM
I know this is a crazy idea, but wouldn't it be awesome to build an adapter that will be able to periodically copy all of the key tables from one environment to another, without overwriting the configuration data and beacons - kind of make it seemless. Just sayin.
Apr 22, 2019 09:26 AM
May 06, 2019 08:51 PM
May 10, 2019 12:00 PM
You Delete the beacons from the old Environment and load the new ones for that environment.
May 12, 2019 12:09 PM
May 12, 2019 05:53 PM
Which would be great if you only had one or two beacons. we have quite a few more than that. Honestly, cloning would only be realistic on a monthly basis. I am hoping for a more real time solution than that.
@jasonlu wrote:
regarding beacons, prior to cloning the prod db over the top, download all the beacon config (flxconfig) files for the uat environment. After cloning, open on the flxconfig config files and grab the beacon uids. Configure the beacons again using those uids, rather than generating new ones. j
May 13, 2019 04:40 PM