If I knew who wrote it, I would give them credit! I believe this pertains to all installations of SQL Server 2008 x64. We found that most ADNM installation issues are dealing with SQL and NOT with avast ADNM. You have to know the SQL instance name, and get that inserted correctly during the install. I haven’t had to support an installation yet with the new Administration Console (SBC) and 64 bit SQL Server 2008 yet. However, the SQL requirements haven’t changed. You have SQL free and SQL Pay 32 bit, and you have free SQL and Pay SQL 64 bit. This is the number 1 issue! J.R.
no offense meant but i have not ever read such a load of crap…
last december (2010) i installed ADNM on a Windows 2008 R2 server with a dedicated database server running Windows 2008 R2 and MS SQL 2008 R2.
I installed the database instance i wanted to use for Avast with mixed mode security since this is required for ADNM, ADNM doesnt handle SSPI (windows authentication).
I had not have to delete files
AMS tool runs perfectly the only thing is that even if you are logged in on the server using an account with administrative rights, you need to start AMS tool in elevated mode (runas administrator). This would have probably saved this guys time and effort…
and the guy explained btw that it was an installation of SQL so it was not loaded on the server yet
BUT if it had been already then you had to change things…
he makes the whole a confusing posting by talking about situations that are non-excistant and handled wrongly by him if they excisted.
