I've uploaded the NIC drivers to the Boot image files for both x86 and x64. When I do a PXE boot on the server it does find my WDS server and does recieve the boot file to boot up. After it downloads via tftp if then configures nic and storage settings. But right after that (right before the password screen usually prompts) the server just reboots with no errors.

I've looked at my SMSPXE logs on the WDS server and it doesn't report any errors. SCCM doesn't report any errors as well. I keep thinking it's something to do with the NIC drivers. Or possible the Storage drivers? How do I verify the storage drivers are actually getting pulled to the machine?

It just kind of strange to me, because every other machine i've imaged all have booted up flawless with an exception of importing NIC drivers every once in a while. But i've never seen a machine just reboot in WinPE without any warning.

Thank you for all your help.. it's greatly appreciated.

I am very new to SCCM 2012 and currently looking into deploying Win2008 R2 via boot (we have chosen not to go for pxe as we dont have DHCP enabled).

I have read many sites which mention we must build and capture the image - im a bit confused as for a boot image how is this done?

if anyone can point me to a link or youtube vid will be grateful.

many thanks for all help in advance.

Kabir

I understood that you can name machines like desktop001, laptop001 based on above but currently we have a spreadsheet for inventory/mac/user.

How do I proceed if isVM is true? It can be a VDI PC image or server.

I am yet to fully understand the significance of these variables when I can find the Model #

I configured the SCCM as per part 1, 2 and 3.

and tried to deploy new server but received errors shown on the screen attached.

Can you please help?

Thanks

Dritani

