Pete,
Yes, it would be nice. You can control the Service Packs somewhat by using
a file SP.TXT, in the QCA400/WIN32 folder. If the first character of this
file is a 'Y' or if the file doesn't exist, users can install the latest
Service Pack. However, if you put a 'N' as the first character, users
cannot install a service pack, even if they browse to the Client Access
Accessories folder and try to do it manually. They instead get a message
that their Client Access Administrator has disabled service pack
installation (BWAHAHAHA). Also, you can add your own text to the SP.TXT
file, which will be displayed at the bottom of the dialog box notifying the
user of a new Pack. Mine has a message that the Service Pack has been
tested and is approved for install, with my name and extension. Of course I
still get calls asking if it's alright to press 'Ok.'

HTH,
Jeff

Jeff Velten, Operations Analyst
The AT-A-GLANCE Group - http://www.at-a-glance.com
Phone: (607) 563-9411 x679
Fax: (607) 563-8811





Pete Massiello <pmassiello@os-solutions.com> on 11/10/97 02:59:01 PM

Please respond to MIDRANGE-L@midrange.com
                                                              
                                                              
                                                              
 To:      MIDRANGE-L@midrange.com                             
                                                              
 cc:      (bcc: Jeff Velten/Sidney/AT-A-GLANCE)               
                                                              
                                                              
                                                              
 Subject: Re: How Should CA Service Packs Be Administered?    
                                                              






Jeff_Velten@at-a-glance.com wrote:
>
> Bill,
> I normally pull down the Service Packs from the Web and load them onto a
> few select PCs for testing. After two weeks or so I order the PTF, so
it's
> available for all the user PCs. I used to just order the Service Pack,
but
> we got burned by a Service Pack that was recalled several months ago. A
few
> of my more PC-literate users (the ones that knew enough to cause
problems)
> deselected the check box to allow Service Pack un-install. So... I ended
up
> having to re-install Client Access on those machines...
>
> Jeff
>
> Jeff Velten, Operations Analyst
> The AT-A-GLANCE Group - http://www.at-a-glance.com
> Phone: (607) 563-9411 x679
> Fax: (607) 563-8811
Jeff,
   Wouldn't it be nice if we could control the service pack from some
type of Client Access window on the AS/400.  With the ability to say,
don't let this new service pack be available to everyone yet. Only make
these 4 PCs (or userids) get this service pack. All others get the
previous service pack (that has been tested).  Then once the 4 PCs have
verified there are no problems, release the service pack to all.
   Hopes, Dreams, Wishes....
--
Pete Massiello
OS Solutions International
Phone: (203)-744-7854  Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].