This message was deleted.
# citrix-wems
Slackbot
10/04/2023, 8:48 PMThis message was deleted.
h
Hal Lange
10/04/2023, 8:48 PMyes.
a
Andrew Gresbach
10/04/2023, 8:51 PMthanks! whats the simplest way to reconfigure the agents to look at the new server? was hoping it would be a simple registry key but not seeing it
Andrew Gresbach
10/04/2023, 8:52 PMalso, any issue temporarily having 2 wem servers pointed to the same db ? i assumed not
r
Rob Zylowski
10/04/2023, 8:53 PMdid you create an spn originally
a
Andrew Gresbach
10/04/2023, 8:53 PMunfortunately no, we just installed the agent w/ a trigger for the server name
r
Rob Zylowski
10/04/2023, 8:54 PMok then yes i think
h
Hal Lange
10/04/2023, 8:56 PMif using a service account, then the SPN would follow that anyways.
if not using a service account, and just doing the VUEM account for SQL, and did not create an SPN you are fine.
Hal Lange
10/04/2023, 8:56 PMthere is a reg key on the WEM client that will need to be updated
Copy code
HKLM\Software\Policies\Norskale\Agent Host\BrokerSvcNamea
Andrew Gresbach
10/04/2023, 8:57 PMahh thats right! i always forget the Norskale name! so just update that, restart the service and good i'm thinking?
h
Hal Lange
10/04/2023, 8:58 PMthat would work. I would suggest a restart as well
a
Andrew Gresbach
10/04/2023, 8:58 PMand yup we're just using the VUEM account to connect to the db i'm pretty sure
Andrew Gresbach
10/04/2023, 8:58 PMcool yup i'll definitely do that if i can
Andrew Gresbach
10/04/2023, 8:58 PMthanks for the quick help guys!
Andrew Gresbach
10/05/2023, 6:14 PMdo you guys know if this is something i could safely do during business hours for the initial server setup and connection to the db (while the other server is still running and connected to the same DB)? i would wait until off hours to make the registry change on the agents
h
Hal Lange
10/05/2023, 7:21 PMYou can do all the above safely during business hours... it is the same DB... so it is the same configs
Hal Lange
10/05/2023, 7:22 PMchange the reg key and reboot after hours
a
Andrew Gresbach
10/05/2023, 7:26 PMok perfect thank you! i just was not certain if the db would have any issue w/ 2 management servers connected to it at once.
h
Hal Lange
10/05/2023, 7:42 PMi have 30+ mgmt servers connected to same DB
a
Andrew Gresbach
10/05/2023, 7:42 PMok yup my 2 will be fine i'm sure then š thanks for talking me off the ledge!
Andrew Gresbach
10/05/2023, 8:15 PMthat worked like a charm after i updated the reg key and ran the script called out here (basically just restarts the service and clears the local cache db.....i was getting the question mark w/out it.). i'm sure a reboot would have taken care of it too but thought this might expedite things if i cant https://support.citrix.com/article/CTX229024/synchronization-state-for-wem-agents-shows-question-mark-on-wem-administration-console
h
Hal Lange
10/05/2023, 8:27 PMit will show a question mark because it is still technically connected to the other WEM server. It does not cross pollinate to be able to administer from either. you can only administer the client from the server it has actually connected to
Hal Lange
10/05/2023, 8:28 PMso you can change the reg key and reboot the boxes at their normal time... at that point they would connect to the new server. if you restart the service with users on, you can run the risk of killing their client
a
Andrew Gresbach
10/05/2023, 8:42 PMok good to know! for what its worth, on my box when i updated the key, restarted the service my client did say it was connected to the new server..(but w/ the question mark) but i get what you're saying. we have a scheduled reboot on the weekends so ill just update that key prior to that and let the reboot do the rest
Andrew Gresbach
10/06/2023, 1:09 AMso i found that if i update the reg key, reboot the console shows the last connection time that updates every few min but it sticks w/ the question mark status unless i refresh the cache on the wem agent. even after i do that , if i reboot again it wont go green until i do the cache command again. it doesn't do that on the agents w/ the old server. "C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\AgentCacheUtility.exe" -refreshcache
n
Nick Panaccio
10/06/2023, 12:17 PMHow long did you wait for it to go green, and what do you have set for the agent cache and SQL settings refresh delays (Advanced Settings\Service Options)? If you waited longer than those timeouts, perhaps you should give @James Kindonās WEM startup script a try: https://github.com/JamesKindon/Citrix/blob/master/Citrix%20WEM%20Startup%20Scripts/RestartWEMServices.ps1
Nick Panaccio
10/06/2023, 12:17 PMI used this at my last place and it worked flawlessly for us, deployed as a startup script via GPO.
a
Andrew Gresbach
10/06/2023, 1:09 PMok yup i was just being impatient! 15 min is what we have the cache refresh to hit at so that seems to work. for some reason i could have sworn w/ more recent versions after a reboot it would sync right away. i used to use that script but found i didnt need to anymore after a certain version