Tech Blogs

SMSTS.LOG is very useful in troubleshooting the SCCM OSD issues. The location of this log file varies with the stage of OSD depending on the build and architecture. You have to press F8 during the OSD to get the command prompt window. Phase of OSD Location of SMSTS.LOG WindowsPE, before HDD format:  x:\windows\temp\smstslog\smsts.log WindowsPE, after HDD format: x:\smstslog\smsts.log Windows, SCCM agent not installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log Windows, SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log Windows x64, SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log Task Sequence completed: c:\windows\system32\ccm\logs\smsts.log Task Sequence completed x64: c:\windows\sysWOW64\ccm\logs\smsts.log

This post explains the step by step by procedure (flow) to build, capture and deploy Operating System to a bare metal machine. It covers: A] Preparing SCCM Server for OSD B] Building and capturing OS image C] Deploying Operating Systems. There are two methods to capture OS image. a] Using Task sequence to capture  the OS from a reference machine.(Automating BUILD as well) b] Using Manual method.( build an operating system and then capture using SCCM) Here, I am building and capturing the image through Task Sequence. And also not using any USMT to migrate data since it is a plain bare metal deployment, not an upgrade. A]. Preparing SCCM Server for OSD: 1. Install WDS server role WDS 2. Install and configure PXE service point. PXE Service Point 3. General Supported Configurations. 4. Create and set Network access account.  5. Create and distribute the Configuration Manager 2007 package, all the relevant KB updates as packages. This post helps to create...

The below post explains the steps to create a Task Sequence for Deploying Windows 7 1. In the SCCM 2007 Console, navigate to Site Database / Computer Management / Operating System Deployment and right-click the Task Sequences node and select New – Task Sequence. 2. On the New Task Sequence Wizard, in the Create a New Task Sequence screen, select Install an existing image package and then click Next . 3.  Task Sequence Information : On this screen, enter the appropriate task sequence name, comments and select the Boot Image that has to be used. Here, I am deploying 32 bit OS and I have selected X86 boot image as shown.  Click Next to proceed. 4.  Install Windows  : On the  Install the Windows Operating System  screen, at the Package field, select Browse. Select the Operating System Install Package i.e.  Windows7 32 Bit OS 1 en-US  ( here). On the  Edition field , use the drop-down to select image : ...

The following post shows the process how the reference machine image is captured. The below components are already in place. 1. PXE Service Point is installed. 2. DHCP  Server is configured for automatic IP assignment. 3. OSD Source specified and distributed the package to all DP's Steps: 1. Start the Reference machine and allow it to boot from the network. In this phase- it gets the IP Address from DHCP Server, IP address of SCCM Server, checks the architecture( whether it 32 or 64 bit) and contacts the SCCM Server for further actions. 2. Next it downloads  the BOOT.WIM  File from the DP and the process is shown as " Windows is downloading the files". 3. After the download is complete, it opens  the "Task Sequence Wizard". Enter the password and click next to retrieve the policy. Press F8 Key to get the Command Prompt support as shown. 4. The Task Sequence Wizard will appear displaying a list of task sequences available, se...

After the Task sequence is created, it has to be advertised to computers to capture the image. The below steps detail the tasks to be followed when advertising a task sequence. 1. In the SCCM 2007 Console, go to the task sequence that has to be advertised. Right click on the task sequence( here it  is "Windows7 Reference machine") and click Advertise. 2. On the New Advertisement Wizard screen, in the Collection field, click Browse to select the All Unknown Computers collection. 3. To PXE Boot, check the Make this task sequence available to boot media and PXE and then click Next . 4. Schedule : On the schedule tab, leave the defaults and click next. 5. Distribution Points : On the Distribution points screen, select the  Access content directly from a distribution point when needed by the running task sequence. Click Next. 6. Interaction : Since it is not a mandatory advertisement, users will have an option to  run independen...

Definitions : Task sequence:  A task sequence is a series of one or more task steps that can be advertised to Configuration Manager 2007 clients to run user-specified actions. Task sequences are used with Operating System Deployment to build source computers, capture an operating system image, migrate user and computer settings, and deploy an image to a collection of target computers. Reference Computer : A reference computer is a fully-configured computer from which a WIM file can be  generated  that will be used to distribute operating system images to target computers. Target Computer:   The target computer is the computer on which you install a Microsoft® Windows operating system image using Configuration Manager 2007 Operating System Deployment. The below post explains the steps to create a Task sequence to build and capture Windows 7 Reference machine. 1. In the SCCM 2007 Console, navigate to Site Database / Computer Management / Operating Sys...

To initiate Operating System Deployment and in order for machine to use WinPE Boot images, the boot images available in SCCM should be first distributed to all the available Distribution Points. The below post explains how to enable the command Prompt support and distributing Boot images. Command Prompt support helps in troubleshooting OS deployment issues. When F8 is  pressed during the OS Deployment or capturing process, a command prompt window pops out which can be used to view the SMSTS.LOG. Enable Command Prompt: In the SCCM Console, go to Boot images under OSD node of Computer management. Select "Boot image (x86)" ,Click on properties from Actions menu and select the "Windows PE" tab. Check the " Enable Command Support" ( Testing Only) to enable command prompt support. Click OK, it will pop up a dialogue box asking to update DP's. Click  yes and click Ok.The “Manage Distribution points Wizard” will appear, click Next to continue...

If the Boot images in the OSD node of the SCCM 2007 are deleted by mistake, there is  no need to worry as we can retain them from the SCCM Server itself. The SCCM server has the boot images in the below path. \\SCCMServer\sms_SiteCode\OSD\boot\i386 for 32 bit Operating System boot image and \\SCCMServer\sms_SiteCode\OSD\boot\x64 for 64 bit The below steps explains how to retrieve the deleted boot images: 1.In SCCM 2007 console, go to Boot Images node under Operating System Deployment under Computer Management. Click on "Add Boot Image" as shown.Provide the network path where the boot images are stored. Click Next 2. Provide a name, here I am importing the 64 bit boot image and I have named it as "Boot image (x64)".Click  Next. 3. On the summary page, review and click Next. It will take a couple of minutes to import. Once it is done, click Close and the deleted boot image re-appears in the console.

To deploy SCCM 2007 Client agent using software distribution or OSD, we have to create a package for it. As the client source files already exists on the server, we have an option called " Package from Defintion" on the software distribution >> packages node. This "Package from definition" can be used to create the SCCM 2007 Client package. There is no need to create  additional program, it will be created automatically and just needs to be distributed to DP's for installing on clients. The program name that will be created is " Advanced Client Silent Upgrade". We can further customize this program to suit the organizational requirements. Creating the SCCM Client package: The procedure to create SCCM 2007 client package : 1. In the SCCM 2007 Console, go to  Site Database / Computer Management / Software Distribution/ Packages node> Right click on it and select " Package from definition" as shown. 2. On  Create Packag...

The primary function of  this Network access account is to access the network resources. The access level can be "domain users" and that would suffice for the account to work fine in accessing any resources over the network.( with proper permissions) Uses : in OSD, Software Distribution for accessing packages. Access level : part  of Domain Users group. Here, I have created a domain user account "SMSADMIN" and set it as Network  access account. The below procedure can be followed to set Network access account. 1. In the SCCM Console Go to  Site Database / Site Management / <site code> - <site name> / Site Settings / Client Agents. 2. Select Computer client agent, right click and click  properties. 3. Under General Tab>>>Network Access account>>> click on "Set" button 4. On the windows user account dialogue box, enter domain\username and password. Click OK, apply to  set the Network access account. ...