Вы находитесь на странице: 1из 8

Wells Fargo & Company

Windows 2003 Server


Standard Product Offering (SSO) Lending Post Factory Procedure

IBSS-Lending-Windows

12/21/10
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

363797036.doc Page 2 of 8
8/23/2017
Revision History
Date Version Description Author
12-21-10 1.0 Initial SSO7 version doc Soraqa Paika

363797036.doc Page 3 of 8
8/23/2017
Overview
This write-up details the various steps needed to complete the Post SSO Factory Lending SDT Windows
servers builds. Servers from SSO-Factory will be imaged and ready for these post build steps.

Description
See Overview above

Inventory/Configuration

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

Hardware Information

Dell PowerEdge Blade and Standalone


VMWare Virtual Servers

http://stspcenter.homestead.wellsfargo.com/index.aspx

Software Information
Windows 2003 SP2 (x86, x64) Standard/Enterprise

363797036.doc Page 4 of 8
8/23/2017
Installation Information

SSO Factory L-SDT Post build Procedure

Requirements:
1. IRBA normally attached to PTP, should hopefully contains most all items for build/software/priveleges
2. Lending Build sheet and/or Lending SID excel doc

This document is divided into 2 sections


1. General steps which applies to all SSO builds
2. VM or Dell steps which is specific to hardware

GENERAL STEPS for VM/STANDALONE

1. Submit SAF (Server Add Forms)


http://pqc.wellsfargo.com/cgi-bin/wpqc/wpqcsrvadd.cgi
Use of Bulk Form (if needed) send form to all recipients in a typical SAF email
http://tis.homestead.wellsfargo.com/sites/bass/asset/EHS%20Asset%20Management
%20Process%20Library/Forms/AllItems.aspx
2. Windows 2003 SP2 SSO Factory built servers computer objects (VM or Standalone) reside
in \ENT\SVR\Datacenter Servers\STP_Stage_2003 OU Move the computer object from this OU into
\ENT\SVR\Datacenter Servers\Lending\ respective ENV. sub OU -
3. Modify Computer Object properties (add description, location and GPO goups)
Put PTP info in Description follow other server examples
Put location info in Location Tab
Verify AltirisAutoBuild account in Security tab has Full Control this should already be there
Add Lending Baseline GPOs to your computer object, in the Member OF tab
You can add additional GPOs for application specific (e.g. Step 11/12/13)
Note: Click link below to get latest Lending GPO Cheat sheet -
http://tis.homestead.wellsfargo.com/sites/communitysupport/lending/buildteam/Design
%20Engineering%20and%20Support%20Docs/Forms/AllItems.aspx?RootFolder=%2fsites
%2fcommunitysupport%2flending%2fbuildteam%2fDesign%20Engineering%20and%20Support
%20Docs%2fWindows%20Support%2fBuilds&FolderCTID=&View=%7b7339F30E
%2d98D1%2d46B4%2d9112%2dD5E899334640%7d

Click APPLY and OKAY


4. Restart server to complete application of new GPOs
5. Logon to Server with your Server Admin account and click command ICON on quick launch and type
gpupdate /force to re-issue a forced GPO refresh.
6. Open Start/Run, type rsop.msc and confirm under computer configuration properties that GPO is
applied you can also expand folder to confirm the settings

363797036.doc Page 5 of 8
8/23/2017
7. Verify SNMP service in service.msc is configured in the Agent tab with hostname and location this
should most likely already be done from SSO team
8. Open Disk Management (VM) or Veritas Storage Foundation (DELL) to setup your disk based on build
sheet or SID sheet if anything is not clear, either check with SI or another fellow team member
Note: New baseline policy for Windows 2003 / 2008 do not change any default root volume security
permissions anymore leave default settings after you do a format of the disks/volumes

HPSA STEPS
9. Launch SAS client connecting to one of the Production cores

i. TEMPE Core: opsware-tp2.wellsfargo.com


