what's new and some what's (hopefully) old in ibm lotus …€¦ · ©2011 ibm...

©2011 IBM Corporation

What's New and Some What's (Hopefully) Old in IBM® Lotus Notes™ Client Administration

Jeff EisenLotus Notes Chief ArchitectIBM Distinguished [email protected]

©2011 IBM Corporation 2

Agenda●IBM Lotus Notes Installation Overview

●Notes Deployment Technologies and Best Practices

●Recent Stuff (8.5.2 and later)

●Sneak Peek at What's Coming

●Questions? Answers!


IBM Lotus Notes Architecture● Lotus Notes 8 Installer

─ Uses MSI on Microsoft WindowsTM

─ Uses RPM on Linux─ Uses PackageMakerTM on Apple®

MacsTM

● Package deploys Lotus Notes Core and Provisioning Engine

● Provisioning Engine deploys Lotus Notes Features

Packaging

Notes Core

Provisioning Engine

UpdateSite

Notes 8 Installer

Sametime

Symphony

Etc.


Lotus Notes Installer Flavors

Two client install types:● Designer Client (a.k.a. Allclient) – Standard only (8.5.x)

─ Notes, Designer and Admin clients in one package─ Only supports “Single User” install─ Supports roaming user─ Windows only

● Notes Client – Basic (Windows and Mac) and Standard (all platforms)─ Only Notes client─ Supports both “Multi-user” and “Single User” installs on Windows─ Only Supports “Multi-user” on Mac and Linux─ Supports roaming user


Lotus Notes Installer Packages● Web kit (Windows)● Self extracting zip file containing the full install kit● Usable in SmartUpgrade, 3rd party software, Active Directory etc. ● Designer, Notes Client, Standard and Basic● New extraction option in 8.5.1 – choose to keep or remove install files on

machine


Lotus Notes Installer Packages● Web kit (Linux)

─ Available as tarballs– .deb in a tarball (for SLED and Ubuntu)– .rpm in a tarball (for Red Hat)

─ Notes Standard Client only

● Web kit (Mac)─ Notes Standard Client available in .dmg format─ Notes Basic Client available as tarball


Yet More Packages● Upgrade kit (Windows Only)

─ Single file executable─ Usable in SmartUpgrade, 3rd party software─ Checks for existing version of Lotus Notes already installed

● Full kit─ Available on the CD/DVD─ Same contents (and size) as webkits


Package Proliferation ● 3 Kit types x 3 Packages = 9 choices for each release on Windows!

─ Lotus Domino Designer Web kit, Upgrade kit, Full kit─ Lotus Notes Standard Client Web kit, Upgrade kit, Full kit─ Lotus Notes Basic Client Web kit, Upgrade kit, Full kit

● Chose the right package for your deployment─ Full Kit / Web kit for new installs─ Upgrade kits for upgrade installs─ How much customizationsw are you doing?

● All kits can be used in any combination─ Install 8.5.1 with web kit, upgrade to 8.5.2 with upgrade kit, upgrade again to 8.5.3

with full kit etc.


Installer Customization● Changing the defaults

─ Add and remove features (Sametime, Symphony, NSL etc.)– TrimUpdateSite, AddToKit, and UpdateSiteMgr (8.5.3)

─ Installation location─ OS Integration points (Shortcuts, Menu items, etc)─ InstallShield® Tuner for Lotus Notes

– Allows full control over every MSI aspect of the installer– Windows only

─ Install manifest (install.xml)

● Customizing features─ New notes.ini entries─ Customized plugin settings


Editing the Install Manifest● Install Manifest can be edited on all the platforms.● Install.xml is located in the "deploy" dir in the install kit● Allows control of the eclipse features that will be installed● Also allows control of which eclipse features should be visible/required


Tuning Up the Install Kit● Tuner for Lotus Notes available on Passport Advantage and CD/DVDs.

─ Used to manipulate MSI tables that control the Installer behavior─ No new version for Notes 8.x, version 7.0 works─ Fully supported by Windows including Active Directory and SMS─ Allows one install kit to have many different personalities─ Also allows control of built in Eclipse feature states as of 8.5.1─ Important properties:

– ALLUSERS, PROGDIR,DATADIR,SELECTINSTALLFEATURES,MSAD_SUPPORT

