(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2010/0095294 A1
`(43) Pub. Date:
`Apr. 15, 2010
`Yamada
`
`US 2010.0095294A1
`
`(54) INFORMATION PROCESSING METHOD AND
`PROGRAM
`
`Koji Yamada, Yokohama-shi (JP)
`(75) Inventor:
`Correspondence Address:
`FITZPATRICK CELLAHARPER & SCINTO
`1290 Avenue of the Americas
`NEW YORK, NY 10104-3800 (US)
`(73) Assignee:
`
`CANON KABUSHIK KAISHA,
`Tokyo (JP)
`
`(21) Appl. No.:
`
`12/531,889
`
`May 28, 2008
`
`PCT/UP2008/06O2SO
`
`(22) PCT Filed:
`(86). PCT No.:
`S371 (c)(1),
`Sep. 18, 2009
`(2), (4) Date:
`Foreign Application Priority Data
`
`(30)
`
`Jun. 12, 2007 (JP) ................................. 2007-155374
`
`
`
`
`
`Publication Classification
`
`(51) Int. Cl.
`G06F 9/445
`
`(2006.01)
`
`(52) U.S. Cl. ........................................................ T17/174
`
`ABSTRACT
`(57)
`Commands such as installation operation and launch program
`commands need to be executed after appropriately Switching
`between an administrator account and another account, for
`each command, when an installer constituting a program for
`readily performing installation operations collectively for a
`plurality of pieces of software or the like is launched. When
`an installer is launched in the present invention, process-to
`process communication is secured between the processes of
`an administrator account and a user account, and an account
`to execute a command included in the installer is determined
`in the process of the administrator account. If the determina
`tion result indicates that the account to execute the command
`is the user account, the command is executed in the process of
`the user account rather than in the process of the administrator
`acCOunt.
`
`OK TO LAUNCH
`BROWSER UNDER
`ADMINISTRATOR
`ACCOUNT
`
`PROCESS
`TO-PROCESS
`COMMUNICATION
`CHANNEL
`SECURED?
`
`SECURE PROCESS-TO-PROCESS
`COMMUNICATION CHANNEL
`
`LAUNCHADMINISTRAOR
`ACCOUNT INSTALLER
`
`ADMINISTRATOR
`ACCOUNTINSTALLER
`CLOSED?
`
`FROMADMINISTRATOR
`ACCOUNT
`NSTALLEB
`
`
`
`
`
`
`
`
`
`NOTIFYOPERATION RESULT
`TO ADMINISTRATOR
`ACCOUNT INSTALLER
`
`SO6
`
`ironSource Exhibit 1004
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 1 of 14
`
`US 2010/0095294 A1
`
`F. G. 1
`
`HO8
`
`PRINTER
`
`HO1
`
`HO2
`HO3
`HO7
`KEYBOARD Gray) INTERFACE
`
`PRINTER
`
`HO4
`
`H05
`
`H06
`
`HO
`
`H10
`
`HARD DISK
`
`CD-ROM
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 2 of 14
`
`US 2010/0095294 A1
`
`LOGINACCOUNT
`INSTALLER START
`S1101
`
`SECURE PROCESS-TO-PROCESS
`COMMUNICATION CHANNEL
`
`-
`
`--
`
`LAUNCHADMINISTRATOR L
`ACCOUNT INSTALLER
`
`S1102
`
`ADMINISTRATOR
`ACCOUNT INSTALLER
`CLOSED?
`
`YES
`
`
`
`
`
`
`
`
`
`
`
`
`
`OK TO LAUNCH
`BROWSER UNDER
`ADMINISTRATOR
`ACCOUNT
`
`YES
`
`S1212
`PROCESS
`TO-PROCESS
`COMMUNICATION
`CHANNEL
`SECURED?
`
`OPERATION
`REQUEST RECEIVED
`FROMADMINISTRATOR
`ACCOUNT
`NSTALLEB
`YES
`
`S1213
`
`LAUNCHBROWSER
`
`S1214 G3)
`
`w
`w
`N
`
`Y.
`
`TRANSFERLOGIN
`ACCOUNT OPERATION
`
`NOTIFYOPERATION RESULT
`TO ADMINISTRATOR
`ACCOUNT INSTALLER
`
`a
`
`WAIT FOR
`OPERATION RESULT
`
`S1106
`
`S1215
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 3 of 14
`
`US 2010/0095294 A1
`
`
`
`O as a a
`
`-
`
`-
`
`-
`
`-
`
`-
`
`ADMINISTRATOR
`ACCOUNT INSTALLER F G. 2B
`START
`
`
`
`ACOUREINSTALLATION
`OPERATION COMMAND
`
`G2)
`G3)
`
`S1202
`YES
`BROWSER
`LAUNCH OPERATION
`NO
`S12O3
`INSTALLER
`LAUNCH OPERATION
`
`
`
`YES
`
`S1204
`LAUNCH INSTALLER
`
`
`
`S1205
`FILE1 DIRECTORY
`OPERATION?
`
`
`
`
`
`OPERATION ON
`FILE1 DIRECTORY
`
`
`
`OPERATION ON REGISTRY
`
`S12O7
`
`REGISTRY
`OPERATION?
`
`
`
`
`
`
`
`
`
`ERROR
`DISPLAY
`
`
`
`
`
`OCCURRED
`IN INSTALLATION
`QPERAT.9)
`NO
`
`INSTALLATION
`OPERATIONS ENDED
`YES
`
`GO- a
`
`-
`
`-
`
`-
`
`-
`
`END
`
`

