Ok I am having an issue in regards to OSDs and yes I am a newbie in regards to this. I was able to get these to successfully work during the Evaluation period prior to SP1, I have since bought a License for SCCM 2012 SP1 and nothing seems to work anymore.

First Issue: I am trying to deploy Windows 7 Pro x86 to Clients but it keeps installing on D: instead of C:

I have tried multiple steps in regards to the  Deploy TS

a) Apply Operations Systems>Specified Logical Drive Letter, failed to install on C:

b) Added TS Variable "Assign C:\ to Boot Drive" OSDPreserveDriveLetter = False, failed

c) Tried the above with True, failed

d) Removed

e) removed the Partition Disk 0 - BIOS and the UEFI, created Set Task Sequence Variable "Set OSDisk Variable" OSDisk=C,

Created Format and Partition Disk 0 Standard MBR, Volume: Windows (Primary) 100%, Make this boot partition, File System: NTFS w/ quick format, Variable=OSDisk.

This installs to C: but when trying to login I always get the error "The User Profile Service failed to load".

WHY IS THIS SO COMPLICATING JUST TO RUN AN OSD??? Things worked prior to SP1 and I love how the documentation/steps for OSDs are non-existent for SP1 or perhaps it is just me...most likely me but meh.

Hello,

I have two questions about SCCM 2012 R2 SP1,

1- What is different between SCCM 2012 R2 SP1 vs SCCM Current Branch 1511?

2- Is SCCM 2012 R2 SP1 able to deploy Windows 10 Anniversary update as OSD or part of windows update?

thanks

Hi,

 I have a laptop Model "10DKK..."

I have 2 Departments: Accounting, and IT

I have 2 Operating Systems: Win 10 and Win 7

Account wants Win10 in this device and IT wants Win7 on this same device. What is the best plan for this regarding Task Sequence for SCCM 2012 R2?

Thank you

HI

I want to run script in the start of Task sequence to backup all profile.

after I get it and tried to run the TS i get the following error:

win32_UserProfile invalid class and this happened in the line:

$LocalProfiles = Get-WMIObject Win32_UserProfile -filter "Special != 'true'"     of script

when i tried to run Get-WMIObject - class Win32_UserProfile , i found the same error invalid class

info: my boot image is support Powershell  and i can list all WMIObject

any help

Mahmoud

Hi.

I would lige the Fuzzy Lookup Add-In for Excel to be installed silently, but it seems only to be possible for a Per-User installation with the parameter "setup.exe /passive"

I need the installation to be for All Users, but I can´t find any parameter that makes that possible.

/ Torsten  

I've been through the whole gamut of tablets and each one presented it's own problems with PXE booting and WinPE.

I'm now stuck on the new Dell Latitude 7350 with the Dell FM76N (which is a Realtek based USB3 --> Ethernet adapter).

Drivers have been added but it doesn't appear to work as expected.

Booting to WinPE and it doesn't pick up an IP address. I first assumed it was just a driver issue, but if I open a command window before it reboots I can unplug / replug the device and it immediately picks up an address!

So it's clearly not a driver issue related to the device, but maybe with the USB host?

Anybody encountered this before?

Hi All,

From what I understand the architecture for the boot image during PXE boot must match the architecture of the boot imaged used in the task sequence and therefore match the architecture of the deployed operating system. Correct me if I'm wrong here.

We have a mix of clients running x64 and x86 Windows 7. During PXE boot I'm having trouble with determining which architecture kicks off depending on whether or not I need to image an x64 based client or x86. This is easy enough to control in the task sequence, I can also look at the properties of the boot image, select Data Source and uncheck the option to "Deploy this boot image from the PXE-enabled distribution point" option if I don't want to use a particular boot image. I've found even doing this causes problems. If I disable the x86 boot image then try to PXE boot a device that needs the x64 boot image (the x64 boot image is PXE-enabled) then the device doesn't pick up the boot image and times out Contacting Server..........

What's the go there? There must be a more simple solution. I have also tried updating the distribution point when I wanted to use the x64 Boot image in order to put it at the front of the queue, this didn't work either. 

Thanks for any feedback!

P

Hello guys,

i create a standard TS for a Windows 10 OSD, exisiting image package and the install.wim from Windows 10 LTSB.

So far so good, the installation runs smooth, but the SCCM client at the end of the OSD will not be installed.

The log says the files are copyd to C:\_SMSTaskSequence, but no installation starts (see smsts.log) below.

Versions:

Windows Server 2012 R2 Std.

SCCM 2012 R2 SP1 (Console Version 5.0.8239.1403, Site Version 5.00.8239.1000) 