– New in 8.5.1: MULTIUSERBASEDIR, MULTIUSERCOMMONDIR,SELECT_EDITORS

─ Extremely powerful and extremely dangerous


Adding and Removing Features● AddToKit (replaced in 8.5.3 with UpdateSiteMgr)

─ Add new, signed features to the Lotus Notes install kit prior to installing or upgrading─ Available as of 8.5.1 on the DVD/CD and in the web kit in the utility directory within

NotesCustomizationKit_1_0.zip (previously download only)─ Updates the updateSite.zip, the install.xml and the site.xml for a given install kit─ Usage: addToKit.exe c:\Notes851StdKit c:\temp\myFeature\

● TrimUpdateSite (replaced in 8.5.3 with UpdateSiteMgr)─ Used to remove "optional" installfeatures from "deploy\install.xml" and from

updateSite.zip to decrease the overall size of an install image.─ Available as of 8.5.1 on the DVD/CD and in the web kit in the utility directory within

NotesCustomizationKit_1_0.zip (previously download only)─ Repackages the updateSite.zip making it smaller

● UpdateSiteMgr (new with 8.5.3)─ Combines functionality of AddToKit and TrimUpdateSite into one command line utility.


Two Deployment Approaches...

1) Roll out and hope pray it works...

2) Plan/Test/Pilot/General Rollout/Manage...

Which do you do?


Major Steps of Deployment

Plan the deployment

Download and customize the install kit

Build and test the deployment package

Roll out the deployment

Manage the desktop

Pilot the upgraded client


Planning the Deployment● General planning references

─ READ THE RELEASE NOTES!─ Admin Guide - Notes Client Installation and Upgrade ─ Notes/Domino Wiki: http://www.lotus.com/ldd/dominowiki.nsf─ Notes/Domino Info Center:

http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp─ Tech Notes: http://www.ibm.com/software/lotus/support/notes/support.html─ And many more...

http://www-10.lotus.com/ldd/dominowiki.nsfNotes/Domino



http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jspTech



http://www-01.ibm.com/software/lotus/support/notes/support.htmlSupported

http://www-01.ibm.com/software/lotus/support/notes/support.htmlSupported


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates

─ Recommendation is to upgrade servers first, then the client deployment and then the templates.

─ Consider use of managed or local mail replicas to optimize server bandwidth.─ Consider the use of Notes shared login, Roaming User, and ID Vault capabilities.


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users

─ Make sure you have user acceptance and that they are prepared for new client. – Don't overdo it though...

─ Will significantly reduce support costs in the long run...


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning

─ Consider all the applications that need to be tested with new version of Notes and the time it will take to accomplish this....


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning

─ The pilot is a critical part of the deployment so it needs careful planning.─ Feedback from the pilot will help in creating a realistic roll out plan.


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning

─ Deployments are expensive and time consuming - need to be realistic about the time frame in which this can be accomplished.

─ If you have 3rd party or custom plugins to deploy consider using the widget catalog


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning● Multi-User install recommended for general population of users

─ Use a single user install for power users only (Designer and Admin clients included in Single User Install kit).

─ If your previous install was single user you will need to move data to the multi-user layout.


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning● Multi-User install recommended for general population of users● Standard client recommended

─ Unless hardware is inadequate you should plan to use the standard client. ─ For those cases where basic client is needed you should install the standard client

and configure the installer to launch the basic client (ini variable preferred or can use the "-sa" or "-basic" switch in the shortcut)


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning● Multi-User install recommended for general population of users● Standard client recommended● What Languages are Needed?

─ English only kit is default, if other language is needed get language specific kit. ─ If multiple language support needed get MUI Install kit ─ Consider adding additional dictionaries to kit.


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning● Multi-User install recommended for general population of users● Standard client recommended● What Languages are Needed?● Does User Data Need to be Moved?

─ If data was in a non-standard location consider moving it to recommended location for multi-user install.

─ For users who will frequently change machines consider a roaming user deployment.


Planning the Deployment● General planning references● Architecture Planning: Server, Client, Templates● Training and Communication for New Users● Test Planning● Pilot Planning● Deployment Planning● Multi-User install recommended for general population of users● Standard client recommended● What Languages are Needed?● Does User Data Need to be Moved?● Other Cleanup Required?

─ Each upgrade is an opportunity to remove extraneous applications from the desktop and clean up Notes.ini settings that are no longer required, hard-coded IP addresses of servers in address book, etc ....


