To simplify, hopefully:
I use an Operating System disk. Operating system and programs are installed here.
A separate disk stores Projects (active projects Iām working on and ususally the last two I already finished (in case I need to review them for clients, to have them quickly available)).
A third disk with assets (object libraries, textures, ā¦)
So, Iād have (Iām on Linux but that works the same in Windows):
C: for system and software
D: for assets (object libraries, textures, add-ons, ā¦)
E: for projects (the ones Iām working on and the las ones done to have them handy if clients need adjustments or further work on them).
Then a NAS for backup of everything.
To have many workstations working the same, I syncthing contents of D: and E: (in this simplified case, whole disks, letās say). When I prompt the syncthing, it syncs the content on different machines, so when I change from one to the next, to me itās as if I was working on the same machine, as it were.
Now, a crucial part of this to me is to also sync the contents of the user preferences of the software I use. So, when I open Blender on either machine, Iād have the same Blender, with the same settings, and I can go and open a scene as if I was on the other workstation, seamlessly.
For this, I need to sync Blenderās configuration folders and files. And for that to work, it helps if everything is in the same place, and with the same name. So all configs will look for the same things and find it in the same places. Hence the strict drive and contents set-up for all machines.
Backups are made similarly to a NAS, but that is out of the scope of this monumental block of text thatās testing your patience now.
I found working from a NAS adds a slight lag in fetching assets, so I replicated them (the assets) on local machines and never looked back. Some less used ones are on the NAS and brought locally on either machine if needed, in the folders of the Assets disk. Then theyāll get synced in the other machine and done. You can also delete-sync if you wish, but Iāll live it to you so I wonāt get sued if something goes wrong.
Itās perfectly fine to work from a NAS, though, preferably with fast drives, with nvme caches on the NAS, and fast network and good cables.
In Windows, the config of your Blender is in %USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\ (if Iām not mistaken, you can look for it). That folder sync is the one that will present the āsameā Blender to you in either machine.
If that is an issue to sync because of Windows restrictions or whatever other reason, Iād download Blenderās build, extract it to a folder in C:\ (letās say C:\Programs\Blender) and manually create a config folder (called āconfigā) in the extracted Blender folder (before launching Blender, preferably). It would look like this:
C:\Programs\Blender_extracted_folder\4.2\config ā in this case I assumed weāre doing it with a 4.2 version of Blender, but itād be the same with the folder name and number that the version you use sets.
With that folder, when launching Blender (you may want to make a shortcut for that) all configs will be stored in that config folder and NOT in the Windows user and roaming folders.
If all of this is not what you really need, and only sporadically you switch from one machine to the other, you can still use the same structure, and just use a pen drive or external drive to move things around. Or install all in the external drive, using the config folder mentioned, and it should work as well.
In any case, all we did here is have a sort of duplicate of our workstation to more or less seamlessly work on different machines.
Work is done in the local machine, though. So if you have different rendering GPUās you may want to just copy manually the config folder of Blender, WITHOUT syncing it, and then change the rendering device in Blender settings.
Later today Iāll take a look at this babbling in case I missed something. Sorry if itās not of much help. Ask away if Iām way off-course for your needs.
I do understand this things can be stressful or confusing and it was for me before I figured it out. Now Iām just stressed if Iām doing two jobs at a time. But, hey, thatās better anyway!
The goal is to be in the exact same state of things when working on either workstation. And let the systems sync everything for you. You can work on either one as you please or need.
Have a good one!
First Edit: To work on one machine and render in another Iād just let it sync, remote desktop to the other and hit render, or just do it manually, without the Remote Desktop program (the best approach would depend on your hardware setup, physical workspace, and other needs). I donāt recommend using Remote Desktop to work on intense GPU/Graphics programs using simple remote desktop setups. It can be done, properly, but itās expensive and a tad complex, and hardly worth the trouble if weāre talking about few machines that are also physically close to each other.
You can try RDP in Windows though, and see if it works for you.
Second Edit:
In your case, if all drives and folder were setup the same, you wouldnāt need to pack anything, since the copying of the scenes would be seamless because in the other machine all things would be in the same place locally. If you use a NAS, then as long as the mapping of the folders or drives on the NAS are set equally on either machine, scenes would find everything were it should be. It also may help if user names are the same in both machineās Operating System, to avoid possible configuration conflicts down the line.