Hi all i have noticed during setup windows and configuration manager it creates some random junk folder on C drive not sure why it creates. if any one experienced same issue?

I have a task sequence that fails while downloading the WIM. It starts downloading, gets to a certain percentage then starts over, it does this a couple times before failing with error 80070002.

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 16% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 39% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

Here's the really strange part, If I F8 and ping the server, it replies and the download continues. The ping is losing packets which I suspect is why the download is failing. I plug into the same port with a working laptop and I don't lose packets. I tried updating the drivers in the Boot WIM to the most current version, older versions, same result. I know it's not Network Access Account since the download starts (and finishes as long as I'm pinging). Any ideas?

Thanks!

We are currently seeing a problem with Task Sequences and the OS Deployment WinPE environment since upgrading to SCCM 2012 R2 SP1.  The issue we’re seeing is with a Powershell email script that we have created and runs at the beginning, end and error sections of our task sequences.  The idea of the script is to send an email to our team and to the user who is initiating the OS Deployment, to let us know when the task sequence begins, when it ends and then if/when it errors.  This allows us to have visibility of when a task sequences errors and also how many task sequences complete.

The error we’re seeing is that the email is successfully sent to the user who initiates the task sequence (their username is taken and stored in a variable), but the email does not get sent using the CC field to our distribution list.  The email address begins with 'exeit-patchreports@....uk' but this is truncated to just '-@.....uk'.  When we run the Powershell script manually the email address works fine.  We have also noticed that the email that is successfully sent to the user has most of the subject text missing and the email body is formatted differently to how it usually is.  It appears to be happening when SCCM runs the script.

As I said before, this problem has only come about since we upgraded to SCCM 2012 R2 SP1.  Before then it worked fine with no errors and was successful each time it ran.  We are wondering if this could be a problem caused by the SCCM upgrade but MDT has not been, due to it still being in preview?  We are currently running MDT 2013.  Has anyone else seen this problem or similar?  If so, do you have a solution?

Hello

I have a number of shortsuts I want to delete on the start menu within a TS. I am using the command line input.  Is there a way I can put in one command line rather than one command line for every shortcut I want to delete?

Best regards, Wayne

Hi,

Can anybody offer any assistance.

I am testing SCCM 2012R2 - i was on CU5 and i got OSD to work on both a Physical PC and a HyperV Guest Machine.

I upgraded to SP1 for Windows 10 support.

Since then i cannot get anything to OSD.

A machine will PXE boot - will get to "Preparing Network Connections" and then reboot.

The log file says: There are no task sequences available to this computer.

But I have 1 task sequence and it is 110% deployed to the "Test" collection that contains my 2 test machines ( 1x Phy + 1x HV)

The PXE cleint gets an IP address so its got no issues communicting to the DP during PXE boot.

I have tried creating new boot images and distributing them rather than the built in provided ones but still goes no further then "Preparing Network Connections.

Tried new task sequences - nothing changes.

I deployed test images of Windows 7 to both the physical and hyper-v guest machine Friday morning prior to the SP1 upgrade.

Anybody help me troubleshoot this further please?

Many Thanks

I am trying to UEFI boot this machine using the SMSC LAN7500 Dongle and to no luck.  We have set the IP Helpers for both DHCP & Distribution Point and removed the DHCP Scope Options (66/67) but yet I get nothing.  Legacy BIOS machines are booting but even if I put the Tablet in Legacy it still errors out.  Am I missing something?

Servers (DHCP & Distribution Point) on 1 subnet and Client on another

IP Helpers set to both DHCP & DP

DHCP Options Removed (Legacy BIOS Still Works)

Both the Dell 7350 & Surface Pro Tablets will not PXE Boot.

We are using SCCM 2012 R2 on Windows Server 2012 R2

Any help would be greatly appreciated.

IN trying to enable bitlocker on my laptop, I get the above error message. Here is the complete message:

Administrator must set the “Allow bitlocker without a compatible TPM” option in the “Require additional authentication at startup” policy for OS volumes.

What does this mean, and how do I do it?

Hi,

I have a weird problem which never occurred in test machines running on Hyper-V.

I have created a boot media from my server task sequence. When I mount the .iso in the iLo Virtual Media and boot the server the WinPE boots, custom backgroup image comes and after a while the server boots automatically.

From 5 tries it happens 3 times. 2 times everything is ok and it comes up with the task sequence wizard, I can configure IP address, enter boot media password and everything works.

I have copied the smsts.log from a failed try. Would be great to get any hints!

"