smsts.log

Any ideas?

Thanks

My goal is to change BIOS settings from BIOS Legacy to UEFI (or UEFI CSM) during OSD on a HP laptop. So to do that I have created some steps in Windows PE Phase.
- Reboot in WinPE, Clean disk (diskpart), then Partition Disk (MBR) if not already UEFI-Mode

So far ok.

I use HP BIOSConfigurationUtility to change some BIOS settings to fit my standard and change to UEFI-Mode. It works great. But I can't reboot in Windows PE automatically because Partition is MBR and not GPT. So I decided to change that before restart in Windows PE.

- Clean disk (diskpart) a second time, Partition Disk (GPT) and Restart in Windows PE step.

Unfortunately it doesn't work because Windows PE isn't in EFI-Mode now. So I tried to correct that with bcdboot before "Restart in Windows PE" step:

- "bcdboot X:\Windows /S: C: /F EFI" and "bootsect /nt60 C: /force" and then "Restart in Windows PE" step.

"Restart in Windows PE" step still fails but after the system reboots, it starts Windows PE in EFI-Mode and I can select my OSD and everything is ok.

Is it possible to automate the whole process? My Scenario works well but it fails the first time if BIOS not already in UEFI.

I hope my post is clear enough... :-)

Hi,

I am doing OSD from SCCM 2012 server. It asks for pressing F12. However after pressing F12 ,it goes to SCCM screen and do not ask for any PXE password and get rebooted.

I have enabled password for PXE as well.

In log also it throws error in one of the machine like

Failed to download pxe variable file. Code(0x00000001)

PxeGetPxeData failed with 0x80004005

Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

Hi folks,

I'm having an issue running W8.1 sequence on Surface Pro 3, this is working properly on BIOS based devices.

Couple of Format & Partition Disk (UEFI) steps after which I've another step for Pre-provision Bitlocker using %OSDISK% variable however on UEFI devices, it fails to detect OSDisk variable and returns the following error as per SMSTS.log--

==============================[ OSDOfflineBitlocker.exe ]==============================OSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Command line: "OSDOfflineBitlocker.exe" /enable /drive:%OSDisk% /ignoretpm:TrueOSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Initialized COMOSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Command line for extension .exe is "%1" %*OSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Set command line: "OSDOfflineBitlocker.exe" /enable /drive:%OSDisk% /ignoretpm:TrueOSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
IsValidDriveLetter(argInfo.sDrive.c_str()), HRESULT=80070057 (e:\qfe\nts\sms\client\osdeployment\offlinebitlocker\main.cpp,363)OSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Invalid drive letter %OSDisk%OSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
ProcessCommandLine(argInfo), HRESULT=80070057 (e:\qfe\nts\sms\client\osdeployment\offlinebitlocker\main.cpp,418)OSDOfflineBitLocker11-08-2016 13:02:191292 (0x050C)
Process completed with exit code 2147942487 TSManager11-08-2016 13:02:191872 (0x0750)
!--------------------------------------------------------------------------------------------!TSManager11-08-2016 13:02:191872 (0x0750)
Failed to run the action: Pre-provision BitLocker. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)TSManager11-08-2016 13:02:191872 (0x0750)

Prior to this, there was this Format & Partition Disk(UEFI) step which was completed successfully, here's a snip--

==============================[ OSDDiskPart.exe ]==============================OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Command line: "osddiskpart.exe"OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Reading partition size info for partition 0 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size before partition: 256052966400 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
size units: SIZE_MBOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Set partition size: 524288000OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size after partition 0: 255528678400 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Reading partition size info for partition 1 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size before partition: 255528678400 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
size units: SIZE_MBOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Set partition size: 536870912OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size after partition 1: 254991807488 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Reading partition size info for partition 2 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size before partition: 254991807488 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
size units: SIZE_MBOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Set partition size: 134217728OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size after partition 2: 254857589760 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Failed to read filesystem from OSDPartitions2FileSystem, not formattingOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Reading partition size info for partition 3 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size before partition: 254857589760 OSDDiskPart11-08-2016 13:02:091560 (0x0618)
size units: SIZE_PERCENTOSDDiskPart11-08-2016 13:02:091560 (0x0618)
100% size specified.OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Remaining size after partition 3: 0OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Checking volume 'C:' for BitLockerOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Volume 'C:' is on disk '0l'OSDDiskPart11-08-2016 13:02:091560 (0x0618)
Volume 'C:' is fully decryptedOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Checking volume 'D:' for BitLockerOSDDiskPart11-08-2016 13:02:091560 (0x0618)
Checking volume 'X:' for BitLockerOSDDiskPart11-08-2016 13:02:091560 (0x0618)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition primary size=500
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
OSDDiskPart 11-08-2016 13:02:091560 (0x0618)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition primary size=500
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
create partition MSR size=128
OSDDiskPart 11-08-2016 13:02:091560 (0x0618)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition primary size=500
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
create partition MSR size=128
create partition PRIMARY
assign
OSDDiskPart 11-08-2016 13:02:091560 (0x0618)
Diskpart: list volume 
select disk 0
clean
convert gpt
create partition primary size=500
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
create partition MSR size=128
create partition PRIMARY
assign
rescan
 list volume
