Because of a certain set of requirements we have a Windows Server 2008 R2 environment without Domain Controllers in which the MS-SQL 2008 R2 server resides on a different machine from the machine that BE2012 will be running on. Both machines are heavily secured but I've already installed multiple other applications that are successfully using this SQL server for their access.
When I try to install BE2012 and I get to the Choose SQL Server step I get the "Cannot connect to Microsoft SQL Server NAME. On the remote SQL Server." Which the debugging about the remote connections part is not the issue as I've verified it from multiple other application installations. I've also ensured Named Pipes and the Browser service are enabled as well. So I'm pretty sure my issue is the "The user who is currently logged on to this system is a member of the Administrators group on the SQL Server NAME." The account I'm using exists on both systems, however as I stated they are not domain accounts so they're not truly the same account.
I know the BEUTILITY and installation process actually attempt to move files via system access which requires the account being used to be a domain admin account which I do not have. Is there some way around this? Could I do a local installation and then move the DB to the remote system manually? The issue I still see happening is the lack of identical accounts across both systems in order to do this. If BE just used stored user credentials this would be so much easier instead of the direct account login requirements.