Hi all,

Can we Capture an image from a Windows 10 reference machine using capture media created from SCCM 2012 R2 SP1? If yes what are the requirements on the reference machine as well as on the SCCM?

Note: I installed Windows ADK for Windows 10 on SCCM server and added a x64 boot image from the installation path of the ADK to the SCCM and used it to create the capture media.

SCCM 2012 R2 was running, I uninstalled WAIK 8.1 and installed WAIK 10, I then upgraded SCCM 2012 to SP2. Now we're trying to deploy an OS and it's complaining that it can not find the bootwim file. This file has been deployed to the MP\DP and local DP. I've tried using both DP's from a boot stick. No errors are showing in the system status, everything is green. Below is the smsts.log file. SAV00005 is the bootx64.wim

Content location request: TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Package : SAV00005.51 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Client  : GUID:6f9f4255-279e-4e45-8515-ec4a83838ed7 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Local   : 1 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Remote  : 0 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Internet: 0 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Sending RequestContentLocations for SAV00005 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Setting message signatures. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Setting the authenticator. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
CLibSMSMessageWinHttpTransport::Send: URL: ServMP.DOMAIN1.com:80  CCM_POST /ccm_system/request TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Request was successful. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
::DecompressBuffer(65536) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Decompression (zlib) succeeded: original size 632, uncompressed size 3014. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Location Reply: <ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="1073742992"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="SAV" MasterSiteCode="SAV" SiteLocality="FALLBACK" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><SMBPath Name="<URL">\\ServDP.DOMAIN1.com\SMSPKGD$\SAV00005\"/><URL Name="http://ServDP.DOMAIN1.com/SMS_DP_SMSPKG$/SAV00005" Signature="<ADSite">http://ServDP.DOMAIN1.com/SMS_DP_SMSSIG$/SAV00005"/><ADSite Name="Arlington"/><IPSubnets><IPSubnet Address="192.168.80.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>8239</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>ServDP.DOMAIN1.com</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="0"/><Locality>FALLBACK</Locality></LocationRecord><LocationRecord><SMBPath Name="<URL">\\ServMP.DOMAIN1.com\SMSPKGD$\SAV00005\"/><URL Name="http://ServMP.DOMAIN1.com/SMS_DP_SMSPKG$/SAV00005" Signature="<ADSite">http://ServMP.DOMAIN1.com/SMS_DP_SMSSIG$/SAV00005"/><ADSite Name="Savvis"/><IPSubnets><IPSubnet Address="192.168.60.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>8239</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>ServMP.DOMAIN1.com</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="0"/><Locality>FALLBACK</Locality></LocationRecord></LocationRecords></Site></Sites><RelatedContentIDs/></ContentLocationReply> TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
MCS server:  TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Found location: http://ServDP.DOMAIN1.com/SMS_DP_SMSPKG$/SAV00005 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Local=0 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
MCS server:  TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Found location: http://ServMP.DOMAIN1.com/SMS_DP_SMSPKG$/SAV00005 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Local=0 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Processing 2 locations. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Not processing remote location: TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Flags: 40000490 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  URLs : 1 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  SMB  : \\ServDP.DOMAIN1.com\SMSPKGD$\SAV00005\ TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  MCS  :  TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Not processing remote location: TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  Flags: 40000490 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  URLs : 1 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  SMB  : \\ServMP.DOMAIN1.com\SMSPKGD$\SAV00005\ TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
  MCS  :  TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
No static content server. TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
(LocationsList.size() + slistHttpPaths.size() + slistSMBPaths.size()) > 0, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,2427) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
FALSE, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2000) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Content location request for SAV00005:51 failed. (Code 0x80040102) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
hr, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2786) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Failed to resolve PackageID=SAV00005 TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,3634) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1482) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
Failed to resolve selected task sequence dependencies. Code(0x80040102) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
hrReturn, HRESULT=80040102 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102) TSMBootstrap 1/12/2016 3:45:12 PM 1424 (0x0590)
ThreadToResolveAndExecuteTaskSequence returned code 0x80040102 TSMBootstrap 1/12/2016 3:45:12 PM 1280 (0x0500)
Setting wizard error: This task sequence cannot be run because the program files for SAV00005 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator. TSMBootstrap 1/12/2016 3:45:12 PM 1280 (0x0500)
ResolveProgressPage::OnWizardNext() TSMBootstrap 1/12/2016 3:45:12 PM 1280 (0x0500)
Activating Finish Page. TSMBootstrap 1/12/2016 3:45:12 PM 1280 (0x0500)
Loading bitmap TSMBootstrap 1/12/2016 3:45:12 PM 1280 (0x0500)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 1/12/2016 3:45:30 PM 996 (0x03E4)
The command completed successfully. TSBootShell 1/12/2016 3:45:30 PM 996 (0x03E4)
Successfully launched command shell. TSBootShell 1/12/2016 3:45:30 PM 996 (0x03E4)