Download and Customize Install Kit● Download the multi-user Notes client kit for required language

─ Use a single user install for power users only (Designer and Admin clients included in this kit).

─ If multiple language support needed consider whether needed on all desktops


Download and Customize Install Kit● Download the multi-user Notes client kit for required language● New stuff in the Lotus Notes install kits

─ The kit now includes the translation for all the install panels. ─ The Install blog explains the new contents. (http://www-

10.lotus.com/ldd/installblog.nsf/dx/whats-all-this-stuff-in-the-lotus-notes-install-kits)


Download and Customize Install Kit● Download the multi-user Notes client kit for required language● New stuff in the Lotus Notes install kits● Customize which features must be installed, optional, presented in

feature panel, etc.─ Edit the install manifest (install.xml) to control which features are available for

installation and what the user sees on the feature installation panel.


Download and Customize Install Kit● Download the multi-user Notes client kit for required language● New stuff in the Lotus Notes install kits● Customize which features must be installed, optional, presented in feature

panel, etc.● Remove default components that are not required by your company

─ If your company is not using Connections, Sametime or Symphony as part of the standard desktop these can optionally be removed from the kit.

─ Makes kit smaller for distribution over network.─ Use TrimUpdateSite (pre 8.5.3) or UpdateSiteMgr (8.5.3) tool.



panel, etc.● Remove default components that are not required by your company● Add custom plugins used by your company

─ If your company uses custom plugins as part of the standard desktop these can be added to the kit.

─ Use AddToKit (pre-8.5.3) or UpdateSiteMgr (8.5.3) tool.─ Use the validation tool to validate your changes.



panel, etc.● Remove default components that are not required by your company● Add custom plugins used by your company● Customize Notes installer

─ Set silent install settings via transforms, default components to be installed via command line arguments, etc.



panel, etc.● Remove default components that are not required by your company● Add custom plugins used by your company● Customize Notes installer● Set Notes runtime settings

─ These can be Notes.ini, Domino policy and plugin_customization.ini settings. ─ In general policies are recommended where available. ─ Dynamic policies can only be used from 8.5 on, policies need to be changed when

moving from previous releases.



panel, etc.● Remove default components that are not required by your company● Add custom plugins used by your company● Customize Notes installer● Set Notes runtime settings● Scriptable setup configuration

─ Not needed when upgrading, but useful for new installs. This now supports environment variables in the script (Windows only).

─ Roaming user will store key data files on server and pull down to new client at initial setup.

─ ID Vault could be used instead of moving around id files.



panel, etc.● Remove default components that are not required by your company● Add custom plugins used by your company● Customize Notes installer● Set Notes runtime settings● Scriptable setup configuration● Pre-populate cross certificates in deployment

─ You can avoid users needing to respond to cross-certificate prompts by pre-populating the deploy.nsf file with admin generated cross certificates which are then copied to the user address book at first launch.

─ Can also be done via Policy.


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool

─ Yes, some customers just use a F: drive, but wouldn't recommend.─ Use silent install settings packed in a 3rd party 'push' tool.─ Lots of tool choices: ZENworks®, Tivoli®, SMS, etc. or Notes specific tools like

Desktop Manager, Marvel Client, Automated Deployment Toolkit (ADT), InstallPump®, etc.), SmartUpgrade...

─ Each deployment application is different but Smart Upgrade supports chaining of Notes client installers – If you need a fixpack it can be deployed along with the install kit.


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool● Consider un-installing the old client

─ Notes Installer supports upgrading from existing clients but many customers get better results by doing an explicit un-install of existing client (and cleanup if needed) before upgrading.

─ This is the only way you can change the program and data paths during the install.


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool● Consider un-installing the old client● Make sure the Notes client is shut down before new install

─ Add scripting to shutdown the Notes client if it is still running. ─ Consider re-booting the machine via scripting before starting the install.


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool● Consider un-installing the old client● Make sure the Notes client is shut down before new install● Use verbose install logging for the pilot

─ Add parameters for verbose install logging in pilot deployment package─ Default in 8.5.3 and beyond


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool● Consider un-installing the old client● Make sure the Notes client is shut down before new install● Use verbose install logging for the pilot● Antivirus settings should be taken into account

