Deployment Problem

I’m trying to install the NetClient version onto the machine I’ll also be using as the ADNM. I got the computers catalogued via the Discovery Task and set up the Deployment Task using the IP numbers of the machines on the network.

Here’s the error I get:

06/03/09 10:37:17: rinstInstall begin
06/03/09 10:37:17: Init 50 60 C:\WINDOWS\TEMP\asw33.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw32.tmp 0
06/03/09 10:37:18: Store
06/03/09 10:37:18: Domains:
06/03/09 10:37:18: Init MMWG\C9
06/03/09 10:37:18: C9: GetAccount
06/03/09 10:37:18: C9: not found in domain list
06/03/09 10:37:18: C9: Finished with error
06/03/09 10:37:18: TerminateAll
06/03/09 10:37:18: rinstInstall end 87

Any idea what I might be missing here or if I made a mistake while cataloguing the computers?

Thanks!

On the Status field, the note it gives me reads

failed (Access is denied) – please check the Remote Install Log for details.

The Remote Install Log is what I copied & pasted above.

I have already disabled Simple File Sharing on this computer… anything else I should do?

06/03/09 10:37:18: Init MMWG\C9 06/03/09 10:37:18: C9: GetAccount 06/03/09 10:37:18: C9: not found in domain list 06/03/09 10:37:18: C9: Finished with error

this usually means that the account that you are using to install the client is not known on the client you try to install it on.

is that (MMWG\C9) an account that has administrator rights? if so then try to use the local administrator account from the machine

MMWG\C9 does not have administrator rights on the network. I was planning on monitoring the status of the other computers on the network from this workstation since the server itself is in a different room and I would not be able to monitor it as readily.

I would have to grant this workstation administrator rights before I’m able to make the ADNM function properly, yes?

no

the username that u filled in in your deployment task, in your case the MMWG\C9, should have administrator rights because it is installing software on a restricted machine (a normal workstation) so either u create a special account for installing avast or you grant C9 administrator rights… its not the workstation u have to grant the rights to but the useraccount that tries to install avast

but i think u are posing 2 different things now

  1. you cant install the avast netclient
  2. you want the ADNM console installed on a workstation

to install software you have to have administrator rights, this goes for the net client as wel as the adnm console…

once its installed the ADNM console should be able to be run by any user, it will detect the mirror server itself and u have to fill in the ADNM administrator account to get access

“not found in domain list” means that you did not specify credentials for this computer on the “Login Accounts” tab.

Ok, I think I might not have properly described the network, but here’s what we’re working with:

9 workstations running Windows XP connected to a Windows 2003 Small Business Server.

Each of the workstations have local admin, users can install programs on thier own computers without needing special permissions from the network admin.

The workstations, however, do not have admin rights across the network on other computers, so I think that might be part of the problem.

I am currently trying to set up ADNM on one of the 9 workstations. I was able to install the software, but it the deployment task fails when I try to push it onto other computers on the network. I have run the discovery task and identified the two workgroups involved (one workgroup is for the server itself, the other one is for the workstations), and checked the information from the discovery task with the ipconfig on each workstations and all the information checks out OK.

When looking at the properties for the workstation I’m trying to do the deployment task from, it has the correct computer name and the Domain & Computer Group are both identified as the workgroup where all the workstations are allocated.

When I check the Access Rights for the deployment task, the “Object Security Settings…” window shows me the following information:

“Object Name”: Installing C9 Package (this is the workstation name where I’ve created an installation package to deploy to the rest of the network).
Object type: Session
The window below has just one object labeled “Administrator”. The program verifies by the “Test Access” feature that it has all the Rights listed: Full Control, Read, Write, Delete, Execute.

So I guess that’s why I’m a bit confused as to why it won’t deploy, it seems that it verifies that it has full rights, but when I try to run the installation task it fails every time.

Here is the log for my most recent attempt to run the installation task

The workgroup for all the Windows XP workstations is named MMWG.
The workgroup for the Windows 2003 Small Business server is MMSERVER.
The workstations are named C1, C2, C3, C4, etc.
My workstation is C9. Avast! appears to assign my comptuer as MMWG\C9

And the Remote Install Log:

