I've been finding that I need to restart the Microsoft SQL server and
agent on a daily basis, and then restart the entire Win 2k3 server that
my standalone ZAM is on in order for services withing ZAM to be started.
If I don't the ZAM server shows itself as "Unavailable" consistantly
every day.

Also I've instlled the OS X client on seven workstations, and of those
seven only one has communicated it's information back up to the ZAM
server. The other six appear to the ZAM server under Network discovery
as Windows stations with Pre-3.00 ZAM clients.

Has anyone out there experienced similar events, and/or have solutions.

Thank you,
Zachary Power