Yes, the temporary use of a license would be the normal approach.

There is also a somewhat involved backup batch file that can be used with the Windows Task Scheduler. If you are familiar with configuring such, and you are using Timeslips 2017 and higher, you should refer to Knowledgebase article 93565.

Thanks, Roger. I'd almost given up when nobody had commented after 2 weeks. Perhaps this isn't a common issue. 

I actually found out that running TS as Administrator allowed me to successfully set up Scheduled Backups and that I didn't need to do the setup on the server. I'd also seen the backup batch file but wanted to see if there was a way to do it within TS first. 

Thanks again for the reply! 

Thanks, Roger. I'd almost given up when nobody had commented after 2 weeks. Perhaps this isn't a common issue. 

I actually found out that running TS as Administrator allowed me to successfully set up Scheduled Backups and that I didn't need to do the setup on the server. I'd also seen the backup batch file but wanted to see if there was a way to do it within TS first. 

Thanks again for the reply! 

I'm glad you were successful.  We do however recommend only doing a scheduled backup from the 'server', since obviously that machine will be powered on at the time. The client may not be and you may miss a critical backup point.

The task scheduler method may be even more reliable when run on the server.

Ah, good point. I did set it up on a workstation that is rarely shut down as its user remotes to it daily. Still, I'll take your suggestion and redo the sched backup setup on the server. 

I did see a post comment where someone from TS (or a TS consultant, can't tell) recommended against using the batch file method. 

www.sagecity.com/.../remove_exclusive_access_requirement_from_timeslips_2017_backup_utility

Thanks again for the info. Much appreciated.