Physical Preparation

Before starting the re-imagine process, take the hard drive out of the computer. Then place a Device Tag on the hard drive and fill in the person’s details of who you are re-imaging the computer for. Take a ready to use hard drive from the office cabinet and check to make sure that it is the same or bigger size. Put this hard drive into the computer and begin the re-imaging process. Keep the original hard drive out for the subsequent BackUp & Restore Process (BURP) and then place Hard Drive on cart which will deliver the HD into the “Needs Approval” hard drive drawer in Client Support office.

 


Inventory and Network Membership

This will need to be done by a supervisor or someone with Access to these systems. Once this is done you can proceed to reimage the unit.

Pre-image Step 1: Load Configuration Manager Console with your SU account (Shift + right click, select “Run as different user” and enter in your SU login details.

Pre-image Step 2: Go to Site Database > Computer Management > Collections > All Systems. Then search for the OxyID of the Unit to find it.

Pre-image Step 3: Right click on the Unit and select “Manage Collection Membership” select the default package at the bottom of the page “Windows 7 64 Deployment” hit “OK“

Pre-image Step 4: Remove all of the other “Collection Memberships” this unit belongs to, only leaving the “Windows 7 64 Deployment” membership. You do this under Configuration Manager Console by going to Site Database > Computer Management > Collections > and selecting the Specific memberships the unit has listed on its packages selection page. You see the list it belongs to while doing the re-imaging.

Pre-image Step 5: Select the Specific membership group you see the unit assigned to, Then search for the OxyID of the Unit to find it in that group.

Pre-image Step 6: Right click on the Unit and select “Manage Collection Membership” select the “Remove from Collection” option and hit “OK

Pre-image Step 7: In ACID open the Inventory tool under “H:\NOS\Tools\ACID\InventoryUpdate\InventoryUpdate.exe” run that and Enter in the unit’s OxyID under Computer Name, to see who the “Current owner” is. change it to “Stock” from the owner dropdown menu and set the building it will be placed in. (Usually this will be ITSBackRoom.) hit Assign, Your done!.


Re-imaging

Step 1: Plug in the bootable reimaging USB labeled “SCCM”

Step 2: Press F12 as the computer starts up

Step 3: If the Boot Mode is set to LEGACY, switch to UEFI by selecting “Change Boot mode” use the “bios” password when prompted for a password.

Step 4: Select UEFI USB Storage Device

(If you don’t see Internal HDD as an option, that means the Hard drive is not functioning or connected properly and will fail)

reimage-6

 

Step 5: Hit F8 when it asks for a password so you can partition and clean (format) the hard drive

reimage-7

 

Step 6: Type: diskpart

reimage-2

 

Step 7: Type: list disk (this will show you all the Hard drives connected to the PC, if you don’t see the hard drive on disk 0, check Harddrive connection)

 

Step 6: Type: select disk 0

reimage-1

 

Step 7: Type: clean

reimage-5

 

Step 8: Type: exit

Step 9: Type: exit

reimage-3

 

Step 10 Type the techs account password

reimage-8

 

Step 11: Select Win7x64 Image

Step 12: Pull out USB and then hit Finish

reimage-4


Note: If the re-image fails at this point, you can check the logs by opening the command prompt (F8), the log file (smsts.log) will be located in either of these 5 locations depending on when it failed. Here is where they would be

Phase Location
Windows PE
(Before the hard disk are formatted)
x:\windows\temp\smstslog\smsts.log
Windows PE
(After the hard disk are formatted)
x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows Operating System
(Before the SCCM client is installed)
c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows Operating System
(After the SCCM client is installed)
c:\windows\ccm\logs\Smstslog\smsts.log
Windows Operating System
(When the Task Sequence is complete)
c:\windows\ccm\logs\smsts.log

navigate to log directory and open log in notepad, (notepad smsts.log) you will need to check the end of this file’s content to see where it stopped, Core/Steven needs this info if we need them to diagnose a reimaging error. Read more


If this re-image is successful, continue…

Step 13: Start up the Unit and login with the “techs” user account, there will be a bunch of installs that run once you get in, let those finish and then run any Windows updates in the system tray then logoff and shut down the Unit.

Step 14: Take unit to Client Support office and place on the ready to deploy shelf.

The computer will reboot and after which it will go through the imaging process (installing the Operating System and standard programs). It takes about an hour and a half (sometimes more). When the reimaging is finished, you will receive the CTRL-ALT-DELETE screen. At this point you should log in as techs to install any other applications and print drivers.

Step 15: your Done! … now pat yourself on the back.


 

Trouble Shooting

Popup asking for Computer number – This is due to the unit not having it’s MAC id or OxyID stored on the network. Enter in the ID and wait 30mins for the data to propagate over the network, then press “OK” on popup to continue the re-imaging. You will then see a Popup with the Units OxyID and the LDAP membership details. press “OK” and continue the install. If it failed you will need to Delete the MACs file for that unit remote desktopping into sccm03 with your SU account and heading to C:\MACs on that server. You will also need to check SCCM to make sure the unit has not been placed in “Unprovisioned Computers”