`

`Patent Application Publication
`
`Apr. 15
`
`2010
`
`Sheet 4 of 14
`
`US 2010/0095294 A1
`
`
`
`
`
`ENITIÑO NOLIWHEdO
`
`
`
`TWNHEIXE HON[\WT
`
`
`
`ÅHO LOETHIO EI WEHO
`
`
`
`,\!HO LOEHIO E HETEC]
`
`
`
`EWW.NET!—; E0NWHO
`
`
`
`€ "5) | H
`
`
`
`
`
`
`
`HOLVH1SINIWGW | EWWN Å HOLOBHICIELWE HO | \HOLOBHIG ELVE8090?GWO
`
`w0IGWO | |
`
`
`
`HESMO HE HONTAWT| 03C]WO
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 5 of 14
`
`US 2010/0095294 A1
`
`F. G. 4A
`
`YES
`
`S1301
`WEBBROWSER
`RUNNING UNDER
`ADMINISTRATOR
`ACCOUNT2
`
`
`
`
`
`ENABLE PROTECTED MODE
`
`DISABLE PROTECTED MODE
`
`S13O2
`
`DISPLAY HOMEPAGE
`
`S1304
`
`
`
`WAIT FOR USER INPUT
`
`S1305
`
`YES
`
`S1312
`
`DOWNLOAD PAGE OF URL
`
`END PROGRAM?
`
`YES
`
`DISPLAY
`DOWNLOADED PAGE
`
`S1313
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 6 of 14
`
`US 2010/0095294 A1
`
`F. G. 4B
`
`S1321
`
`URL SPECIFIES
`EXECUTABLE FILE
`
`
`
`
`
`S1322
`PROTECTED
`MODE ENABLED?
`
`
`
`
`
`
`
`
`
`
`S1331
`
`URL
`SPECIFIES
`FILE OPENED USING
`EXTERNAL
`PROGRAy
`
`DISPLAY EXECUTION
`AUTHORIZATION
`CONFIRMATION SCREEN
`
`PROTECTED
`MODE ENABLED?
`
`DISPLAY EXECUTION
`AUTHORIZATION
`CONFIRMATION SCREEN
`
`WAT FOR EXECUTION
`CONFIRMATION INPUT
`
`
`
`
`
`EXECUTE FILE
`
`DOWNLOAD FILE OF URL
`
`
`
`LAUNCH EXTERNAL
`PROGRAM & OPEN FILE
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 7 of 14
`
`US 2010/0095294 A1
`
`F. G. 5A
`S2101
`S2102
`
`LOGENACCOUNT
`
`SEQUREPROCESSTQPROCESS
`COMMUNICATION CHANNEL
`LAUNCHADMINISTRATOR
`ACCOUNT INSTALLER
`
`G8)
`
`ADMINISTRATOR
`ACCOUNT INSTALLER
`CLOSED?
`
`YES
`
`END
`
`
`
`S2105 G)
`
`OPERATION
`REQUEST RECEIVED FROM
`ADMINISTRATOR ACCOUNT
`NSTALLER2-1---- s
`YES
`BROWSER LAUNCH
`OPERATION?
`NO
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`S2106
`
`YES
`
`LAUNCHBROWSER
`
`S2108
`
`OPERATION ON FILE1 DIRECTORY
`
`S2110
`
`YES
`
`OPERATION ON REGISTRY
`
`S2112
`
`ES
`Y
`
`LAUNCHRESIDENT PROGRAM
`
`S2111 s RESIDENT
`
`S21 O7
`
`FILE1 DIRECTORY
`OPERATION?
`NO
`
`S2109
`REGISTRY OPERATION?
`
`NO
`
`PROGRAMLAUNCH
`OPERATION?
`NO
`
`S2113
`DEFAULT
`YES-PRINTER SEROPERATION
`S2114
`SET DEFAULT PRINTER
`NO
`S2115
`NOTIFYOPERATION RESULT TO
`ADMINISTRATOR ACCOUNTINSTALLER
`
`-0)
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 8 of 14
`
`US 2010/0095294 A1
`
`F. G. 5B
`
`---
`
`r
`
`INSTALLER START
`
`---
`
`S22O1
`
`(8)
`
`
`
`
`
`
`
`NO
`
`S2203
`OK TO LAUNCH
`BROWSER UNDER
`ADMINISTRATOR
`ACCOUNT?
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`WRITE TO
`SYSTEMAREA?
`
`OPERATION ON FILE1 DIRECTORY
`
`S2209
`
`WRITE TO
`SYSTEM AREA?
`
`
`
`
`
`REGISTRY OPERATION?
`
`OPERATION ON REGISTRY
`
`RESIDENT
`PROGRAMLAUNCH
`OPERATION?
`
`PROGRAM
`RESIDES UNDER LOGIN
`ACCOUNT
`
`LAUNCHRESIDENT PROGRAM
`
`
`
`ACOUREINSTALLATION
`OPERATION COMMAND
`S22O2
`NO
`
`BROWSER
`LAUNCHOPERATION?
`
`LAUNCHBROWSER
`
`FILE1 DIRECTORY
`OPERATION?
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 9 of 14
`
`US 2010/0095294 A1
`
`F. G. 5C
`
`
`
`
`
`
`
`YES
`
`S2217
`G)- or NSS
`
`
`
`
`
`
`
`
`
`OPERATION
`S2218
`
`
`
`WAIT FOR
`
`GO-1 'E' LAUNCH INSTALLER
`
`DEFAULT
`PRINTER SETTING
`OPERATION
`NO
`
`INSTALLER S2215
`LAUNCH
`OPERATION
`p
`NO
`
`
`
`S2220
`
`
`
`ERRORDISPLAY
`
`
`
`
`
`S2219
`
`ERROR
`OCCURRED IN
`INSTALLATION
`QPERATIO)
`
`S2221
`
`ALL
`INSTALLATION
`OPERATIONS
`ENDED?
`
`NO
`
`G)------
`
`END
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 10 of 14
`
`US 2010/0095294 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`F. G. 6
`
`START
`
`S2301
`
`END PROGRAM?
`
`YES
`
`NO
`
`RECEIVESCAN START
`INSTRUCTION FROMDEVICE
`
`S2302
`
`S23O3
`
`S
`YE
`
`S2305
`
`S2306
`
`END
`
`

`