This 3 part guide is aimed at those of you who can succesfully deploy applications (such as Microsoft Office or Firefox) and Operating Systems (such as Windows Vista SP1 and Windows XP sp3. You'll need to be familiar with Microsoft SMS or SCCM and understand what packages, advertisements and collections mean, the guide will however link you to other guides to bring you every step of the way down the entire path.

Part 1.

* Add new Operating System Install Package

* Import new Task Sequence

Part 2.

* Create and then Update distribution points for the MDT Server packages

* Editing the Task Sequence

* Adding Server Roles and Features

Part 3.

* Create a new collection

* Advertise the Task sequence to a collection

* Add server to collection

* Set the IP address as a variable

* The Deployment

* Troubleshooting PXE errors

The guide above has taken a lot of time to document and I'm quite sure that you will find it helpful (lots of screenshots of every step..)

good luck,

cheers

anyweb

I am doing a simple image deployment of the install.wim in the source folder that comes with the Server 2008 CD. I have added the install.wim to operating system images and created a task sequence using just the wim. I didn't create a package for the root of the ISO as shown in the set by step document on this site. Anyway, the install.wim deploys fine, everything boots all drivers load that I have loaded in SCCM, the only problem I am having is that the system drive keeps reverting to the D: drive.....Anyway around this????

Once.

After trying to redeploy it, it doesn't work now.

So i tried a different task sequence that will join the pc to the domain and also enable the admin account.

No love.

won't even return to the task sequence to apply the windows settings....

it will apply the operating system and then reboot to set it up. and then after a reboot it comes right up to the windows 2008 logon screen.

Am I missing something? I can't get to the logs, because there is only one account on the server and it is stripped of its administrator capabilities.

Any thoughts?

Configuring PXE boot, what services need to be setup what filename to look towards for deployments

Configuring Boot file to contain a boot cd for both x86 x64 configurations

Configuting A windows Pe image.

Thanks for anyones help in this matter...

When attempting to PXE boot using a Windows PE x64 image, the actual .wim is downloaded from the PXE service point/distribution point as shown by the progress bar. After 100% completion the screen goes black, Windows PE is not loaded and the VM turns off.

Details:

I am using an MDT Task Sequence for deploying the Windows Server 2008 Operating System Install package. I simply copied it and changed the boot image on the Task Sequence instead of creating a new Task Sequence from scratch (not sure if this makes a difference or not). I was able to boot into it by using the Create a Task Sequence wizard (non MDT) but the sequence stalled before doing anything and rebooted.

The drivers for VMware have been imported into the boot image as well.

Environment:

SCCM 2007 SP2 R2 running on Windows Server 2003 SP2

Target VM: 2GB of RAM, 40GB harddrive

Any assistance would be great.

Let me Start off my thanking you for the Step by Step Guide you created.. Great Job!!

I am resposible for maintaining our server images and have now been tasked with getting them ready for deployment via SCCM.

Being a total SCCM NOOB your guide is greatly appreciated!

My problem:

In Following the guide "How can I deploy Windows Server 2008 using SCCM 2007 sp1 step by step guide -Part 1"

the option "Import Microsoft Deployment Task Sequence" is missing from my drop down menu.

Any ideas on what I am doing wrong?

We are on SP2.. and not sure if that would be the reason behind that option not being available.

Thanks in advance.

http://blogs.technet.com/configurationmgr/archive/2010/02/17/when-deploying-windows-server-2008-using-an-sccm-2007-osd-task-sequence-additional-disks-may-show-as-offline-when-the-task-sequence-completes.aspx

J.C. Hornbeck | Microsoft

http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/7e06ee89-df1f-4db4-a164-b1ae0679956c

Based on your step-by-step guide for how to deploy w2k8 with sccm07, i have build a task sequence.

the ts begins to run, settings being captured, client reboots to boot image, but os image is not being installed.

the report of the ts looks like this:

Report Name: Advertisement status messages for a particular client and advertisement

Category: Software Distribution - Advertisement Status

Comment: This report shows the status messages reported for a particular computer and advertisement.

Parameters: Advertisement ID JIZ20052

Computer Name ******

Advertisement status messages for a particular client and advertisement

09.02.2010 08:57:48 (Number of Records: 43)

Time Message State Name Message Name Message ID Record ID

09.02.2010 08:52:52 Waiting Waiting for content 10035 254923

09.02.2010 08:52:54 Accepted Program received 10002 254924

09.02.2010 08:52:55 Running Program started 10005 254925

09.02.2010 08:52:57 Running The task sequence execution engine started execution of a task sequence 11140 254926

09.02.2010 08:52:57 Running The task sequence execution engine started a group 11124 254927

09.02.2010 08:52:57 Running The task sequence execution engine started a group 11124 254928

09.02.2010 08:52:57 Running The task sequence execution engine skipped a disabled action 11128 254929

09.02.2010 08:52:57 Running The task sequence execution engine skipped an action because the condition was evaluated to be false 11130 254930

09.02.2010 08:53:39 Running The task sequence execution engine successfully completed an action 11134 254932

09.02.2010 08:53:40 Running The task sequence execution engine successfully completed an action 11134 254933

09.02.2010 08:53:42 Running The task sequence execution engine successfully completed an action 11134 254935

09.02.2010 08:53:42 Running The task sequence execution engine successfully completed execution of a group 11127 254936

09.02.2010 08:53:42 Running The task sequence execution engine started a group 11124 254937

09.02.2010 08:53:42 Running The task sequence execution engine started a group 11124 254938

09.02.2010 08:53:43 Running The task sequence execution engine successfully completed an action 11134 254939

09.02.2010 08:53:44 Running The task sequence execution engine successfully completed an action 11134 254940

09.02.2010 08:53:44 Running The task sequence execution engine successfully completed execution of a group 11127 254942

09.02.2010 08:53:44 Running The task sequence execution engine successfully completed execution of a group 11127 254943

09.02.2010 08:53:44 Running The task sequence execution engine started a group 11124 254944

09.02.2010 08:53:45 Running The task sequence execution engine successfully completed an action 11134 254945

09.02.2010 08:53:46 Running The task sequence execution engine successfully completed an action 11134 254946

09.02.2010 08:53:46 Running The task sequence execution engine successfully completed execution of a group 11127 254947

09.02.2010 08:53:46 Running The task sequence execution engine started a group 11124 254948

09.02.2010 08:53:46 Running The task sequence execution engine skipped a group because the condition was evaluated to be false 11122 254949

09.02.2010 08:53:46 Running The task sequence execution engine successfully completed execution of a group 11127 254950

09.02.2010 08:53:47 Running The task sequence execution engine started a group 11124 254951

09.02.2010 08:53:47 Running The task sequence execution engine started a group 11124 254952

09.02.2010 08:53:47 Running The task sequence execution engine successfully completed an action 11134 254953

09.02.2010 08:54:32 Running The task sequence execution engine performed a system reboot initiated by an action 11142 254956

09.02.2010 08:56:08 Running The task sequence execution engine started execution of a task sequence 11140 254960

09.02.2010 08:56:10 Running The task sequence execution engine successfully completed an action 11134 254961

09.02.2010 08:56:12 Running The task sequence execution engine successfully completed an action 11134 254962

09.02.2010 08:56:13 Running The task sequence execution engine failed executing an action 11135 254963

09.02.2010 08:56:13 Running The task sequence execution engine ignored execution failure of an action 11138 254964

09.02.2010 08:56:36 Running The task sequence execution engine failed executing an action 11135 254965

09.02.2010 08:56:36 Running The task sequence execution engine started a group 11124 254966

09.02.2010 08:56:36 Running The task sequence execution engine successfully completed an action 11134 254967

09.02.2010 08:56:39 Running The task sequence execution engine successfully completed an action 11134 254970

09.02.2010 08:57:09 Running The task sequence execution engine successfully completed an action 11134 254971

09.02.2010 08:57:10 Running The task sequence execution engine successfully completed an action 11134 254972

09.02.2010 08:57:10 Running The task sequence execution engine successfully completed execution of a group 11127 254973

09.02.2010 08:57:10 Succeeded The task sequence execution engine successfully completed a task sequence 11143 254974

09.02.2010 08:57:10 Succeeded The task sequence manager successfully completed execution of the task sequence 11171 254975

the two errors saying this:

The task sequence execution engine failed executing the action (Request State Store) in the group (Refresh Only) with the error code 50 Action output: . The operating system reported error 50: The request is not supported.

The task sequence execution engine failed executing the action (Backup) in the group (Refresh Only) with the error code 2 Action output: 5.0.1641.0 The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. Drive C: 9073644 Local store path = C:\_SMSTaskSequence\StateStore Total used space: 9073644 Available space atC:\_SMSTaskSequence\StateStore: 22389624 Backup can use local path Property OSDStateStorePath is now = Computer backup will use network path (ComputerBackupLocation=AUTO) WARNING - Unable to validation connection because a blank UNC was specified.Beginning backup of drive C: About to run command: cmd /c ""C:\_SMSTaskSequence\WDPackage\Tools\X64\imagex.exe" /capture /compress maximum C: "\*****.wim" "201002091756CDrive" >> X:\windows\TEMP\SMSTSLog\ZTIBackup_imagex.log 2>&1" Process completed with exit code 2 Return code from command = 2 Error creating an image of drive C:, rc = 2 ztibackup COMPLETED. Return Value = 2 Property BackupScriptComplete is now = YES ZTI ERROR - Non-zero return code by ztibackup, rc = 2 Command line returned 2. The operating system reported error 2: The system cannot find the file specified.

Any ideas what the problem could be?

thanks

Create and then Update distribution points for the MDT Server packages

Now that we have created the Task Sequence, packages files and folders necessary to support the Server deployment we need to make sure to create and then update distribution points for each MDT Server package, the Configuration Manager Client Installation package has already been pushed out to the distribution points so we don't need to do that again.

Expand Microsoft MDT Server Settings files and right click on distribution points, click new distribution points and when the wizard starts click next.

Select the standard distribution point only and click next, then close when done.

Right click the Distribution point and choose upadte distribution points,

answer yes at the confirmation screen

Repeat the above (create distribution points and then update them) for Microsoft MDT Server Source Files.

The boot.wim is being applied and the TS is successfully processing up till the State Restore function at this point in time the Gather tasks fails.

The apply updates has been disabled (I've re-enabled it this morning) if I set the gather task to continue on error I then fail on the subsequent Tattoo task. (this occurs on both x86 and 64bit builds)

This problem does not occur with the virtual server builds, it feels like drivers as this is really the only difference between a virtual platform and physical but I figured I'd ask the question here and see if this has occurred to anyone else before and how they overcame the issue.

I guess my real question is what do these tasks do as I can't honestly say I know at this point in time.

If I look at the ztitatoo.wsf it looks to just edit registry and appling a mof file while the gather task well doesn’t have a rule to run by default.

cheers