Jump to content




anyweb

using System Center 2012 Configuration Manager - Part 12. Connecting PowerShell and Building a reference image of Windows 8 with .Net 3.5



Recommended Posts

In Part 1 of this series we created our new LAB, we got the System Center 2012 Configuration Manager ISO and extracted it, then copied it to our Active Directory server. We then created the System Management container in AD, delegated permissions to the container, extended the Schema for Configuration Manager. We then opened TCP ports 1433 and 4022 for SQL replication between sites, installed some prerequisites like .NET Framework 4.0, added some features and then downloaded and installed SQL Server 2008 R2 SP1 CU6. We then configured SQL Server using SQL Server Management Studio for security and memory configurations prior to running the Configuration Manager 2012 setup to assess server readiness. Finally we installed a central administration site (CAS). In Part 2 we setup our Primary server with SQL Server 2008 R2 SP1 CU6. We then installed Configuration Manager 2012 on our primary server (P01) and verified that it was replicating to our central administration site (CAS) server. Then we configured Discovery methods for our Hierarchy and then configure Boundaries and Boundary Groups.

In Part 3 we configured Discovery methods and configured boundaries and created a boundary group, we then configured them for Automatic Site Assignment and Content Location. In Part 4 we added the Application Catalog roles to our Hierarchy. We then configured Custom Client Device Settings and then deployed those settings to the All Systems collection on site P01. After that we created Custom Client User Settings and deployed them to the All Users collection in order to allow users to define their own User and Device affinity settings. In Part 5 we installed the WSUS server role (it is required for the Software Update Point role). We then installed the Software Update Point role on our CAS and Primary servers and we configured the SUP to support ConfigMgr Client Agent deployment which is a recommended Best Practice method of deploying the Configuration Manager Client Agent.

In Part 6 we prepared our server for the Endpoint Protection Point role, and installed that role before configuring custom client device settings and custom antimalware policies. We then deployed those custom client device settings and custom antimalware policies to our newly created Endpoint Protection collections. In Part 7 we added operating system deployment ability to our hierarchy by adding Windows 7 X64. We used the Build and Capture process to capture a WIM image which we can later deploy to targeted computers using network boot (PXE). PXE boot requires specific settings on our distribution points and the boot images used to deliver the operating system WIM images were therefore also enabled for PXE support.

In Part 8 we added Applications to our Software Library and configured the requirements in the Deployment Type to add new abilities to the application delivery process. We monitored the approval process of our applications and saw how requirements can influence whether an application is installed or not and we noted the difference between deploying to Users versus Devices. Now we will take a look at how Automatic Deployment Rules can be used to automate the deployment of windows updates on Patch Tuesday using a recurring schedule to patch your infrastructure using Software Updates.

In Part 9 we created some folders and collections using a PowerShell script to make targeting of Windows Updates easier, we then performed a full synchronization of our Software Update Point before creating an Automatic Deployment Rule (ADR) for Windows 7 monthly updates for Patch Tuesday. In Part 10 we monitored our previously created ADR and monitored the downloading and deployment of those updates both to the distribution points and finally to our Windows 7 client computers. We reviewed the process in fine detail in order to understand the sequence of events when an ADR is run on a schedule.

In Part 11 we upgraded our Hierarchy to System Center 2012 Configuration Manager Service Pack 1 and now we shall begin using some of the new features that Service Pack 1 provides, one of which is the ability to Deploy Windows 8 and another is the PowerShell integration.

Introduction
System Center Configuration Manager 2012 Service Pack 1 has changed the method used to create and deploy operating systems, the first major change is in the build and capture task sequence itself, previous to SP1 you would select the operating system installation files (setup.exe) however now you can point to the install.wim file directly from the DVD in the build and capture task sequence. Indeed you don't even need to use a build and capture process anymore (if that's what you prefer), you could go straight to creating the deploy task sequence and deploy Windows 8 using the install.wim from the original media.

Most organizations however will want to customize their Corporate image somewhat and using the build and capture process still allows us to do that. One of the features that is notably missing in Windows 8 is .Net 3.5, so we’ll add that in our Build and Capture process. In this post we'll create a new Windows 8 image using the Build and Capture method and later deploy that image with the .Net 3.5 feature pre-installed, we will also see how we can accomplish some of these steps using Powershell CMDLets that are built into the product, so be warned there will be a lot of PowerShell used in this post and from this point onwards, so you may as well get used to it :). Trust me, if you feel afraid of PowerShell, don't be, go through every step in this guide and you'll feel much better once it's all complete.