LOGGING: Finalize process ID set to 948 TSBootShell 6/18/2015 10:19:29 PM 952 (0x03B8)
==============================[ TSBootShell.exe ]============================== TSBootShell 6/18/2015 10:19:29 PM 952 (0x03B8)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 6/18/2015 10:19:29 PM 952 (0x03B8)
Debug shell is enabled TSBootShell 6/18/2015 10:19:29 PM 952 (0x03B8)
Waiting for PNP initialization... TSBootShell 6/18/2015 10:19:29 PM 956 (0x03BC)
RAM Disk Boot Path: MULTI(0)DISK(0)CDROM(0)\SOURCES\BOOT.WIM TSBootShell 6/18/2015 10:19:29 PM 956 (0x03BC)
Booted from removable media TSBootShell 6/18/2015 10:19:29 PM 956 (0x03BC)
Checking for "D:\SOURCES\BOOT.WIM" TSBootShell 6/18/2015 10:19:29 PM 956 (0x03BC)
Checking for "E:\SOURCES\BOOT.WIM" TSBootShell 6/18/2015 10:19:29 PM 956 (0x03BC)
Found E:\SOURCES\BOOT.WIM TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
Remoable media path: E:\SOURCES\BOOT.WIM TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
Found config path E:\ TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
Booting from removable media, not restoring bootloaders on hard drive TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
E:\WinPE does not exist. TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
E:\_SmsTsWinPE\WinPE does not exist. TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
Executing command line: wpeinit.exe -winpe TSBootShell 6/18/2015 10:19:32 PM 956 (0x03BC)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 6/18/2015 10:19:40 PM 952 (0x03B8)
The command completed successfully. TSBootShell 6/18/2015 10:19:40 PM 952 (0x03B8)
Successfully launched command shell. TSBootShell 6/18/2015 10:19:40 PM 952 (0x03B8)
The command completed successfully. TSBootShell 6/18/2015 10:21:07 PM 956 (0x03BC)
Starting DNS client service. TSBootShell 6/18/2015 10:21:07 PM 956 (0x03BC)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:E:\ TSBootShell 6/18/2015 10:21:07 PM 956 (0x03BC)
The command completed successfully. TSBootShell 6/18/2015 10:21:07 PM 956 (0x03BC)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:E:\ TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Current OS version is 6.2.9200.0 TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Media Root = E:\ TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Dynamicallly found media is launched in WinPE from CD/DVD' TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Executing from Media in WinPE TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 6/18/2015 10:21:08 PM 1296 (0x0510)
TsPxe.dll loaded TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
Failed to open PXE registry key. Not a PXE boot. TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
FALSE, HRESULT=80004001 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2695) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
Unknown case. PXE not present and bootstrap ini not present. TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004001 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1042) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004001 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
Exiting with return code 0x80004001 TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553) TSPxe 6/18/2015 10:21:08 PM 1296 (0x0510)
Execution complete. TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553) TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,809) TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
End program:  TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
Finalizing logging from process 948 TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
Finalizing logs to root of first available drive TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)
LOGGING: Setting log directory to "X:\SMSTSLog". TSBootShell 6/18/2015 10:21:08 PM 956 (0x03BC)

"

I have created a DaRT recovery image and generated the boot.wim file. However, I am unable to import it into our config manager environment, which was just upgraded to 2012 R2 SP1. For reference, I am following the instructions here: Making PC Recovery Easier with the Microsoft Diagnostics and Recovery Toolset (DaRT). The DaRT version being used is the most recent version, 8 SP1.

The logs read as follows:

ERROR> failed to mount wim file err=3 SMS Provider 6/29/2015 3:38:09 PM 8844 (0x228C)

*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(4019) : Failed to insert OSD binaries into the WIM file~*~*SMS Provider 6/29/2015 3:38:09 PM 8844 (0x228C)

*~*~Failed to insert OSD binaries into the WIM file ~*~* SMS Provider 6/29/2015 3:38:09 PM 8844 (0x228C)

The TechEd talk did not specify anything special to do other than generate the disk and import it, so I am at a loss as to what I might be doing wrong.

I have set WinPE 5.0 wim to Eastern Standard time and tzutil show it correctly. I also have WinPE sync with my NTP server to a EST. But after use Net Time\\my_NTP_Server /Set /y which it will show correct time. But once I enter "time" in the command prompt it will show an hour earlier than the correct time. Not sure what causing this. please help.

Thanks,

Greetings,

I have a SCCM 2012R2 Task Sequence for my Windows Servers (OS: 2012R2) that has been working on one model of server (IBM x3650 M4) but now with the new model (Lenovo x3650 M5) it is not working anymore. The step it fails on is right after the image gets applied, and Windows Setup kicks off, after the automatic reboot that Windows Setup initiates it fails upon the setup of windows. The error message is: "Windows Setup could not configure Windows on this computer's hardware" and is explained in thislink.

