• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4332
  • Last Modified:

Microsoft System Center Configuration Manager 2012 SP1 OSD fails

Hello Experts,

we just migrated from SCCM2007 to SCCM2012 SP1, Migration as far as you can call this a migration went fine. Clients are upgraded, Windows Updates are provided by SCCM and so on.

This week i tried to deploy Windows XP to new computers using a newly created OSD Tasksequence and the "old" .wim file from the 2007 SCCM-Server. The OSD fails at step three which is deploying the image. Step one and two are partitioning and formating the disk.

On the client the smsts.log file contains the following error:
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)

Open in new window


i searched the web and found some hints that "allow anonymous access" on the IIS fixed that issue which is unfortunately no solution for me. I tried to access the DP URL for that specific .wim file, as found in the smsts.log (http://DESTR01-WIW032.DOMAIN.NAME.de/SMS_DP_SMSPKG$/STR00002)  and yes, it can be accessed, even from foreign computers/users (freshly installed Laptop, no Domainmembership) so its - as far as it seems for me- not an authentication thing. I`m really running out of ideas now, so help is highly appreciated.

Here are the details to my system:
Microsoft System Center 2012 Configuration Manager Service Pack 1
Ver. 5.0.7804.1000

Attached you'll find the smsts.log from x:\windows\temp the one from x:\smslog contains nearly no interesting information.

Cheers Ingo
smstslog55---Copy.log
0
Rhenus
Asked:
Rhenus
  • 2
  • 2
1 Solution
 
Nagendra Pratap SinghCommented:
It seems that the package _SMSTSSTR00016 has not been distributed. This could be the SCCM client package.

Please check if all shares have been updated.
0
 
Nagendra Pratap SinghCommented:
Also try this

The resolution was to change the deployment properties on the Task Sequence from "Access content directly from a distribution Point" to "Download content locally".

http://configurationmanager2012.blogspot.in/2013/02/task-sequence-problem-after-migration.html
0
 
RhenusAuthor Commented:
Hi thanks for the fast responses.

i double checked if the packages are distributed and available. Both packages are targeted for the DP and are 100% compliant. From a webbrowser it`s possible to download the packages in question.

I also checked the network-access-account and made sure "download content locally" is enabled.

@npsingh123 maybe this is the problem, in the OSD deployment wizard you cannot select anything else then "download content locally when needed by tasksequence" if you do have an option i`m probably looking at the wrong settings page.

Please see the attached pictures for illustration, i tried to capture anything that might be of interest.

Cheers Ingo
hp6300proMT.png
os-package.png
STR0002-package.png
client-package.png
access-content-localy.png
network-access-account.png
access-content-localy-2007.png
0
 
RhenusAuthor Commented:
Ok found it, i read the link posted from "npsingh123" again carefully and can confirm the last sentence:
I Believe that changing the operating system package properties under Data Access to "Copy the content in this package to a package share on distribution Points" would have been the other solution to this problem.
yes thats true. i checked the box, sccm copied that package again on the DP and here we go! Deployment works as expected. I´m curious to find out, why the same package needs to be in two different folders on the same DP but thats not part of my question here.

Cheers Experts, you saved my weekend!

Ingo
copy-content-to-share.png
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now