I have upgraded my workstation (just as a test) to 3.1.0.7
Since upgrading each time my workstation starts I get the following RED
event messages in the event log:

Failed reading the ADSM client "First Counter" registry value.  Status code
is returned in the attached data.

The Open Procedure for service "ADSM Client Performance" in DLL
"dsmcperf.dll" failed.  Performance data for this service will not be
available. Status code  returned is DWORD 0.

I didn't see anything in the docs about perf counters being added for ADSM.
Futhermore they don't appear to be working either.

What gives?

Nathan

        -----Original Message-----
        From:   Loon, E.J. van - SPLXM [SMTP:Eric-van.Loon AT KLM DOT NL]
        Sent:   Thursday, June 03, 1999 7:50 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Win32 client needs reboot after install

        Hi ADSM-ers!
        I have upgraded my Win32 3.1.0.6 client to level 3.1.0.7.
        After the upgrade you are prompted to reboot. This is no problem on
my
        workstation, but I also have several servers running the ADSM client
and
        they aren't easy to reboot (they are used by users 7 * 24 hours).
        Is a reboot really necessary? I tried to run the client straight
after the
        upgrade and it seems to work fine.
        If it is necessary to reboot, I don't think this is acceptable for
us. Am I
        the only one having problems with this?
        Kindest regards,
        Eric van Loon
        KLM Royal Dutch Airlines