OSDDiskPart 11-08-2016 13:02:101560 (0x0618)
Executing diskpart script: list volume 
select disk 0
clean
convert gpt
create partition primary size=500
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
create partition MSR size=128
create partition PRIMARY
assign
rescan
 list volume
OSDDiskPart 11-08-2016 13:02:101560 (0x0618)
Command line for extension .exe is "%1" %*OSDDiskPart11-08-2016 13:02:101560 (0x0618)
Set command line: "X:\windows\system32\diskpart.exe" /s "X:\windows\TEMP\DiskPartScript.txt"OSDDiskPart11-08-2016 13:02:101560 (0x0618)
Executing command line: "X:\windows\system32\diskpart.exe" /s "X:\windows\TEMP\DiskPartScript.txt"OSDDiskPart11-08-2016 13:02:101560 (0x0618)
Process completed with exit code 0OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Formatting partitionsOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Partition: 1 RECOVERYOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Partition: 2 MSROSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found MSR partition: 2OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Partition: 3 PRIMARYOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Adding logical drive: C:OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Skipping non-local logical drive: D:OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Skipping non-local logical drive: X:OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Formatting drive C: with NTFS filesystem, method quickOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Creating instance of service loaderOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Loading serviceOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Waiting for service to initializeOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for software providersOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a VDS software providerOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsSwProviderOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for packsOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a VDS packOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsPackOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for volumesOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a VDS software providerOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsSwProviderOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for packsOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a VDS packOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsPackOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for volumesOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a VDS volumeOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsVolumeMFOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for access pathsOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Found a volume with access path 'C:\'OSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsVolumeOSDDiskPart11-08-2016 13:02:141560 (0x0618)
Querying for IVdsVolumeMFOSDDiskPart11-08-2016 13:02:141560 (0x0618)
OSDDiskPart.exe completed successfullyOSDDiskPart11-08-2016 13:02:171560 (0x0618)
Process completed with exit code 0TSManager11-08-2016 13:02:171872 (0x0750)
!--------------------------------------------------------------------------------------------!TSManager11-08-2016 13:02:171872 (0x0750)
Successfully completed the action (Format and Partition Disk (UEFI)) with the exit win32 code 0TSManager11-08-2016 13:02:171872 (0x0750)

Also, when i review diskpart output for Disk 0, it looks alright with OSDisk variable mapped--

 X:\Windows\temp\SMSTSLog>diskpart

Microsoft DiskPart version 10.0.10586

Copyright (C) 1999-2013 Microsoft Corporation.
On computer: MININT-D0VBE3G

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB      0 B        *
  Disk 1    Online         7381 MB      0 B

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
Volume 0     C   OSDisk       NTFS   Partition    237 GB  Healthy
  Volume 1         Windows RE   NTFS   Partition    500 MB  Healthy    Hidden
  Volume 2     D   KINGSTON     FAT32  Removable   7380 MB  Healthy

DISKPART> sel vol 1

Volume 1 is the selected volume.

DISKPART> list par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
* Partition 1    Recovery           500 MB  1024 KB
  Partition 2    Reserved           128 MB   501 MB
  Partition 3    Primary            237 GB   629 MB

DISKPART>

Appreciate if someone could share ideas around this.

thanks in advance..

I'm using SCCM 2012 sp2 to deploy Windows 10 via a pre-canned windows 10 upgrade task sequence referred to here:

https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-to-windows-10-with-system-center-configuraton-manager

It has worked on many machines but I have a couple that consistently get this message in the SMSTS.log

Process completed with exit code 2147942405 

TSManager 8/12/2016 3:55:27 PM 7184 (0x1C10)
!--------------------------------------------------------------------------------------------! 

TSManager 8/12/2016 3:55:27 PM 7184 (0x1C10)
Failed to run the action: Upgrade Windows. Permissions on the requested may be configured incorrectly.
Access is denied. (Error: 80070005; Source: Windows) TSManager 8/12/2016 3:55:27 PM 7184 (0x1C10)