`Patent Application Publication
`
`4
`
`US 2010/0095294 A1
`
`EoBmmaEfimoEmmamszzEosmmaEmma#5593madeEm,$05meE55mszzEosmmaE58Emmszzficwwzéo mgmszzEZBEEmma>EmammEmma%mEobmmamszzE:mszzmmégMEmmdo
`
`
`
`
`
`
`
`
`
`
`
`
`5.0.“.
`_>_<m_oomn_mm._..<._.wz_.22.“.me10235m2<zm.__n_m._m<._.30mxmmm._._<.rmz_102355820
`
`
`
`
`
`
`
`
`mmwgommmm>>._<zmm_.xm10235.E:mmw>>0mm1023505920
`
`
`
`
`
`
`
`..w.__n_ECOm=2<zm_.__n_>n_Oom2“.>n_Oo«08.20
`
`
`
`
`
`m_z_._._bozO_._.<mmmOmmEE<m<mm_>_<zQz<§§oooz<_>=>_oo
`
`
`
`
`
`E<mOOmm._.zwn=mmEIoz:<.__>_<moom_n_.rzmemm10235@0820 m_>_<zm.__u_m._m<l50mxm
`
`
`
`
`
`
`
`
`mmHzEm53¢.meEmm_>_<zmm._.z_mn_mmHzEm53.1meEm2820
`
`
`
`
`
`
`
`
`m=>_<zm.__n_Emmam2“.mhmjmo,8820
`
`$5552
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 12 of 14
`
`US 2010/0095294 A1
`
`LOGINACCOUNT
`INSTALLER START
`
`SECURE PROCEss-To-PRocess h-S3101
`COMMUNICATION CHANNEL
`
`LAUNCHADMINISTRATOR
`ACCOUNT INSTALLER
`
`S31 O2
`---------
`
`ACQUIREINSTALLATION
`OPERATION COMMAND
`
`S31 O3
`
`S3104
`
`BROWSER
`LAUNCH OPERATION
`
`LAUNCHBROWSER
`
`S31 O7
`FILE1 DIRECTORY
`OPERATION?
`
`
`
`OPERATION ON FILE1 DIRECTORY
`
`NO
`
`REGISTRY
`OPERATION?
`
`OPERATION ON REGISTRY
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`S3105
`
`OKTO
`LAUNCHBROWSER
`UNDERADMINISTRATOR
`ACCOUNT
`
`YES
`
`
`
`
`
`
`
`WRITE TO
`SYSTEM AREA?
`
`WRITE TO .
`SYSTEM AREA?
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 13 of 14
`
`US 2010/0095294 A1
`
`(14)
`
`(5)
`
`F. G. 8B
`
`
`
`S3113
`RESIDENT
`PROGRAMLAUNCH
`OPERATION?
`
`YES
`
`S3114
`PROGRAM
`RESIDES UNDER
`LOGIN AgCOU
`
`NO
`
`
`
`
`
`
`
`LAUNCHRESIDENT
`PROGRAM
`
`S316
`DEFAULT
`PRINTER SETTING
`OPERATION
`
`
`
`SETDEFAULT PRINTER
`
`S3119
`
`S3118
`INSTALLER
`LAUNCH
`OPERATION
`
`
`
`S3121
`
`OCCURRED
`- NINSTALLATION
`QPERATION
`
`TRANSFER
`ADMINISTRATOR
`ACCOUNT OPERATION
`
`ar
`
`WAIT FOR
`OPERATION RESULT
`S3 120
`
`G9)
`
`S3122
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`S3123
`
`
`
`NO
`
`
`
`ALL
`INSTALLATION
`OPERATIONS
`ENDED?
`YES
`
`END
`
`Y--------
`
`

`

