If you enable the log shipping it might take sometime to update the secondary server, depending upon the number of transactions piled up on the log. Best thing is to stop the log shipping as is, take fresh complete database backup from primary and then apply to secondary. Once this is finished you can...

Fair enough, in this case you can take help of log shipping (manual) to perform updates between central repository and client's end (laptop). Also replication will help you to update only required tables. If the client's database is READONLY then simply you could schedule a manual job to backup...