ii. SHOREVIEW Core: opsware-sv2.wellsfargo.com
iii. Des Moines Core:opsware-dm.wellsfargo.com
Under Devices go to All managed servers
Find the server name in the list right click open
Click properties
On the right click Change next Customer
Select Lending Services Delivery
Click Select
Click the Relationships tab
On the right hand side right click and select Add to group
Expand Public groups Lending
Left click IBSS-Lending Windows
Hold Control to select the proper environment for the server as well
You should see 2 items selected
Click Add Servers to Device Group
Go to the File Menu Save
Close the Window

10. For all Windows 2003 servers Run the respective OS architecture Job:
L-SDT Post Build 2003 x64 Policy software HPSA job
L-SDT Post Build 2003 x86 Policy software HPSA job
11. If IIS 6.0 is going to be installed,
Add the LEND-EC -A- 2K3 IIS Servers Policy GPO - (restart required)
Use HPSA script for IIS 6.0 use your so_ account to run the job (not Local System)
12. If SQL is going to be installed, then complete these bullet items,
Add the LEND-EC -A- 2K3 SQL Servers Policy GPO
Run one of the following OS arch. Specific job
i. Lending DSG Post Build 2003 x64 software policy
ii. Lending DSG Post Build 2003 x86 software policy
13. If NDM:Connect Direct will be installed then complete this bullet item:
Add the LEND-EC -A- 2k3/2k8 Standard NDM Baseline Settings GPO. (restart required)
14. HPSA patching policy
In HPSA, right click your server and attach the respective patch policy -

363797036.doc Page 6 of 8
8/23/2017
a. For x86: Windows 2003 x32 Layer1
b. For x86: Windows 2003 x32 Layer 2.NET

c. For x64: Windows 2003 x64 Layer1


d. For x64: Windows 2003 x64 Layer2.NET

15. Remediate To run patch policy and windows minimum tools requirements. You can remove the
previous software policies that were run in Steps 10/12 in the Remediation windows by highlighting
and clicking the icon, if you wish to speed up the run -

16. HPSA Audit


See link below for latest OperationalReadinessVerificationX.X doc
http://tis.homestead.wellsfargo.com/sites/ORM/EHSConfigurationManagement/ORV/default.aspx

Virtual Machine (VMWARE) Steps


17. FYI - Per Standard build, Veritas Storage Foundation Suite (includes Enterprise Admin and DMP) is not
installed on VM because no HBA card or multipathing required
18. FYI - Per Standard build, SAN Surfer is not installed on VM because no HBA card

DELL PowerEdge R910/R900/r710/M600/M610 Steps

19. Qlogic San Surfer Utility


RDP to server with your admin account, under start/programs/qlogic folder, open San Surfer.
Under each HBA port, go into Parameters tab and make sure the connection type is Point to
Point and Speed is (Auto) we should be at 4 GB
Update firmware to 1.79 on QLE2460/2462 BIN file is stored in location
\\mtgbaztm001\E$\Software\Server_Software\QLogic\qlx246xaf1.79risc4.06.02-01
Use the San Surfer utility and in that utility in the menu options is a Flash Update Utility which
will ask for the BIN file and it will update all ports -
20. Network Connections Disable any unused/unplugged LAN connections and rename Production Team
to TEAMED NIC
Dell standlone - Confirm in Teaming software that member adapters in Team are using 1 GB
Full Auto speed instead of Auto
21. Configure DRAC5/iDRAC6
Modify network settings with correct hostname, DNS, disable auto select and make sure speed
is set to 100MB/FD. Click Apply, and wait for quick refresh.
Change root password to calvin
22. Update Dell System Firmware/Drivers (if needed) use OSHE firmware baseline link below
http://tis.homestead.wellsfargo.com/Topics/Divisions/HCSM/HE/OSHE/firmware/pages/Firmw
are%20Baselines.aspx

363797036.doc Page 7 of 8
8/23/2017
We are done with SSO Factory Lending Post build build tasks, and ready for turnover to SI and app teams.

Please keep in mind, through the course of the PTP, you will be engaged with additional items of concerns,
perhaps additional software installs, shared/folder setup, testing access with LOB, etc. All this will occur prior to
OR-CR. Here is a copy of the Lending Server Access Policy, which you can forward to customer, if needed.

IBSS Lending Server


Access Policy v1.1.xls
DEV, they will get Admin but others will be least privilege.

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

363797036.doc Page 8 of 8
8/23/2017

Вам также может понравиться