─ Some antivirus applications can impact the installer so make sure to test with the settings that your users have on their desktops.

─ Important both to ensure “correctness” and reasonable performance


Build and Test Deployment Package● Deployment should be automated as much as possible by a push tool● Consider un-installing the old client● Make sure the Notes client is shut down before new install● Use verbose install logging for the pilot● Antivirus settings should be taken into account● Consider de-fragmentation before/after the install

─ This can improve performance in cases where the desktop disks are close to capacity.


Piloting the New Client● Enable the ADC fault reporting database

─ Ensure that you can compare ADC stats from before the pilot with new stats.


Piloting the New Client● Enable the ADC fault reporting database● Use the test deployment to pilot the new release

─ Look for user feedback, other issues with new release. ─ Make sure to check release notes for known issues, etc. ─ Use pilot experience to estimate support cost of final roll out.


Piloting the New Client● Enable the ADC fault reporting database● Use the test deployment to pilot the new release● Certify custom apps work with new release

─ Notes applications (self developed and purchased) and 3rd party applications should be tested thoroughly.


Piloting the New Client● Enable the ADC fault reporting database● Use the test deployment to pilot the new release● Certify custom apps work with new release● Consider which users to include in pilot

─ At least 100 users distributed 80% in main site, 20% in remote site, preferably not all IT users. Consider a separate pilot for Citrix users.

─ Worthwhile including Administrative Assistants─ Admin and Designer client feedback can be tracked separately.


Piloting the New Client● Enable the ADC fault reporting database● Use the test deployment to pilot the new release● Certify custom apps work with new release● Consider which users to include in pilot● Co-existence of old and new clients

─ Try to ensure a consistent user experience across the pilot group. For example, if a manager is in the pilot group consider also including the manager's AA.


Piloting the New Client● Enable the ADC fault reporting database● Use the test deployment to pilot the new release● Certify custom apps work with new release● Consider which users to include in pilot● Co-existence of old and new clients● Length of pilot

─ Should allow a month for adequate customer feedback, longer if your schedule permits.


Roll Out the Deployment● Plan the rollout based on bandwidth

─ Consider how many desktops need to be upgraded and plan your roll out based on network bandwidth as well as your IT support capabilities. In case of low WAN bandwidth consider alternatives such as LAN storage device etc.

─ Smart Upgrade governor can throttle server load.


Roll Out the Deployment● Plan the rollout based on bandwidth● Monitor the deployment

─ Smart Upgrade will provide this – other packages presumably also provide similar tracking capabilities.

─ View in server NAB also indicates Notes client version for each user.


Roll Out the Deployment● Plan the rollout based on bandwidth● Monitor the deployment● Have a plan to provide desk side support

─ Use pilot as indicator or how much desk side support will be needed.


Roll Out the Deployment● Plan the rollout based on bandwidth● Monitor the deployment● Have a plan to provide desk side support● Initial policy settings

─ Use hierarchical policy settings to control the desktop configuration – these are automatically detected at first client launch so no explicit install action required. Remember you need to use the new Admin client (8.5 or newer) to set these policies.


Roll Out the Deployment● Plan the rollout based on bandwidth● Monitor the deployment● Have a plan to provide desk side support● Initial policy settings● Update mail templates, folder designs

─ This should be done AFTER desktops gets upgraded. ─ Note that folder design is not automatically updated with a template change - it

needs to be explicitly set via desktop policy. ─ Administrator should request users to empty their Trash folders because if these

have customized design the contents will no longer remain in the Trash folder after the new Trash folder design takes effect ...


Managing the Desktop● Apply fixpacks as they become available

─ If possible apply fixpacks regularly.─ Consider using Smart Upgrade for these otherwise your favorite 'push' application.


Managing the Desktop● Apply fixpacks as they become available● Change to policy settings as needed

─ Policies can be added, edited and deleted as necessary


Managing the Desktop● Apply fixpacks as they become available● Change to policy settings as needed● Updating the Notes dektop to add/remove features

─ If necessary you can modify your user desktops by re-running the Installer in modify mode. This can also be customized as needed.


Managing the Desktop● Apply fixpacks as they become available● Change to policy settings as needed● Updating the Notes dektop to add/remove features● Updating components out of cycle

─ If, for example, you wish to upgrade your embedded Sametime to a newer version use a Sametime provided Add On Installer to upgrade to desired level....