Hi,

 The computer obtains an IP when logs into windows. However, when reboot and start reimage from boot image with sccm 2012, it only detect private ip: 169.x.x.x. What could be the issue? log files shows the private IP.

Thanks

Tuan

We have had an ongoing issue with Office 2013 (this is the only application I have noted this is an issue with) not installing during OSD. What is odd is the SMSTS Log shows that it did in fact install:

Successfully completed the action (Install Office) with the exit win32 code 0

However, on the newly imaged machines there is no record of it in the ccmcache or program files folders. This issue never occurs when deployed to a machine after imaging, just during OSD. The only atypical part of the office deployment is that we have updates in the Updates folder in the Office 2013 media.

Any ideas?

Task sequences had been running without any issues until recently. Now I'm getting Failed to open the Task Sequencing Environment. Code 0x80004005. every time I try to deploy the image to any of our computer models. I've already checked the BIOS clock, diskpart and cleaned the hard drive, and created new boot media. Nothing really has changed in the environment. Any suggestions? 

Hello Experts,

We have a requirement to migrate OS Images from SCCM 2007 to SCCM 2012. Based on TechEd videos (WIN-B346 / Building the Perfect Windows 8.1 Image - TechEd - North America 2014) and different blogs, I understand that the existing 2007 Images which have SCCM 2007 client as a part of the Image cannot be reused in SCCM 2012.

My question is –

Can we reissue the OS Images which had been captured in SCCM 2007 from Reference Computers using capture media and do not have SCCM 2007 client as a part of the base image?

Does it imply on the OS Images which had been built using MDT 10 Task Sequences as well?

Hi there

i have to install - for special testing purposes - windows pe on an tablet with an ATOM Z3795. This means this devices should use the Intel HD Graphics 4000/2500 driver. I´ve injected the Intel driver but it seems it isn´t used.

After booting my pe-stick the Tablet is using the Microsoft Basic Display driver and haves 1920x1200 as one and only resolution

Now i would like to reduce the resolution, but with setres.exe i get "are not supported by your video device"

I understand that a very/too high resolution/refresh rate may harm my screen - but why can´t i run a lower than the maximal resolution???

When I install Windows 8.1 on this device the Intel driver is installed (problably because the driver-setup is a 32bit-app and pe doesnt support 32-bit apps) so i can reduce the resolution to 1024x768 - but why cant i do it with PE???

thx

netlord

We have a few Lenovo models to support Windows 7 x64 deployment via SCCM 2012. We have folders for each hardware model with proper drivers imported within SCCM console. For now we have WinPE (boot image 64 bit) with drivers which are located within folders designed for hardware models (so not all drivers in WinPE are specially designed for WinPE and they are normal Windows 7 drivers located in proper folder for hardware model within SCCM console).

What I want to do is to copy these drivers (which are used for WinPE) from existing folders for specific hardware model and copy them to new create WinPEx64 folder for drivers for WinPE. But SCCM 2012 does not allow me to have duplicate drivers - I can only move those drivers to WinPEx64 folder, but when I will move them they will be missing for existing driver packages.

What is the best approach in such situation, do not import drivers for WinPE to SCCM console (to specific WinPE folder), store them in specific folder (or network share) and inject them into WinPE.wim file using dism? Then use such WinPE.wim file in SCCM as boot image

Hello,

I have SCCM2012 SP2 facing issue with client push installation alo when i tried to install he client manual on windows 7 sp2 it displays comparability issue warning.

- auto client push installation enabled.

- Network service account configured for domain admin ( for troubleshooting )

Please advise.

thanks.

Our environment is SCCM 2012 R2 SP1.  I have deployed a task sequence to 12 computers in the same office.  All are healthy active clients in the same boundary assigned to the same DP.  The task sequence succeeded on 10 of them. 

