Wells Fargo & Company

IBSS Lending Windows Pre and

Post OS Build Task List

IBSS Lending Team

Windows

07/09/07
Table of Contents

Table of Contents................................................................................................................................................... 2
Revision History..................................................................................................................................................... 3
Overview................................................................................................................................................................ 4
Description............................................................................................................................................................. 4
Inventory/Configuration.......................................................................................................................................... 4
Hardware Information............................................................................................................................................ 4
Software Information.............................................................................................................................................. 4
Installation Information........................................................................................................................................... 5
Pre-requites........................................................................................................................................................ 5
Lending Windows Pre and Post Build Process................................................................................................... 5
Pre- Altiris Imaging.......................................................................................................................................... 5
Post Build Tasks................................................................................................................................................. 6
Documentation Sign-Off Checklist......................................................................................................................... 8

363797024.doc Page 2 of 9
8/23/2017
Revision History
Date Version Description Author
07/09/07 1.0 IBSS Lnd-Windows Task List Soraqa/Greg/Jim
12/10/07 2.1 Review doc Soraqa
04/01/08 3.0 Review Soraqa

363797024.doc Page 3 of 9
8/23/2017
Overview
IBSS Lending Windows Pre and Post OS build task list. This is specific to Lending community.

Description
This document lays out the specific tasks for Lending community Windows builds. These tasks are used as best
practice to ensure consistent builds and additional Lending specific software requirements.

Inventory/Configuration

This document applies to all hardware platforms, currently being used for Windows builds.

Hardware Information
HP, IBM, Dell and others (Blades and Standalone)

Software Information
Windows 2000, Windows 2003

363797024.doc Page 4 of 9
8/23/2017
Installation Information
Pre-requites
Jim Carilli or designate will assign build engineer/s a PTP build spreadsheet.

Lending Windows Pre and Post Build Process

Pre- Altiris Imaging
Please complete below steps before you start with Altiris imaging using latest Sierra Automated doc located
here: http://ehs.homestead.wellsfargo.com/Topics/Divisions/SSS/ESS/SECS/SSE/Windows
%20Documentation/Forms/AllItems.aspx

These are Lending community specifics and other LOB may not use these exact steps. Most of them are
informational and reminders!

1) Submit Windows Server Add Form, 48 hour SLA for Production Assurance to create the record in Remedy
Asset Management (Pac2000) Here is a link to the Windows Add Form: http://pqc.wellsfargo.com/cgi-
bin/wpqc/wpqcsrvadd.cgi
Note: We decided to list this as Step 1 however; it would be a good idea to verify some of the other steps below
before submitting Add Form since certain information on the Add Form pertains to the other steps (e.g. S/N,
hardware type, etc.).

This step is applicable if its a new or rebuild/upgrade/re-image hardware AND has fiber card installed
and/or being used.

2) Verify HBA WWN (World Wide Port Numbers) match-up with their respective servers on the server build
spreadsheet form you are supplied.
Note: If SS does not have WWPN, then we need to record them into the SS. You can verify the WWPN using
one of the following methods:
Restart server hardware and use CTRL-Q to enter QLogic configuration utility.
If OS is available, then you can use San Surfer if installed. You can use the utility to check WWPN.
If OS image is available, you can also use the fcinfo utility go get WWPN using command line: the Fcinfo
utility can be found at; \\AltirisServer\Prod\Tools\HBA\fcinfo_x86\fcinfo Copy the 3 files in this folder to C:\
on your server and run C:\fcinfo at the command prompt. You will get an output with the WWPN. In some
cases, HBA driver may need to be upgraded in order for this utility to work, although ICOD images should
not have this issue.

3) Verify S/N match the server build form you are supplied. If blades/rackmount, you can use the MM, ILO,
RSA or DRAC, depending on hardware type, to verify/confirm the S/N. In some cases, you may have to visit
the system BIOS to verify this. Also, verify the hardware type you have (e.g. HP Proliant XXX and its
Generation) and see if it matches the SS and/or DSD. The DSD should have this information but may not.
The DSD are posted in the PTP as Design Specification Document and contains hardware/software
information. Depending on the version posted to the PTP, it may or may not match up with the build SS
supplied. Please check with Jim, Soraqa or Greg, if you see any issues.
4) Depending on the DSD and Server Build Spreadsheet supplied, you may or may not use Internal SCSI or
SAS disks for the Windows OS. If not using internal disks, then disable the controller in the System BIOS.
Do not create any Arrays if not using Internal disks. For boot to SAN and how to configure QLogic HBA,
please refer to this SSE document; http://ose.homestead.wellsfargo.com/docs/builds/Configuring%20an
%20HBA%20for%20Windows.pdf
5) Check versions of System BIOS and QLogic BIOS, and then update if needed
a) For IBM Blades, us this link: http://ehs.homestead.wellsfargo.com/C18/Firmware
%20Services/default.aspx The link has the current approved versions.

