ADNM Error - OpenSCManager error 5

[anm]

Hello!

We have a problem deploying to Windows 7 Professional Clients. I can deploy to Windows XP Professional Clients without any Problems. At Windows 7 professional i get the following log:

rinstInstall begin
01/18/10 14:36:29:   Init 50 60 C:\Windows\TEMP\aswF757.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\Windows\TEMP\aswF756.tmp 0
01/18/10 14:36:30:   Store
01/18/10 14:36:30:   Domains: schulnetz,
01/18/10 14:36:30:   Init SCHULNETZ\KLASSE-1A
01/18/10 14:36:30:   KLASSE-1A: GetAccount
01/18/10 14:36:30:   KLASSE-1A: Queueing
01/18/10 14:36:30:   StartThread
01/18/10 14:36:30:   Loop
01/18/10 14:36:30:   SpawnThreads
01/18/10 14:36:30:   KLASSE-1A: StartSetup
01/18/10 14:36:30:   KLASSE-1A: Connecting
01/18/10 14:36:30:   KLASSE-1A: OpenSCManager error 5 (Zugriff verweigert)
01/18/10 14:36:30:   KLASSE-1A: OpenSCMImpersonated
01/18/10 14:36:30:   KLASSE-1A: LogonUser administrator schulnetz error 1385 (Anmeldung fehlgeschlagen: Der Benutzer besitzt nicht den benötigten Anmeldetyp auf diesem Computer)
01/18/10 14:36:30:   KLASSE-1A: RemoveOnError
01/18/10 14:36:30:   KLASSE-1A: CloseConnection
01/18/10 14:36:30:   KLASSE-1A: Finished with error
01/18/10 14:36:30:   TerminateAll
01/18/10 14:36:30:   rinstInstall end 0

Thanks for help!

Regards,

Andi

[anm]

So, I got an answer from the official support. They said, that I have not enough system rights. But I use the Domain-Admin-Account - so what system rights do I need??

[wpn]

logically i assume the computer is joined to the domain already
but i have to ask:  the computer is actually joined to the domain and working good with it?

for another way:
you can create an MSI package to deploy the avast clients too, if you cant get it to work then i would suggest installing the client with an MSI package (GPO deploy?) and dont put too much effort anymore in getting it remotely deployed since there should be a new ADNM version on the way with the avast 5 setup (but from what i heard i could take up to 6 months before that product is here, but thats hear say....)

i also see that you use the account  administrator... have you tried with a different account that also has installation rights?
You sure that you filled in the accounts username in the adnm as:   domain\username  if you used without the domain in it, avast will deploy using the standard computer account. If you have set your local administrator account password the same as the domain password then its logical that in XP the installation succeeds since the local admin account is enabled, where in Windows 7 this account is disabled by default, therefor possibly creating an error like you have

[anm]

logically i assume the computer is joined to the domain already
but i have to ask:  the computer is actually joined to the domain and working good with it?

Yes, the computer joined the domain and works perfectly with it!

for another way:
you can create an MSI package to deploy the avast clients too, if you cant get it to work then i would suggest installing the client with an MSI package (GPO deploy?) and dont put too much effort anymore in getting it remotely deployed since there should be a new ADNM version on the way with the avast 5 setup (but from what i heard i could take up to 6 months before that product is here, but thats hear say....)

I know that way. We already did it with the MSI package, this works fine. The easier method would be the push-installation....

i also see that you use the account  administrator... have you tried with a different account that also has installation rights?
You sure that you filled in the accounts username in the adnm as:   domain\username  if you used without the domain in it, avast will deploy using the standard computer account. If you have set your local administrator account password the same as the domain password then its logical that in XP the installation succeeds since the local admin account is enabled, where in Windows 7 this account is disabled by default, therefor possibly creating an error like you have

We are using the domain administrator in the way you said. All machines have different local administrator passwords than the domain administrator password is...


We did the installation by the MSI package now, but it would be great, if there is a solution for the push-installation.

Thanks.