I have tried several items from previous articles such as turning off antivirus and using a network service account on installation, but neither worked.

Any help is appreciated.

I am trying to image a computer with Windows10 using stand alone media.

I build Standalone USB media using Create a Task sequence media wizard> Stand-alone media.

I am able to boot from usb and start image. Image applies successfully and during Install Configuration Manager step> Computer reboots into Task Sequence wizard again and doesn't proceed.

BIOS is set as following sequence

USB

HDD

Network

Error in smsts.log: Failed to open PXE registry key. Not a PXE boot. Failed to find the source drive where WinPE was booted from

smsts.log file:

LOGGING: Finalize process ID set to 936 TSBootShell 8/12/2016 10:28:18 AM 940 (0x03AC)
==============================[ TSBootShell.exe ]============================== TSBootShell 8/12/2016 10:28:18 AM 940 (0x03AC)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 8/12/2016 10:28:18 AM 940 (0x03AC)
Debug shell is enabled TSBootShell 8/12/2016 10:28:18 AM 940 (0x03AC)
Waiting for PNP initialization... TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
WinPE boot path: E:\SOURCES\BOOT.WIM TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
Booted from removable device TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
Found config path E:\ TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
Booting from removable media, not restoring bootloaders on hard drive TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
E:\WinPE does not exist. TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
E:\_SmsTsWinPE\WinPE does not exist. TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
Executing command line: wpeinit.exe -winpe TSBootShell 8/12/2016 10:28:18 AM 964 (0x03C4)
The command completed successfully. TSBootShell 8/12/2016 10:28:30 AM 964 (0x03C4)
Starting DNS client service. TSBootShell 8/12/2016 10:28:30 AM 964 (0x03C4)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:E:\ TSBootShell 8/12/2016 10:28:30 AM 964 (0x03C4)
The command completed successfully. TSBootShell 8/12/2016 10:28:30 AM 964 (0x03C4)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 8/12/2016 10:28:30 AM 1272 (0x04F8)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:E:\ TSMBootstrap 8/12/2016 10:28:30 AM 1272 (0x04F8)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 8/12/2016 10:28:30 AM 1272 (0x04F8)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 8/12/2016 10:28:30 AM 1272 (0x04F8)
Current OS version is 10.0.10240.0 TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Media Root = E:\ TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
WinPE boot type: 'Ramdisk:SourceIdentified' TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Failed to find the source drive where WinPE was booted from TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Executing from Media in WinPE TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Verifying Media Layout. TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
MediaType = FullMedia TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
PasswordRequired = false TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Running Wizard in Interactive mode TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Loading Media Variables from "E:\sms\data\variables.dat" TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
no password for vars file TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Activating Welcome Page. TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
Loading bitmap TSMBootstrap 8/12/2016 10:28:31 AM 1272 (0x04F8)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,561) TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)
The command completed successfully. TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)
Successfully launched command shell. TSBootShell 8/12/2016 10:29:23 AM 940 (0x03AC)

Requesting Assistance

RJ

RJ09

I am using SCCM 2012 R2 to deploy an image Windows 7 Ent SP1 x64 to this system. I use this same image for all other HP devises with no issues. I downloaded and expanded the driver package SP73082 and installed those drivers on SCCM like I have for all other devices. Upon the completion of installing the OS and drivers and at the first reboot the system will BSOD and restart, at which point I attempt to stop the page from changing with no luck, so am unable to capture the error code that is being generated. I validated that the drivers were the correct ones, the number of files and folders are the same. I even changed the amount of RAM to see if that was the issue to no avail.

Troubleshooting steps:

I have validated that the drivers are the correct ones for this model and OS.
I have verified that the drivers are setup correctly within SCCM 2012 and are being pushed out to the system during the installation process.
There is nothing that shows this system is failing to load any of the drivers or that it is having an issue with the OS.
The system once the initial reboot happens continues to BSOD. Even attempting to load in safe mode does not resolve. Loads up to disk.sys and fails.

I used this image today to image a HP Elitebook Folio 1040 G2 with no issues so I know the image is working.

I also verified that the drivers when uncompressed match what was imported into SCCM to deploy to this system.

Any assistance with understanding what could be causing this would be great. 

Mark Reny

Hello. I have Win 10 OSD working perfectly on computers using Legacy BIOS mode. Recently I have had to migrate all devices to UEFI BIOS mode.

OSD using UEFI mode works perfectly (exactly like in Legacy BIOS mode) when the computer being imaged has a blank disk (i.e. I run Diskpart > Select Disk 0 > Clean).