One thought I had was that this could be Storage driver related. All that I've added to the boot image are NIC drivers, I have not added any storage related drivers. I'm not sure if they are needed however. My Task Sequence correctly kicks off with WinPE, formats and partitions the hard drive, and copies down my custom .wim successfully. I can run diskpart and see my disk. So is a storage driver actually needed?

Unfortunately when the error is encountered it is not during the Task Sequence so I can't get any logs. I also can't get to a command prompt with shift+f10 to see what exactly might be causing the error.

Any insight as to when storage drivers are actually needed in the boot image?

Hi Guys,

I am deploying "Win 2008 SP2 ENT x86" on VM using vSphare Client. After certain steps IP configuration is getting removed and task sequence fails due to unavailability of the network.

Please find the steps which I am performing and getting error.

1. Configured Network Setting manually. Fetching task sequence successfully and IP configuration is set

2. Next, it shows 'Ready to Start' task. Clicked on Finish to start the task sequence, after this step IP configuration is getting removed automatically as shown below.

Note: It is x86 Operating System. x86 boot image is used in the task sequence. 

Can you guys please provide the solution on this issue.

Many Thanks in Advance !

I have been using SCCM 2012 R2 to build several different models of Dell laptops and desktops. After adding the new drivers to the corporate WinPE boot image to support the Dell E7450 laptop, the network card stopped connecting to the domain on the Dell Optiplex 9020 desktop. The device driver loaded, but I got a local IP address and could not connect to any network. The Corporate WinPE had been updated several times. It included drivers for many versions of lenovo and dell products, and not all of the drivers were WinPE drivers.

I created a new boot image from the WinPE boot image included with SCCM 2012 R2 and added just the WinPE drivers for the Optiplex 9020. This resolved the IP issue, I am able to join the machine to the domain, but now the OSD image deployment does not complete. I am seeing a variety of error messages in the smsts log files. Sometimes the log files say a file cannot be found. Other times the log contains several entries saying a file is being downloaded, or a file is being deleted, and it seems to time out while this is happening. When this happens, there usually are no errors in the log, it seems to just 'fill up' and the machine just stops running the image deploy. When the build does not stall, the build fails on the last step, and the last thing the machine does is install Checkpoint Security's Pointsec 7.5.

On the same day that the Win7 driver package was updated to support the 7450, the Dell E6430 machine stopped building completely. The new driver for the 7450 is causing the 6430 to blue screen the first time the image deploy process boots the laptop from the laptops local disk drive. The 6430 is using it's own driver package, none of the files changed in the 6430 package when the 7450 package was created. The image deploy process makes it to the point where it has copied all the files to the local hard drive and the laptop has is booting from the local C: drive. It blue screens while installing device drivers. I have tried last known good and safe mode and they both blue screen. I used the same stripped down WinPE boot image created for the 9020 on the 6430 and did not resolve the issue. I created a new 6430 driver package, and it did not resolve the issue either.

Is there a known issue with any 7450 driver affecting the 6430 & 9020 dell machines? Any mention of a missing driver causing a dell product to stop installing pointsec?

One last note, we recently captured a new image. It was working for a few weeks. After adding the 7450 drivers and having image deploy fail on the 9020 desktop & 6430 laptop, I tried the old image & the build completes on both pieces of hardware. I do have to change the old build process to use the stripped down WinPE boot image, but after that, the old captured image of win 7 deploys fine. The old image is a dual partition image and the new image is a single partition image. The old image was patched to February of 2015, the new image is patched to June of 2015. All of the software and driver packages have been checked, and they are all installing files to the C Drive. The whole process was working on a single drive image until I updated WinPE & Win 7 device drivers to support the E7450.

Could this be a combination of a microsoft update deployed in the last few months and a dell driver conflict?

I will be able to provide log files if you would like to have more detail.

Hi All

I am having an issue in my TS with the following model

HP ProDesk 600 G1 TWR

I have to deploy win7 x64 Pro using OSD

I am using SCCM 2012 R2 and ADK 8.1

The OS install but the drivers for the NIC does not install and obviously it does not get joined to the domain, also the password that I specify for administrator also does not get applied

I am now struggling for about 2 weeks and cannot find a resolution

previously I had a boot image with most of the drivers injected into it but I have reverted to a "clean" boot image as I read that it can also cause issue

in other words I have a "clean" boot image as well as a "clean" windows 7 capture image -

I have now created a separate TS with a new "Clean" Boot image - which contains no drivers for this model