Managing the Desktop● Apply fixpacks as they become available● Change to policy settings as needed● Updating the Notes dektop to add/remove features● Updating components out of cycle● Adding new widgets

─ New widgets can be deployed as needed via the catalog


Managing the Desktop● Apply fixpacks as they become available● Change to policy settings as needed● Updating the Notes dektop to add/remove features● Updating components out of cycle● Adding new widgets● Adding new 3rd party applications

─ We provide an Add On Installer framework for building installers for 3rd party apps if needed.


Deployment Technologies● Active Directory

─ A technology created by Microsoft that provides a variety of network services including deploying software via policies

● System Center Configuration Manager (SCCM)─ The technology formerly known as SMS (no the other SMS)─ A systems management software product by Microsoft for managing large groups of

Windows-based computer systems.

● Citrix XenApp─ An application virtualization/application delivery product that allows users to connect

to their corporate applications.

● Smart Upgrade─ Technology integrated into Lotus Notes to provide automatic client upgrades


Active Directory● Create a new Group Policy Object giving it a descriptive name like “Lotus Notes

8.5.3 Deployment”● Target the correct hierarchy in the directory, typically this is all Organizational

Units.● Create a new security group. It is recommended you name it the same as the

GPO but is not required.● Prepare the install kit with any customizations you require (as transforms) then

copy it to a network share on a fileserver. Ensure the security group created has appropiate access to both the share and the files.

● Update the GPO security filter to include the security group and remove the “Authenticated Users”

● Edit the new GPO and add a new Software Package. Configure it to the UNC Path of the install kit and select the Lotus Notes.msi file. Add your transform to the Advanced Modifications setting if required.

● Finally add computer accounts to the security group.


SCCM● SCCM will deploy Notes client as a systems account ● Create a batch file to run the Notes client installation with silent install

parameters of your choice. Sample batch file below:─ @Echo off─ Set MYDIR=%~dp0─ %MYDIR%setup.exe /s /v”/l*v %MYDIR%installation.log TRANSFORMS=%MYDIR

%MyTransform.mst /qb+”─ REM Optionally create a cab file with the log to be sent easily to support for review─ Makecab.exe %MYDIR%installation.log %MYDIR%installog.cab

● Setup your Advertisement option to download locally from the distribution point


Citrix® XenApp™

● Recommended use "Notes Client Only" standard client install kit as this kit supports Multi-user

● Log directly onto the Citrix server as the Administrator.● From the Microsoft® Windows Control Panel, select Add/Remove Programs.● Click Add New Programs and select the Notes install kit● Locate and run the SETUP.EXE installation executable.● Choose the "Multi-user Install" setting when prompted● Proceed with Installation● MULTIUSERBASEDIR and MULTIUSERCOMMONDIR properties allow for

network based data directories. ─ setup.exe /v "SETMULTIUSER=1 MULTIUSERBASEDIR=C:\LocalAppDataUsers\!

USERNAME! MULTIUSERCOMMONDIR=C:\LocalAppDataCommon CITRIX=1”─ setup.exe /v “TRANSFORMS=Citrix.mst”


Smart Upgrade● Create a database using the Smart Upgrade kits to host Notes client update

kits.● Update the Configurations Settings document in the Domino Directory with a

link to the Smart Upgrade database● Create a an upgrade kit document in the Smart Upgrade database and attach a

Notes client kit or an All Client kit to the kit document, or designate a shared network drive in the kit document.

● Create or modify a desktop policy settings document to specify the updated release to deploy and the date on which the grace period for updating a Notes client ends.

● Create or modify a master policy to assign users or groups to the desktop policy settings document.

● Depending on the master policy created, edit Person documents to assign users to the master policy and/or set the Lotus Notes Smart Upgrade desktop policy settings document for one or more groups.


Smart Upgrade


ADC and Fault Analysis● Automatic Data Collection (ADC) is a mechanism to automatically collect

diagnostic data from client and/or servers around...● Crashes, Hangs and manual ISA data● Configuration...

─ A server is controlled through Configuration documents─ A client is controlled through Desktop Setting policies─ Alternatively, ADC collection can be specified through INI settings

● What is collected?─ NSD & Console output.─ Memory dumps, Notes_Child_PID output, Memcheck errors, Semaphore debug. ─ The size of the data sent can be controlled

