Manual en
Manual en
MSI Installer
Installation Guide
Contents
1 Overview
1.1 About the MSI Installer ...................................................................... 1-1
1.2 Required System Environment ......................................................... 1-1
2 Workflow
5 Other Operations
5.1 Uninstalling Software......................................................................... 5-1
5.2 Manually Updating Group Policies ................................................... 5-5
5.3 Outputting Event Logs.......................................................................5-6
5.3.1 Enabling Log Output ....................................................................... 5-6
5.3.2 Checking an Event Log ................................................................ 5-10
5.4 Displaying Group Policy Messages ................................................ 5-11
5.4.1 Enabling Messages ...................................................................... 5-11
MSI Installer i
About This Product
The MSI Installer is a program for installing software distributed in ".msi" file
format. Our company normally distributes its software in exe file format, but
some of our software is distributed in msi file format instead. By using the
MSI Installer, automatic distribution and automatic installation of software
from a server to a client computer is possible in an Active Directory
environment.
About This Document
This installation guide explains how to automatically distribute software to a
client computer using the MSI file installer and Active Directory, and install
this software automatically without the user needing to do anything. This
document is meant for Active Directory administrators. For information on
how to install other software, refer to that software's user guide.
Usage Environment
The following system environments are used for the explanations in this
document.
- Server: Computers with "Microsoft Windows Server 2008 R2"
- Client Computer: Computers with "Microsoft Windows 7"
Dialog boxes
The dialog boxes shown in this manual are those that appear in Windows 7
and Windows Server 2008 R2.
!
Detail
The dialog boxes that appear in this document may differ from those that
appear on your PC, depending on the installed devices, specified
settings, and PC that you are using.
MSI Installer ii
Note
Unauthorized reproduction, translation or duplication of this document,
whether in its entirety or in part, is strictly prohibited.
The contents of this document are subject to change without notice.
Copyright © 2011 KONICA MINOLTA, INC. All rights reserved.
1 Overview
1.1 About the MSI Installer
By linking the MSI file installer and Active Directory server, software can be
automatically distributed from the server to a client computer and installed.
Because installation/uninstallation is done automatically when the client
computer is started up, no installation/uninstallation operations are required.
By configuring the distribution settings for multiple programs, the total
amount of administration time needed to install the software can be reduced.
MSI files can also be installed directly using a client computer.
2 Workflow
This section will explain the workflow up to software installation.
Operations are broadly categorized into server procedures and client
computer procedures.
Preparing Software Distribution (p. 3-5) Preparing VC Runtime Distribution* (p. 3-26)
Complete
*VC Runtime must be installed in order to distribute some MSI files. When
distributing and installing VC Runtime, follow the procedure in Preparing VC
Runtime Distribution. Refer to "Preparing VC Runtime Distribution" on
page 3-26 for details on software that requires VC Runtime.
2
Note
32-bit MSI files have x86 on the end.
2
Note
64-bit MSI files have x64 on the end.
MSI file for both 32-bit and
64-bit DirectPrint_Setup_en.msi
Software Language
2
Note
MSI files for both 32-bit and 64-bit do not contain the
CPU type in their name.
List of Languages
1 Place the MSI file of the distributed software in all of the shared folder
distribution points.
– Create a new folder distribution point into which the MSI file can be
placed.
– If MSI files of multiple languages are being placed in the distribution
point, the software of the language used in the OS on the client
computer will be installed. If the OS language on the client
computer does not exist in the placed MSI file, the English version
of the software will be installed.
– If both 32-bit and 64-bit client computers are used, place both the
32-bit and the 64-bit MSI files in the distribution point. Either the 32-
bit or the 64-bit version of the software will be installed, depending
on the bit version of the OS on the client computer.
– The 64-bit version of VC Runtime is required for distributing some
MSI files. Make sure that the MSI file is placed when also
distributing VC Runtime. All related files must be placed when
placing files with VC Runtime, not only the MSI file. For information
on how to obtain VC Runtime, refer to "Preparing VC Runtime
Distribution" on page 3-26.
2
Note
When distributing VC Runtime, create a new group policy object for VC
Runtime separate from the software.
Procedure
8 Create an Active Directory user for the group policy object (GPO) in the
organizational unit (OU) or transfer an existing user to the OU.
– In Box Operator, you must create an applicable Active Directory
Computer or transfer an existing computer beforehand.
– Right-click [ads.local (or the default domain)] and select [Active
Directory User and Computers].
10 Enter the information of the user for the distribution, and click [Next].
12 Click [Finish].
2
Note
Administrator privileges for the client computer must be given to the
Active Directory user in order to properly distribute some MSI files. If the
administrator privileges were not given to the Active Directory user, add
them. Refer to "Adding Administrator Privileges" on page 4-3 for
information on how to add the administrator privileges.
2
Note
When upgrading a previous version of the software that has already been
distributed, refer to "Configuring a Group Policy Object (Upgrade)" on
page 3-19.
6 Select the MSI file placed in the shared folder distribution point, and
click [Open].
– Designate the path to the MSI file using a network path (\\<Name of
server>\<Name of shared folder>\<Name of MSI file>). Files cannot
be obtained on a client computer with a local path.
10 Click [Advanced].
2
Note
If the software was installed using a setup file in exe file format, Active
Directory cannot be used to distribute software in order to upgrade a
previous version of the software.
The software can be upgraded only if the previous version of the software
was distributed in MSI file format.
6 Select the [Upgrades] tab and check [Required upgrade for existing
packages].
7 Click [Add].
9 Select [Package can upgrade over the existing package] and click [OK].
2
Note
For 64-bit Box Operator version 3.2.08000 and later, the procedure in
"Preparing VC Runtime Distribution" is not necessary.
2
Note
If the above URL no longer works, search for the package from the home
page of the "Microsoft Download Center".
Procedure
1 Create a folder with whatever name you like directly on the C drive, and
download "vcredist_x64.exe" into it.
– In this example, a folder with the name "VC" is created.
– Do not use double-byte characters in the folder name.
3 Designate the location where the file will be expanded and click [OK].
– Designate the VC folder.
5 The User Account Control dialog box will be displayed. Click [OK].
– It may not be displayed, depending on the server environment.
6 Designate the location where the expanded file will be saved and click
[OK].
– Designate the "VC" folder.
2
Note
The client computer must be on an Active Directory domain for the
automatic installation to work. Refer to the Active Directory manual for
information on how to join a domain.
2
Note
Some software requires the system to be restarted during the initial login,
after which the installation will finish during the second login.
2
Note
After the software has been distributed, it will not install when you are
logged in. You must restart the client computer and log in again.
2
Reminder
Installation-related messages are not normally displayed during the
installation. However, messages may be displayed if the group policy
settings are changed on the server. Refer to "Displaying Group Policy
Messages" on page 5-11 for details.
2
Note
For 32-bit/64-bit Box Operator version 3.2.08000 and later, the
procedure in "Adding Administrator Privileges" is not necessary.
2
Note
The client computer must be on an Active Directory domain before you
add administrator privileges.
Procedure
1 Log on to the client computer using a local user account that has
administrator privileges.
– Do not log on using an Active Directory user account. Be sure to log
on to the client computer using a local user account that has
administrator privileges.
6 In the "Enter the object names to select" box, enter the name of the
Active Directory user to add the administrator privileges to, and click
[Check Names].
– The "aduser01" Active Directory user is used as the example in this
explanation.
8 Confirm the Active Directory user name in the "Enter the object names
to select" box, and click [OK].
5 Other Operations
This section will explain how to uninstall software, manually update group
policies, and output event logs.
3 Under [Group Policy Objects], right-click [MSI (or the default group
policy object)], and select [Edit].
5 Right-click the software package you wish to uninstall, and select [All
Tasks] - [Remove].
– The package will be removed from the list, and the software will be
uninstalled from the client computer the next time you log on.
– No user operations are required during the uninstallation, but it may
take some time until the logon finishes.
2
Note
The server will be overloaded if all client computers are updated at the
same time. As a general rule, apply the group policy alteration at an
update interval set in the Active Directory.
Procedure
3 Under [Group Policy Objects], right-click [MSI (or the default group
policy object)], and select [Edit].
2
Note
These messages will not be displayed if [Remove Boot/Shutdown
/Logon/Logoff status messages] is enabled for the group policy.
3 Under [Group Policy Objects], right-click [MSI (or the default group
policy object)], and select [Edit].