open mic “upgrade notes client using smart upgrade”€¦ · open mic “upgrade notes client...

1

Presenters :Rahul KumarJyutika Kathe

Open Mic

“Upgrade Notes Client using Smart Upgrade”

2

OPEN MIC LOTUS TEAMOPEN MIC LOTUS TEAM

● Soumitra Limaye – Lotus Support ● Facilitator for Open Mics

● Jyutika Kathe – Tech Support Engineer● Presenter

● Rahul Kumar – Tech Support Engineer● Presenter

● Hansraj Mali - Lotus Technical Advisor● Focussing on Notes/Domino, LotusLive

● Ranjit Rai - Lotus Technical Advisor● Focussing on Notes/Domino, LotusLive

3

AgendaAgenda

Introduction

Planning

Deploy

Troubleshooting

Useful Links

Q&A

4

IntroductionIntroduction● To automate the Client upgrade process

● Reduces the time, cost, and efforts involved in upgrading clients.

● Greater administrative control and flexibility over the upgrade process

● Various ways to track and troubleshoot the upgrade process.

Note : It is important to upgrade to the latest version of Lotus Notes and Domino because it can help your organization receive a high return on investment, potentially lower your cost of ownership, and help improve user productivity and business responsiveness.

5

PlanningPlanning

● Current Client environment

● Which client installation kits to be used?

● Domino environment and network configuration considerations

● Preparing your team for the upgrade

● Deploying Smart Upgrade

● Confirming successful upgrade of Notes Clients

6

Deployment TopologyDeployment Topology

● Centralized deployment topology

● Distributed deployment topology

7

Smart Upgrade Run As FeatureSmart Upgrade Run As Feature● For users who do not have the proper operating system rights to upgrade

their Notes client installations.

● First need to extract the files from the kit. e.g. notes_designer_admin852_w32en.exe. Specify the location.

8

Smart Upgrade Run As FeatureSmart Upgrade Run As Feature

Let “Extracting files” gets completed. You need to cancel the screen just next to these two screens.

9


You can see the extracted files at the location you specified.

10


● Use SUSetRunAsWizard.exe to create a install kit.

● Run SUSetRunAsWizard.exe from Notes program directory of one machine where Destination version already installed

11

Specify the user name( administrative access), password and Domain


12

Select “Store files into the SURunAs executable, creating a self-contained package


13

On the Account Information screen, if you select Create self-extracting package without using Username and Password then the fields gets grayed out.


14

You will have only first option available as below


15

If you select “Store files into the SURunAs executable, you will be prompted next with the ‘SUSetRunAs Wizard – Select Attachments’ screen. Select Add Files.


16

Browse to the location where you extracted the files. Select Open.


17

Select to point to setup.exe


18

If you reference an installation kit on a network path, the SUSetRunAs wizard asks for the UNC path to the installation executable (normally setup.exe)


19

Specify the correct path over there. Click on Check UNC Path to verify that the file is getting detected correctly.


20

● The most common parameters are /s /v"ALLUSERS=1 /qb+" in which /s makes the install silent, and /v would pass the ALLUSERS=1 and the qb+ command to the MSI installer.

● If multi-user upgrade, specify as below ( for example)

■ /s /v"ALLUSERS=1 SETMULTIUSER=1 /qb+"


21

Specify the location where the SURUNAS.exe will reside


22

It shows summary and results when selected file on a network share


23

It shows summary and results when selected store files onto SURunAs executable.


24

● After completion of SUSETRUNASWIZARD.exe, a SUSetRunasWizard.log is created in the directory where the SURUNAS.exe was generated.