● Where does it go? ─ Data is sent to a ADC mail-in Db – grouped based on similarities of crash stacks

● Why would an Admin want this data?─ Frequency of a issues can provide an overview of the health of clients and servers─ The data (centrally) collected for a crash is essential for troubleshooting and IBM Support.─ See for more info: http://www.ibm.com/developerworks/lotus/library/domino7-serviceability/


LotusLive Notes considerations● LotusLive Notes provides Domino-based PIM (email, calendar, contacts) as a

service (SaaS)● Supports 100% SaaS as well as hybrid (mix of SaaS and on premises)● Lots of server/migration considerations – focusing on client considerations here● Can be used with installed client (Lotus Notes) or browser (LotusLive Notes Web)● For Lotus Notes usage:

─ Requires 8.5.1 FP5 or higher─ Deploy/Install Notes clients “normally” -- customer “owns” desktop─ Configure by logging in to www.lotuslive.com with browser, specifying that you want to

use service “with a Lotus Notes client”. Then, download and execute config.nsf application.

● Policies:─ Only supports policies that explicitly specify the group/users; not policies applied via

references in person record─ Many but not all policies are applicable to LotusLive Notes─ See Wiki article for more details (easy to find Googling “LotusLive Notes policies”)

http://www.lotuslive.com/

http://www.lotuslive.com/


