How to rename halcust folders when updating versions
janis@burti.lv
1-30-17
Hello,

Some time ago I was informed that when updating server versions we should use halcust.newver or similar folders?
Can you give any examples on how this should work?
Kristaps Žogots
2-11-17
I will try to cover two cases: updating from Cloud Controller (applies only to partners who has a separate Cloud Controller) and updating from MyStandard page.

MyStandard:
At the current moment it's not possible to do halcust updates when updating version. You by default the server will keep the same halcust/halpatch for the new version. In coming weeks we will add option to upload halcust/halpatch just before update.

Cloud Controller:
1. In the server folder you need to create a folder newver.XXX, where XXX is the version code of the version you will update the server to. For example, newver.STDSVR_8.3-2017-01-08-0011
2. Put the new halcust and halpatch in the newly created folder.
3. In the remote cloud server record you need to set Halcust Update and Halpatch Update radio buttons to values "Use Updated"
4. Perform the server update function.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Hi Rasmus, We use Global Users as apposed to the Persons but No, the users don't have "Password never expires" ticked - none of our users do. So are you saying we should have this t...
13:19 29 Apr 2024
Hi there, We've noticed that the current version (8.5 2024-03-16) flickers and pauses every minute or so when installed in standalone mode - we have standalone installations for support purpos...
13:08 29 Apr 2024