Hi it is likely that you install the ADSM Client and, straight after, the
Scheduling Service. Then you test the installation.
You are likely using software distribution mechanisms. You could make the
problem go away by installing
the client, connecting to ADSM using the B/A client, and then installing the
scheduling service.
Why? Magic! No, it is because a) the Sched Service installation performs
password validation by connecting
to the server to check it out and the node entry retains the platform info
passed during the first connection.

Regards, Giulio John Tarella IBM Italy