EP1168163A1 - Procédé permettant l'installation d'un logiciel dans un ordinateur client - Google Patents

Procédé permettant l'installation d'un logiciel dans un ordinateur client Download PDF

Info

Publication number
EP1168163A1
EP1168163A1 EP00410063A EP00410063A EP1168163A1 EP 1168163 A1 EP1168163 A1 EP 1168163A1 EP 00410063 A EP00410063 A EP 00410063A EP 00410063 A EP00410063 A EP 00410063A EP 1168163 A1 EP1168163 A1 EP 1168163A1
Authority
EP
European Patent Office
Prior art keywords
service
executable file
client
setup procedure
package
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP00410063A
Other languages
German (de)
English (en)
Inventor
Bruno Richard
Denis Flaven
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HP Inc
Original Assignee
Hewlett Packard Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Co filed Critical Hewlett Packard Co
Priority to EP00410063A priority Critical patent/EP1168163A1/fr
Priority to US09/883,724 priority patent/US20010056572A1/en
Publication of EP1168163A1 publication Critical patent/EP1168163A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation

Definitions

  • the invention relates to computer systems and telecommunications, and more particularly to a process for automatically installing a software package on a client computer which operates under a WINDOWS NT TM or similar environment.
  • I.H.S Information Handling Systems
  • LAN Local Area Network
  • Intranet Intranet network
  • an Information Technology (IT) administrator receives the task of handling and managing the different computers which communicate through the network, and the software packages therein included so as to ensure that those fit the user's needs.
  • IT Information Technology
  • the IT administrator has the responsibility of installing the different software packages in the different computers on the LAN.
  • the IT administrator who wishes to automate the installation procedure may use different solutions in accordance with the particular operating system which is used.
  • the IT administrator may take advantage from the pre-existing TELNET feature present in that OS. That facility allows the remote control of the PC client.
  • the TELNET is based on human interface over a communication protocol, allowing remote operation of a machine in a console mode, as if the user was operating the machine locally.
  • the IT administrator may wish to have a full control over the installation procedures from his own console or computer, wherever the remote physical situation of the PC client. In some situations, he may take advantage of a pre-existing agent for the purpose of controlling the installation procedure with files stored on a remote server but that agent also needs to be installed, what still requires a manual and local setup procedure in the computer client.
  • Another solution is based on the use of the Login Script facility which is provided by the Primary Domain Controller (PDC) of the NT domain.
  • PDC Primary Domain Controller
  • That solution however entails three main drawbacks: A first drawback comes from the fact that administrative access rights to the PDC are required, what could appear haphazard in some situations. Further, the automatic triggering of the logon script by all the users who are logging at the same time might have some bad consequences and result in a overhead of the system resources. In any case, the IT administrator is never aware of the precise instant where the installation procedure has been executed since, clearly, he may never knows when every user is actually logging on and, for those who have not, the problem still remains.
  • the IT administrator should be given the possibility to easily launch an executable file within a remote PC client which is part of a NT Network domain.
  • an executable file (pushservice.exe) is stored on a server as a shared resource and is used for controlling a local setup procedure of a software application.
  • the executable file is being installed as a low level service which is generally available for background local tasks, such as drivers, anti-virus programs, IP protocols, TCP/IP and harddisk compression mechanisms.
  • the process deviates the normal use of those low level services for the purpose of executing a remote executable file located on a server, and shared. Once it has been installed, as a service, the executable filed can be started on the computer without being present on the hard disk of the latter.
  • the executable file is being installed as a NT service under the control of the NT service control manager (SCM) and in accordance with the description contained within a description file ( package.ini ) which may also be stored on a server, as a shared resource.
  • SCM NT service control manager
  • the executable file receives the particular format of a NT service.
  • the executable file ( pushservice.exe ) becomes available to the remote PC client and may control the setup procedure in accordance with the description contained within the description file.
  • the IT manager is therefore given a very simple and effective way for controlling the setup procedure of a software package, stored on a server, and which are installed within a remote client computer, elsewhere in the LAN.
  • the remote setup procedure takes advantage of the LAN existing in the network, and the administrative rights which apply to the considered machines where the software package is to be installed.
  • the process can be immediately applied for triggering the setup of mandatory files on a given machine, such as virus signatures, Operating Systems service packs or patches...
  • the description file ( package.ini ) contains a list of the installation files required for a local setup procedure plus an additional line defining the command which is to be entered for executing an unattended setup procedure of said software application
  • the installation of the NT service is followed by the activation of a Wake-on-LAN function existing in the PC client so that the IT administrator may, at any time, control the setup procedures in the PC clients..
  • GUI Graphical User Interface
  • a process is provided which can be used for triggering the execution of an executable file, stored on a server or on shared resources within a NT domain.
  • the execution can be automatically triggered by means of the formatting of the executable file as a service, with an entry point referring to a service entry, and by correspondingly installing it by the NT Service Control Manager.
  • the invention also provides a new arrangement of servers for a NT domain which can be used for storing installation package which can be easily installed in different remote PC clients under the control of the IT administrator.
  • the new server stores at least one software installation package, and a description file (package.ini) which is associated to that application.
  • an executable file is being stored and is installed as a NT service for the purpose of controlling the remote setup procedure of the application within the remote PC client.
  • FIG 1 there is represented an LAN or Intranet network 5 which defines a NT domain, which control may be given to an IT administrator operating from a console 1 or computer 2.
  • a server 2 may be used as shared resources for storing software installation packages which can be distributed to the different PC clients comprised within the NT domain.
  • Figure 1 represents two PC clients 3 and 4 which are operated under the WINDOWS NTTM or WINDOWS 2000TM.
  • the IT administrator manages the network and particularly controls the installation procedures of software packages stored on server 2 within the PC clients 3 and 4. This will be achieved remotely as will be explained hereinafter.
  • the IT administrator is particularly aware of the administrative account of PC clients where the software packages need to be installed, and the precise particular administrative account name and password assigned to those PC clients.
  • Server 2 includes at least one software package which may be used for installing a given application in PC client 3, for instance, under the control of the IT administrator.
  • one software package includes all the files which are normally required for a local setup procedure and which correspond to the application being considered.
  • Those installation files clearly depends upon the type and the complexity of the particular application for which an installation is required.
  • Such installation files including the Dynamic Link Libraries (DLL) and all the subsequent files which are to be copied on the hard disk drive of PC client 3, for instance, are well known from the skilled man and will not, for that reason, be developed with more details.
  • DLL Dynamic Link Libraries
  • those files include all the files which are normally involved in a local setup procedure and that the particular executable file - the setup.exe - which causes the launching of the installation procedure, has to support an unattended mode, which is that which is being executed when the user types the "-s" switch on the command line (unattended or silent setup).
  • package.ini file may take the form of a text file and contains the description of the installation files which are involved in the setup procedure. It particularly includes the precise list of the installation files required for a local setup procedure, plus an additional line carrying the command which is required for starting the local setup procedure.
  • server 2 is arranged to store the standard Microsoft installation files.
  • server 2 includes a package.ini description file which defines the list of those files and further comprises an additional line to run the silent setup procedure, i.e. the following line: "setup.exe ⁇ s" .
  • console 1 includes a particular so-called pusher.exe executable file, as shown in figure 1.
  • GUI Graphical User Interface
  • the IT administrator is being prompted in step 21 to select one software package available on server 2, for the purpose of associating it to one particular PC client, e.g. PC client 3.
  • the GUI includes a "drag-and-drop" mechanism which permits a direct and very simple association between the considered software package and PC client 3.
  • step 23 the selection of one particular software application, and its association to one particular PC client, causes the pusher.exe to install a new NT service on PC client 3, hereinafter referred to as pushservice.exe.
  • This is achieved by means of the use of the NT Service Control Manager (SCM) of PC client 3, thanks to the administrative rights given to IT administrator on that particular machine.
  • SCM NT Service Control Manager
  • Microsoft NT TM and Microsoft 2000 TM supports an application type known as a service which takes the form of a .exe or .dll , for instance.
  • a service application conforms to the interface rules of the SCM.
  • NT service which is generally used for local files, drivers, anti-virus programs, Internet Protocol and TCP/IP drivers, and hard disk drive compression mechanisms.
  • the particular executable file - herein referred to as the pushservice.exe - is compiled in accordance with the prescriptions applying to the services, and which are defined in the Microsoft specifications.
  • the entry point of that executable file is not referring to WINMAIN as for the usual standard executable files, but refers to a service entry which WINDOWS NT decodes as such.
  • the general rules of the development conventions which are applicable to the services executable files are available in the specifications marketed by Microsoft, and particularly in the Microsoft Software Developer's Network reference book.
  • the registration of executable file pushservice.exe which has been preliminary compiled under the NT service file, is then registered by the NT Service Control Manager as a new NT service, in step 23. It should be noticed that the installation of the NT service for the pushservice.exe file requires that the PC client 3 or 4 are switched on. In one particular embodiment, the process takes advantage of a Wake-on-LAN function which is present within PC client 3, and which permits the actual installation of the service.
  • the NT service which is installed for the purpose of the remote software package installation receives the following reference:
  • a reference to the package software existing on the hard disk of the shared server 2 is used as an option of the command line, e.g.
  • server 2 comprises the standard installation files for a local setup, the additional installation description file package.ini as well as the special pushservice.exe file for supporting the newly registered NT service.
  • the new NT service can be started by the IT administrator in accordance with the usual NT Service Control Manager procedures, in step 24. That causes the instantiation of the service into the memory of the PC client and starts its execution.
  • the new NT service becomes available on the PC client 3, when the latter is started. This achieves the remote execution within PC client 3, under control of console 1, of an executable file which is stored on a server 2 and which has been compiled as a service.
  • the process takes advantage of the NT service control manager for the purpose of an automatic installation procedure through a network
  • Figure 3 particularly shows the process which is executed by the pushservice.exe service in response to the loading into the memory of the NT service under the control the IT administrator.
  • step 31 causes the identification of the software package which is to be installed. This is achieved by means of the extraction of the particular command line which has been associated to the new service by the NT Service Control Manager, as explained above.
  • the process particularly uses the option of the command line defined above, and which contains a reference to the package.ini description file stored on the server 2.
  • the pusherservice.exe opens the package.ini description file and identifies the different files which are to be installed on the PC client being considered, e.g. PC client 3.
  • the process downloads them from the server 2 and stores a copy of those files in a predetermined directory on the hard disk drive of the PC client. As known by the skilled man this can be achieved by means of a path relative to the pushservice.exe path.
  • the storing process of the installation files on the local hard disk of PC client appears most useful and safe. However, it should be possible, in another embodiment, to directly use the original version of the installation files existing on remote server 2 for the purpose of initiating the setup procedure in PC client 3.
  • step 34 the pushservice.exe, which has received the format of a NT service as explained above, un-installs itself and stops, contrary to the usual mechanism of the standard executable files.
  • the IT administrator may take the control, from his own console 1, of a setup procedure on a remote PC client 3. It should be noticed that, while the process has been described in reference to the IT administrator, it can also be useful for any users who receive the possibility of launching an executable file, stored on a remote server, and which are to be executed on a remote PC client. In that case, the pusher.exe program may alternatively prompts the user to enter the particularly context for which the executable file is to be executed in the remote PC client. Once the user has entered a given context, the pusher.exe program then request the id and the password for giving access to that context.
  • the NT Service Control Manager is used for allowing different users to have a remote control on the execution of file in different PC clients, in accordance with the administration rights which are assigned to the different users.
  • the process can then be used by the IT administrator, who has extensive rights on the Domain, but also by the other users having different, and generally lower, access rights.
  • the software package comprising the installation files for a local setup and the additional mechanism description package.ini file are all located on server 2. It should be noticed, however, that this is only an example of embodiment, and that the software package may be located in different locations or shared resources within the NT domain. In particularly, the installation packages may also be loaded into the IT administrator console 1.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
