SILA complements the built-in SIL but it seems the MSI (https://www.microsoft.com/en-us/download/details.aspx?id=49046) has an AD DNS domain/NetBIOS domain disjoint namespace bug.

Assume you had an NT4 domain: OLD_DOMAIN
Migrating to AD you created a proper DNS domain: mydomain.net
Now you have a disjoint namespace (NetBIOS vs. AD DNS).

Trying to install SILA on a remote server (not the SQL server itself) will lead to the following error:

Microsoft.AnalysisServices.OperationException: Errors in the metadata manager. The 'Administrators' role includes domain account that does not exist. The following domain user account is no longer valid for this role: 'mydomain\SERVERNAME$'.
at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError) at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate, XmlaWarningCollection warnings) at ...

It seems the developer(s) just split the leftmost part of the DNS domain name instead of properly handling/resolving NetBIOS vs. DNS name issues.

In the fictious example mydomain.net when creating an AD from scratch the assumption of MYDOMAIN for the NetBIOS name would be correct.