Advertisement

12.02.2008 at 07:01PM PST, ID: 23952043
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.3

Receiving a 80004005 error during SMS OSD deployment

Asked by Lorrec in MS System Center

Tags: , ,

Hello. I have started experiencing problems with builds recently. I am hoping that I can get some assistance.

The build process starts correctly. I have the ability to debug so I can see that the machines are pulling an ip address. However, after the ip address is set I receive an unspecified error 80004005. When I look in the osdinstallwizard.log, I see an error message about the package path not being set and when I look in the osdenv.ini I see that the OSDpackagepath is equal to blank and program is equal to blank.

I have found several posts and tried numerous thing but nothing has resolved the problem. Any advice on what I can do? What would cause the package patch to not populate?

We have not made the switch to SCCM and are still on SMS 2003.

Thank you for any help. Start Free Trial
[+][-]12.06.2008 at 10:32AM PST, ID: 23113161

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MS System Center
Tags: Microsoft, SMS, 2003
Sign Up Now!
Solution Provided By: matrixnz
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 - Hierarchy / EE_QW_2_20070628