Note : The Smart Upgrade RunAs utility (SURunas.exe) is not supported on Windows Vista and Windows 7. It has been proposed for R8.5.3 ( SPR # JSTN84CSC7 ).

File on a network share

Self-contained package

25

Chained Smart UpgradeChained Smart Upgrade

Smart Upgrade can be used to upgrade a series of different versions at one time

Test Case:

Objective : Upgrade Lotus Notes Client 7.0.2 to version 8.5.2 FP2

26

Steps:

● Create a Smart Upgrade database

● Defining the Smart Upgrade database in the server’s Configuration document

● Creating a Smart Upgrade kit document

● Create Desktop Policy to enforce Smart Upgrade

● Apply Desktop Policy


27

Create a Smart Upgrade database


28

Defining the Smart Upgrade database in the server’s Configuration document

■ In the Domino Administrator client, click the Files tab.

● Go to Smart Upgrade database, and choose Edit Copy as Application → →link.

● On the Configuration tab, open the Server Configurations view.→● Select the Configuration document for the server, and click Edit Configuration

● Paste it in Smart Upgrade Database Link field

● Save and close the Configuration document.


29

Pattern Matching

● Release 8.5.1* would match:

■ Release 8.5.1

■ Release 8.5.1FP1 OR FP2 ...

■ Release 8.5.1HFxxx

● Release 8.5.1FP? would match

■ Release 8.5.1FP1 OR FP2 ...

● Release 8.5.* would match:

■ Release 8.5.1

■ Release 8.5.2


30

Creating Smart Upgrade kit document

● Two kit document has to be created (In both the Kit documents choose Source configuration as Basic)

● One to upgrade from Release 7.0.2 to 8.5.2


31



32


In case using shared network option, kit document should be created as


33


Second to apply Lotus Notes Release 8.5.2 Fix Pack2


34



In case using shared network option for R8.5.2FP2, kit document can be created as

35

Desktop Policy to Enforce Smart Upgrade


36

Deployment

User Login, and will get the prompt as shown in the screenshot.

The message will differ depending upon the deadline specified in the desktop policy. This message shows once deadline has passed.

Time specified before Smart Upgrade deadline. This shows that 67days left for the deadline.


37

The installer will get downloaded on user's machine in Temp folder. The progress bar will appear at the bottom as shown below.


38

Once the package is downloaded, it gives the following pop up message.


39

Once the user selects “Yes”, Following message window Pops up


40

The following message will come while package is being extracted.


41

The installation will start. If you use parameter as qb+, it will show cancel button. If you use qb+ with exclamation as qb+!, it will not show cancel button. In case you use qn+ parameter you will not see progress bar.


42

Lotus 8.5.2 has been installed and you will get following window message. Click OK


43

Now the Smart Upgrade will automatically initiate the installation of 8.5.2 FP2 the moment you click OK


44

Once the 8.5.2 FP2 installation completes, you will get the following message. Simply Click OK


45

Lotus Notes 8.5.2 will start automatically (because of the “Restart” checkbox in the Kit document)


46

You can go to smart upgrade tracking database, and check the status of installation


47

How Smart Upgrade Report looks like


48

TroubleshootingTroubleshooting

Important files to be referred for troubleshooting Smart Upgrade issues :

● Smart upgrade tracking report database (LNDSUTR.NTF)● Lotusinstall.log● Notes.ini● Names.nsf (Personal Address Book)● Debug parameter (Debug_Smart_Upgrade=1)● Smart Upgrade log file

49

Common Problem

● User is not Prompted for Smart Upgrade

● When user initiates Smart Upgrade manually gets error as shown below

TroubleshootingTroubleshooting

50

Useful LinksUseful Links

Smart Upgrade RedBook:● http://www.redbooks.ibm.com/abstracts/redp4180.html

Configuring for Lotus Notes 8.5 Smart Upgrade on Linux for RPM or DEB● https://www-304.ibm.com/support/docview.wss?uid=swg21314162

How to deploy non-versioned patches via Smart Upgrade● http://www-10.lotus.com/ldd/dominowiki.nsf/dx/How_to_deploy_non-

versioned_patches_via_SmartUpgrade

http://www.redbooks.ibm.com/abstracts/redp4180.html

http://www.redbooks.ibm.com/abstracts/redp4180.html

https://www-304.ibm.com/support/docview.wss?uid=swg21314162

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/How_to_deploy_non-versioned_patches_via_SmartUpgrade

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/How_to_deploy_non-versioned_patches_via_SmartUpgrade

51

Q&A

52

Back up slide : Optional argumentsArgument Definition

/s Instructs setup.exe to run in silent mode.

/v Passes arguments to MSIexec.exe. Used with command lines for MSIexec.exe; for example, /v”qb+” would

pass the qb+ command to the MSI installer. The commands are surrounded by quotation marks. There is no

space between the /v and the quotation marks.

/qn+ No user interface displayed during the installation of the client except for a modal

dialog box displayed at the end to notify that the installation was completed.

/qb+ User sees progress bar showing status of the installation of the client with a modal dialog box displayed at the

end to notify that the installation was completed. The modal box is not displayed if the user cancels the

installation. Use qb+! or qb!+ to hide the Cancel button.

-d Specifies that installation files are extracted to a temporary directory, from which they are deleted when the

update is complete. -d must be first in the series of arguments. This argument is used when using a

installation kit that is packaged in a single .exe file.

-s Makes the unpacking of the detached kit on the user's computer silent and uses the default locations for the

files it will extract.

-a Passes all arguments to the file that is being launched. For example, -a used in launching a single file

installation kit would pass further arguments to the installer application. Example: -s -a /s /v”qb+” passes the

arguments /s /v ”qb+” to setup.exe

-px or /px Hides the Location To Save Files and Remove Installation Files end user dialog boxes. The behavior of the package is the same as it would have been if the dialog box had been displayed and the end user had clicked Next, accepting all default selections in that dialog box.

53

Thank you!

open mic “upgrade notes client using smart upgrade”€¦ · open mic “upgrade notes client...

Documents