Re: Error Installing client on NT 4.0

>Hi Chris,
>
>I actually came across that error message as well.  It's quite frustrating
>because it says that the client is installed in the directory,
>you verify it and then it turns around and says it is not - and keeps going
>in circles.  I'll let you know what worked for me.  At the beginning when
>the Schedule services asked me if I was installing on machine "local", I
>always replied "no" and typed in the machine name and continued, normally
>this worked every other time with every other machine until this one.  I
did
>everything, re-installed and the works, finally out of frustration I said
>"Yes" to install it on the machine "local" and the whole procedure went all
>the way through, it even found the directory.  I then started the
>Scedule Services again, removed the current ADSM service (machine local),
>and added it in once again with the proper machine name and it worked!
>
>Hope this works for you too!
>Julie
>
>
>On Wed, 27 May 1998, Chris Berthaut wrote:
>
>> Tony,
>> I apologize, I said latest but forgot to mention that it is the 2.x ADSM
>> client. After installing that, one of the options (icons) is ADSM
scheduler
>> Service Installation, which launches a DOS based app that installs the
>> scheduler service for NT. Don't know if you are familiar with the 2.x
client
>> or not, but if so, that should clarify things.
>> thanks!
>> cb
>>
>> -----Original Message-----
>> From: Tony White <tony.white AT GTRI.GATECH DOT EDU>
>> To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
>> Date: Wednesday, May 27, 1998 1:47 PM
>> Subject: Re: Error Installing client on NT 4.0
>>
>>
>> >Chris,
>> >
>> >I haven't seen your particular problem, but I can tell you what worked
with
>> us. We have the ADSM v3.1.1.1 server on AIX 4.x, and are installing the
ADSM
>> client v3.1.0.3 on NT v4.0 (SP3) nodes. All nodes use a closely
controlled
>> configuration, and the users don't know the 'Administrator' passwords (so
>> they can't mess with the basic configuration or install software).
>> >
>> >From what I saw in previous postings to this list, the v3.1.0.3 client
for
>> Windows-32 doesn't have an interactive utility to install the scheduler -
>> just the DSMCUTIL command-line utility. So I'm puzzled when you say
>> "...prompts for the directory, ..." What command or utility are you using
to
>> install the scheduler?
>> >
>> >What we do for each node:
>> >
>> >- set up a definition for the node on the server, using the NetBIOS node
>> name and a password we choose, call it <password-1> . Passwords on the
>> server are set NOT to expire.
>> >
>> >- Login on the client machine as Administrator, and install the ADSM
client
>> software - to reside locally - from a network file server. Suppose it is
>> installed under c:\win32app\ibm\adsm\baclient . We install *only* the B/A
>> client - none of the other garbage.
>> >
>> >- to install the ADSM scheduler, we start an MS-DOS command session and
>> enter these commands:
>> >
>> >CD C:\win32app\ibm\adsm\baclient
>> >DSMCUTIL INSTALL /Name:"ADSM Scheduler" /Password:<password-1>
>> >/Clientdir:C:\win32app\ibm\adsm\baclient /Autostart:Yes
>> >DSMCUTIL UPDATEPW /Node:<nodename> /Password:<password-1> /Validate:No
>> >
>> >- I don't know why the second command is necessary, the "UPDATEPW" - but
it
>> is!
>> >- Then, still in the same MS-DOS session, we have the user run a small
>> program we have created, whose effect is to allow them to enter a
password
>> of their own choosing, call it <password-2>, without us knowing the
password
>> (no echo to screen) - and then the program executes the command:
>> >
>> >DSMCUTIL UPDATEPW /Node:<nodename> /Oldpassword:<password-1>
>> >/Updateonserver:Yes /Password:<password-2>
>> >
>> >- This last command sets a new password and updates it on the server
also
>> >
>> >- Then we exit the MS-DOS session, and shutdown/reboot the machine -
which
>> installs and starts the scheduler.
>> >
>> >That sequence has been working well for us. We have expended
considerable
>> effort to automate the installation of the software and scheduler.
>> >
>> >Hope this helps you. Feel free to write directly to me if you have more
>> questions!
>> >
>> >- Tony
>> >=========================================
>> >At 09:13 AM 5/26/98 -0500, you wrote:
>> >>>>>
>> >
>> >Having a problem installing the latest ADSM client on an NT 4.0 server.
>> Actually, the installation goes fine, but when I try to install the
service,
>> I get to the point where it prompts for the directory, and I accept the
>> default, which is correct but it shows
>> >    fileExists():FindFirstFile:Win32 RC=67 Path
>> (c:\win32app\ibm\adsm\baclient) is invalid, reenter
>> >    I have tried rebooting, reinstalling, and changing the path name to
no
>> avail. What's up with this error message? and how can I get around it?!
>> >    thanks!!!
>> >
>> >
>> >    Chris Berthaut
>> >    <mailto:cberthaut AT worldnet.att DOT net>cberthaut AT worldnet.att DOT 
>> > net
>> >
>> >
>> >    <<<<
>> >
>> >
>> >
>> >----------------------------------
>> >Tony White, Research Scientist II Tony.White AT gtri.gatech DOT edu
>> >GTRI Computer Coordinator (404) 894-8157 fax: 894-9337
>> >GT/GTRI/AIST, Atlanta, GA 30332-0816
>> >
>> >"It's as bad as you think, and they are out to get you."
>> >
>>
>
>**************************************************************************
>Julie Walter                           Phone: 492-9338  Fax:  492-1729
>Help Desk Analyst                      E-Mail: Julie.Walter AT ualberta DOT ca
>Computing and Network Services
>Rm 302 General Services Building
>University of Alberta
>Edmonton, Alberta. CA
>T6G 2H1