Plant SCADA 2023 R2: Timely Deploy of a previous version ?

Even without deployment manager, I will sometimes put two runnable versions of the project on the same installation(like a _Test suffix on the project) and clean up the new copy when I am done testing.  Roll back is just a quick project setup run.  Yes, it does require signing into each computer with a remote operating program, but all of the networking is already in place if Citect is working properly. I'm sure there are ways to switch the .ini files and restart from the station you are working from. ProjectGet() and ProjectSet() could give you a way of doing it by cicode.  I know this is not in Deployment manager.  I've had at least a half dozen Deployment installations, and we have always had to go back to the manual method due to problems.

Even without deployment manager, I will sometimes put two runnable versions of the project on the same installation(like a _Test suffix on the project) and clean up the new copy when I am done testing.  Roll back is just a quick project setup run.  Yes, it does require signing into each computer with a remote operating program, but all of the networking is already in place if Citect is working properly. I'm sure there are ways to switch the .ini files and restart from the station you are working from. ProjectGet() and ProjectSet() could give you a way of doing it by cicode.  I know this is not in Deployment manager.  I've had at least a half dozen Deployment installations, and we have always had to go back to the manual method due to problems.