I’m so frustrated with this whole process. We bought a 5-user SBS suite to run on Windows SBS2008 and workstations. My first attempt at the install failed because of a problem I had with my SQLServer configuration, so I uninstalled and rebooted, then ran another install, following as many tips as I could find on this forum. I now have the same problem so many others are having - I get the “actively refused” error message when trying to launch ADNM at the server even though the Tools SQL Check says everything is OK. I also don’t see any servers when I click the Detect Servers button. What am I doing wrong?
After reading more threads by other people, I caught something that wasn’t clear before. There were several mentions of the license file not copying correctly. I bought my license online and received it via email attachment, where it was named License.avastlic instead of license.dat. During install, the program found the location where I downloaded it and it showed which products I was licensed for and how long, so I assumed it was a good file.
The kicker is that the license.avastlic file gets copied to the production installation folder as-is. I had to rename it to license.dat and then restart services. Now things are working!
Is it just me, or are there a lot of steps missing from the installation guide, licensing email (and the download site, since the file was the same there)?
Now on to figuring out how to deploy the software to server and workstations… this ought to be good.
The kicker is that the license.avastlic file gets copied to the production installation folder as-is. I had to rename it to license.dat and then restart services. Now things are working!Is it just me, or are there a lot of steps missing from the installation guide, licensing email (and the download site, since the file was the same there)?
I believe the new license file naming is due to the new release of version 5 for the home and pro products. The problem is that the netclients are still on 4.8 until late summer / early fall. I guess they don’t take that into account when they issue licenses for the SBS Suite product.
I’m assuming that the ADNM manual will be updated with it’s new release, and then it should use the new licensing model as well, so these problems will be addressed at that time.
I guess we’ll just have to fuddle with it until they get things straight. I had to do the same thing (rename the license file) and also had to copy the file manually due to SBS 2008 preventing the program access to the folder (there’s a UAC or file permission problem that should be addressed).
Just glad you got it installed, and hope you have better luck once everything is up and running. I’ll agree, that it’s a bit hard to start with, but once it’s installed / deployed, it works pretty darn well.