I then created a driver package - I have in fact tried several different methods to create the driver package - from using the original driver that came with the DVD to downloading the drivers from the following URL to capturing drivers from an installed HP ProDesk 600 G1 TWR - none worked

if I build a system from a WIN 7 DVD I can install the supplied drivers or even the drivers that I have downloaded

http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html

here is the WMI query that I am using to detect the model

SELECT * FROM Win32_ComputerSystem WHERE Model = "HP ProDesk 600 G1 TWR"

In my task sequence I am also catering for KMDF driver and I followed this post - I tried to do it through offline servicing but it failed for some reason as well

https://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/#comment-134

here is a link on one drive to the smsts.log file

http://1drv.ms/1GLSOuk

from the log file it does not seem to create the "scratch" folder for some reason and then the KMDF driver does not install either and this I believe is what is causing the failure for the drivers not to install

if I test the TS on "older" models it works without a problem (on these models I however I do not use KMDF)

I need some clarity I on this

Is anyone please able to tell me if i need to manually need to add a sysprep step into my task sequence which deployed to a VHD before i import it to SCVMM?

I want to use SCCM to manage a base image/vhd which will just be the OS and the latest updates and import this into SCVMM to use as the base VHD for deploying with. Everywhere i read describes the process of importing into SCVMM, but i know when vhds are imported into SCVMM manually they obviously need to be sysprepped. 

Many thanks for any pointers

Hi,

I have recently taken over within a new position and I am tasked to deploy a windows 8.1 OS image to 10 Dell Venue Pro 7130's.

I am having an issue where I am able to successfully PXE boot and download the boot.wim package, but as soon as I see the Windows PE screen the device restarts.

I have ensured that the device is successfully obtaining an IP address by pressing F8 and running an IPconfig, therefore do not believe it is a NIC driver issue.

No error is displayed on the screen and when I boot into the existing OS installed on there, nothing shows so far in the SMSTS.log file (although I wouldn't expect this as I am not even getting to the stage where I am able to select an image to install)

Can someone please recommend the next steps I can take, or indeed point me to the log files I can review?

Regards

Leon

Hi everyone,

I seem to have something strange going on with my Boot Image(x64). It seems to work as I'm able to boot WinPE off of it.

The issues:

1. If I go to SCCM and go to the boot image properties and then click on Images tab and press on the Reload button, I get: Image is not available. Verify that the source is available and Configuration Manager has the appropriate permissions to access the source.
2. If I go to Drivers tab and remove/add drivers, and then update the DP, the following comes up:

Error: The wizard detected the following problems when updating the boot image.
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"GLH00112\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
};

So, at this point I'm assuming that my WIM file is corrupted and needs to be replaced.

Now, the issues comes when I try to create a new Boot Image. I browse to C:\Program Files\Windows AIK\Tools\PETools\amd64 and copy the winpe.wim file to my shared folder where I put all my boot files for SCCM.

When I go to SCCM to create a new boot image, I browse to the URL where I placed my new winpe.wim file (the original file) and none of the boot images from the wim file get loaded (see screenshot). This is happening to almost any winpe.wim file I try to load.

I'm running SCCM 2012 SP1.

Any ideas as to what might be happening?

Hi

We have some issues trying to use the Auto Apply Drivers step. We have 1 CAS and 3 primaries. This situation only happen on one primary

smsts.log :

MP_DriverManger.log on verbose mode:

I notify that the client fail before the process on the server complete.

All the process on the task sequence work fine except Auto Apply Driver steps.

Using Driver Package work fine but we are interested to use Auto Apply Driver that work fine on other sites.

Any clue about this?

I am trying to deploy Windows 7 and all the needed applications using a SCCM 2012 R2 task sequence. The process works flawlessly until I get to installing Microsoft CRM 2011. I have read several posting on how to make this happen but I always get an error 0x80004005 and the task fails when it is trying to install CRM 2011. The CRM 2011 install is the 7th application installed in the task sequence, The application is a script type of deployment, where the full UNC (\\server\share\folder\Sub-folder\Sub-folder) to the location of the install files on the SCCM server is in the content tab, The installation program is "SetupClient.exe" /q INSTALLLEVEL=2, The user experence is set to install for system, whether or not a user is logged in, Installation program visibilty = normal.

If I open a command prompt on the PC that I just ran the task sequence to install the OS and other applications as administrator and enter \\server\share\folder\Sub-folder\Sub-folder\SetupClient.exe /q INSTALLLEVEL=2 the application and all dependent applications will install.

Does anyone have a idea where to look for the reasons or why this application will not install from my task sequence?

Alan Schroeder