EP00410063A 2000-06-19 2000-06-19 Procédé permettant l'installation d'un logiciel dans un ordinateur client Withdrawn EP1168163A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP00410063A EP1168163A1 (fr) 2000-06-19 2000-06-19 Procédé permettant l'installation d'un logiciel dans un ordinateur client
US09/883,724 US20010056572A1 (en) 2000-06-19 2001-06-18 Process for installing a software package in a client computer, and server for doing the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP00410063A EP1168163A1 (fr) 2000-06-19 2000-06-19 Procédé permettant l'installation d'un logiciel dans un ordinateur client

Publications (1)

Publication Number Publication Date
EP1168163A1 true EP1168163A1 (fr) 2002-01-02

Family

ID=8174034

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00410063A Withdrawn EP1168163A1 (fr) 2000-06-19 2000-06-19 Procédé permettant l'installation d'un logiciel dans un ordinateur client

Country Status (2)

Country Link
US (1) US20010056572A1 (fr)
EP (1) EP1168163A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003073698A1 (fr) * 2002-02-15 2003-09-04 Electronic Data Systems Corporation Procede et systeme de gestion centrale d'un reseau d'ordinateurs
DE10249611B3 (de) * 2002-10-18 2004-04-01 Völcker Informatik AG Verfahren zur Installation von Software auf einem Computer und Computersystem zur Durchführung des Verfahrens
EP2341428A1 (fr) * 2009-12-04 2011-07-06 Samsung Electronics Co., Ltd. Serveur connecté à un appareil de formation d'images et client, client, et procédé d'installation à distance du pilote de l'appareil de formation d'images

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6976068B2 (en) 2001-09-13 2005-12-13 Mcafee, Inc. Method and apparatus to facilitate remote software management by applying network address-sorting rules on a hierarchical directory structure
US7069581B2 (en) * 2001-10-04 2006-06-27 Mcafee, Inc. Method and apparatus to facilitate cross-domain push deployment of software in an enterprise environment
US9009694B2 (en) * 2002-05-22 2015-04-14 Oracle America, Inc. Pre-verification and sequencing of patches
US7823148B2 (en) * 2002-05-22 2010-10-26 Oracle America, Inc. System and method for performing patch installation via a graphical user interface
US20040003390A1 (en) * 2002-06-27 2004-01-01 Microsoft Corporation System and method for installing a software application in a non-impactfull manner
US7735078B1 (en) 2003-10-30 2010-06-08 Oracle America, Inc. System and method for software patching for cross-platform products
US20050114499A1 (en) * 2003-11-24 2005-05-26 Monk John M. System and method for updating testing devices in a distributed environment
DE102004005730A1 (de) * 2004-02-05 2005-08-25 Robert Bosch Gmbh Verfahren zur Konfiguration eines Computerprogramms
US20050180326A1 (en) * 2004-02-13 2005-08-18 Goldflam Michael S. Method and system for remotely booting a computer device using a peer device
US20070016638A1 (en) * 2005-06-30 2007-01-18 Ian Elbury System and method of application provisioning
US8019827B2 (en) * 2005-08-15 2011-09-13 Microsoft Corporation Quick deploy of content
KR101370349B1 (ko) * 2008-10-24 2014-03-05 삼성전자 주식회사 화상형성장치 및 클라이언트와 연결된 서버, 이를 포함하는화상형성시스템, 및 화상형성장치의 드라이버 원격설치방법
US8893119B2 (en) 2009-04-29 2014-11-18 Adobe Systems Incorporated Software selection based on estimated available storage space
US8856778B2 (en) * 2009-04-29 2014-10-07 Adobe Systems Incorporated Software selection based on available storage space
US20110041124A1 (en) * 2009-08-17 2011-02-17 Fishman Neil S Version Management System
US8462922B2 (en) 2010-09-21 2013-06-11 Hartford Fire Insurance Company Storage, processing, and display of service desk performance metrics
JP7505277B2 (ja) 2020-06-11 2024-06-25 ブラザー工業株式会社 セットアップシステムおよびセットアッププログラム
CN115774561A (zh) * 2021-09-06 2023-03-10 花瓣云科技有限公司 应用程序升级方法、电子设备、芯片及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5421009A (en) * 1993-12-22 1995-05-30 Hewlett-Packard Company Method of remotely installing software directly from a central computer
EP0710914A1 (fr) * 1994-11-04 1996-05-08 Canon Information Systems, Inc. Reprogrammation intelligente d'une mémoire flash
US5860012A (en) * 1993-09-30 1999-01-12 Intel Corporation Installation of application software through a network from a source computer system on to a target computer system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6282712B1 (en) * 1995-03-10 2001-08-28 Microsoft Corporation Automatic software installation on heterogeneous networked computer systems
US5742286A (en) * 1995-11-20 1998-04-21 International Business Machines Corporation Graphical user interface system and method for multiple simultaneous targets
US5793982A (en) * 1995-12-07 1998-08-11 International Business Machine Corporation Validating an installation plan containing multiple transports and redirectors by adding data structure of the modules to the plan if the indicated transport and redirector modules are unavailable
US5881236A (en) * 1996-04-26 1999-03-09 Hewlett-Packard Company System for installation of software on a remote computer system over a network using checksums and password protection
US5790796A (en) * 1996-06-14 1998-08-04 Symantec Corporation Polymorphic package files to update software components
US6029246A (en) * 1997-03-31 2000-02-22 Symantec Corporation Network distributed system for updating locally secured objects in client machines
US6523166B1 (en) * 1998-09-21 2003-02-18 Microsoft Corporation Method and system for on-demand installation of software implementations
US6418554B1 (en) * 1998-09-21 2002-07-09 Microsoft Corporation Software implementation installer mechanism

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5860012A (en) * 1993-09-30 1999-01-12 Intel Corporation Installation of application software through a network from a source computer system on to a target computer system
US5421009A (en) * 1993-12-22 1995-05-30 Hewlett-Packard Company Method of remotely installing software directly from a central computer
EP0710914A1 (fr) * 1994-11-04 1996-05-08 Canon Information Systems, Inc. Reprogrammation intelligente d'une mémoire flash

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7120684B2 (en) 1998-10-22 2006-10-10 Electronic Data Systems Corporation Method and system for central management of a computer network
WO2003073698A1 (fr) * 2002-02-15 2003-09-04 Electronic Data Systems Corporation Procede et systeme de gestion centrale d'un reseau d'ordinateurs
AU2003219776B2 (en) * 2002-02-15 2007-04-19 Electronic Data Systems Corporation Method and system for central management of a computer network
AU2003219776B8 (en) * 2002-02-15 2007-05-17 Electronic Data Systems Corporation Method and system for central management of a computer network
DE10249611B3 (de) * 2002-10-18 2004-04-01 Völcker Informatik AG Verfahren zur Installation von Software auf einem Computer und Computersystem zur Durchführung des Verfahrens
EP2341428A1 (fr) * 2009-12-04 2011-07-06 Samsung Electronics Co., Ltd. Serveur connecté à un appareil de formation d'images et client, client, et procédé d'installation à distance du pilote de l'appareil de formation d'images
US9075627B2 (en) 2009-12-04 2015-07-07 Samsung Electronics Co., Ltd. Server connected to image forming apparatus and client, client, and method of remotely installing driver of image forming apparatus