`Patent Application Publication
`
`Apr. 15, 2010 Sheet 14 of 14
`
`US 2010/0095294 A1
`
`---
`
`ADMINISTRATOR ACCOUN
`
`F. G. 8C
`
`-
`
`s
`
`YES
`
`1OGINACCOUNT
`INSTALLER CLOSED?
`
`S32O1
`
`NO
`
`
`
`S3202
`OPERATION
`REGUEST RECEIVED
`NO
`FROM LOGINACCOUNT
`INSTALLER2
`-1
`YES
`S3203
`BROWSER LAUNCH
`OPERATION?
`NO
`
`YES
`
`S3204
`
`LAUNCHBROWSER
`
`END
`
`G).
`
`
`
`
`
`
`
`
`
`S3205
`FILE1 DIRECTORY
`OPERATION?
`NO
`
`S32O7
`
`YES
`
`S3206
`
`OPERATION ON FILE1 DIRECTORY
`
`5 REGISTRY OPERATION?
`NO
`
`S3208
`YES
`OPERATION ON REGISTRY
`
`S3209
`
`RESIDENT
`PROGRAM LAUNCH
`OPERATION?
`NO
`
`
`
`ES
`Y
`
`S3210
`
`LAUNCHRESIDENT PROGRAM
`
`S3211
`T
`NSTALLER
`YES
`LAUNCHOPERATION?
`S3212
`O
`- LAUNCH INSTALLER
`S3213 .
`NO
`NOTIFYOPERATION RESULT TO
`ADMINISTRATOR ACCOUNT INSTALLER
`
`(9)
`
`