06/10/09 10:04:12: rinstInstall begin
06/10/09 10:04:12: Init 50 60 C:\WINDOWS\TEMP\asw13.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\asw12.tmp 0
06/10/09 10:04:13: Store
06/10/09 10:04:13: Domains: MMWG,
06/10/09 10:04:13: Init MMWG\C9
06/10/09 10:04:13: C9: GetAccount
06/10/09 10:04:13: C9: Queueing
06/10/09 10:04:13: Init MMWG\C5
06/10/09 10:04:13: C5: GetAccount
06/10/09 10:04:13: C5: Queueing
06/10/09 10:04:13: Init MMWG\C6
06/10/09 10:04:13: C6: GetAccount
06/10/09 10:04:13: C6: Queueing
06/10/09 10:04:13: Init MMDOMAIN\MMSERVER
06/10/09 10:04:13: MMSERVER: GetAccount
06/10/09 10:04:13: MMSERVER: not found in domain list
06/10/09 10:04:13: MMSERVER: Finished with error
06/10/09 10:04:13: Init MMWG\C2
06/10/09 10:04:13: C2: GetAccount
06/10/09 10:04:13: C2: Queueing
06/10/09 10:04:14: Init MMWG\C3
06/10/09 10:04:14: C3: GetAccount
06/10/09 10:04:14: C3: Queueing
06/10/09 10:04:14: Init MMWG\C7
06/10/09 10:04:14: C7: GetAccount
06/10/09 10:04:14: C7: Queueing
06/10/09 10:04:14: Init MMWG\C10
06/10/09 10:04:14: C10: GetAccount
06/10/09 10:04:14: C10: Queueing
06/10/09 10:04:14: Init MMWG\C4
06/10/09 10:04:14: C4: GetAccount
06/10/09 10:04:14: C4: Queueing
06/10/09 10:04:14: Init MMWG\C8
06/10/09 10:04:14: C8: GetAccount
06/10/09 10:04:14: C8: Queueing
06/10/09 10:04:14: StartThread
06/10/09 10:04:14: Loop
06/10/09 10:04:14: SpawnThreads
06/10/09 10:04:14: C9: StartSetup
06/10/09 10:04:14: C9: Connecting
06/10/09 10:04:14: C5: StartSetup
06/10/09 10:04:14: C5: Connecting
06/10/09 10:04:14: C6: StartSetup
06/10/09 10:04:14: C6: Connecting
06/10/09 10:04:14: C2: StartSetup
06/10/09 10:04:14: C2: Connecting
06/10/09 10:04:14: C3: StartSetup
06/10/09 10:04:14: C3: Connecting
06/10/09 10:04:14: C7: StartSetup
06/10/09 10:04:14: C7: Connecting
06/10/09 10:04:14: C10: StartSetup
06/10/09 10:04:14: C10: Connecting
06/10/09 10:04:14: C4: StartSetup
06/10/09 10:04:14: C4: Connecting
06/10/09 10:04:14: C8: StartSetup
06/10/09 10:04:14: C8: Connecting
06/10/09 10:04:22: C4: WNetAddConnection2 \C4\C$ MMWG\avast error 53 (The network path was not found)
06/10/09 10:04:25: C4: WNetAddConnection2 \C4\ADMIN$ MMWG\avast error 53 (The network path was not found)
06/10/09 10:04:25: C4: RemoveOnError
06/10/09 10:04:25: C4: Finished with error
06/10/09 10:04:39: C7: WNetAddConnection2 \C7\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:04:43: C8: WNetAddConnection2 \C8\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:04:46: C5: WNetAddConnection2 \C5\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:04:47: C9: WNetAddConnection2 \C9\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:00: C6: WNetAddConnection2 \C6\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C7: WNetAddConnection2 \C7\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C7: RemoveOnError
06/10/09 10:05:04: C7: Finished with error
06/10/09 10:05:04: C8: WNetAddConnection2 \C8\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C8: RemoveOnError
06/10/09 10:05:04: C8: Finished with error
06/10/09 10:05:04: C2: WNetAddConnection2 \C2\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C5: WNetAddConnection2 \C5\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C5: RemoveOnError
06/10/09 10:05:04: C5: Finished with error
06/10/09 10:05:04: C9: WNetAddConnection2 \C9\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C9: RemoveOnError
06/10/09 10:05:04: C9: Finished with error
06/10/09 10:05:04: C6: WNetAddConnection2 \C6\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C6: RemoveOnError
06/10/09 10:05:04: C6: Finished with error
06/10/09 10:05:04: C2: WNetAddConnection2 \C2\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:04: C2: RemoveOnError
06/10/09 10:05:04: C2: Finished with error
06/10/09 10:05:08: C10: WNetAddConnection2 \C10\C$ MMWG\avast error 1326 (Logon failure: unknown user name or bad password)
06/10/09 10:05:08: C10: WNetAddConnection2 \C10\ADMIN$ MMWG\avast error 1326 (Logon failure: unknown user name or bad password)
06/10/09 10:05:08: C10: RemoveOnError
06/10/09 10:05:08: C10: Finished with error
06/10/09 10:05:21: C3: WNetAddConnection2 \C3\C$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:21: C3: WNetAddConnection2 \C3\ADMIN$ MMWG\avast error 5 (Access is denied)
06/10/09 10:05:21: C3: RemoveOnError
06/10/09 10:05:21: C3: Finished with error
06/10/09 10:05:21: TerminateAll
06/10/09 10:05:21: rinstInstall end 0

