Client Licenses for SBS Suite Trial

Hi, I noticed that the SBS installation installs the server client with Exchange, ISA, and other plugins, and automatically accounts for a trial license. Great. What about the workstations? I have around 15 that I want on the client for the SBS suite, presumably the Avast 4 Professional version.

What do I do?

So I found the answer to my own question. I’ve installed ADNM as per another thread:

http://forum.avast.com/index.php?topic=25184.0

Having read that thread, I decided I wanted to be able to manage all of the clients centrally in ADNM.

Did really well so far. I installed ADNM & AMS, enabled the SA account for SQL Server 2005 (this is Small Business Server 2003 Premium with R2), and created an installation package as well as a deployment task that points to a single Windows XP machine for testing. All good there.

The problem is I’m getting an Access Denied (0x00000005) error when I run the deployment task. Session Status says to check the Remote Install log. Where is this log? I looked at the “events” section after running the task and then refreshing the console.

At the server, I have the “Login Accounts” item configured as follows, where is a member of the Domain Administrators group.
Domain/Workgroup: domain.local
Account: domain<username>
Password:

On the target machine, I have the Windows XP Firewall turned on, with the “Don’t allow exceptions” box unchecked. File and Printer Sharing is configured as an exception, as per section 5.0 in the Administrator’s Guide.

Any ideas?

Strike 1:

I turned on logging of dropped packets on the target machine’s XP Firewall. Back to the server’s ADNM console, re-run the deployment task to the target computer, Access Denied again.

XP Firewall log shows no entries with source IP for the ADNM server.

Strike 2:

I found the Remote Install log. Here is the process I have (over and over) logged in this file:

02/12/07 20:07:02: rinstInstall begin
02/12/07 20:07:02: Init 50 60 C:\WINDOWS\TEMP\aswB1.tmp C:\Program Files\Alwil Software\Management Tools\InstPkgs NULL C:\WINDOWS\TEMP\aswB0.tmp 0
02/12/07 20:07:02: Store
02/12/07 20:07:02: Domains: domain.local,
02/12/07 20:07:02: Init DOMAIN\COMPUTER1
02/12/07 20:07:02: COMPUTER1: GetAccount
02/12/07 20:07:02: COMPUTER1: not found in domain list
02/12/07 20:07:02: COMPUTER1: Finished with error
02/12/07 20:07:02: TerminateAll
02/12/07 20:07:03: rinstInstall end 87

Ran IPCONFIG at COMPUTER1, and compared the results to “NSLOOKUP COMPUTER1”. DNS resolves the netbios name to its proper address.

Questions abound…Does this indicate a resolution issue? Should I re-discover using the NT LAN Mangler option instead of Active Directory?

Home Run.

I ran the deployment task successfully. This is only after experimenting with the “Login Accounts” settings.

Apparently, the “Domain/Workgroup” field seems to want a friendly NETBIOS style domain name, i.e. “domain”, and NOT a DNS style domain name like “domain.local”.

I’m glad the learning curve for ADNM isn’t too daunting, though it’s not for the faint of heart. :wink:

Thanks.

netjustin