On the other two the deployment status is "In Progress" with the description "Waiting for content".  If I walk over to the machines and open-up Software Center I can see the task sequence listed with "Downloading content 0%".  It has been like this for about 3 hours now.

The content is obviously on the DPs.  The DP is healthy (Green check).  Where do I start troubleshooting this?

Thanks for any suggestions!

FP

Is it possible to use the collected informations from Software Inventory or Hardware Inventory in the task sequence?

My situation:

We use a HTA to set informations during the installation like: computername, computer description, OS version, different PC-settings, language, ...

I want to preset the current settings in the HTA, therefor I need the informations from the database in variables.

But I have no idea what to do.

thanks

Silenos

Hi there

Testing SCCM 2012 OSD against a Surface Pro 4, not enjoying it too much.

The tablet does successfully pxe boot, however immediately after seeing the 'Preparing network connections' popup there is a restart.

Using a command prompt to block the restart, I can see the network is not available in time i.e. in the smsts.log there is this line: "Surface Pro ethernet adapter ip address is 0.0.0.0".

Within perhaps 10 seconds after seeing the 'Preparing network connections' popup disappear, the device gets an ip address.

I am testing using both the official Microsoft Surface Pro ethernet adapter and Surface Pro dock.

These are the official Microsoft devices - and plainly these are the problem, namely that connecting an ethernet cable to a Surface Pro via one of these devices is not the same as connecting an ethernet cable directly to a pc (obviously).

I tried a pre-start command, namely a vbs script with a 20 second pause, this made no difference.

I have read that SCCM OSD is possible with Surface Pro 4's, so presumably something can be done to get past this.

Hoping someone can advise.

Best regards

John

I'm trying to PXE boot a laptop from a remote DP, but when I PXE boot I can't even get an IP address. I'm not getting an error message either. When I check smspxe.log on the remote DP the last message is from a year ago saying "PXE Provider Shutdown".

I've restarted both the remote DP and main site SCCM 2012 R2. I've also tried restarting WDS service. Flow control and Loop back protection on switch is off, I've verified that the laptop is not listed in Device Assets.

Hi all,

I'm deploying the Windows Management Framework during an OSD task sequence. I'm using a 1-line PowerShell script as my detection method for the Windows Management Framework application:

if (Get-WmiObject -Query "Select * from WIN32_QuickFixEngineering where HotFixID = 'KB2506143'"){write-host "Installed"}

When the task sequence reaches this step, it fails to run. The AppDiscovery.log file contains the following lines:

    Performing detection of app deployment type WMF 3.0 Win7SP1 x64 and 2008 R2 SP1(ScopeId_C2C3E2A6-CD6C-4041-815A-40099562602C/DeploymentType_5c5f1be5-647e-4203-9e93-e10f76a4ffe0, revision 18) for system.	AppDiscovery	3/11/2013 5:41:33 PM	2168 (0x0878)
Failed to read script execution time-out from policy. Use default 60 seconds.	AppDiscovery	3/11/2013 5:41:33 PM	2168 (0x0878)
    In-line script returned error output: & : File C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1
cannot be loaded. The file
C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1 is not
digitally signed. The script will not execute on the system. For more
information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3+ & 'C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1'+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : SecurityError: (:) [], PSSecurityException+ FullyQualifiedErrorId : UnauthorizedAccess
	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)
Script Execution returned error message: & : File C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1
cannot be loaded. The file
C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1 is not
digitally signed. The script will not execute on the system. For more
information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3+ & 'C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1'+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : SecurityError: (:) [], PSSecurityException+ FullyQualifiedErrorId : UnauthorizedAccess
, ExitCode: 1	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)
  Script Execution Returned :1, Error Message: & : File C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1
cannot be loaded. The file
C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1 is not
digitally signed. The script will not execute on the system. For more
information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3+ & 'C:\Windows\CCM\SystemTemp\67d54b0a-d6ee-4fed-809a-6ce225bf9b48.ps1'+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : SecurityError: (:) [], PSSecurityException+ FullyQualifiedErrorId : UnauthorizedAccess
. [AppDT Id: ScopeId_C2C3E2A6-CD6C-4041-815A-40099562602C/DeploymentType_5c5f1be5-647e-4203-9e93-e10f76a4ffe0, Revision: 18]	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)
CScriptHandler::DiscoverApp failed (0x87d00327).	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)
Deployment type detection failed with error 0x87d00327.	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)
Failed to perform detection of app deployment type WMF 3.0 Win7SP1 x64 and 2008 R2 SP1(WMF 3.0 Win7SP1 x64 and 2008 R2 SP1, revision 18) for system. Error 0x87d00327	AppDiscovery	3/11/2013 5:41:36 PM	2168 (0x0878)