However if I want to reimage the same computer it will fail to PXE boot with Error "PXE-E18: PXE server response timeout".

If I wipe the disk, then UEFI PXE works just as it did before, and OSD works as expected.

I do not understand why it is doing this in this specific scenario.

My environment:

1. SCCM 2012 R2 SP1 standalone site on 10.10.100.112. DP with PXE is installed on this server

2. DHCP installed on DC with IP 10.10.100.10. DHCP Scope does not have Options 60, 66 or 67 which is correct since SCCM DP and DHCP server are on the same subnet.

3. OS Deployment is using ask Task Sequence based on MDT 2013 Update 1, with WDK 10. The OS Image being deployed is a Windows 10 Build 1511 Enterprise x64. The boot images are working fine and distributed to the DP's etc.

4. The computer being imaged is an HP Probook 650 G1 (very recent model) and has full UEFI BIOS enabled with all CSM modules disabled

5. The OSD Task Sequence enables Bitlocker. However I have tried this with no Bitlocker enabled with the same result.

I am stumped! Can anyone suggest something I am missing? Thanks in advance!

Hi all,

We have started to encounter problems with OSD in our production environment during the bitlocker process. The problem is not consistently appearing though it is happening more and more frequently.

We are on SCCM 2012 R2 SP1 hosted on Windows 2008 R2 server with SQL Server 2008 R2 hosted on another Windows 2008 R2 Server. We are only building Windows 7 machines where the above error appears. This problem never existed before.

The OSD is failing with the below error:

*******************************************************************

"The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147950640: There is no such object on the server."

"The task sequence execution engine failed executing the action (Enable BitLocker) in the group (BitLocker) with the error code 2147950640
Action output: ... 39
Creating TPM owner authorization value
Succeeded loading resource DLL 'C:\windows\CCM\1033\TSRES.DLL'
Taking ownership of TPM
uStatus == 0, HRESULT=80072030 (e:\nts_sccm_release\sms\framework\tscore\tpm.cpp,645)
pTpm->TakeOwnership( sOwnerAuth ), HRESULT=80072030 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,499)
InitializeTpm(), HRESULT=80072030 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1284)
ConfigureKeyProtection( keyMode, pwdMode, pszStartupKeyVolume ), HRESULT=80072030 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\bitlocker.cpp,1489)
pBitLocker->Enable( argInfo.keyMode, argInfo.passwordMode, argInfo.sStartupKeyVolume, argInfo.bWait ), HRESULT=80072030 (e:\nts_sccm_release\sms\client\osdeployment\bitlocker\main.cpp,382)
'TakeOwnership' failed (2147950640)
Failed to take ownership of TPM. Ensure that Active Directory permissions are properly configured
here is no such object on the server. (Error: 80072030; Source: Windows). The operating system reported error 2147950640: There is no such object on the server.

*******************************************************************

please note, once we log into the failed OSD machine after the failed build, and try to start the bitlocker/setup TPM manually we get the same above error "There is no such object on the server.".  The machine has joined the domain correctly by the looks of it and any domain user can log in.

Please also note, I have come across another thread about similar issue elsewhere but that was pertaining to Windows 8 machines where the solution is to upgrade the AD schema. But we are still on Windows 7 OSD and machines have built successfully until recently. It's only a relatively recent phenomenon and that to the problem is not entirely consistent. Some builds do complete the bitlocker process, though nowadays most are failing.

Any help will be much appreciated.

Steve

I'm running a test deployments of the Windows 10 Anniversary Update 1607 image and having problem with the svchost.exe CPU  consumption (100%) for two hours after the deployment. All the latest patches is installed on the image.

I have tried to stop and disabling the Windows Update service but the problem seems to be something else. I have deployed two different computer models with the same problem.

When I look at the Threads in the process with Process Explorer I see that it's DsmSvc (Device Setup Manager) that are consuming CPU.

Any ideas? 

I have tryed to deployed Windows 10 build 1607 With SCCM 2012 build 1511, createt a New MDT task Sequences in SCCM. Deployment go without any error. But after i loged in the client, OS disk are D:\ not C:\. If i change the OSDPreserveDriveLetter to True the OS disk set to X:\. I have tryed a older win 10 (build 1511) wim file with the same Task Sequences its no problem. Then OS drive are C:\. I hope somebody can help me here. Do I have to upgrade the SCCM server to the newest build?

Hi all,

During the installation of SCCM2012R2, when Deployment Share mode has to be changed in Deployment Workbench, I get the error: "Dism Host Servicing Process has stopped working".

I checked the local policies but again I have the same problem. 

Any hint?

Genc VOJKA