Mikrotik massively add static routes

From the looks of things, you will need to make changes to both VPNs.

On the Home <--> Work VPN, you will need to make sure that all your remote networks are routeable from your home worker VPN clients.

There are two options for this:

1. Send specific routes for all of your remote networks as part of the VPN client configuration. This could be quite configuration intensive if your client/remote server VPNs are spread across lots of different address blocks.

2. Configure your home worker VPN clients to use their tunnel interface as their default route. This is a lot simpler from a configuration management point of view, but it will force all traffic from the VPN clients through the office, including their browsing traffic, which may not be desirable.

Could you be a little more specific when you say your home users use hardware VPNs? Do you provide a VPN appliance that they plug into their home broadband, and then plug their laptops in behind the VPN end point? If that's the case, then the above probably won't be needed, as the home VPN client's default route will point back to the office.

On the Work <--> Remote Server|Client Site VPNs, you will need to advertise routes for all of your 'Home VPN' address ranges. (from your example above, 192.168.1.0/24). How do you currently exchange routes with your clients and remote service sites?

This may not be possible with windows

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx

Quote: For locally attached subnet routes, the gateway address is the IP address assigned to the interface that is attached to the subnet.