ADSM-L

FW: ADSM - platforms

2015-10-04 18:08:48
Subject: FW: ADSM - platforms
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at ASUPO
Date: 4/14/97 10:49AM
If what you are looking at is the output from a Q Node, or the node GUI, then
the bad news is that there is no wasy way to change the platform field.  The
good news, though, is that this field really doesn't matter much.  The field
in question gets set the first time the user signs on, and is not updateable.
There have been may requests to be able o change this field, or have the
server update the field when a change is detected.

However, if you look at a Q session while one of your nodes is in session,
you will find the server recognizes the correct platform.  My own personal
node definition has gone from OS/2 to Win95 to NT, and I probably used it for
some Macintosh testing too - all without problems.

While it would be nice to look at a node definition and be able to tell the
last platform that used this id, the truth is it doesn't really matter.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: FW: ADSM - platforms
Author:  INTERNET.OWNERAD at SNADGATE
Date:    4/14/97 10:49 AM


Our ADSM admin person asked me to forward this on.  We are going to be
going through a lot of Windows for WG to Windows NT changes.  I have
seen references to this in the past in the list, but can't put my
fingers on the correct thread.
Jim Bohnsack
Raytheon E-Systems

>----------
>From:  Bond, CD Dianne (4828)
>Sent:  Friday, April 11, 1997 8:34AM
>To:    Bohnsack, JA Jim (6030)
>Subject:       ADSM - platforms
>
>Please submit the following to ADSM-L to see if anybody has found a work
>around.  We have multiple users upgrading from Windows 3.11 to Windows NT and
>ADSM doesn't recognize platform changes. I tried the following without
>success:
> I register a new node for the Windows NT using the machine name.  Because
>there is no way to assign an existing filespace to a new node I did the
>following:
>
>rename node WINNT to temp
>rename node WIN3.11 to WINNT
>export node WINNT Filedata=all Dev=cartridge
>rename node WINNT to WIN3.11
>rename node temp to WINNT
>import node WINNT DEV=cartridge vol=038273 filedata=all
>
>all worked well except due to the platform change I received the following
>error
>
>04/10/1997 14:45:48      ANR0689W IMPORT NODE: Client platform type (Windows)
 >for
>                          imported node MCDUFFIEWN conflicts with an existing
>node
>                          with the same name - the node will not be imported.
>
>04/10/1997 14:45:48      ANR0617I IMPORT NODE: Processing completed
>successfully.
>04/10/1997 14:45:48      ANR0620I IMPORT NODE: Copied 0 domain(s).
>
>04/10/1997 14:45:48      ANR0621I IMPORT NODE: Copied 0 policy sets.
>
>04/10/1997 14:45:48      ANR0622I IMPORT NODE: Copied 0 management classes.
>
>04/10/1997 14:45:48      ANR0623I IMPORT NODE: Copied 0 copy groups.
>
>04/10/1997 14:45:48      ANR0624I IMPORT NODE: Copied 0 schedules.
>
>04/10/1997 14:45:48      ANR0625I IMPORT NODE: Copied 0 administrators.
>
>04/10/1997 14:45:48      ANR0626I IMPORT NODE: Copied 0 node definitions.
>
>04/10/1997 14:45:48      ANR0627I IMPORT NODE: Copied 0 file space 0 archive
>files,
>                          0 backup files, and 0 space managed files.
>
>04/10/1997 14:45:48      ANR0628I IMPORT NODE: Used 0 volume(s).
>
>04/10/1997 14:45:48      ANR0629I IMPORT NODE: Copied 22 bytes of data.
>
>04/10/1997 14:45:48      ANR0634I IMPORT NODE: Detected 1 errors.
>
>04/10/1997 14:45:48      ANR1364I Input volume 038273 closed.
>
>04/10/1997 14:45:48      ANR0611I IMPORT NODE started by CDB as process 16
>has
>                          ended.
>
>
>Archived files are my biggest concern.  Are we going to have to have two
>nodes for these users until the files expire.
>
>
>
>
>
>
>
>
<Prev in Thread] Current Thread [Next in Thread>