I undestand that with 2025(.1) some things have changed with licensing, users, etc. We’re about to do a clean system wipe and install 2025.1. I want to be absolutely sure that I will be able to import my many, many user bin nodes in Batch – and I’m not going to be doing some text editing stuff someone else had to.
What is the best workflow to make this as painless as possible? I have half an hour before we wipe.
Thanks!
My safe solution was to just pull out all of my user bin setups into a batch in 2024, archive the batch, restore the batch on 2025, and put it back into the user bin on 2025. I think that seems safe.
I’m guessing you can also navigate to the 2024 User Bin location, just save that or zip that up, and then manually drop it into the 2025 User Bin location to make it even easier, but that’s not something I did so I can’t really vouch for it. The stakes are high if you’re talking about wiping 2024 before 2025 is live.
I live in the cloud where we normally have both Flame versions active on separate VM’s and can pull from one onto the other without any high stakes, so I don’t think I did too much thinking when we migrated.
Thanks, Jeff.
I would build my new system on a new drive and keep the old one in the machine. Just make sure the new one is at the top of the boot order. This way you still have everything from your old system saved on the machine. I never burn my old systems. I still have a centOS drive in one slot. Drives are pretty cheap these days. I use Seagate Ironwolf 1tb’s. And remember: you may need to rebuild your hot keys. I always save screen shots of the hotkey menu sorted by User.
Central S+W Project Server for the win here again.
You guys live in the same town. Why don’t you go set him up?
So in 2024.1.1 I went to my Batch user bin, saved the bin .xml file, and in 2025.1, I go to the Batch user bin, load – and it does not recognize the .xml file as a loadable file. Wtf.
Solved. I’d backed up my 2024 user folder and loaded the batch/pref/_user file and all is fine.