363797024.doc Page 5 of 9
8/23/2017
 b) For HP and Dells, please visit the vendor site and update to latest, if needed.
6) Check the IBM MM or ILO for hardware errors. If you find any errors during the POST startup or in the logs
from the MM or ILO or DRAC or RSA, please let Jim know.
7) Verify the SAN disk LUN sizes provisioned by OSSM (matches what is on the build sheet)
c) If you have an OS available, you can use Veritas Enterprise Admin or Disk Management (Win2K).
d) If No OS is present, then you can use the WinPE ISO. WinPE ISO is located at
\\buildserver\prod\altirisPE folder. Boot with ISO from the ILO, MM or DRAC and when WinPE is at the
command prompt type techsup\windows\showdisk v. Press enter and you will see the sizes of each
disk. The last disk is normally the local disk (if applicable) otherwise you will see (2) entries for each
SAN disk since they are multi-pathed. Confirm that the sizes are approximately matching with what
is mentioned on the SS. If they dont and are way off, then let Jim know.
e) The other option is to burn the WinPE ISO to CD, if you have an issue with booting to ISO and pop it
into the CD tray and boot from the physical CD. Using this method is faster if you are building a server
that is not in the same site as your office space.
8) Verify you can see both paths to the SAN if OS is available then you can verify this using Veritas
Enterprise Administrator, San Surfer or reboot and enter QLogic Configuration utility.
9) INFORMATIONAL*** If a Linux image exists contact Jim Carilli. This may be applicable to LUN 0 on blades
and rackmount boot to SAN scenario. Linux standard is 34 GB LUN 0, whereas Windows standard is 15 GB
LUN 0. ICOD may assign hardware from Linux pool, if Windows pool is exhausted and we may see this
scenario.
10) Reminder to configure ILO/ILO2/RILOEII you can do this either before or after server is built. Use any of
the following method to setup / configure the ILO. I like the method in the bold below, its quick and you wont
be in the ILO to do it so no reset needed.
f) Use F8 menu during system restart see instruction document here:
\\Mtgbaztm001\E$\Documentation\Engineers\Soraqa\RILOE ILO Setup.TIF requires reset so you will
loose access to ILO and will need to logon again.
g) Use hpconfig utility see instruction document here:
\\Mtgbaztm001\E$\Documentation\Engineers\Soraqa\HPONCFG utility.doc No reset required for
ILO since this is performed from within OS.
h) Use the GUI and under Administration tab / Network Settings requires ILO reset so you will loose GUI
access and will have to logon again.

Post Build Tasks

Starts once the engineer has completed the OS build using the SSE standard. These are Lending community
specifics.

1) Run the respective OS Post Lending Build Job located: Jobs build server > IB2S Jobs > IB2S
Lending > Post Build > I2S Lending Post Build x86 or x64
a) Installs Radmin
b) Runs Diskeeper fix (this is also run during SSE software job but we are running once more
c) Disables SSE auto patching
d) Run script to add few group account in Local Admin group of server (Lending specific groups)

2) For new IIS 6.0 builds ONLY (Initial IIS hardening - to be used directly after IIS installation and .NET, if
applicable ) job located here: Jobs - buildserver > IB2S Jobs > IB2S Lending > Build Jobs > Post IIS
Install Hardening > IIS Hardening Post Installation

3) Use TEAMED NIC (all Caps Lock) for our teamed connection name.
4) Send an email request for Heather, Mandy and Jim to have server added to the master SS.

Z:\Info\Server List\
Server Form Format.xls