Managed Mail Replicas● New with Notes 8.5.2 – “Local Replicas on steroids”● End-user just “opens mail” – system does the right thing● Replica created automatically – switches from server to local when ready● Automatically temporarily switches to server replica when local needs fixup● Server can throttle replica creation to manage load & network bandwidth● Keeps ODS version up to date● Optimizes new mail polling and sending – eliminates lags● Automatically sets up local full-text index● Multi-threaded replicator (sending and receiving mail don't block each other)


Managed Mail Replicas● Simple to deploy – either via policy or client notes.ini variables● Notes 8.5.3 machine-based policies allows deployment “just on laptops”● Several config choices, but defaults are probably what you want:

─ E.g. default is older documents are truncated and retrieved on demand

● Use “Server” location settings● Looks almost like a regular local replica


NICE (Notes Installer Cleanup Executable)● Clear registry and disk of Notes program files and configuration providing a

clean environment into which you can install new Notes version● Comes packaged in installer starting with Notes 8.5.3● Optionally removes data files● Backward compatible to Notes 6.0

Usage● Nice.exe [-option [/modifier]]● -rp – Remove program files● -rd – Remove Data files (ONLY if installed in Single-user mode)● -wipe – Clear Notes registry entries even if Notes is not installed● /qb – Silent mode with progress bar● /qb+ – Silent mode with progress bar and results confirmation dialog● /qn – Silent mode● /qn+ – Silent mode with results confirmation dialog


NICE (Notes Installer Cleanup Executable)


Multi-User Migration Assistant (MUMA)

● New with 8.5.3● Single User to Multi-user Migration Utility● For Windows only (MAC and Linux already only Multi-user)● MUMigrationAssistant VB script in utility directory● Migrates data files from single user to standard multi-user locations● Works on customized data directory locations● Preview mode to see exactly what's going to happen● Works on many, not necessarily all migrations – looking for feedback

● Likely to be part of installer (in addition to standalone tool) in future version


Smart Upgrade – Improvement in 8.5.3...● New “Smart Upgrade Service” ● Allows SURunAs to work on Windows Vista and Windows 7


Notes Preloader

Motivation● Enable faster client startup times for Lotus Notes

─ Preloads DLLs and multiple Java® JAR files.─ Improves startup time, particularly, on Windows XP (less so on Vista and Win7)─ Requires Notes 8.5.2 FP4 or Notes 8.5.3

Installation● Install with Notes client

─ setup.exe /v"PRELOADNOTES=1 /l*v NotesInstall.log /qb""─ Or, option on install screen

● Install to existing Notes installation─ setup.exe /s /v"ADDFEATURES=Preloader /l*v Preloader.log /qb"

More Information● Understanding Lotus Notes preloader (t/n 1424193)


Machine-based Policies● New with 8.5.3● Allow policies to be based on machine characteristics, not just set of users● Motivated by Managed Mail Replicas● New @Function to support machine-based policies – @GetMachineInfo● Syntax: @GetMachineInfo( [Keyword]; "Needed for some Keywords string")

─ Boolean check keywords – IsLaptop, IsDesktop, IsSingleLogOn, IsMultiUser, HasDesigner, HasAdmin, IsStandard

─ Retrieve value keywords – MachineName, Memory, DiskSpace, EnvVariable, SysEnvVariable, IP, MAC

● Public NAB template now allows entering formula for subset of settings─ Subset of settings likely to be machine-dependant enabled in out of box template─ NAB template extendible to allow formulas for other settings


Machine-based Policies – example


Serviceability: Notes 8.5.2● “One Click” ISA Data Collection

─ Customers found the 8.0/8.5.1 ISA data collection confusing.─ For 8.5.2, the common case has been simplified from 9 steps to 2

● Notes Hang Data Collection─ Previous versions required multiple steps and knowledge to collect data for a hang.─ Notes 8.5.2 provides an OS menu choice to collect and send hang or slow-down

data (if customer uses ADC)─ This was the 1st of several steps to collect data, via ADC, beyond crashes

● NSD Improvements─ Allow NSD to be run manually from any directory on the Client─ Clarify NSD when Notes2 process disappears

– If user killed the process, indicate it– Do not mark NLNOTES process/thread as FATAL


Serviceability: Notes 8.5.3● Improvements to Fault Analyzer analysis

─ Add the ability to identify and aggregate hang data from NSD and javacore collected

● ADC “Rescan”─ Calculate a disposition and blame a specific stack

– Out of memory– Hangs– Misparsed data– Newly identified issues based on data


The Usual Caveats...


Notes Startup Auditor Tool

Motivation● Monitor key events and environment during the Notes startup and Mail db

open and post results to a centralized db● Determine bottleneck sources for startup● Work with existing and already installed Notes 8.x clients

Installation● Create a centralized db using the new auditor.ntf● Installer for auditor add-on and plugin for startup monitoring

Data Collected● Times for Notes standard client startup events● Times for Mail & Calendar open events● System Stats (using Notes Stats package)● Machine and OS information● Notes Build info


Notes Startup Auditor Data Example (1/2)● Notes Startup

Time 07/07/2011 11:14:15:21 AM

Auditor Version 1.1

Machine Name TST291

Startup Time 28 seconds

Authentication Time

Java Startup Time 15 seconds

Core Startup Time 28 seconds

Cold Start Yes

Mail/Cal Open Time 7 seconds

Mail/Cal Open at Startup No

User Name Test076

Notes Version Release 8.5.2FP2

OS Version Windows/XP 5.1 [32-bit] (Build 2600), PlatID=2, Service Pack 3 (2 Processors)

Number of Active Bundles

70

SideBar State Thin

Avg Disk Queue Length 2.2


Notes Startup Auditor Data Example (2/2)● Mail & Calendar Detail

● Other Times

File Name: Test076.NSF

Is Remote: No

Swiftfile Max CPU Util: 24.99

Access Time: 0 seconds

Start Open Time: 07/07/2011 11:13:46:64 AM

Navigator Ready Time: 07/07/2011 11:13:51:11 AM

UI Ready Time 07/07/2011 11:13:54:18 AM

OS Boot Time: 07/07/2011 11:04:39:16 AM

nslsvice.exe 07/07/2011 11:05:09:32 AM

notes.exe 07/07/2011 11:13:14:93 AM

nlnotes.exe 07/07/2011 11:13:15:31 AM

notes2.exe 07/07/2011 11:13:20:64 AM

Authentication Started:

Authentication Completed: 07/07/2011 11:13:22:69 AM

ntaskldr.exe 07/07/2011 11:14:03:54 AM

Eclipse Initialized: 07/07/2011 11:13:35:75 AM

swiftsrv.exe 07/07/2011 11:13:50:40 AM


Notes Install ValidatorMotivation

● Validate that all needed files are present in a Notes installation and output a report that can be compared to Notes installations on other machines

● Enable validation for Notes installations on remote machines using standard desktop management software

Usage● niv [-p notes_prog] [-d notes_data] [options]

─ -d arg -- specify notes data dir to override registry─ -p arg -- specify notes program dir to override registry─ -i -- output incremental file paths─ -m -- provide file md5 checksums only─ -v -- show additional output useful for debug


Notes Install Validator Sample Output

…C:\notes\nlnotes.exe, 3827080, 20110620.103454, 20110620.103454, 22e040049e32ceea5813e4c4d9b786b6C:\notes\nlnotes.exe.manifest, 809, 20100812.090412, 20100812.090412, bb9e8156470e08f208a7fdf1014e4a4aC:\notes\nlnvp.dll, 37232, 20110621.151540, 20101111.023924, ecefb6fccd1387689ec8454155265f75C:\notes\nlogasio.exe, 46472, 20110620.102856, 20110620.102856, 38cc6f6c03fc93690d831ccbd8b0b0ecC:\notes\nlsccstr.dll, 2523136, 20110620.025134, 20110620.025134, 39529eebcc4fc8b0c803eca141cea8ecC:\notes\nlsxbe.dll, 2207744, 20110620.024940, 20110620.024940, ec09243189672b7f9b5234e2553650c5C:\notes\nlsxlc.dll, 159744, 20110620.025052, 20110620.025052, 27815652fabfe11664251fe50cba6973C:\notes\nlsxodbc.dll, 240128, 20110620.025304, 20110620.025304, 75dfd043f8b9084eed82a7b0b9b4b785C:\notes\nmailman.dll, 22528, 20110620.025306, 20110620.025306, 836b651170651893adf0c0779ae26ff9C:\notes\nmeter.dcx, 69632, 20110620.025052, 20110620.025052, 72319634c1eda87a6c80076496008019C:\notes\nminder.exe, 394632, 20110620.102912, 20110620.102912, 0cffb3a4b619abc59a0254e5cc791e63C:\notes\nnet.dll, 6144, 20110620.025410, 20110620.025410, 1d6cfa332b67e9fa5b3c1009764284b4C:\notes\nnetbios.dll, 45056, 20110620.025326, 20110620.025326, 90f7fba455ea39ebc5247344ada0e0c0C:\notes\nnntpcl.dll, 20992, 20110620.025100, 20110620.025100, 59e469c5492e67a92f3341e532a837dbC:\notes\nnotes.dll, 36663296, 20110620.091412, 20110620.091412, ab6c08123a09726700a32bb9d2b44305C:\notes\nnotesei.dcx, 122880, 20110620.025052, 20110620.025052, 4ca7c6ba84fbaf514a310d6cfb738917C:\notes\nnotesmm.exe, 14216, 20110620.102928, 20110620.102928, 9690e519d6518e8c472c78c7b97c308eC:\notes\nnoteswc.dll, 69632, 20110620.025412, 20110620.025412, 51957182e265bd7286e40008a5deee20...


Notes Next Installer

Themes● Simplified, faster installer for Windows based on MSI● Unification of All-Client and Notes-only kits into a single kit

─ E.g., Trim install to Notes only for mass deployment─ Later add Designer, Admin and other applications─ Removes decision of which kit to deploy – there is only one

● Standardize to multi-user, machine install over single user install─ Better fit into Windows UAC model─ Linux and Mac already support this mode exclusively

● More condition handling to reduce install/upgrade failure rate─ Locked files, access, other pre-checking and in-process checking

● Hook for inclusion of Multiuser Migration Assistant script during upgrade─ Auto-conversion from single to multi-user─ You can modify the MUMA script to meet your migration process needs

● More serviceable Notes installation


Key Notes Next Installer Design Points (1 of 2)

● Use simpler file copy and configure settings installer model● Single MSI-controlled install program for file delivery

─ XPD provisioning no longer used during installation─ Provisioning is supported for Add-on installer and Widget Catalog

● Multi-user mode only─ i.e., Windows “all users” install model─ Single user mode achieved through multiuser install with one user

● Single-to-multiuser support─ Script driven through MUMA

● Standard installer only─ Notes basic configuration delivered through standard installer ─ Installer includes Designer and Admin tools

● Multiple CAB files for application packaging─ One for each major system/application─ E.g., Notes, XPD, Sametime, …


Key Notes Next Installer Design Points (2 of 2)

● Default Programs and Shared Data are both under program files─ Single install location─ Support configurable shared data location

● Rollback install/upgrade on error─ New install is only committed on no errors

● Installer extension through install pre/post script hooks─ Enable vb scripts before and after installation

● Install post validation─ Used for after installation troubleshooting


Questions and Answers

what's new and some what's (hopefully) old in ibm lotus …€¦ · ©2011 ibm...

Documents