Hi
I am running a machine with Vista Business x64bit and I have SQL server installed (see attached image) since I also run Faronics Deep Freeze and Core Console
My question is does ADMN work on a Vista x64 machine? If so, which version do I use? (the bigger file or the smaller file?) I downloaded the ADNM that is 109mb, and when I try to install it it gives me two options to install and either one doesnât work. I have received my license.dat file from AWIL so now what?
Avast support was kind enough to tell me that I can install adnm on my machine but the ADNM manual states that it is NOT supported?
UPDATE - I tried installing the ADNM without MSDE (the smaller download) and it gives me an error that I have specified an invalid username and password on SKYNET server, do you want to continue?
I havenât installed ADNM on a Vista machine yet, and I donât think I ever will. I usually install it on an actual server OS.
I donât think it should be a problem though. I have successfully installed ADNM on Server 2008 x64 machines.
Looking at your screenshot, the server name should be SKYNET/âavast instance nameâ I believe. Provided that you have already installed SQL server, created an instance for avast, and have created your own SA username and password. A randomly generated one wonât work, because if you donât know the password, then you canât tell avast what it is so that it can use the databaseâŚ
Other than that, it should work fine. Let us know.
Scythe,
Thanks for the reply. I do have SQL server installed, but I donât know how to create an instance for avast or an SA username and password to give to ADNM when it asks for it. How do I do that?
I checked the SQL server settings by going to Start- Programs - MS SQL Server 2005 - Configuration Manager and noticed that the SQL Server Browser was set at Disabled. (see image) I started it and set it to Automatic. Could this be the problem while installing ADNM?
Scythe,
I am running vista business x64. MSDE is not supported according to the ADNM installation guide. It just says that MSDE isnât supported on x64bit systems but sql server should work just fine.
How do you create a new instance so I can call it avast and set up an SA account username and password so the ADNM install will point to it?
Thanks again,
Philip
I checked the two threads but didnât see information on how to create a new instance :-\
OK,
I went over the threads again you recommended and I did see instructions for creating a new instance. Iâm going to try to launch the SQL server installer and hopefully it will create a new database instance that I can call avast! and weâll see if that works. Unless installing SQL Management Studio will be even easier.
I think avast should make it a lot easier to set this up. I know ADNM is free but stillâŚ
Well I was able to launch the SQL express installer and add another server database called avast, make up an SA account and password, but going through the ADNM install, the program doesnât see it. Keeps giving me that âcanât find specified server, invalid username/passwordâ error. I have enabled all network protocols (TCP, etc) and itâs running, the browser is running so I donât know what the problem is. Sounds like the issue is with the ADNM program
I do not have the windows firewall enabled. Iâm running avast pro and if they have a firewall that is interfering with it that would be quite embarrassing for them I would think⌠:
Remember, for the instance name you have to put SERVERNAME/INSTANCENAME in order for it to work (use a forward slash, not a backslash).
I know itâs a pain in the rear to get setup, Iâm hoping with Avast 5, theyâll start incorporating SQL Express 2k5 or 2k8, and we wonât have to do all of the manual configuration to get it to work, like we have to do now.
If that doesnât work, Iâm pretty much stuck. Give us any more info that you can so we can help further.
besides the problems:
is there any particular reason you need to install ADNM (server software) on a vista client? Is it possible to that you format the that client and install XP or even beter Windows Server 2008 R2?
I said that before, I wouldnât install ADNM on a vista machine, nor XP for that matter, but if thatâs what fairlane has to work with and nothing else, then weâll try to help as best as we can.
fairlane, did you check to see if your sql server service is running and set to automatic? Any event logs on the machine that shows abnormal operation or errors?
Hopefully you donât have to give up on the ADNM, because once you get it running, itâs the beeâs knees. Especially if you have a bunch of machines that you want to control with it.
Woops!! :o I just looked at my server here and saw that I have âSERVER2\avastâ in my sql server instance. I told you it was a forward slash, but I think I may have been mistaken. Let me check one of my 2008 boxes⌠yep. I was wrong.
Use a Backslash!!! \\\\\\\\\\\\\\\\\\\\\
Sorry about that!
Let me know if that works (got my fingers crossed for ya)
Scythe,
I am out sick today, will be back on Thurs. Iâm pretty sure all required services are up and running (did you see the pics I uploaded?)
I will try again with a backslash when I get in on Thurs.
As to the OS, vista x64 bit is what Iâm running. I wonât go back to x32bit (whatâs the point?) and running a server OS is overkill. I only have around 50 pcâs on three floors to deal with in a small public library. Itâs not crucial, but I would like to be able to monitor the machines I have to see if and when any get infected, which is why Iâm trying to get ADNM to work. I wonder how it would fare if I upgraded to windows 7 Enterprise x64 and tried installing ADNM. hrmmmmmmmmmmmmmm ;D
Incidentally, a colleague of mine told me to install SQLExpress 2005 x64bit edition. He thinks that would fix it. At this point I feel it couldnât hurt, but who knows with SQL. I just donât want to mess up my faronics instances but again, if it gets ADNM to work, so be it.
highly probable is that the slash mix up is the sollution
but to go into your question abuot whats the point
that question i ask you to for the x64 machine
whats the point for that machine to be 64 bit? Most programmes (INCLUDING ADNM) dont harness the possibilities of 64bit yet since there is no need for that to harnes yet.
64bit is getting popular yes and it will soon take over the world⌠but not just yetâŚ
you dont have a server infrastructure for your network in the library where u possibly could put avast on, since this would centralise administration of the network itself too which makes your life easier (unless its setup to keep your job ;))?
if you run SQL 2005 32bit whats the whole point of the machine, since the database wont be able to use the 64bit functionality eitherâŚ
just some ideaâs
like i said the slash mix up from scythe is probably the sollution for your problem just put the \ instead of the /
Scythe,
Almost there!! OK your backslash worked flawlessly. It saw the server and continued to install the mirror files from avast, but when the setup was finished I launched the ADNM from the desktop but cannot log in? (see image) This is the default login that pops up, should this be changed? I hit the Detect Servers button and it found my machine SkyNET not the SkyNET\avast (or the Faronics for that matter). I tried to put in SkyNET\avast and skyNET/avast and use administrator and password and it gives me an error (not valid context etcâŚ) I put in sa for the username and the password I created for the avast instance but I still canât login? :-[
When I installed ADNM (adnm_no_msde.exe) I didnât uncheck the âManagement Serverâ. Is that right? I also created certificates and had them stored locally.
Now the problem is that youâre trying to login to the ADNM console using your database credentials. Do not mistake them to be the same. They are different.
I believe the default user and password for the ADNM console are admin/admin.
Once you get in, you can change that password, and/or create users and new passwords, if required.
Hope that worksâŚ
EDIT *
Just read the manual, and I was wrong again. Looks like:
The default username is Administrator, and the password is admin.
We strongly encourage all users to change the password as soon as possible after
logging on to the server, because leaving the password set to its default value
10 Chapter 2. Installation
directly compromises system security.