`

`US 2010/0095294 A1
`
`Apr. 15, 2010
`
`INFORMATION PROCESSING METHOD AND
`PROGRAM
`
`TECHNICAL FIELD
`0001. The present invention relates to software installation
`operations, and more particularly to installation operations in
`an operating system (OS) in which authorities differ between
`an administrator account and other accounts such as a general
`user account.
`
`BACKGROUND ART
`0002 With operating systems (OS) such as Microsoft
`Windows NT (registered trademark) (including its successors
`such as Windows 2000/XP/Vista (all registered trademarks)),
`and UNIX (registered trademark), an administrator account
`and a general user account can be administered separately.
`Here, an account is an ID for when using a computer. Each
`account is provided with authorities for using the computer.
`For example, an administrator account is provided with
`execution authorities with respect to various operations. Such
`as changing files and registries affecting the entire system. On
`the other hand, a general user account has limited execution
`authorities, and is not provided with authorities for executing
`operations such as changing files and registries affecting the
`entire system. Therefore, since software cannot be installed
`on a system with a general user account, an administrator
`account is required to perform the installation operation.
`0003. Even the UNIX (registered trademark) operating
`system has a special account called a root account. The root
`account is provided with authorities to change files affecting
`the entire system, and Such authorities are not provided to
`other accounts.
`0004 Passwords are associated with accounts, and when
`using a computer, the user enters an account name and a
`password, and performs authentication with the system. This
`is called login or logon. Login is allowed if the password
`associated with the account name is correctly entered, thereby
`enabling the user to use the computer. The account entered
`when logging in is generally called a login account. The login
`account may be an administrator account or a general user
`account. If logging in with an administrator account, the login
`account is the administrator account, which implies that the
`user will use the computer as an administrator. If logging in
`with a general user account, the login account is the general
`user account, which implies that the user will use the com
`puter as a non-administrator.
`0005. Further, in order to perform strict account adminis
`tration in Such operating systems, Sub-processes also Succeed
`authorities. In other words, when a program run under an
`administrator account launches a separate program, that pro
`gram is also run under the administrator account. Conversely,
`when a program run under a general user account launches a
`separate program, that program is also run under the general
`user account. Heretofore, a program run with a given account
`could not execute the program of a separate account without
`a password being entered.
`0006. On the other hand, the existence of “malicious soft
`ware' following the spread of personal computers and the
`Internet is problematic. An example of this is when software
`is installed simply as a result of the user accessing a homep
`age, or when software different from a nominal program is
`installed when a program attached to an email is run. Such
`software acts maliciously to send the user's files over the
`
`Internet without the user's knowledge or delete the user's
`local files, and has become a prevalent social problem.
`0007 Even with a conventional OS, the user merely
`needed to ensure to access the Web and view emails when
`logged in with a general user account, and to install software
`after logging in with an administrator account. This was
`enough to prevent "malicious Software' from being automati
`cally installed simply as a result of the user accessing a
`homepage or executing an attached file.
`0008. However, users often log in as an administrator
`account with little restrictions, and use the computer as an
`administrator. Therefore, the installation of malicious soft
`ware is not prevented. Also, it is conceivable that users are
`themselves not aware of whether or not their account is an
`administrator account or some other account.
`0009. With patent document 1 (Japanese Patent Laid
`Open No. 2002-5 17853), processing is normally performed
`under a general user account oran administrator account with
`a restricted token. It has also been proposed to restrict opera
`tions by providing what were originally administrator
`authorities to a program when the program is run. An admin
`istrator account with a restricted token is an account having
`the same ID as an administrator account, but with reduced
`authorities.
`0010 For example, in a given OS, even if the user logs in
`with an administrator account, the account will be treated as
`an administrator account whose authorities are somewhat
`restricted, and confirmation will always be required when
`executing operations that change the system. Operations will
`not be executed with the true administrator account until the
`user agrees to this. Similarly, even if the user logs in with a
`general user account, an account name and password prompt
`screenwill be automatically displayed when executing opera
`tions that changes the system and operations will be tempo
`rarily executed under the administrator account.
`0011. According to this method, confirmation is required
`before performing an operation that alters the system such as
`an installation operation, thereby enabling the user to reject
`the operation.
`0012. Also, in another given OS, assume that a special
`account can be provided for a given operation. By only pro
`viding authorities related to printing to a resident program
`(daemon) related to printing, for example, the system also
`cannot be altered when there is a bug in the resident program
`or the resident program related to printing is illegally
`accessed.
`0013. In recent years, a great deal of software has been
`developed following the spread of personal computers (PCs),
`and electrical appliances such as digital cameras and printers
`now typically bundle with plural pieces of software. Electri
`cal appliances that interface with PCs may come with overten
`pieces of software when it is purchase.
`0014 Software called a master installer (or installer) is
`typically provided to avoid complication of the software
`installation procedures due to the increased number of pieces
`of software. The master installer is support software for
`sequentially running a plurality of Software installers, and
`allowing the user to perform all of the installation operations
`as if installing one piece of Software.
`0015. However, installing software takes time and effort if
`the administrator account name and password prompt screen
`is displayed every time the installer is launched, as with patent
`document 1. Therefore, the possibility arises of not being able
`to adequately fulfill the original objective of the master
`
`

`

