Enterprise Deployment for Windows: Difference between revisions

From Research
Jump to navigation Jump to search
 
(85 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Due to the unique nature of SIAT Research, the deployment strategy for our Windows workstations is divided into a 2-step process.  
Due to the unique nature of SIAT Research, the deployment strategy for our Windows workstations is divided into 2 easy steps.  


An administrator would begin the process with the installation DVD. No network connection is required in this step. If the workstation in question has a previous user (i.e. not new), the administrator should wipe the hard drive(s) clean to avoid any potential conflicts or privacy issues.
== Introduction ==
=== The 2-step Process ===


Once Windows is successfully installed, the administrator would update all device drivers, perform system-level setups, set appropriate local accounts and passwords, and join it to the RESEARCH domain. With the workstation on the domain, the administrator will continue second part of the installation, which involves software (with installation scripts) that are stored on the file server.  
'''This is the fall-back deployment method. Only use this if the MDT2010 deployment fails on the client machine.'''


The deployment image is for a clean installation of Microsoft Windows to a PC. The purpose of the image is to consolidate all the various required software (from different media) to one central source. This eliminates disc swapping and makes automated/unattended installation possible, thus minimizing installation time and human attention.  
An administrator would first begin the process with the installation DVD. No network connection is required in this step. If the workstation in question has a previous user (i.e. not new), the administrator should wipe the hard drive(s) clean to avoid any potential conflicts or privacy issues.


Once Windows is successfully installed, the administrator should update all device drivers, perform system-level setups, set appropriate local accounts and passwords, and join it to the RESEARCH domain.
With the workstation on the domain, the administrator should continue the second step, which involves installation of software (with installation scripts) that are stored on the file server.
The deployment image is for a clean installation of Microsoft Windows to a PC. The purpose of the image is to consolidate all the various required software (from different media) to one central source. This eliminates disc swapping and makes automated/unattended installation possible, thus minimizing installation time and human attention.
=== The Microsoft Deployment Toolkit (MDT2011) Method ===
# Choose the correct deployment disk based on the OS you want to install.  The x86 disk will allow you to install XP.  The x64 disk will allow you to install Windows 7 and other 64-bit OSes.  Always choose the disk with the most recent date.
# Boot the target machine using the deployment disk.
# At the first prompt, click on Run the Deployment Wizard to install a new Operating System.
# At the next prompt, enter your login credentials that will allow access to '''\\hurricane'''.
# '''SELECT A TASK SEQUENCE TO EXECUTE ON THE COMPUTER'''  Generally speaking, you should choose the one with the most recent date.
# '''CONFIGURE THE COMPUTER NAME'''  Enter the computers "sr-" name and click on NEXT.
# '''JOIN THE COMPUTER TO A DOMAIN OR WORKGROUP''' Choose DOMAIN and enter RESEARCH as the domain.  Also type in your login credentials.  Click NEXT.
# '''SPECIFY WHETHER TO RESTORE DATA'''  Choose Do not restore user data and settings, then click on NEXT.
# '''SET THE TIME ZONE'''  It should default to the Pacific time zone.  Click NEXT.
# If you see a screen showing which applications you can install, do not select any of them.  The image you are deploying will contain the applications.
# '''READY TO BEGIN'''  Click BEGIN.
# When the machine re-boots, let it boot from the hard-drive, not the DVD.  It should now start in Windows XP.
# Login to XP as Administrator, with the password: G????????? (you know one I mean).
# New hardware will probably be detected.  Most drivers should already be on the machine so theres no need to allow XP to search the web.  Work through all the new hardware discovery prompts.
# Go into the Device Manager and make sure there are no problems listed.
# Add the rootxxx user and password, and make sure that account as Administrator privileges.
# After the various drivers have been installed, go into CONTROL PANEL / SYSTEM / COMPUTER NAME and click on Change...  Change the name of the computer to SR-whatever-it-should-be.  Also make sure it is set to join the RESEARCH domain.  You will probably have to re-boot to make these changes take effect.
# After re-booting, try logging, as yourself, onto the RESEARCH domain.
# Open a browser and open a web page with lots of content.  Scroll up and down to see if the video driver is working correctly.  Or open System / Hardware and check the Devices list to see if the Display Adapter is setup properly.
=== Errors ===
If you encounter any errors, have a look at this Wiki entry: [[Enterprise_Deployment_Errors]]
=== Updates ===
The images shall be updated at least every 6 months.  
The images shall be updated at least every 6 months.  


== Windows XP DVD image ==
Latest update was for the MDT2010 Deployment method and was done in '''January 2011'''.
This section covers our standard workstation configuration.
 
=== Licensing Restrictions ===
* The software mentioned on this page can only be installed on SFU assets (ones with SFU asset bar-code label).
* Administrators MUST verify the ownership of the workstations they are dealing with.
* Installation media (and file server access) should NEVER be lent out to any user under any circumstances.
* All concerns and exceptions to these practices should be directed to your supervisor or manager.
 
== Windows XP MDT2010 Deployment DVD image ==


=== DVD contents ===
=== DVD contents ===
* Microsoft Windows XP Professional (32bit), VLK, SP3-integrated
* Microsoft Windows XP Professional (32bit), VLK, SP3-integrated
** customized with [http://www.nliteos.com/ nLite] deployment tool for unattended installation
** injected with the drivers for:  
** injected with printer (HP Color LaserJet 4600, Lexmark T630, Lexmark T640) drivers
*** audio chips, from various manufacturers
** injected with device (LAN and Mass Storage mostly) drivers for most of our various platforms
*** chipsets, from various manufacturers
** injected with post-SP3 hotfixes
*** mass storage devices, from various manufacturers
** set with a password for the administrator account (new account creation and built-in accounts are all disabled by default)
*** network interface cards/chips, from various manufacturers
** plus tons of more goodies that only administrators get to know ;)
*** HP Color LaserJet 4600
* [http://www.sassafras.com Sassafras] K2 Keyserver Client
*** HP Color LaserJet 4650
** customized MSI package with pre-configured settings
*** Lexmark T630
* McAfee VirusScan Enterprise 8
*** Lexmark T640
** Scripted install?
** injected with utility applications such as:
* Miscellaneous software utilities
*** Microsoft DirectX Runtimes 9.0c
** [http://www.7-zip.org/ 7Zip]
*** Microsoft Windows XP post-SP3 hotfixes
** [http://java.sun.com/javase/downloads/index.jsp Sun Microsystems JDK]
*** Microsoft .Net Framework 4
** .NET 3.5 Update
*** [http://java.sun.com/javase/downloads Sun Java Development Kit (JDK)]  
** [http://www.mozilla.com/en-US/firefox/ Mozilla Firefox]
* Common drivers
** WSUS script (registry update)
** ATI Catalyst 9.3 (for legacy cards commonly found in Dell PCs)
** Windows Installer 4.5
** ATI Catalyst 9.6 (for new cards from 3x00 series and newer)
* Latest graphics card drivers
** ATI Catalyst 9.1 (for all ATI graphics cards)
** nVidia 175.19 (for legacy cards like GeForce 3, GeForce 4, FX5x00, etc.)
** nVidia 175.19 (for legacy cards like GeForce 3, GeForce 4, FX5x00, etc.)
** nVidia 182.06 (for new cards from GeForce 6 and newer)
** nVidia 182.08 (for new cards from GeForce 6 and newer)
** DirectX 9.0c (for games?)
** nVidia nForce 05.10 (for nForce2 motherboards)
* more to add later
** nVidia nForce 15.23 (for nForce4 motherboards)
** DirectX 9.0c (Mar-2009)
* regedit mod to update Windows from our WSUS server.
* Applications
** 7zip 9.20
** Adobe Acrobat Reader
** Adobe CS4
*** Adobe Updates
** AutoCAD 2011
** AutoCAD - Architect 2011
** AutoCAD - Revit 2011
** Audacity 1.2.6
** Autodesk Maya 2011
** Cycling 74 MAX/MSP/Jitter 5.1.3
** Firefox
** Google Earth
** Google Sketchup 7.1
** ImgBurn - CD/DVD burner
** Microsoft Internet Explorer
** Microsoft Office 2010
** Trend Micro Virus Scanner
** Notepad Plus 5.8.5
** Putty .06
** [http://www.sassafras.com Sassafras] K2 Keyserver Client
*** Host DNS Name = '''research-keyserver.iat.sfu.ca'''
** SolidWorks 2011-2012 Educational Version
** VLC 1.1.5
** WinSCP (file transfer client)


== Windows 7 DVD image ==
== Windows 7 DVD image ==
Line 42: Line 106:


=== DVD contents ===
=== DVD contents ===
Final DVD not available yet.
Final DVD available. Work on unattended deployment in progress.


== Server-based Software Deployment ==
== Server-based Software Deployment ==
This section covers information about software on the file server. Updates will be available as they become available.
This section covers information about software on the file server. Updates will be available as they become available.


* Microsoft Office 2007 Enterprise Edition
=== Adobe Acrobat 9 Reader ===
** TBD
* configured such that the destination folder is C:\Adobe\
** TBD
* configured such that the Reader is for viewing PDF (and Acrobat Professional for creating/editing)
* Adobe Creative Suite 3
* configured to '''unattended install''' via special shortcut
** TBD
 
** TBD
=== Adobe Creative Suite 3 Master Collection ===
* Adobe Creative Suite 4
* scripted to install everything
** TBD
* configured such that the destination folder is C:\Adobe\
** TBD
* configured to '''unattended install''' via special shortcut
* SolidWorks 200X???
* includes clean-up script in separate folder (MUST run this prior to the installation if a previous version of Adobe product was present)
** TBD
* SSE2 (or better) processor is required for Premiere, Encore, and After Effects
** TBD
 
=== Adobe Creative Suite 4 Master Collection ===
* scripted to install everything
* configured such that the destination folder is C:\Adobe\
* configured to '''unattended install''' via special shortcut
* includes clean-up script in separate folder (MUST run this prior to the installation if a previous version of Adobe product was present)
* SSE2 (or better) processor is required for Premiere, Encore, and After Effects
* Minimum 2GB of memory is required
 
=== Autodesk AutoCAD Architecture Suite 2009 ===
* TBA
 
=== Autodesk Maya 2008 ===
* manual installation only
 
=== Microsoft Office 2007 Enterprise Edition ===
* patched with service pack 2
* scripted to install everything except Outlook
* scripted to add registry values to modify the following settings:
** Windows Update - Points to Lancer
** [http://support.microsoft.com/kb/299656 LAN Manager Hash] - Disable
** NumLock - Defaults to ON so users can use NumPad for numeric input
** Adobe Product Improvement Program  - Disable
* configured to '''unattended install''' via special shortcut
 
=== Microsoft Visio 2007 Professional ===
* patched with service pack 2
* configured to '''unattended install''' via special shortcut
 
=== Microsoft Visual Studio 2008 Professional ===
* got disc, now working on integration of SP1 and MSDN updates
* TBD
 
=== Dassault Systemes SolidWorks 2008 Office Premium ===
* upgraded to SP5.0
* configured to '''unattended install''' via special shortcut
 
=== TechSmith Morae 3.1.0 ===
* Manager - for viewing and analysing recorded data
* Recorder - for recording
* Observer - for viewing user remotely

Latest revision as of 19:29, 22 July 2011

Retrieved from "https://research.wiki.iat.sfu.ca/research/index.php?title=Enterprise_Deployment_for_Windows&oldid=5355"