Note: Throughout this post I provide sample PowerShell commands for you to execute, unless otherwise mentioned these have only been tested on Configuration Manager 2012 Service Pack 1, in other words, Cumulative Update 1 is not installed unless I directly refer to it.

Step 1. Connect to Windows PowerShell

In this post we will familiarize ourselves with some of the Configuration Manager PowerShell integration provided in System Center 2012 Configuration Manager Service Pack 1. PowerShell gives you the ability to automate many functions and this ability is now integrated in the console. To enable Powershell integration from within the console click on the blue drop down menu in the top left corner of the console and select Connect via Windows PowerShell.

Connect via Windows PowerShell.png

A PowerShell command window should appear, select [A] Always run when prompted, note that the site code of your Configuration Manager site that you are connected to (in this case the CAS) is listed.

Always run.png

In the screenshot below you can see the same action performed on our Primary site P01, notice the difference in display output.

PS P01.png

ok Now that we've connected to Powershell, in the CAS PowerShell console let's list the commands available.

Get-Command -Module ConfigurationManager  

That will scroll off screen as there are so many commands available

list of CmdLets.png

you may want to output that to a text file so that you can scroll through it at your leisure or search for a command. To create a list of available PowerShell commands, we will use PowerShell's Out-File command. Create a folder on D:\ called D:\Temp and then do the following:

Get-Command -Module ConfigurationManager | Out-File D:\temp\CM12_PowerShell_Commands.txt


