Jump to content


nate8282

Windows 10 issues with SCCM 2012 R2 SP1

Recommended Posts

First, thanks for any help with this. I have the following 2 issues.

 

1. I can't import a Windows 10 WIM file in to SCCM 2012 R2 SP1. I get the error "The specified UNC path does not contain a valid WIM file or you do not have permission to access it." It is not a UNC path name issue. I can import any WIM file except Windows 10. This is the original WIM in the sources folder that I've downloaded from MVLC.

 

2. I can't create a capture for Windows 10 using Task Sequence Media. I created the media after upgrading to SCCM 2012 R2 SP1, uninstalling Windows ADK 8 and installing Windows ADK 10 and using the boot images from it (10.0.10240.16384). I get error (0x00004005) I've attached a log. It's a new install so it doesn't have the 3 max per computer issue and Windows 10 is installed on VMWare Workstation.

 

Any help would be appreciated.

 

smsts.log

Share this post


Link to post
Share on other sites

as regards #1 are you pointing to the path and media as i show here

 

as regards #2 see the errors below

<![LOG[Sysprep state set to IMAGE_STATE_UNDEPLOYABLE]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="offlineos.cpp:386">
<![LOG[The OS has not been generalized using sysprep.exe, or sysprep did not complete.]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="1" thread="3056" file="offlineos.cpp:402">
<![LOG[bSysPreped, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,514)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:514">
<![LOG[Sysprep did not complete successfully]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="prepareos.cpp:514">
<![LOG[RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:1375">
<![LOG[Unable to sysprep the machine, hr=80004005]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="prepareos.cpp:1389">
<![LOG[pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="main.cpp:270">
<![LOG[Sysprep'ing the machine failed, hr=80004005]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="main.cpp:270">
<![LOG[De-Initialization successful]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:1147">
<![LOG[Exiting with error code 16389]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="1" thread="3056" file="main.cpp:293">
<![LOG[Process completed with exit code 16389]LOG]!><time="13:09:21.938+300" date="09-03-2015" component="TSManager" context="" type="1" thread="1824" file="commandline.cpp:1124">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:09:21.938+300" date="09-03-2015" component="TSManager" context="" type="1" thread="1824" file="instruction.cxx:805">

you need to examine your sysprep log files for more info as to why it failed sysprep

 

The errors will be logged in the following folder:-

 

C:\Windows\System32\Sysprep\Panther

 

and the following files will point to the failure:-

  • setupact.log
  • setuperr.log

Share this post


Link to post
Share on other sites

I'd really suggest that you give up on using ConfigMgr for creating your Windows 10 reference image and start using MDT instead. Follow Johan's excellent guide below:

 

http://deploymentresearch.com/Research/Post/496/Building-a-Windows-10-Reference-Image-using-MDT-2013-Update-1

 

By doing this, you'll not have to import the install.wim from the Windows 10 ISO, and you'll not have your issue with taking a capture.

 

Simply put it, always use MDT for reference image creations :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

There are known errors that Syspre fails if modern/universal apps are installed or updated during the reference image build.. could be the issue, check the log file that Niall pointed out to find the root cause.

Regards,

Jörgen

Share this post


Link to post
Share on other sites

SCCM will let me import the Windows 10 Enterprise LTSB WIM file, but it will not let me import the Windows 10 Education Edition WIM, which is of course is the one my boss wants me to use so people can have their default metro apps. I haven't figured out yet why it will let me do one and not the other.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...