Good morning. We're reviewing posts that have not been marked as answered. Apologies for the delay in updating this one.

The message received during installation usually means that it hasn't been possible to determine whether the Windows user entered as the Sage 200 services account is part of the Sage 200 Admins group, despite you visibly being able to see it is in Active Directory.

The cause is normally down to the Windows permissions of those service accounts where they don't have sufficient rights to interrogate Active Directory. However there could other possibilities where, for example, using the ADBrowser utility previously discussed need to be used.
 
With regards to this type of message, as Business Partners, you can contact the Sage 200 support team and we have an 'Installation Helper' tool we can use to assist you with finding the potential cause of the problem.

Many thanks.

Chris

Good morning. We're reviewing posts that have not been marked as answered. Apologies for the delay in updating this one.

The message received during installation usually means that it hasn't been possible to determine whether the Windows user entered as the Sage 200 services account is part of the Sage 200 Admins group, despite you visibly being able to see it is in Active Directory.

The cause is normally down to the Windows permissions of those service accounts where they don't have sufficient rights to interrogate Active Directory. However there could other possibilities where, for example, using the ADBrowser utility previously discussed need to be used.
 
With regards to this type of message, as Business Partners, you can contact the Sage 200 support team and we have an 'Installation Helper' tool we can use to assist you with finding the potential cause of the problem.

Many thanks.

Chris

Half the issue here is that no one can tell us exactly what checks are being done with the installer.

One fix I have come up with that works 90% of the time is switching the users primary group to be the sage admins group.

Would be nice to know how the look up is being done by the installer as I have had the issue where AD Browser sees the users and correctly reports the group but the sage installer refuses to continue as it reports the user not being in the correct group (which it is).

when we contact sage support we would get a response of "put user in the correct group" and then when pressing for how this installer lookup is done or what logic it uses we get a revert to you need to setup a supported environment.

I seem to think the fact the memberof attribute in Active Directory is a computed back-link attribute could be causing some issues but I can't be sure.

We deploy to pretty standard setups and we run into this issues intermittently but it's really frustrating to fix

Just my two cents