Also Published As

Publication number Publication date
US20010056572A1 (en) 2001-12-27

Similar Documents

Publication Publication Date Title
EP1168163A1 (fr) Procédé permettant l'installation d'un logiciel dans un ordinateur client
KR100318977B1 (ko) 유저 스테이션에서 실행하는 애플리케이션에 대한 유저 구성의 실행 환경을 관리하는 방법, 장치 및 그 컴퓨터 프로그램 제품
US8732182B2 (en) System and method for launching a resource in a network
US6195678B1 (en) Remote resource management system for automatically downloading required files from application server depending on contents of selected files on requesting computer
US6681392B1 (en) Method and apparatus for remote peripheral software installation
US6871221B1 (en) Method and apparatus to manage network client logon scripts using a graphical management and administration tool
US6282709B1 (en) Software update manager
US7363374B2 (en) Method and system for fault-tolerant remote boot in the presence of boot server overload/failure with self-throttling boot servers
US7120684B2 (en) Method and system for central management of a computer network
US6842766B2 (en) Client side caching of printer configuration
US20080222160A1 (en) Method and system for providing a program for execution without requiring installation
EP1669858A2 (fr) Procédé et système pour fournir un système d'exploitation commune
US6651095B2 (en) Methods, systems and computer program products for management of preferences in a heterogeneous computing environment
US20110271226A1 (en) Integrated Icon View in a Server-Based Computing Environment
AU2002309834A1 (en) Operating system abstraction and protection layer
EP1419437A1 (fr) Couche d'abstraction et de protection de systeme d'exploitation
EP1331556B1 (fr) Environnement d'ordinateur basé sur un serveur
US8973017B2 (en) Productivity application management
WO2001011466A2 (fr) Gestionnaire de telechargement
Cisco Installing and Uninstalling the Cisco Dialout Utility
Cisco Installing and Uninstalling the Cisco Dialout Utility
KR100431049B1 (ko) 서버에서 클라이언트 컴퓨터에 소프트웨어를 원격설치하기 위한 방법 및 시스템
KR100631784B1 (ko) 컴퓨터 바이러스로부터의 감염을 방지하기 위한 시스템 및방법
EP1720098A1 (fr) Système incluant un exécuteur permettant l'exécution de l'application du logiciel sur une plate-forme d'ordinateur incompatible
Murray et al. Effective use of individual user profiles with software distribution

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

Kind code of ref document: A1

Designated state(s): DE FR GB

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

AKX Designation fees paid
REG Reference to a national code

Ref country code: DE

Ref legal event code: 8566

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

17P Request for examination filed

Effective date: 20020711

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20070315

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20080402