Re: ADSM Webshell

Thanks!!
Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584

> ----------
> From:         Andrew Raibeck[SMTP:storman AT US.IBM DOT COM]
> Sent:         Monday, March 23, 1998 1:14 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: ADSM Webshell
>
> Hello,
>
> I authored the post describing how to use SRVANY.EXE to run the
> webshell client
> as a service. I did this with the version 3.1.0.1 client. Using these
> procedures I was able to log off the machine running the webshell, and
> use a
> web browser on another machine to access the first machine (via the
> webshell
> client).
>
> The webshell requires you to log on via an ID and password established
> with the
> MKWSPSWD utility. This utility needs to be run on the machine running
> the
> webshell client. Here's how I set mine up:
>
> 1) c:
>
> 2) cd \win32app\ibm\adsm\baclient
>
> 3) mkwspswd p webshell pw a wsstuff
>
> This creates an ID called 'webshell' and a password called 'pw' and
> encrypts it
> in a file that is stored in the 'wsstuff' subdirectory
> (c:\win32app\ibm\adsm\baclient\wsstuff). The file name is adsmweb.ws.
>
> The ADSMPSWD utility is used to generate a file that stores the ADSM
> node
> password. If you are using PASSWORDACCESS GENERATE, you do not need to
> run this
> utility. Otherwise, you can run it as follows:
>
> 1) c:
>
> 2) cd \win32app\ibm\adsm\baclient
>
> 3) adsmpswd p nodepw wsstuff
>
> This creates a file in the c:\win32app\ibm\adsm\baclient\wsstuff
> directory with
> the node's password. The file name is adsmpswd.ws.
>
> When I start the webshell (not as a service), I use these commands:
>
> 1) c:
>
> 2) cd \win32app\ibm\adsm\baclient
>
> 3) webshell 3019 c:\win32app\ibm\adsm\baclient\wsstuff
>
> In my example, 3019 is the port number I use to connect to the
> webshell client
> with (from the web browser), and c:\win32app\ibm\adsm\baclient\wsstuff
> is where
> the *.ws passwords are kept.
>
> When running this as a service, go by my procedures I posted earlier
> (or as
> reposted below). I've tried to make my examples here consistent with
> my prior
> post.
>
> Andy
>
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
> Please respond to ADSM-L AT VM.MARIST DOT EDU
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Re: ADSM Webshell
>
> Jim,
>
>         Yes, I seen your e-mail earlier, but when you run it this way,
> does it open a MS-DOS window??  I've also been having troubles with
> the
> ADSMPSWD and MKWSPSWD utilities.  Is there a bug in V3??
>
> Thanks,
> Rick Smith
> Maritz, Inc.
> Storage & Security Administration
> smithrr AT maritz DOT com
> (314) 827-1584
>
> > ----------
> > From:         Jim Hunt[SMTP:Jim_Hunt AT VENCOR DOT COM]
> > Sent:         Monday, March 23, 1998 12:11 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: ADSM Webshell
> >
> > This is the info I have collected on it so far.
> >
> > You can run the webshell client as an NT service using the
> SRVANY.EXE
> > utility
> > that comes with the Windows NT Resource Kit.In that directory are
> the
> > SRVANY.EXE file and the SRVANY.WRI file. The latter is in Windows
> > Write
> > format
> > (can be read with WordPad), and provides general information on
> using
> > SRVANY.EXE to run a Windows NT applicaiton as a service.
> > Using the SRVANY.WRI file for reference, here is my procedure:
> > 1) Install SRVANY.EXE as a service with this command (from an MS-DOS
> > prompt):
> >      INSTSRV WebShell D:\NTRESKIT\SRVANY.EXE
> > This will create a new NT service called "WebShell".
> > 2) Run REGEDT32 to edit the NT registry. ***** CAUTION ***** Always
> > use
> > this
> > utility with extreme care. Incorrect changes to the registry can
> cause
> > problems
> > for your system, even possibly rendering it unbootable.
> > 3) Add a key under
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebShell called
> > "Parameters". To that key, add the three values shown in the table
> > below:
> > VALUE NAME        DATA TYPE     STRING
> > -------------     ---------
> > -------------------------------------------
> > Application        REG_SZ
> > c:\win32app\ibm\adsm\baclient\webshell.exe
> > AppParameters      REG_SZ       3019
> > c:\win32app\ibm\adsm\baclient\wsstuff
> > AppDirectory       REG_SZ       c:\win32app\ibm\adsm\baclient
> > "Application" represents the path to the webshell executable. Your
> > path may
> > be
> > different, depending on where you installed ADSM.
> > "AppParameters" represents the port number used to connect to the
> > webshell,
> > and
> > the directory of the webshell and ADSM IDs and passwords (these are
> > the
> > ones
> > you created with the MKWSPSWD.EXE and ADSMPSWD.EXE utilities). I
> > picked
> > port
> > number 3019, and I stored my password files in the ...\wsstuff
> > directory.
> > Your
> > port number and password file directory may be different.
> > "AppDirectory" is the directory where the DSMC.EXE executable
> resides.
> > Your
> > directory may be different.
> > 4) Close the registry editor.
> > 5) Go into the "Services" applet (from "Control Panel"), and start
> the
> > WebShell
> > service.
> > At this point, you should be able to start your browser and point it
> > to the
> > webshell. In my sample scenario above, the URL is
> > http://storman.sanjose.ibm.com:3019/webshell
> >
> >
> >
> >
> > smithrr AT MARITZ DOT COM on 03/23/98 12:24:04 PM
> >
> > Please respond to ADSM-L AT VM.MARIST DOT EDU
> >
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > cc:    (bcc: Jim Hunt/IS/Vencor)
> > Subject:  ADSM Webshell
> >
> >
> >
> >
> > ADSMer's
> >         Is there any way to run the webshell as a service without
> > starting a MS-DOS window??  We are trying to do this on the NT
> servers
> > that we are backing up, and to keep the MS-DOS session running you
> > must
> > leave yourself logged in, which poses a security threat.  Any
> ideas??
> >
> > Rick Smith
> > Maritz, Inc.
> > Storage & Security Administration
> > smithrr AT maritz DOT com
> > (314) 827-1584
> >
>
>
>
>