Has anyone dealt with a scenario where when joinin...
# citrix-storefront
f
Has anyone dealt with a scenario where when joining a second storefront server the join says successful, propagation fails, and numerous services/features on the second node fail to get setup? E.g. on the second node the credential wallet service is missing and the features folder only has 8 items compared to the primary (or a working instance) that has 38 items? I've gone through a number of checks from the articles re: troubleshooting propagation, but it seems like the fundamental deployment of the necessary services is not addressed in those articles. This is CVAD/SF 2402CU3.
j
I have seen that, I believe there was some type of local group permissions that had to be adjusted. There was a citrix article that I followed that fixed it from the errors in the event log.
f
Thanks @Jeff Riechers I'll see if I can track that down.
c
It's NT SERVICE\CitrixConfigurationReplication and NT SERVICE\CitrixClusterService have to be part of local administrators group
f
Thanks John, those end up being present on both servers, but the deployment on the secondary node still ends up incomplete. I'm going to test on a black primary (with maybe a clean test site configured) to see if it's something about the imported site data that is causing problems.
c
are both storefront on the same datacenter? We had this issue due to unstability of network line between two datacenters.