363797024.doc Page 6 of 9
8/23/2017
5) For IIS 6.0 server builds, please run IIS 6.0 harden script
a) IB2S Jobs --> IB2S Lending --> Build Jobs --> Post IIS Install Hardening --> IIS Hardening Post
Installation
6) Reminder checks
a) All servers - add /PAE switch if over 4 GB of RAM present (restart required)
b) HP configure SIM settings via wilsonjp account.
c) Any hardware disable any hardware not being used (e.g storage controllers, Hba cards/port in
System BIOS)
d) Run latest HP firmware and PSP current version is 8.0 in SSE Software Job
e) ILO configuration / setup configure ILO with its hostname, IP, DNS/WINS information, use 100 / FD for
speed instead of automatic
f) GPO application combination of gpresult and rsop.msc to confirm GPO application is complete. You
should see no warning (in rsop.msc) If you see, run gpupdate /force from command line and do a
restart.
g) San Surfer make sure HBA port/s is Point to Point and 2 GB speed
i) HP Qlogic BIOS verson
(1) 1.45 for 2 GB cards
(2) 1.26 or 1.09 for 4 GB cards If you need to update from 1.09 to 1.26, please contact Soraqa for
the BIN file
ii) IBM Qlogic (HS20, HS40) 1.47
h) Teaming software use respective vendor software for teaming (available in SSE builds)
i) Intel NIC use Intel software
ii) Broadcom NIC use Broadcom software
iii) HP NIC use NCU
i) For IIS 6.0 do not modify root volume permission where IIS is installed. The installation adds accounts
to the root of volume where IIS is installed.
j) Netbackup client check hostname (should be all lowercase) and check master / media server are
correct for the server. Clean out old (all caps) hostname from the client list tab
k) For SAN attached disks and/or Tape, 2 paths should exist for disk and if using Tape, (2 paths to SAN
tape)
i) For Win2k3 - you can use Veritas, San Surfer or Qlogic config utility to verify. Please make sure the
2 paths are on different HBA cards/port.
ii) For Win2k use HDLM software instead of Veritas, if online 2 lines should shows going to disk
l) Volume permission should all have Administrators and System with FC Volume C: is normally
controlled via GPO.
m) Check event logs after restart to make sure we dont have any services not started (event archiver,
appstor, Radmin, etc)

In a nutshell, here is what you should do, if time permits and you have the tools handy

1. Check your build sheet for server columns to make sure all info is there (relevant to the build). you can
verify IP with Ipaa.wellsfargo.com site and do a DNS lookup
2. Before starting your server build, update your firmware (if applicable or time permits)
a. For HP, you can use virtual ISO or CD tray current firmware version is 8.0, in some builds you
may have to use 7.91 both firmware version ISO are stored on our tools box
\\Mtgbaztm001\e$\Software\Server_Software\HP\Proliant Firmware CD\
b. For IBM, you can visit, HE firmware page:
http://ehs.homestead.wellsfargo.com/Topics/Divisions/HCSM/HE/OSHE/Firmware
%20Services/Pages/default.aspx?sdupgwelredir=1&bucketwebredir=1
3. Drop image per SSE steps -
4. After the Image and Software job is run, make sure you complete the steps in the Altiris Auto doc which
is baseline standard, (e.g. SIM settings, SNMP service properties settings, NIC settings, etc)
5. Run the POST BUILD Lending job/s
6. If IIS, use SSE IIS build doc.

363797024.doc Page 7 of 9
8/23/2017
 7. Run the Post Harden IIS script after IIS 6.0 is installed and the doc is followed till end of completion
8. Make sure GPO applied is correct use combination of gpresult and rsop.msc (on Win2k3) to confirm
settings applied. In some case, you may have to run gpupdate /force from the command line to force
settings
9. Always check the event logs after a fresh restart to make sure all is good. Any errors that is not
common, should be investigated.
10. Always do a visual POST startup via ILO, DRAC or IBM RSA or MM to make sure we dont have any
hardware issues, glitches, etc
11. Setup SYSTEM BIOS disable hardware not used by system, boot order should normally be CD-ROM,
Floppy, Disk and Network adapter (embedded) This item can be changed depending on the situation
with server.

363797024.doc Page 8 of 9
8/23/2017
 1.

Documentation Sign-Off Checklist

Review the following list and then sign/date for validation:
1. Is the current file still valid?
2. Read entire document and validate the content.
3. Make updates using track changes and return to Workflow Coordinators for publication.

Content Reason for Review Completed Checklist Reviewed By

Review Date
First draft of doc Soraqa Paika
09/27/07 Doc review; added some steps Soraqa Paika
and modified some
12/10/07 Doc review, delete and revise Soraqa Paika
steps

363797024.doc Page 9 of 9
8/23/2017