`US 2010/0095294 A1
`
`Apr. 15, 2010
`
`installer, which is to provide simple batch installation with
`minimum effort on the part of the user.
`0016. If the master installer is itself run under an admin
`istrator account, the administrator account name and pass
`word prompt screen is displayed only once, but other prob
`lems arise in this case.
`0017. One such problem occurs when the master installer
`is used to execute a program whose operating mode differs
`depending on whether the program is run with an administra
`tor account execution unit (e.g., process under the control of
`an administrator account) or with a general user account
`execution unit (e.g., process under the control of a general
`user account). For example, assume the default web browser
`in a given OS is run under a general user account execution
`unit or the like. Then, if different software from the browser
`needs to be run in order to open files on the Internet, a high
`security mode that prevents this will be enabled. Also, when
`the web browser is run under an administrator account, this
`high security mode will be disabled. In other words, it will be
`possible to freely open files on the Internet by executing
`different software from the browser.
`0018. Because the master installer is operated under an
`administrator account, this high security mode will be dis
`abled if, for example, a given browser is launched from the
`master installer execution unit, given that the browser is oper
`ated under an administrator account. The launching of a
`browser for performing user registration to web services or
`the like in customer services, for example, is given as an
`example of an operation performed using a web browser
`provided by a master installer. Administrator authorities are
`not particularly necessary with regard to user registration to
`web services or the like. In other words, if the aforementioned
`launching of a browser is performed from a master installer,
`despite administrator authorities not being particularly nec
`essary, the security level of the user's computer is lowered as
`a result.
`0019. Further, different problems occur in the case where
`the login account is a general user account. For example,
`assume a resident program exists that receives data from a
`scanner and saves the received data in a user default image
`data folder. Typically, Image data folders are administered per
`account, and configured so that the image data folders of
`separate accounts cannot be seen. If this resident program is
`operated under the login account, the resident program saves
`the scan data to an image data folder of the login account.
`However, if the accounts are temporarily switched so that the
`resident program is operated under an administrator account,
`the scanner data will Subsequently be stored to an image data
`folder of the administrator account. Therefore, a general user
`constituting the login user becomes unable to access this scan
`data. In other words, this problem will arise when a resident
`program such as this is run in the case where a master installer
`operates the resident program as an administrator account in
`order to perform an installation operation.
`0020. As a similar example, operating systems have con
`ventionally been provided with a function enabling a default
`printer to be set. This setting is for determining a printer driver
`to be chosen by default when the user performs printing, and
`can also be set separately for each account. In the case where
`the master installer installs the printer driver, the master
`installer, after installing the printer driver, sets the installed
`printer driver as the default printer. However, if the master
`installer is run under an administrator account, this will not
`result in a default printer being set in the general user account
`
`constituting the login account. In other words, when the user
`installs a printer driver using the master installer, it is only
`possible to set the default printer of the administrator account,
`not his or her own login account which actually needs to be
`Set.
`
`DISCLOSURE OF INVENTION
`
`0021. Therefore, an object of the present invention is to
`provide an information processing method that enables com
`mands Such as installation operation and launch program
`commands to be executed after appropriately Switching
`between an administrator account and another account, for
`each command, when an installer is launched, and a computer
`program for realizing the information processing method.
`0022. In view of the above problems, an information pro
`cessing method of the present invention in an information
`processing apparatus in which an administrator account and a
`user account with more limited authorities in the information
`processing apparatus than the administrator account are reg
`istered, and that executes a command included in an installer
`in a process of each account, includes the steps of determin
`ing, in the process of the administrator account, an account to
`execute the command included in the installer, and executing,
`if the account to execute the command included in the
`installer determined in the determining step is the user
`account, the command included in the installer in the process
`of the user account, rather than in the process of the admin
`istrator account.
`0023. Also, a computer program of the present invention is
`a computer-executable program for providing the informa
`tion processing method.
`0024. Further features of the present invention will
`become apparent from the following description of exem
`plary embodiments with reference to the attached drawings.
`
`BRIEF DESCRIPTION OF DRAWINGS
`
`0025 The accompanying drawings, which are incorpo
`rated in and constitute a part of the specification, illustrate
`embodiments of the invention and, together with the descrip
`tion, serve to explain the principles of the invention.
`0026 FIG. 1 shows a hardware configuration diagram of
`an information processing apparatus in the present invention.
`0027 FIGS. 2A and 2B show flowcharts based on process
`ing steps of the information processing apparatus when a
`master installer is run in an Embodiment 1.
`0028 FIG.3 shows an exemplary command classification
`table in Embodiment 1.
`0029 FIGS. 4A and 4B show flowcharts based on process
`ing steps of a web browser run in the information processing
`apparatus of Embodiment 1.
`0030 FIGS. 5A, 5B and 5C show flowcharts based on
`processing steps of the information processing apparatus
`when a master installer is run in an Embodiment 2.
`0031
`FIG. 6 shows a flowchart based on scan data save
`processing steps realized in the information processing appa
`ratus of Embodiment 2.
`0032 FIG. 7 shows an exemplary command classification
`table in Embodiment 2.
`
`

`

`US 2010/0095294 A1
`
`Apr. 15, 2010
`
`0033 FIGS. 8A, 8B and 8C show flowcharts based on
`processing steps of the information processing apparatus
`when a master installer is run in an Embodiment 3.
`
`BEST MODE FOR CARRYING OUT THE
`INVENTION
`
`First Embodiment
`0034 Preferred embodiments of the present invention will
`now be described in detail with reference to the accompany
`ing drawings. The following embodiments are not intended to
`limit the claims of the present invention.
`0035 Firstly, a first embodiment of a preferred master
`installer of the present invention will be described. The mas
`ter installer is a program for readily performing installation
`operations collectively for a plurality of pieces of software or
`the like. The main operations of the master installer are to
`copy files to prescribed locations, write registries, and launch
`separate installers. The master installer might also delete
`files, launch external programs, and launch resident pro
`grams. Further, operations provided by the master installer
`include a browser launch operation for performing user reg
`istration to web services or the like in customer services, in
`addition to operations such as installing printer drivers and
`peripheral software, and configuring default settings. Opera
`tions performed after launching this web browser do not need
`to be performed with a process under the control of an account
`with administrator authorities.
`0036. In the first embodiment, commands included in a
`master installer whose operating mode differ depending on
`whether the master installer is run with an administrator
`account execution unit (process under the control of an
`administrator account) or with a general user account execu
`tion unit (process under the control of a user account) will be
`described.
`0037. With commands such as software installation opera
`tion commands or a Launch Browser command for perform
`ing user registration to web services or the like, the master
`installer performs the respective commands after Switching
`between account execution units for executing the com
`mands. Specifically, by setting the Launch Browser com
`mand as a login account operation command, the launching of
`a web browser will be performed from the login account,
`thereby enabling the command to be executed with the high
`security mode of the web browser enabled.
`0038 Here, Internet Explorer 7 (IE7; registered trade
`mark), for example, is given as a web browser.
`0039. The master installer of the first embodiment defines
`installation operations as operation commands, and processes
`them sequentially. FIG.3 shows operation commands used in
`the first embodiment. A command number CMD101 is a
`Launch Installer command for giving the instruction for an
`external installation program launch operation. A command
`number CMD102 is a Copy File command for giving the
`instruction for a file copy operation. A command number
`CMD103 is a Delete File command for giving the instruction
`for a file delete operation. A command number CMD104 is a
`Rename File command for giving the instruction for a file
`name change operation. A command number CMD105 is a
`Create Directory command for giving the instruction for a
`directory create operation. A command number CMD106 is a
`Delete Directory command for giving the instruction for a
`directory delete operation. A command number CMD107 is a
`registry write command for instructing a registry write opera
`
`tion. A command number CMD108 is a Delete Registry com
`mand forgiving the instruction for a registry delete operation.
`A command number CMD201 is a Launch Browser com
`mand for giving the instruction for an external web browser
`launch operation.
`0040. These operation commands can take into account
`the content of an operation, such as the file copy destination or
`the registry write destination, before it is executed, and deter
`mine and set whether the content needs to be processed in an
`administrator account or a login account. Given that in the
`first embodiment only the web browser launch operation
`needs to be executed under a login account, the commands of
`the command numbers CMD101 to CMD108 are defined as
`commands to be processed as an administrator account, and
`the command of command number CMD201 is defined as a
`command to be processed as a login account.
`0041. A master installer program of the first embodiment
`storing various data such as the commands shown in FIG. 3 is
`stored in a storage medium such as a CD-ROM, for example,
`and is provided to a user together with an information pro
`cessing apparatus Such as a printer. The master installer is
`launched as a result of the user setting this CD-ROM in the
`information processing apparatus. Here, the master installer
`can be provided in advance from an Internet site or the like via
`a network or the like, and launched after having been down
`loaded to the information processing apparatus.
`0042. Next, a hardware configuration (FIG. 1) of an infor
`mation processing apparatus (PC, etc.) for realizing the mas
`ter installer in the first embodiment will be described.
`0043. A control unit H01 administers overall control in the
`information processing apparatus. The control unit H01 will
`subsequently be referred to as CPU H01. A keyboard H02
`inputs various data. A color display H03 displays image data
`stored in a RAM H05. A ROM H04 is a read-only memory
`which pre-stores control procedures for controlling the entire
`apparatus and other required information. The RAM H05 is a
`random-access memory which is used in running programs
`and as a work area. A hard disk drive H06 stores programs,
`together with having various data written thereto and read
`therefrom. A printer interface H07 has a printer H08 con
`nected thereto. A CD-ROM drive H10 reads out data from a
`CD-ROM. A data bus H09 has the CPU H01, the keyboard
`H02, the display H03, the ROM H04, the RAM H05, the hard
`disk drive H06, the CD-ROM drive H10 and the printer inter
`face H07 connected thereto, and is used for transferring vari
`ous data between these constituent elements. The hard disk
`drive H06 or CD-ROMs loaded in the CD-ROM drive H10
`will be collectively called external storage device or external
`storage medium, and store application programs, installers,
`printer drivers and the like. These various programs are
`loaded into the RAM H05 and run by the CPU H01.
`0044 FIGS. 2A and 2B are flowcharts based on process
`ing steps of the information processing apparatus when the
`master installer is run in the first embodiment. These process
`ing steps are realized by being executed in accordance with a
`program read by the CPU H01 of the information processing
`apparatus.
`0045. In the first embodiment, the master installer is con
`stituted by two installer, namely, a user account execution unit
`(hereinafter, login account installer) and an administrator
`account execution unit (hereinafter, administrator account
`installer). The user gives the instruction for execution of
`various operations under the login account. A login account
`as shown in the first embodiment indicates an account other
`
`