Do I grant that workstation administrator rights via the computer catalog? It seems to allow me to apply access to the workgroup but not a single workstation. Do I need to create a seperate workgroup and move the ADNM machine into that workgroup and then grant the access rights there?

is the computer actually part of the domain?

suppose this setup:

domain: bozw
administrator account: bozwadmin
password: abcd

configure adnm deployment task like this:
create the package when u arrive at the login credentials fill this in:

domain: bozw
username: bozw\bozwadmin
password: abcd

i believe you also have to grant access rights (the next menu option i think from the installation package) to the container where u put the computer that u want to install on in…

I’ve been corresponding with the guy who set up our network and he is telling me that our computers are connected peer-to-peer.

Must it be set up as a Domain?

Will this work peer-to-peer?

Since it’s set up peer-to-peer, what sort of administrator access would I need, other than local admin?

how many computers do you work with??

if he means with peer-to-peer as in workgroup then i guess it still should work like this:

adnm can do an IP based discovery and see all your computers

the user you have put in the ADNM deployment task for installing the package HAS TO BE PRESENT on EVERY computer you want to install.
OR you have to use several user accounts (with admin rights) in the deployment package from every computer…

I have suggestion to create the installation file (*.msi) then do the manual installation.
for 9 workstation i think is not a big deal for doing the manual installation.

doing the push installation with difference workgroup must using the user name and password on the workstation with administrator right.

Where is your problem? You can add into installation task as many admins accounts as you need… (I use two)

I have 10 computers total: 1 Windows 2003 Small Business Server, and 9 Windows XP workstations.

I did the discovery task and got the IP for the computers. I also went to each workstation and ran ipconfig and confirmed the computer names and such, everything there was OK.

In the final part of your explanation, does that mean I have to create several different usernames, one for each of the computers? I had originally made a deployment task that was pointing the push installation at all the IP numbers I got from the Discovery task.

Definitely not. You have SBS domain, isn’t it?
I recommend create one administrative account (AvastSrv), member of Domain admins group, which you can use for deployment via installation task. And don’t remember, you have to make a hole into embedded XP firewall, if it is not switched off (not recommended). You have to make exception for RPC communication, and I made exception for aswServ.exe. I don’t know SBS to much, but I suppose Group Policy is available in SBS too.

I was able to get this running by using the MSI package installation…

Our network is set up peer-to-peer and for whatever reason, we simply could not get the deployment task to work on any computer other than my workstation which also happens to be the ADNM console. We did end up creating an admin user on each of the workstations and using that same username & password as the login account for all the various workstations.

I found the insturctions very minimal and insufficient. The system appears to be working properly now, but I have yet to get into much of the configuration settings. We’ll see how that goes :slight_smile:

Sorry I can’t understand, what does it means peer-to-peer when you have SBS domain… It means, that in SBS domain is only server and your workstation, and other XP stations are not member of this SBS domain? Why you cannot put XP stations into domain?

since you have SBS i suppose that your workstations are joined to the domain. What your guy tells about peer-to-peer is nice but that is a technique for how computers communicate with eachother, it doesnt say if it is domain based of workgroup based.

there for i have 2 screenshots attached which u can use to verify if your workstations are in a domain or not
you can see the logon to option when you push the OPTIONS button in the login screen (u will see in the screenshots)

domain.png represents a login screen from a computer that is joined to the domain here (sbbzwn_global in my case)
nodomain.png represents a login screen from a computer that is not joined to the domain

if indeed you are connected in a domain then you should be able to use the deployment with a domain administrator account (like Paba suggested) and make sure indeed that the firewall has its ports opened for pushing installations and connectivity.
In the ADNM manual are the ports you need to have opend on the client AND the ADNM server.

If your computers are not joined to the SBS domain then i would kick ur contacts *ss for leaving you with a crippled setup (and if you give me a plane ticket and a hotelroom or something ill be happy to come kick his *ss for you ;))