This list is specifically for Configuration Manager 2012 SP1, if you install Cumulative Update 1 (I have not on this lab, however I've installed it on a separate non-CAS hierarchy) then you’ll get access to even more PowerShell CMDLets. Here's a list I created using the command above.

CM12_PowerShell_Commands.txt


if you want to get help on any PowerShell cmdlet try using get-help command eg:

get-help Update-CMDistributionPoint

Tip: you can also use the PowerShell cmdlets without opening the console, change directory to the adminsconsole\bin folder and start up a powershell console and then use the following line
Import-Module "D:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1"

and lastly if you want to search for commands that have a certain name you can do so like this:

get-command -Name *Computer*

which should return a list of any command with computer in the name. Now that you know how to use the PowerShell integration we’ll return to it later in this guide.

Step 2. Copy the Windows 8 media
Perform the following on the CAS server as SMSadmin

Mount your Windows 8 ISO and copy the entire contents to an appropriately named folder in the sources folder structure on the CAS server, for example I've copied mine to

\\cas\sources\os\os_media\windows8x64

Step 3. Add the Windows 8 X64 Install.WIM file
Perform the following on the CAS server as SMSadmin

In the Operating System Deployment section of the Software Library workspace, select Operating System Images and right click, choose Add Operating System Image

add operating system image.png

Point the wizard to the Install.WIM file in the sources folder of your extracted media files, eg: \\cas\sources\os\os_media\windows8x64\sources\install.wim.

Tip: Prior to SP1 you would not use the Install.WIM file directly from the media as Windows would end up on D:\, however Service Pack 1 has the ability to deal with this natively and adds a new Configuration Manager variable called OSDPreserveDriveLetter

point to the windows 8 Install WIM file.png

On the General screen, fill in information about the Windows 8 image you are adding and edit the version or description info so that it clearly points out that this is the Install.WIM file that you are using (to make it clear later when adding Windows 8 images to any Deploy Windows 8 task sequences).

Fill in general information for the operating system image.png

and continue the wizard through to completion.

complete the wizard.png

 

Note: You would of course want to do the step above using Powershell, and there is a cmdlet provided to do that however at present (29/4/2013) it does not work correctly in that you cannot distribute the image created. The command used to create the image above is

New-CMoperatingSystemImage -Name "Windows 8 Enterprise" -path "\\cas\sources\os\os_media\windows8x64\sources\install.wim" -Version "X64 (Install.WIM)" -Description "This is the Install.wim file from the Windows 8 sources folder. (c) windows-noob.com April 2013"
 

Remember, the command above does not work as you cannot distribute the image, for now create the image manually.


Step 4. Distribute the Windows 8 X64 image
Perform the following on the CAS server as SMSadmin

We could update our content to our distribution points by selecting the image just added, right clicking and choose Distribute Content, however we want to use PowerShell in this instance to update the WIM file to our distribution point.

Enter the following command in your PowerShell console (use the one started in Step 1.)

Start-CMContentDistribution –OperatingSystemImageName "Windows 8 Enterprise" –DistributionPointName "P01.server2008r2.lab.local"


Obviously replace the OperatingSystemImageName with the name you used and replace DistributionPointName with the FQDN of your Distribution Point.

Start-CMContentDistribution.png

Once done, open the distmgr.log in CMTrace on your CAS server to monitor the status of the content distribution

distmgr log file showing the distribution of our Windows 8 image to P01 distribution Point.png

Once distributed you can verify it’s status via the Configuration Manager console or via PowerShell using

Get-WmiObject –NameSpace Root\SMS\Site_CAS –Class SMS_PackageStatusRootSummarizer –Filter "PackageID='CAS00012'"

The output should look similar to below, look for Installed=1 and Targeted=1 this means that the package is distributed successfully.

SMS_PackageStatusRootSummarizer.png

Tip: You can get detailed information about these WMI classes on MSDN here http://msdn.microsoft.com/en-us/library/hh949534.aspx

Step 5. Create a Build and Capture Task Sequence
Perform the following on the CAS server as SMSadmin

A build and capture task sequence is normally used to create a custom WIM file containing your Operating System and some key applications used in your organization, those applications would normally be referred to as ‘FAT’ applications as they are usually big in size (think Office 2013 or SAP). The image generated by this process can later be used in a separate Deploy Task Sequence and in that task sequence you can have several custom steps and smaller applications such as WinZip. Creating a custom wim file this way does allow for greater flexibility and reduced installation time, however you may have to update this reference image once every quarter or so to include updates to your applications and of course Windows Updates themselves.

Navigate to the Windows 8 Build folder in Task Sequences, right click and choose Create Task Sequence.

Create Task Sequence.png

When the wizard appears choose the second option, Build and Capture a reference operating system. Give it an appropriate task sequence name and make sure to choose an X64 boot image when building an X64 operating system otherwise the Capture process will fail.

Build and Capture Windows 8 X64.png

Click next when done. For the Install Windows step, click on browse and select our Install.WIM file we added earlier. The only images you’ll be able to select here are either previously added WIM files or previously captured WIM files.

Image Package.png

Note: You can not select Operating System Installers in this step. If you want to select an Operating System Installer (setup.exe) complete the task sequence wizard and then edit the task sequence and edit the step after it’s created to point to an Operating System Installer (for example for Windows XP).

Enter the local administrator password which is useful if your Build and Capture task sequence fails for whatever reason

Install Windows.png

In the Configure Network step, join a workgroup, do not join the domain (keep the image clean)

Configure Network.png

The Install Configuration Manager client step should point to the FQDN of your site server hosting the Software Update Point role (if you followed this series of guides that will be our Primary server, P01) if you want to install updates during the task sequence, in that case use the following SMSMP=P01.server2008r2.lab.local for installation properties

install configuration manager client.png

In the next step select All Software Updates

All Software Updates.png

Install some applications that you’d like included in your reference image, this is just a lab so I don’t have much, you would typically want to install FAT applications like Office or SAP here

Install applications.png

Fill in some details about the image

Image Properties.png

Fill in a the details for a Capture account and verify that they work before continuing

capture account details and verification.png

Continue through the wizard until completion.

wizard complete.png

Step 6. Create a SXS package for adding Windows Features
Perform the following on the CAS server as SMSadmin

We want to add the .NET 3.5 Windows 8 feature to our reference image and to do so we’ll create a package with the source files required for adding roles and features to Windows 8. As the reference image will not be domain joined (it will join a workgroup) we cannot use a Run Command Line step with the Run As User option to specify a Domain User, instead we’ll create a package (using PowerShell) and copy that locally on our Windows 8 reference computer and install the feature using DISM.

Browse to the location where you copied the Windows 8 DVD and locate the sources\sxs folder, copy that folder (and all it’s subfolders and files) to a new location. Such as in the screenshot below, this will be the source files for our SXS package.

copy the SXS folder.png

Once done, open up our PowerShell connection again, and issue the following command to create our package (change it to suit the path of your SXS package):

New-CMPackage –Name "Windows 8 SXS" –Version "X64" –Description "Windows 8 SXS files needed for adding features, © windows-noob.com April 2013." –Language "English" –Manufacturer "Microsoft" –Path "\\cas\sources\os\os_media\Windows 8 X64 Features" 


New-CMPackage.png

Ok now that we’ve created the package using PowerShell, the next job is to distribute it to our distribution point P01, so issue the following command

Start-CMContentDistribution –PackageName "Windows 8 SXS" –DistributionPointName "P01.server2008r2.lab.local"

distribute package using PowerShell.png

Once again you can monitor distmgr.log for details of the package distribution or use PowerShell to see its status

Get-WmiObject –NameSpace Root\SMS\Site_CAS –Class SMS_PackageStatusRootSummarizer –Filter "PackageID='CAS00015'"


Like in the screenshot below

check package status for Windows 8 SXS using Powershell Get-WmiObject.png

Or you can do it the old fashioned way and verify in the console itself

package status in the console.png

Step 7. Edit the task sequence
Perform the following on the CAS server as SMSadmin

Next we will add two steps to our Build and Capture task sequence, locate the task sequence in the console, right click and choose Edit

Edit task sequence.png

The task sequence opens, select the Setup windows and Configuration manager step and choose the Add drop down menu, General, Run Command Line

Run Command Line.png

and edit it so that it corresponds with the screenshot below

xcopy SXS Locally.png

Next create another Run Command Line step called add .NET 3.5 Features using DISM and use the following command line:

add dot NET 35 feature.png

And that’s our editing done, Apply the changes and close the task sequence editor.

Step 8. Deploy the task sequence
Perform the following on the CAS server as SMSadmin

Next we want to deploy our Build and Capture Windows 8 X64 Enterprise task sequence to our Build Windows 8 collection (if you have not yet created that collection do so now, it should be a device collection with no members).

We will use the following PowerShell CMDLet:

Start-CMTaskSequenceDeployment –Name "Build and Capture Windows 8 X64" –CollectionName "Build Windows 8" –Comment "© windows-noob.com April 2013" –Deploypurpose "Available"

Start-CMTaskSequenceDeployment.png

Side note: After doing this you’ll have to manually edit the deployment to make it available to Configuration manager clients, media and PXE as per the screenshot below, currently in Configuration Manager 2012 SP1.

Configuration Manager clients, media and PXE.png

This has been automated in the Powershell updates from CU1 however the command to install is different

Note: the command below will NOT work on Configuration Manager 2012 SP1 without the CU1 update installed (and the resulting MSP file for the Powershell cmdlets run in order to give you access to the new PowerShell updates...).

Start-CMTaskSequenceDeployment –TaskSequencePackageId "CAS00013" –CollectionName "Build Windows 8" –Comment "© windows-noob.com April 2013" –Deploypurpose "Available" –MakeAvailableTo "ClientsMediaAndPXE" 



Step 9. Import a computer and PXE boot
Perform the following on the CAS server as SMSadmin

Now we are ready to import computer object into Configuration Manager’s database, we do this because the computer is not yet known to Configuration Manager. To do this we need to know the Mac address and computername, lets call the computername W81.

If you are using CU1 you can use PowerShell to import your new computer object (the command below returns an error in SP1, the error implies that your collection “Build Windows 8” does not exist, ignore the error, it just doesn’t work in SP1. If you don't need or want to update to CU1 then import the computer object using computer association.)

Import-CMComputerInformation –ComputerName = "W81" –MacAddress= "00:11:22:33:44:55" –CollectionName= "Build Windows 8"

import-cmcomputerinformation.png

If you are not using CU1 then import the computer information manually (as the Powershell CMDLet doesn’t work currently) as described in this post.

Once the computer has been imported, wait a few minutes before verifying that it shows up in the collection, do not continue until it is present in the collection. Once it appears PXE boot the virtual machine

PXE boot.png

Press F12 when prompted and select our task sequence

Build and Capture Windows 8 X64 ts.png

and off it goes...eventually it will get around to installing the .NET 3.5 feature

add dot net feature.png

it will then install any updates applicable which are targeted to the collection it's in during deployment which is the Build Windows 8 collection, so to recap if you want to get updates installed
you'll need to deploy a software update group containing updates for windows 8 to the build windows 8 collection

installing updates.png

and it will reboot before installing the applications, if your applications don't install check the Deployment Type(s) associated with the applications and make sure that any conditions you've set in there are not stopping the deployment of that application, the SMSTS.log file will help you with any problems here.

install applications - mozilla firefox.png

then and then it will continue before preparing the OS

prepare os.png

running Sysprep and then rebooting to capture the image

capturing the machine.png

and that is it for this post, you've learned how to Build a reference image of Windows 8 X64 Enterprise, you've installed some apps and enabled the .NET 3.5 feature and finally you've captured it for later installation in a Deploy Task Sequence (the next part of this series will cover that.)

In addition, you've done many of the steps above using PowerShell, how awesome is that !

cheers
niall.

 

Here is the next part Part 13. Deploying Windows 8 X64 with custom Start screen.



Recommended Reading


PowerShell/Configuration Manager Blogs

Share this post


Link to post
Share on other sites


Hi all,

 

I am using SCCM 2012 SP1 with Windows 2008 R2 x64 and want to try to deploy Windows 2008 R2. It does not work and I get the error message from x:\SMSTSLog\smsts.log

 

(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)

(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)

(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)

 

And from directory x:\Windows\Temp\SMSTSLog\smsts.log follow errors:

 

401 - Authentication failure on request with anonymous access, retrying with context credentials.

401 - Authentication failure on request with anonymous access, retrying with context credentials.

 

 

Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type

 

 

Failed to run the action: Apply Operating System.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

 

The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)

 

Failed to run the last action: Apply Operating System. Execution of task sequence failed.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

 

Can anybody help me?

 

I did checked follow:

 

  1. Click the Administration section
  2. Right-click the site in question > Configure Site Components > Software Distribution
  3. Choose the Network Access Account tab
  4. Specify the correct credentials to the share

I can connect with my credential the shared folder

 

Best regards

 

Keywan

Share this post


Link to post
Share on other sites

your problem is here

 

 

Failed to run the action: Apply Operating System.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

 

 

 

this post is about building a reference image, is that what you are trying to do ? are you using virtual hardware or a real computer ? have you verified it has a valid ip address and can ping the fqdn of the management point

Share this post


Link to post
Share on other sites

Hi anyweb,

 

Thanks for your replay. What do you mean with "building a reference image"? Yes I did try to do that. It is a real comupter. Yes I have a valid IP address and can ping FQDN of MP.

I'm almost to despair. Did you have a other post for deploying Windows 2008 R2?

 

Thanks for help

 

Regards

 

Keywan

Share this post


Link to post
Share on other sites

if you are not building a reference image (that is what this post is about) then please raise a NEW topic explaining your issue, what you've tried and how you are trying it, thanks.

 

this post is all about building a reference image of Windows 8 .... reference images should be built on virtual machines to keep them clean of drivers.

Share this post


Link to post
Share on other sites

Hi,

 

I have captured and build successfully window 8. But I have add to application(Adobe reader and PSPad) to the image, after finishing it does not installed my applications.

Could somebody tell why? Where can I find the logs for application?

Share this post


Link to post
Share on other sites

My task sequence fails with error code 0x80091007 once it gets to the installation of the configuration manager client. I have followed all the lab instructions and double checked everything. Any ideas what would cause this?post-20482-0-72414800-1371068886_thumb.jpg

Share this post


Link to post
Share on other sites

can you attach both the smsts.log file from the client and ccmsetup.log

Share this post


Link to post
Share on other sites

that log only shows up to the apply drivers step, you need to find the log(s) AFTER the failure

Share this post


Link to post
Share on other sites

and was that after the failure ? are you looking in the right place ? (x: or c: ?)

 

dir /s smsts*.log

 

try that in the root of any drive letter after the failure and before the computer reboots, in other words when you see the message on screen (that you included above) press F8 and grab the logs

Share this post


Link to post
Share on other sites

Tried the process again. Once it failed, I pressed F8 and opened a command prompt. Used the suggested command and found 1 smsts.log file in C:\_TaskSequences\Logs. No ccmsetup file found. I've again attached the smsts.log file.

smsts.log

Share this post


Link to post
Share on other sites

that log doesn't contain the error, how about x:\windows\temp\smstslog anything there ?

you'll note that this log is not the live one as it doesn't even reference you opening a cmd prompt.

Share this post


Link to post
Share on other sites

Ok. I think I've got the correct log files now. Found 2 different smsts.log files on X: One in Windows\Temp\smtslog and one in X:\smstslog\. Attaching both. One named smsts_win.log is from the windows folder. I hope you can give me some idea as to why it keeps erroring out.

smsts.log

smsts_win.log

Share this post


Link to post
Share on other sites

I'm trying to import the install.wim for Windows 8 Enterprise.

It failed with "The specified UNC path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path."

 

The permission is not an issue.

 

I tried to load the wim file using Windows System Image Manager and it's giving another error message.

"Error Opening Windows image at ............with the detail log attached below:

 

1:06 PM : This application requires version 6.2.9200.16384 of the Windows ADK.
Install this version to correct the problem
1:06 PM :
1:06 PM : Error opening Windows image at Y:\Installers\Microsoft\Windows 8\Win8X86\sources\install.wim.

1:06 PM :
1:06 PM : System.ComponentModel.Win32Exception (0x80004005): Reached the end of the file
at Microsoft.ComponentStudio.ComponentPlatformInterface.WimFileHandle..ctor(String wimPath)
at Microsoft.ComponentStudio.ComponentPlatformInterface.WimInfo..ctor(String wimPath)
at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.OpenWim(String wimPath)
at Microsoft.ComponentStudio.ImagePicker.GetImageInfoFromPath(String path)
at Microsoft.ComponentStudio.ImagePicker.ValidateImageFileOrFolder(String fileOrFolder)

=========================================================================

 

I've checked version for the installed Windows ADK and it's exactly 6.2.9200.16384.

I don't see a newer version of windows ADK available anywhere on the net.

 

Does anyone know what's happening with this issue?

Share this post


Link to post
Share on other sites

hi Arvin,

please post a screenshot of the path you are importing from...

 

"The specified UNC path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path."

 

Share this post


Link to post
Share on other sites

Thanks for replying, really appreciated.

It was just a normal UNC path.

I type it in and then browse to the install.wim file manually.
\\bafflo\software$\Installers\Microsoft\Windows 8\WIN8X64\Sources\install.wim

I have also tried to copy the entire directory to the local machine, also failed to load.

There's another copy of Windows 8 Pro within the same location under

\\bafflo\software$\Installers\Microsoft\Windows 8\WIN8PRO\

and it loaded fine.

These Windows 8 Enterprise ISOs I just downloaded were not available from the site. I believe it was only made available recently by Microsoft. Therefore I thought it might be the problem with my ADK, so then I installed the latest package for Windows 8.1 Preview, It still fails.

 

Log from SMSProv.log shows

*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 1/08/2013 8:26:56 AM 852 (0x0354)*~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 1/08/2013 8:26:56 AM 852 (0x0354)

 

Share this post


Link to post
Share on other sites

does the machine account have read access to \\bafflo\software$\

Share this post


Link to post
Share on other sites

Yes, It does.

 

As I mentioned, it worked with different images located at

 

\\bafflo\software$\Installers\Microsoft\Windows 8\WIN8X64PRO\Sources\install.wim and

 

\\bafflo\software$\Installers\Microsoft\Windows 7\WIN7X64\Sources\install.wim and

 

\\bafflo\software$\Installers\Microsoft\Windows 7\WIN7X86\Sources\install.wim

 

I also tried coping the entire folder to the server and create a share that way. Same thing. :(

Share this post


Link to post
Share on other sites

Update 2:

 

Is it me not installing it right ? or Does it (SCCM 2012) require certain magic before it will work?

After my last update, I was able to import all OS images. (Windows 7 and 8)

However, Build and Capture failed to work. (It was working before.)

Therefore I then try to check the report and see what exactly went wrong. Only then discovered Reports weren't working either!!

 

The installation sequence for this trial was SCCM 2012 SP1 -> CU1 -> CU2 -> Configure bounndaries -> following the guide until build and capture and then somewhere around here I added the reporting role.

 

After finding this annoying issue, I revert everything back again and install it with the following sequence.

 

SCCM 2012 SP1 -> Install reporting, catalog roles, test reporting working, reboot > CU1, reboot, test reporting working > CU2, reboot, test reporting ,working again >

 

I will go ahead and follow the guide again. am I the only person who is experiencing this issue??

My environment is Vmware ESXi 5.1 with Windows 2008 R2 and Windows 2008 SQL

 

====================================================================================

 

I just test it again and it's showing that same error message for all wim files!!!

All possible location I can try, local, network, and all......

 

Is this a bug or have I done something wrong which killed it?! :(:(:(:( :(

 

This is really odd. I'm rebuilding the whole server again!

 

Update:

 

It's working again after I rebuilt the server. However, I am not importing Windows 8 Pro image this time.

I have no idea what's the cause of this issue though.

Share this post


Link to post
Share on other sites

Hi everybody !

 

Niall, I'm a huge fan of your work !

Even if I visit this website frequently,this is the first time a post a comment.

I read a lot of your tutorials and I think this is the best place to ask my "expected" question.

 

Let me explain my issue:

I realized a "Build and Capture" task sequence for Windows 8 on a SCCM 2012 SP1.

  • The DotNet 3.5 Feature is implemented as indicated.
  • The Software Updates works perfectly (Network Account setted, ConfigManager client configured with SMSMP=blabla.fqdn and SMSCACHESIZE=10240)
  • I don't use pxe but a boot media.
  • I use a static IP which is configured onto the "Apply Network Settings" Task Sequence.
  • Vmware Virtual Machine (1Go Memory / 30 Go HDD)

 

Everythink works perfectly 'till I add an Application (Office 2013).

I receive the famous 80004005 error.

When I disabled this step, I don't have any issue and I'm able to finish the capture.

 

You wrote on your tutorial :

if your applications don't install check the Deployment Type(s) associated with the applications and make sure that any conditions you've set in there are not stopping the deployment of that application, the SMSTS.log file will help you with any problems here.

 

  • I checked any conditions and the first mistake I've done was concerning the necessary disk space available.
    • For information, if it doesn't respect this condition, the product is not installed but the Task sequence continues to work even if the
      "If an application fails, continue..." combo box is checked and the "Continue on error" is unchecked. So, the capture was done but without Office :rolleyes:
  • I tryed with another "smaller" application.
  • I even try not to put any condition.

I still meet the same issue.

 

Before I post my smsts.log, Could you tell me if a missed something ?

 

Thank,

 

Frederic.

 

Update:

I'm trying to follow this topic: http://www.windows-noob.com/forums/index.php?/topic/6061-change-sms-cache-size/

  • Like 1

Share this post


Link to post
Share on other sites
Niall, I'm a huge fan of your work !

 

 

thanks !

 

 

  • I even try not to put any condition.

I still meet the same issue.

 

 

 

please post the smsts.log including the failure that's the best thing at this point

Share this post


Link to post
Share on other sites

Hey,

Thanks for your quick answer.

I'm trying to add a new task in order to change the SCCM Cache size following this topic http://www.windows-n...sms-cache-size/
Just have to wait 'ill its finish

Here is a 'Light version' of my TS.

B&C.bmp

smsts.log

I can see some:

CAppMgmtSDK::GetEvaluationState ScopeId_D191CFE2-D57B-42EB-BCBB-F1A23D0E2606/RequiredApplication_7936e7d9-ad59-4159-9abf-5d9f29f6ae86.29 = EnforcementFailed

 

 

But i don't understand them.

Share this post


Link to post
Share on other sites

here's the failure

 

<![LOG[install application action failed: 'Microsoft Office Professional Plus 2013'. Error Code 0x80004005]LOG]!><time="12:25:27.039-120" date="09-11-2013" component="InstallApplication" context="" type="3" thread="2176" file="installapplication.cpp:798">
<![LOG[sending error status message]LOG]!><time="12:25:27.039-120" date="09-11-2013" component="InstallApplication" context="" type="1" thread="2176" file="installapplication.cpp:802">

 

 

so what does your Office 2013 log file tell you ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×