`

`US 2010/0095294 A1
`
`Apr. 15, 2010
`
`than an administrator account. That is, a user logs in as a
`“restricted’ administrator account (general user account),
`and launches the login account installer.
`0046 Steps S1101 to S1106 in FIGS. 2A and 2B are
`operations performed by the login account installer, and steps
`S1201 to S1218 are operations performed by the administra
`tor account installer. Firstly, the operations of the login
`account installer will be described, followed by a description
`of the operations of the administrator account installer.
`0047. The login account installer executes step S1101
`when the processing is started. Step S1101 is an operation to
`secure a communication channel with the process of the
`administrator account installer. Step S1101 enables commu
`nication to be secured between the operation processes of the
`accounts. In the first embodiment, a “named pipe' provided
`with the Windows NT (registered trademark) operating sys
`tem is used as the method of inter-process communication.
`Needless to say, the present invention may use any method of
`inter-process communication. Inter-process communication
`can also be performed using methods such as message
`queues, signals, and shared memory, for example.
`0048. Once step S1101 is executed, the processing is pro
`ceeded to step S1102, and the administrator account installer
`is launched. If the login account is a general user account, the
`account name and password of the administrator account
`installer need to be entered when it is launched. If the login
`account is a “restricted’ administrator account in the
`Microsoft Windows Vista (registered trademark) operating
`system, fo