Windows 7 64 Bit is to be deployed on a case-by-case basis. Please review this information to understand all considerations for Windows 7 Early Adopters, and the hardware requirements.

If you have any questions, please e-mail Chris Hester at chris.hester@ucsfmedctr.org.

Windows 7 Early Adopter Candidacy

issued: April 2013

Support Issues Early adopters need to understand that they’re part of a pilot, and that they will need to go through a speci�c channel (TBD) to report issues. We’re currently working out those details.

Data MigrationThis is a touchy subject. There’s a di�erence between a Refresh vs. Replace scenario. A refresh scenario is when an OS is wiped from the system and the user keeps the hardware for an upgrade to Windows 7. A replace scenario is when new hardware is introduced and the user’s original system is retained. The danger in a refresh scenario occurs when the data is extracted; there needs to be assurance that ALL the pertinent data is saved o� (User settings, application data, Favorites, Outlook PST �les, etc). The early adopter and FS tech needs to be heavily involved in ensuring that their data has been completely migrated. The FS tech must follow speci�c procedures using Microsoft Tools (http://www.microsoft.com/en-us/download/details.aspx?id=4503) to ensure the data migration process is thorough and complete. An agreed upon data retention period should be a part of an early adopter sign-o� agreement.

Hardware CompatibilitySee Supported Models tested for Windows 7 64 Bit below.

Software CompatibilityAn inventory of required applications should be gathered by a FS tech, and determine if the applications are Windows 7 64 bit certi�ed. This can be accomplished by running the Windows 7 Upgrade Advisor (http://www.microsoft.com/en-us/download/details.aspx?id=20) against their current XP SP3 system and note what applications are or are not supported in Windows 7. The early adopter needs to understand what will not be supported.

Printing The FS tech must pre-load Windows 7 64 bit drivers to known printers the user will be accessing. Our current printing infrastructure from the server side does not support 64-bit print drivers. The early adopter needs to understand that their printing capabilities will be limited to the drivers that are installed only. This will not be the case when we roll out to production, as 64-bit drivers on our servers will be installed by then.

Other Early adopters forgo the right to be granted “Local administrator” rights on their systems even for laptop owners. Exceptions will be made on a case-by-case basis.

*Based on models provided to Desktop Engineering thus far. More models will be tested/supported . As of 3/15/13

Dell OptiplexModels:

780790

9010 9010 AIO*

990

Dell LatitudeModels:

6430U E6400E4310 E6410E6320 E6420E6330 E6420

Panasonic ToughbookModels:

CF-C1CF-C2

HP Elite AIOModels:

8200

Considerations for Windows 7 Early Adopters:

Supported Models*:

Con�guration Manager (CM) requires you to boot into a WinPE environment to access the build media. The USB stick when complete, will boot your system into WinPE. The process below will involve formatting a

USB stick and then you’ll copy over the necessary CM2012/WinPE �les. Warning! These instructions will result in a format of your USB stick. Make sure you’ve saved o� your data!

System Center Con�guration Manager

issued: April 2013

420.568

Create CM 2012 USB Stick 1. INSERT USB stick into system 2. BROWSE to \\mcsccmwap001\iso$\Step1_Prepare_USB_Stick. 3. DOUBLE-CLICK Make_USB_Stick.bat. Script will take a few seconds to complete 4. BROWSE to \\mcsccmwap001\iso$\Step2_Copy_Files. 5. SELECT ALL FILES 6. COPY to USB Stick

Use USB Stick to Boot into CM 2012 Environment 1. When imaging a system that currently has an OS, be sure to �rst DELETE the host out of Active Directory. This will ensure that your Windows 7 system joins the domain into the correct OU and inherits the correct Windows 7 group policy settings 2. INSERT USB stick into computer that you’d like to image 3. BOOT into system using F12 (if Dell), or possibly ESC if HP or Panasonic model 4. When prompted, SELECT menu option and CLICK Next (Figure 1)

5. When prompted, DOUBLE-CLICK the OSDCOMPUTERNAME (Figure 2) 6. Edit Variable | Specify the value and the Value Settings TYPE the the desired host name in the VALUE �eld (Figure 3) 7. CLICK OK 8. CLICK NEXT to start your build

Created by UCSF Medical Center Learning Services

Figure 1

Figure 2 Figure 3