nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
- Goal Oriented AI
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Migrating Scheduler data to a new PC - missing most scheduled items

garylobermier

I have a customer that is using FTP Voyager and we’re looking at migrating it to a new machine and updated version.

They’re currently running FTP Voyager 15.2.0.19 and making extensive use of the Scheduler functionality. It’s running on a Windows 7 machine. We would like to move it to Windows 10 and the latest version of Voyager / Scheduler.

The problem I’m having is that I can’t seem to get all of the scheduler items to migrate. I found that most settings will migrate fine if I use the following process

On a new PC (Windows 10) install FTP Voyager 15 again
- Copy Settings files from C:\ProgramData
- Copy Settings files from %AppData%
- Copy scheduler settings files from Program Files - .sch and .sch.backup
After that, I can upgrade the install to the latest FTP Voyager and the settings all migrate to the newest version

The problem is that the Old PC shows many more jobs in the Scheduler. The new PC only shows some jobs, and it’s primarily outdated / obsolete schedules that they no longer need.

Is there another location where the scheduler might save it’s data?

I have been referencing this information for the migration - https://support.solarwinds.com/SuccessCenter/s/article/Back-up-and-restore-FTP-Voyager

My understanding is that they previously logged into the PC with an admin account, but have since switched to using a low privilege user account. Could the discrepancy in scheduler data come from different save locations for scheduler data, because of switching to the standard user account? I searched the PC for additional .sch files but didn’t find any (powershell query to recursively search the entire drive for *.sch didn’t find anything other than the standard file that only contained older data)