Hi

I wanted to start a discussion about OS deploy methods.

my organization doesn't want to allow the OSD task sequence to All Systems. even when it's protected with password and it's PXE\Media only - we don't want all computer \ server within the network to be able to boot to F12.

so what we do is allowing the deployment to a specific collection

when a technician is at the client and he want to start an OS deployment - he calls the SCCM team and ask then to add a computer to a collection with MAC Address \ SMBIOS GUID. well... we have some problems with this method, but on the other hand we don't want technicians to have permissions on the console and just install it wherever they want.

we just want them to have this simple option of adding a new\existing computer's MAC address to a specific collection without giving them high privileges on the console.

I have a feeling that this dilemma exists in almost every Enterprise so I was wondering if you have a special tool \ method for that?

thanks

Tamir Levy

Hello,

I'm trying to deploy & capture a Windows 7 x64 Ent SP1, using SCCM 2012 R2 & MDT 2013 U1.

I`m also using Windows Server 2012 R2 Hyper-v, so this is a virtual machine (no drivers etc).

During the TS, on the "Setup is preparing your computer for first use" I receive this error: "Task Sequence failed with error 0x80070002"

I look into Monitoring\Overview\System Status\Status Message Queries\All Status Messages and I have one message ID:11135

The task sequence execution engine failed executing the action (Use Toolkit Package) in the group (State Restore) with the error code 2147942402
Action output: ... pszPkgID, sPath, 0, hUserToken, mapNetworkAccess), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\runcommandline.cpp,399)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,372)
WinHttpSendRequest failed.
SendWinHttpRequest failed. 80072ee2.
DownloadFileWithRanges() failed. 80072ee2.
DownloadFile() failed for http://SCCM01.company.local:80/SMS_DP_SMSPKG$/00100009/sccm?/Scripts/DeployWiz_Applications.xml, C:\_SMSTaskSequence\Packages\00100009\Scripts/DeployWiz_Applications.xml. 80072ee2.
Error downloading file from http://SCCM01.company.local:80/SMS_DP_SMSPKG$/00100009/sccm?/Scripts/DeployWiz_Applications.xml to C:\_SMSTaskSequence\Packages\00100009\Scripts/DeployWiz_Applications.xml
DownloadFiles() failed. 80072ee2.
Download() failed. 80072ee2.
Failed to resolve the source for SMS PKGID=00100009, hr=0x80070002
Install Software failed to run command line, hr=0x80070002. The operating system reported error 2147942402: The system cannot find the file specified.

From the VM, I also look into C:\windows\CCM\Logs\smstslog\smsts.log and one of the messages is:

ZTI deployment failed, Return Code = -2147024894  0x80070002

Any advice on how to troubleshoot this one ?

Thank you.

Hello

Thank you for you time and help

I am trying to set up a test OSD deployment on a virtual system. I have followed my book and it looks like its been set up correctly. I read lots of posts in this forum and others and I am still having issues. 

The Issue

When booting a client system getting "PXE-E53 - No boot filename received"

That I have done

1. Made sure that both my X64 and X86 Boot files have been distributed with "Deploy this boot image to from PXE-enabled DP" on both of them (looked under content statues on my DP and both are at 100)

2.Removed my DP and WSDS role and restarted and reinstalled

3. Created a new Boot image using a windows 2012 R2 DVD and used this in my task sequence, I removed both  of the boot images  (this got a bit further but I got an error telling me that It needs both X64 and X86). SO I readded them to my DP from the boot folder of my  E:\Program Files\Microsoft Configuration Manager\OSD\boot folder)

Here is my SMSPXE file

Client is set to use HTTPS when available. The current state is 224. SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
Adding TRD00015.3 SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
Adding TRD00016.2 SMSPXE 19/04/2015 16:15:47 6616 (0x19D8)
Found new image TRD00015 SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Opening image file E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Found Image file: E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim
 PackageID: TRD00015
 ProductName: Microsoft® Windows® Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Closing image file E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Found new image TRD00016 SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
================= PXE Provider loaded. ===================== SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0) SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
MAC Ignore List Filename in registry is empty SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
Begin validation of Certificate [Thumbprint C4D34F3B6322A19274BBC9EF1F9D71ECC8B9EC71] issued to 'c8b0427c-2014-419b-b251-ef0a6fbd96a0' SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
Completed validation of Certificate [Thumbprint C4D34F3B6322A19274BBC9EF1F9D71ECC8B9EC71] issued to 'c8b0427c-2014-419b-b251-ef0a6fbd96a0' SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
Initializing PXEPerfObject. SMSPXE 19/04/2015 16:17:54 4496 (0x1190)

I have a SCCM 2012 SP1 CU4 environments with Windows 7 SP1 computers.

I am deploying the machines using a task sequence, which all worked fine.

Now I want to Pre-Provision the laptops with BitLocker to save hours of time after the installation which is required for bitlocker the disk. So I want to speed things up.

I changed my current task sequence to use Pre-Provision which seems to work.......but....

After the machine is deployed I sometimes (!) got a D-drive which is the 500MB System Reserved boot partition.

My OS is properly installed on the C-drive...that is worinkg fine and the C-drive is also completely bitlockered.

But why is my boot disk (System reserverved) partition not hidden and does it contain a drive letter ???

Any ideas what goes wrong here ?

I checked the partition section in the task sequence and the 500MB disk should not get a drive letter. I configured it to not get a drive letter !

Could you problem be related to BIOS updates which are installed after the OS is installed during the task sequence ???

Strange however is that is sometimes goes wrong and sometimes OK......I could not found why :-(

I'm not quite sure where to begin but here is some background info:

SCCM 2012 started with initial release (clean install) and was upgraded to SP1 a little more than a month ago.

A large deployment (Cas, 2 primary sites (with dedicated DB servers), and currently around 30 DPs).

Up until last Friday things were going well.  Then starting last Monday (2/18/2013) I initially got reports that endpoint that were trying to be imaged via PXE and bootable media were failing to find task sequences.  The machines would successfully boot into WinPE but report no task sequences are available.  In reviewing the SMSTS.log file on a endpoint, it shows that it successfully finds the preexisting SCCM computer object (SCCM object GUID and name displayed in the log matches what is shown in the SCCM console).  It also shows a successful policy assignment retrieval but 0 policy assignments, 0 collection variables, 0 machine variables even though the SCCM object has more than one TS deployed to it and a machine variable.   The object has both the MAC address and I added the BIOS GUID to make sure it isn't a GUID conflict (which is doubtful since it affects other endpoints) and it still had the same result.

Any other ideas on what is going on?

I have one primary site with Distribution point enabled and all the necessary roles are installed to deploy OS with Task sequence.

All the share permissions are on point

all the site roles status are up without any major/critical error

Now here's the problem I am having, I'm deploying windows 8.1 pro, the task sequnce stops after applying the OS and then rebooting to windows OOBE, from what i have noticed is that the taks seqence stops during the configmgr client installs.

here's the errors i have extracted from the log file from top to bottom:

01)  Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagementClientConfig' class defintion. Error 0x80041002. Default value will be used for this property    TSManager    19/04/2015 21:55:58   936 (0x03A8)

02) Error getting system isolation info. Code 8027000C    TSManager    19/04/2015 21:56:12    936 (0x03A8)

03) Remediation failed. Code 8027000C    TSManager    19/04/2015 21:56:12    936 (0x03A8)

04) Remediation failed with error code 8027000C    TSManager    19/04/2015 21:56:12    936 (0x03A8)

05) Task sequence execution failed with error code 80004005    TSManager    20/04/2015 13:26:20    936 (0x03A8)

06) SetObjectOwner() failed. 0x80070005.    TSManager    20/04/2015 13:26:20    936 (0x03A8)

07) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002    TSManager    20/04/2015 13:26:20    936 (0x03A8)

08) Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    20/04/2015 13:26:21    936 (0x03A8)

09) ReleaseRequest failed with error code 0x87d00317    TSManager    20/04/2015 13:26:21    936 (0x03A8)

any help would be much appreciated.

Many thanks

I have a OSD task sequence with pre-provision of bitlocker and have created partitions following the images in this thread:

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/7a9b6953-7dad-4935-b480-ce4b6f75e5a7

Pre-provision seems to be working, but the BDEDrive is assigned letter C: and the OSDisk gets D: although the BDEDrive should not be assigned a letter.

When the workstation is done installing the BDEDrive is visible. What am I doing wrong? I would like to end up with the os on C: and the BDEDrive not visible.

Carl

I have followed just about every how to I can find to enable and activate the Dell TPM using CCTK. The problem is that it fails every time, whether installing the WinPE HAPI drivers or setting the BIOS password. From everything that I have seen, my run commands are correct. This leads me to believe that my package has files missing/I am not pointing to the right file in the package?

I created two subfolders within my CCTK package, the x86 and x86_64. However, nothing I have read tells me where to place/what to do with the CCTK configuration file I exported.

Any help would be fantastic!

Can you create a task sequence that only runs the steps to enable BitLocker and nothing else and send it to a set of computers?
Or could this cause some problems?

Hi there,

I would appreciate some advice on creating a task sequence for Win8.1 with TPM enabling for Dell laptops; I have BitLocker set up manually with a Group policy, but want to have TPM enabled in the task sequence. I have read older posts on sites such as windows noob, but can't see how to reference the CCTK and get TPM going for win8.1 in a SCCM2012 environment. 

Obviously I haven't created this before so any help would be appreciated; I have noticed when I try to import my CCTK configurations into SCCM as it isn't a zip file I cannot do it.

Dear All...........I am looking to build a solution for our helpdesk who have to install OS and Applications to customers laptops on daily basis.

At the moment, I am trying to understand different aspects so there are some confusions which I would like for others to address:

1.  Can we create different OS Images as VMs for Deployment?  Is this possible? Or we can only have VHDs for different OS Images?

2.  Can we have an OS Image with VMs inside it to be deployed? Such as when we deploy an OS to a laptop, the deployed OS also has a VM inside it for use with legacy applications? 

3.  Once OS is deployed on the laptop, I want users to access the applications through a centralized system and install them as they like it.  Applications should install on the laptop and run from there as well (no streaming)?  Is this possible.

4.   Keeping above requirements in mind, is it possible to implement User Experience Virtualization as well in this imaging scenario?  By keeping User Data and Settings somewhere else so that if they lose the laptop, new installation does not take much time and not much data is lost either.

5.   In such a scenario, can we also implement Bitlocker in the OS Image? OR is it not possible?  If so, does Bitlocker support Data Leakage Protection?

We've been imaging Surface 3 tablets for a while with SCCM 2012 R2 CU4 since CU4 came out. Recently the task sequence is failing while applying drivers. On the screen is a DISM.exe application error.  

"The instruction at 0xa7356ccc referenced memory at 0x258d1a58. The Memory could not be read"

The SCCM task Sequence Error is 0xC0000005

I cannot find a DISM log, probably because it's an application crash. The SMSTS Log isn't much help either.

I've changed from apply driver package to auto-apply, refreshed Distribution Points for the driver packages and the boot images.

Our Windows 7 Task Sequences are unaffected. Seems to only be the Windows 8.1. 

Looking for assistance... I am trying to get Bitlocker/MBAM 2.5 Working on a Windows 7 x64 Enteprise Tast Sequence and I am running into some issues.  (I have read tons of blog post I am just stuck)

First I am doing this on Dell Laptops and I get errors in Task Sequence when trying to run the cctk.exe in the task sequence but I can run it manually (UGH)

Second I know for MBAM to work the TPM needs to be enabled, activated, Not Owned and Endorsement Keys Paired on this machine I have the TPM Enabled, Activated, and Endorsement Keys Paired, but the Stupid thing is owned.   When I try to run a script to take ownership of it it gives me the following error:

ERROR - Failed to take ownership of TPM with the following exit code: 80280014 (Using the ownership script from here)

I am at a lost and frustrated with this whole process.  I would appreciate any guidance on this process.  (Screenshots, TS Exports, Scripts, etc...)

Hello,

We are currently receiving a few machines that have UEFI only firmware. We have been using DHCP option 66 and 67 with SMSBoot\\x86\\wdsnbp.com in 67 for some time now and it worked well. We did face issues with UEFI but we could always choose to select legacy BIOS firmware. This is changing and so must we.

I have been doing some troubleshooting this morning and discovered that setting DHCP Option 67 to point to SMSBoot\\x86\\wdsmgfw.efi does not seem to work.

I am running the DP on Windows Server 2012 R2 so am pretty sure that x86 UEFI should be working.

Anyway I read online that we should try using IPHelpers instead. We spent an awful long time moving away from IPHelpers (our network guys said we should and we didn't see it as a problem at the time - way back when SCCM 2007 was in R2). Setting the IPHelper seems to have worked after changing the boot image on the task sequence to use the x64 boot image. We have asked our network guys to change back to using IPHelper but I have a few questions about UEFI and deployments of x86 operating systems.

• Does the UEFI Firmware or WDS or some other mechanism detect that the machine can support x64 so just download the x64 EFI file from the remoteinstall\SMSBoot\x64 folder? If so then how does it do this detection and can we make it think it is x86? Most machines now have x64 capability so would presumably be detected as x64 but that doesn't always mean we want to deploy x64. Mostly for legacy software etc. Is the only option here to prey that the machines come with a BIOS firmware fallback? What if they don't? Are we going to have to use other boot media?

Thanks in advance for any replies.

Hi,

I am running into this issue. We have SCCM 2012 in place and i have to migrate 900 remote sites (extremely slow bandwidth) with no DP, from XP to windows 7. Each site only have 1 PC running XP and my task is to do migration plus migrate data over from xp to windows 7 too using sccm. Please advise how it can be done? The critical thing is 'extremely slow bandwidth' with DP's or secondary SCCM between locations and head office. (The only server each site has is a old fedora server for POS purpose)

I understand in other scenarios i could have created 'Task Sequence' and had advertised it over the WAN but here it seems i cannot because of extremely slow bandwidth. 

Any help will be deeply appreciated.

Hi,

I hope this is the correct forum, if not I apologise. I have a working MDT2013 Task Sequence but I need to amend it so that it has a C Drive on one vhd file, called OSDisk, and an E Drive on another vhd, called WSUSDisk.

OSDISK is installing onto DISK 0, which is a Standard(MBR) disk. This is working fine.

In the TS, WSUSDisk is created on Disk 1 as a Standard MBR disk, the "Create extra 'Active' Partition checkbox is ticked. In the Volume Properties, I have unchecked the "Make this a boot partition" checkbox, and specified a specific size.

The Task Sequence runs to completion successfully, but when I log onto the completed VM, I need to initialize and format the WSUSDisk before I can use it.

I need to be able to access the WSUSDisk at a later stage of the Task Sequence, so I need to know how to initialize and format the Disk in the task sequence, and how to make sure it gets a specific drive letter - in this case E: as D: will be the DVD drive of the VM. I've had a trawl around but have not been able to locate anything.

Please can someone advise on how to do this best?

Many Thank

John

Regards, John

Hello,

I have been doing some reading about enabling UEFI. Looks pretty straight forward BUT I cant use the default "Unknown Computers" collection anymore for OSD. Looks like I need to create 2 collections, one for x86 and one for x64. My issue is understanding what these collections need in order to work correctly. Reading about UEFI the boot image that is needed needs to equal the architecture of UEFI, meaning even if the CPU is x64 with UEFI x86 enabled I need to use a x86 boot image + x86 OS.

I have read a few blogs about creating the 2 collections based on the hardware architecture but they dont have any indication of what is actually needed in the query. I assume I cannot just go off the CPU architecture since UEFI could be x86 even though the CPU is x64.

Any help is appreciated.

Thanks!

I have a strange issue trying to create standalone media. CreateTsMedia.log is throwing the following error and its related to every driver package that has the igfxexps32.dll file.

<![LOG[CContentDefinition::GetFileProperties failed; 0x80070003]LOG]!><time="00:21:53.884-180" date="04-21-2015" component="CreateTsMedia" context="" type="3" thread="17200" file="contentlibrary.cpp:1435"><![LOG[Failed to find properties of file igfxexps32.dll]LOG]!><time="00:21:53.888-180" date="04-21-2015" component="CreateTsMedia" context="" type="3" thread="17200" file="packagemgr.cpp:1604"><![LOG[PackageMgr::CalculateSizeFromContentLibrary failed; 0x80070003]LOG]!><time="00:21:53.888-180" date="04-21-2015" component="CreateTsMedia" context="" type="3" thread="17200" file="packagemgr.cpp:1620"><![LOG[Faile to calculate size of content for package 00000123]LOG]!><time="00:21:53.889-180" date="04-21-2015" component="CreateTsMedia" context="" type="3" thread="17200" file="packagemgr.cpp:1730"><![LOG[Failed to create media (0x80070003)]LOG]!><time="00:21:53.897-180" date="04-21-2015" component="CreateTsMedia" context="" type="3" thread="17200" file="createtsmedia.cpp:345"><![LOG[CreateTsMedia failed with error 0x80070003, details='']LOG]!><time="00:21:53.897-180" date="04-21-2015" component="CreateTsMedia" context="" type="1" thread="17200" file="createtsmedia.cpp:355"><![LOG[MediaGenerator::~MediaGenerator()]LOG]!><time="00:21:53.897-180" date="04-21-2015" component="CreateTsMedia" context="" type="1" thread="17200" file="mediagenerator.cpp:396">

I can see that the file exists in my driver source folder and it exists in the driver package folder but when i use the ContentLibrary viewer tool the file does not exist! even though the package is showing green on the DP status. The DP is on the Primary Site.

We are running SCCM 2012 R2 CU1.I've tried removing the content, re-adding it, updating content on the DP, validating content on the DP. But nothing works.

I had a similar issue with another driver package (well it was about 6 out of the 31 I have). It was failing for the exact same reason on a different file. When I pushed the content to a nearby DP and added it to the list of DPs when creating the media it worked as I can see the file in the Content Library viewer (well it got past those 6 packages until it hit this new file issue above). The same workaround doesn't work for the 00000123 package because it fails to distribute to the nearby DP - as thats for the exact same reasons according to the logs - doesn't like the igfxexps32.dll file properties.

Thanks!

I kind of have Bitlocker Encryption Working but noticing that it is not getting the settings I Want and I think this is due to WinPE OSD Encryption instead of Pre-Provisioning... Can someone explain the process or share a screenshot of there working task sequence?

This is my current Task Sequence.