How To Move Report Runner Batch Settings To A New Machine

Assuming you have used the recommended storage settings for Report Runner Batch, it's very easy to move from one machine to another.

1. Run the full installer to install Report Runner Batch on the new machine. And be sure and run the current/latest full installer --- do NOT use an old one. The installer will show where the Jeff-Net data folder will be located. If your folders do not match where you installed it previously, please see addendum at bottom of page (in short, you will use our find/replace tool to edit all of your data files to change from old to new path).
2. After installation completes, copy the Report Runner Batch folder from the old Jeff-Net data folder (you may wish to delete the TEMP and/or LOGS folder before copying) to the newly installed Jeff-Net data folder. Allow it to replace all files that come up with copy warnings.
3. Start Report Runner Batch and click the Scheduler button on the main menu. You'll need to go through each schedule and re-save them using the Windows credentials on the new machine (even if the Windows ID/password is the same).
4. Your license key has a backup activation on it. You can activate the new machine with your same license key. Please note, you need to re-activate (manually apply) your licensing like you did originally. You must use your original/base reportrunner.key file. Don't try to re-use the copied key from the previous machine. Once you're happy with move, you can deactivate the license on the old machine to free up your backup license.
5. Open one of your batches that exports to files vs one that emails and test it/run it (file export test because you don't want to accidentally email something duplicate or wrong). Did it work? Are you missing any DSNs or database drivers? Does the output look correct? Does the output MATCH the output from the same batch on the previous machine?
6. Go into the Scheduler on the old machine and either delete the schedules one-by-one or edit them and turn them off. We recommend scheduling the LEAST important schedule first to test and make sure everything is working. After that, schedule 5-10 batches and disable 5-10 batches on the old machine, rinse-and-repeat. Tip... when re-saving your schedules, you have to re-set the start date (because it needs to be in the future)... you can click the word "Start" (because it's a button) and it will "guess" the next start date. It is documented here: https://docs.knownkeep.com/link/14#bkmrk-helpful-tips-on-star

---

Do You Need to (Re)Generate Your Company License Key (reportrunner.key)? Lost Your Original License Key?

You can now get your company license key (reportrunner.key) regenerated and emailed to you without having to contact us/Support (unless you have only a previously generated machine specific key -- if you do, you must contact Support to get it regenerated -- be sure and send a log file from the new machine). Just use the form below. As long as you maintain only one company record with us, your license key can be regenerated based on your email domain. For example if you work for "Big Company Inc" and your email address is [email protected] (and that's the email domain we've used to interact with ANYONE at your company previously), all you have to do is enter your email address in the form below, and it will generate and email you your key immediately. 

https://api.knownkeep.com/kkapi-forms/generate-license.php

---

Additional Important Setup Steps:

1. Don't forget to create any System DSNs your reports need on the new machine. And System DSNs use database drivers, so in some/most cases, you need to install database drivers, too (especially non-standard ones). 

2. Verify Task Scheduler permissions on new machine:

https://help.reportrunner.com/knowledgebase/article/what-permissions-are-needed-for-the-report-runner-batch-user-when-scheduling-a-task

https://help.reportrunner.com/knowledgebase/article/windows-task-scheduler-fails-with-error-code-2147943785

---

That's it! Let us know if you have any additional questions or concerns related to this process.

---

Addendum ::: If You Are Moving From/To a Different Jeff-Net Data Folder

When your old data file path does not match your new data file path, there are extra steps. These steps sometimes require support from Jeff-Net to complete, but you can do them yourself. Here are the steps to send to Support (if you want to edit yourself, skip 1-3):

1. Run the latest, FULL installer on the NEW machine
2. Copy your entire OLD Jeff-Net data folder to a SEPARATE location on the new machine (something like C:\Jeff-Net Old Report Runner Data). Note when you copy the old data, you do NOT need to copy the Temp files or Log files from that folder.
3. ZIP this "old data" folder and send it to us in a help desk ticket. Also send us a log file for the new machine. We will update your old data/settings, re-zip it, and send it back to you with replacement/copy instructions.

In your Jeff-Net data folder, there are various text-based files that have the old path stored. We will be doing a mass find and replace using our Find/Replace utility in the Tools menu of Report Runner Batch. By default this utility only allows you to change the existing Batch data. If you double click in the path area at the top, it will let you paste a new path. You will replace that path with the C:\Jeff-Net Old XP Data directory. Then set ALL files to be found and then replaced. Enter the old path "c:\documents and settings\all users\documents\jeff-net" and replace with "c:\users\public\public documents\jeff-net". That's what Support would do via the help desk ticket. Note, we are backing up (and modifying) the entire Jeff-Net data folder, not only the Report Runner Batch folder within Jeff-Net.

After the Find/Replace is complete, you simply copy the old (now updated) directory to the new directory, and you're ready to go on the new machine.