As you can see, the PowerShell script that performs the application detection can't be run because it is unsigned. I've tried the following to fix it, but nothing is helping:

1. I signed the script using a code signing certificate issued by my enterprise CA

2. I added a "run command line" step before the application that sets the PowerShell execution policy to Bypass. I also tried Unrestricted which didn't help either. After the OSD task sequence failed, I verifid that the PowerShell execution policy had been changed.

I should also note that the above detection method works just fine if I run it using regular application deployment from within the full Windows OS. It only fails if run during an OSD task sequence.

Any suggestions?

Thanks,

--Russel

Hey Everyone

This is more of a general question rather than a specific problem and I wanted to know if others are seeing the same issues we are.

We testing  on Dell Optiplex 5040 and 7040 desktops that have the I219-LM NIC pushing out an SCCM/MDT UDI task sequence using 2012 R2 SP1 CU3. If we select our Win 7 .wim everything works perfectly but where we're seeing issues is if we pick our Win 10 1511 deployment. Our results are mixed. Sometimes it works perfectly, other times it won't add to the domain but installs the client, other times it adds to the domain but doesn't install the client, and yet other times when the doesn't do either and when the system comes up it says there's no network cable attached even though there is and just opening the adapter settings is enough to reconnect the network. When it fails it's always after the forced reboot by the "Setup Windows and ConfigMgr" step and looking at the logs (when no client is installed we end up losing all the logs) the errors are because the system isn't on the domain so it can't talk to the distribution points.

I'm down to pointing at flaky drivers released by Intel/Dell (we're using the latest from Dell) but wanted to check with the rest of the community to see if they're seeing the same results.

Thanks

Hi All,

My organization recently purchased 80 new laptops, and we want to use them as a test bed for Windows 10. We are running SCCM 2012 r2 sp1 CU1 on a Server 2008 r2 VM. I was able to capture the new Windows 10 image, and create the new driver package for the laptop (laptop is an ASUS T100HA, I work at a school and they are for students). I have tried copying my existing task sequence I used for Windows 8.1, and making a new one, but I am still receiving an 80004005 error. I scanned the logs, but I am not an SCCM expert and can't quite figure out where its hung up. The OS image gets downloaded to the client, and then as soon as the apply operating system step completes, I receive the error. I've pasted from the log the line above where the 80004005 error starts, and then the line after where it is last seen. This chuck appears twice in the log and is from the smsts.log on the c:. From what I can tell, it could possibly be a problem with the image file being deployed? My next step is going to be to try and create/capture a new image.

Any help would be greatly appreciated. They would like to begin using these laptops next week! Thank you.

Have been trying to deploy an image, OS Deployment, to a laptop but the error we are seeing on the firewall is that UDP 500 is being blocked to the domain controllers.  The SCCM server is not running on the domain controllers.

We cannot find where this is configured anywhere.

I have looked under Administration / Client settings / Default client settings > Properties > NAP > Enable NAP on clients = NO.

Can anybody advise what I should be looking at?

Hello.  I am trying to capture a Windows 10 image for distribution on my system.  I have created capture media using my 64bit boot image.  When I start the capture it preapares the operating system then restarts.  After restarting it begins scanning the volumes.  It scans volume one (most likely the recovery partition) then starts scanning volume 2.  After a few minutes, I get the failure:

Image Capture Wizard has failed with error code (0x8007000D).

Any ideas?

I am getting the TS error 0x80070643 when executing a specific packages in an OSD task sequence.  It is a rather large Adobe Creative cloud package.    I checked the SMSTS log and didn't see anything in there pertaining to my package

But here's the weird part it doesn't consistently fail.  On some of the computers it works just fine, on others it fails.  I can run the OSD task sequence again and it very well may work on the machines that it failed on. 

The package is set to install directly from the DP.  Previous to today I have never had this problem with this package or TS in general.  Any ideas?