HAP Not picking up new domain controllers

[ctstone]

Good morning all,

 

We're trying to demote our old domain controller (Which I will call DC-OLD for this) however whenever we turn the server off, no one can access their folders, you get an error message at the top-left that says "Something went wrong".

 

Users can still log in and authenticate successfully so it must still be connecting to AD somehow.

The HAP Server has the new DC as its only DNS Address.

 

Is there something that needs to be changed in the configuration?

 

Thanks in advance for any help! We are stuck.

 

Charlie

[nickbro]

can you check the hapconfig.xml file and see what's set in there

[ctstone]

I cant see a Hapcongif.xml file? Where am I looking for this?

 

[nickbro]

App_Data/hapconfig.xml

[ctstone]

Thanks,

 

The UPN is just the main domain address. Not pointing to any specific DC.

[nickbro]

Ok, that's odd then, the system should use the UPN to find the domain controllers, is there any DNS issues on the server?

[hammy]

Hello,

 

Did you ever get this resolved? We are currently in the same situtation and have also come unstuck with this.

 

Thanks

[DBazeley95]

We are having the same issue, has anyone got any tips?

[nickbro]

1. HAP+ should not be installed on a domain controller, it should be on a member server
   
2. The UPN should be the full domain name (NOT a FQDN of a DC)
   
3. Use v10.5 for forms based logins
   
4. Use v10.6 + Azure AD App Proxy for SSO constrained Kerberos delegation (this is the recommended configuration)
   
5. If you move HAP+ to a new server, or the server name changes the encryption of the password will break, disable authentication on setup.aspx and re-enter the admin password and save (re apply the authentication on setup.aspx)
   
6. Consider moving from on premise file storage to using OneDrive/SharePoint (this was the main reason I stopped working on HAP+)
   

Edited April 4, 2022 by nickbro

[DBazeley95]

Hi Nick,

 

Thanks for your response.

 

1. The server is a member server

2. We are using the full domain name

3. We are using pre-10.6

4. Unfortunately not ready for this yet.

5. We have changed our Domain Controllers names but retained the IPs of the domain controllers. Would you recommend running the same setup.aspx fix you have suggested?

6. I'd love to move to SharePoint but that is in the pipeline.

[nickbro]

Try upgrading to v10.6 and see if that makes things work or not, take a backup so you can revert if needed.

 

Running setup.aspx again can see if there's some configuration issue, so might be worth resetting the password