I know the autoupdate process works for patches and other custom files within the same version, but I’m wondering how I can get the 2023.1 client to upgrade itself to the 2025.2 client - since it’s a different deployment path.
I see some posts about editing the old version’s sysconfig file, but no details/specifics. Can anyone shed some light on this to save me some time?
Hi Mike , the delimma you are going to have is any 2023 artifacts if you tried to do the the update to the later version.
With that being said, and I would have to test, you would need to change your deployment directory location and the (off the top of my head) customs directory, and if the app server is a different Url then you would have to change that.
You should be able to change that on the app servers client directory and hopefully it will pull down the new app server Url and then do the install. Going totally of my head here
I can test this in my lab if you want.
understood - I figured I could use the ‘flush’ sysconfig params to cause the directory to be emptied. But I can’t control the directory for install…
And I wasnt’ sure if I could simply change the deployment folder in the 11.2 sysconfig to the 12.1 share/folder and get it to completely reinstall as 12.1
I played with it ia bit this last week, but couldn’t get it to do it properly. No need to worry yourself. It’ll be cleaner if we do the client install properly anyway.
Thanks!
For future answer seeker - nothing I can find works. I tried combinations of sysconfig entries and locations, but it always failed. We ended up doing an MS Intune package delivery.