RE: Ghost imaging and Millennium client

["Aaron Beebe" <ABeebe at thegdl dot org>]

Larry,

They will also need read write permissions for the millennium directory.



Aaron Beebe
Database Administrator
Genesee District Library

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Bissen, Sheryl
Sent: Thursday, September 23, 2004 4:03 PM
To: IUG INNOPAC List
Subject: RE: Ghost imaging and Millennium client

If each user has their own User Profile on the pc, you might need to
make sure that 'everyone' has permissions to the icon.  I know it is
something I have had to do on Windows XP installations.

Sheryl Bissen
Library Systems Support Technician
Grinnell College Libraries
1111 6th Ave.
Grinnell, IA 50112

email   bissen at grinnell dot edu
Phone 641-269-3359
Fax  641-269-4283
 

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Larry Mozer
Sent: Thursday, September 23, 2004 2:57 PM
To: innopac at innopacusers dot org
Subject: Ghost imaging and Millennium client





We are having a problem with the Millennium client not working after
restoring a ghost image (using Symantic Ghost).  In discussing this with
III, she told me she has heard of others having problems with the client
not working after imaging and suggested that I write this list to see if
anyone has any experience with this issue.  I did check the archives and
could not find any message addressing this specific problem.

Here is what is happening:

We ghost all our computers to create images so if the hard drive crashes
on that computer we can restore it using the image and at least it will
have everything up to the point the image was taken.  This does not
include their documents, favorites etc. as we keep those on a server and
provide each staff member with space on that server for these items.
That way they can log into any machine in the library into our domain
and have access to their stuff.  So for the ghost image we just capture
what is actually on the hard drive which would be the O.S. (with all
updates) and any applications  etc.

If the machine hard drive crashes, we then restore the image and they
still have access to the server with all their documents et al without
losing anything.

We recently have had some hard drives go out and have used this process.
The problem is that due to limited staff time and many machines to
ghost, some of these images are over a year old.  I know they are trying
to get them more up to date.  Recently we have had to restore the image
on some where the image was a year or so old.  The Millennium client on
the image was old (JRE 1.3) and so we needed to upgrade it to the
lastest version of the client (JRE 1.4.1_02).  When attempting to do
this it claimed to
install successfully BUT with a non-fatal error.   According to the
install
log:

ERROR  Additional Notes: ERROR - couldn't determine via status:
Unexpected end of file from server

When attempting to start the application (does not matter if it is from
a shortcut on desktop, program menu or directly clicking on IIIrunner
executable) we get the following error:

"This application has unexpectedly quit.  Invocation of this java
application has caused an InvocationTargetException.  This application
will!
now exit (LAX)."  When clicking on details it shows:

java.lang.NullPointerException      at
java.util.StringTokenizer.<init>(Unknown Source)     at
java.util.StringTokenizer.<init>(Unknown Source)     at
iiirunner.<init>(iiirunner.java:73)     at
iiirunner.main(iiirunner.java:43)  at
sun.reflect.NativeMethodAccessorlmpl.invokeO(Native Method)     at
sun.reflect.NativeMethodAccessorlmpl.invoke(Unknown Source)  at
sun.reflect.DelegatingMethodAccessorlmpl.invoke(Unknown Source)     at
java.lang.reflect.Method.invoke(Unknown Source)  at
com.zerog.lax.LAX.Iaunch(Unknown Source)       at
com.zerog.lax.LAX.main(Unknown Source)

I had totally unistalled the earlier verison of Millennium and any
earlier version of JRE.  I used the lastest version of Millennium client
directly downloaded from CS-Direct.  I tried it as the user (as
administrator) and
as administrator to the computer.  I even tried it in safe mode.   The
same
error occurred everytime.

What is strange is that when we originally had upgraded the client on
these machines (some point after the image had been taken and we had not
reimaged
since) it worked fine as it did with all our computers.  The image
should be exactly what is was before so why would it not work now.  The
person I talked with at III thinks that somehow the process of imaging
causes a problem with client and so when the image is restored the
client will not work.  She suggested wiping the hard drive and reloading
everything from scratch.  Yes we could do that but it defeats the whole
point for using Ghost--that is what we were trying to get away from.  We
are trying to save time in getting these machines up and running for the
staff member.  These machines are all Windows 2000 and we will be
upgrading to XP Pro after the first of the year and we will be wiping
the hard drives on some of those but in the meantime if there is a way
of getting Millennium to work without having to load from scratch then I
would like to find out.

Anybody out there experience this and hopefully find a solution to it
(short of wiping the hard drive)?

Thanks,
Larry

--------------------------------------
B. Larry Mozer
Computing Operations & Research Services
31 LL (4100)
UN-Lincoln
(402) 472-2538
e-mail: BMOZER1 at unl dot edu

--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies:  INNOPAC at innopacusers dot org Update your subscription
options: http://innopacusers.org/mailman/listinfo/innopac



--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies:  INNOPAC at innopacusers dot org Update your subscription
options: http://innopacusers.org/mailman/listinfo/innopac