Hash error

I tried adding another BDD Package after the software installed as suggested by the MD team but that didn’t help in my case.

1/18/2008 11:00:44 AM   60   Use BDD Package   State Restore   11134   The task sequence execution engine successfully completed an action   0   on to the share \\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030\ with network access account Connection request for "\\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030" Connecting to "\\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030" Successfully connected to "\\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030" Resolved source to '\\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030' Command line for extension .exe is "%1" %* Set command line: Run command line Working dir '\\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030' Executing command line: Run command line Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Process completed with exit code 0 Command line returned 0 EnteringReleaseSource() for \\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030reference count 1 for the source \\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030\ before releasing Released the resolved source \\OACONFIGMGR01.SMSlab.OA\SCCM_DP\SMSPKG\CM100030\ 

So now I am going to try and disabled the Move State Store task and see if that fixes the problem but that will be another task for another day as I am tired and ready to go home.

Chris Stauffer

here is another excerpt for you from the install doc

Configure SSL on the WSUS Server

1. Right-click the Web site or virtual directory, and then click Properties.

2. Click the Directory Security tab, and then click Edit in the Secure Communications section.

3. Select Require secure channel (SSL), and then click OK.

4. Click OK to close the properties for the virtual root.

5. Close IIS Manager.

6. Run the following command from <WSUS Installation Folder>\Tools: WSUSUtil.exe configuressl <subject name in the signing certificate>.

ok i have a document created for installing SCCM from scratch but unfortunitly i can not release it yet because it has information that i dont want released about the new commonwealth's site yet. So since people seems to be having this issue i figure i will cut and paste what to do to fix the problem.

WSUS Installation

http://technet.microsoft.com/en-us/library/bb693980.aspx

 How to Install Windows Server Update Services 3.0

Before a software update point can successfully be installed and configured on a site system server in Configuration Manager 2007, Windows Server Update Services (WSUS) 3.0 must be installed on the server.

Use the following procedure to plan for the WSUS 3.0 structure and to install WSUS 3.0 on a server that will be configured as a software update point.

To install WSUS 3.0 using the Setup wizard

• 1. Review Determine the Software Update Point Infrastructure to determine how many WSUS3.0 servers need to be installed at the site and where in your environment they should be installed.
• 2. Download the WSUS installer file (WSUS3Setupx<platform>.exe) from the Windows Server Update Services Home Web page (http://go.microsoft.com/fwlink/?LinkId=92650) and save it to a location accessible from the server that will install WSUS.
• 3. Double-click the WSUS installation file, WSUS3Setupx<platform>.exe.
• 4. Click Next, select Full server installation including Administration Console, and then click Next.
• 5. Click I accept the terms of the License agreement, and then click Next.
• 6. Select Store updates locally, specify the path (path should be the same drive that you will install SCCM on), and then click Next.
• 7. Specify the software used SQL Server2005 on a local or remote computer. By default, Install Microsoft SQL Server2005 Embedded Edition (Windows) on this computer is selected. WSUS will create the Windows Internal Database or test the connection to the existing Microsoft SQL2005 server and instance. Click Next.
• 8. Specify create a custom WSUS3.0 Web site. When using the WSUS server for a software update point, it is recommended that Create a Windows Server Update Services3.0 Web site is selected. By default, the custom WSUS Web site uses HTTP port 8530 and HTTPS (SSL) port 8531. Click Next.
• 9. Review the specified settings, and then click Next. When the wizard completes, click Finish.
• 10. When the install is completed the WSUS configuration wizard will open. Close it.

DO NOT CONFIGURE WSUS though the Configuration Wizard.

Note: I will go into this further in the configuration of the Software Update Point so just keep this in mind for now:

• If you have multiple SCCM Software Update Points, only the top level one (Enterprise Central Site) points to Microsoft Update. The others should get their updates from the central site.
• The purpose of multiple update points is to reduce traffic from clients to the CSS. Clients get update metadata from the update point, and check that point for new updates every time they run a scan. That could be a lot of activity for one server and the associated network.

This can also be done on other primaries.

Chris Stauffer

I have been testing Microsoft Deployment with SCCM inigration for about 3 weeks now. I just wanted to make note of a few things that i have discovered.

I had several issues untill i upgraded from VMWARE GSX to VMWARE Server 1.04 once doing this all of my previous error went away and instead i got a whole new set of errors.

I have been getting this error "wpeinit.exe error missing WDI.dll" for over 2 weeks now and just discovered today that the drivers for VMware where not needed to boot.

I removed all of the drivers from the Boot.win for WinPE (x86) and went with just a base boot.wim and my error is gone. And it booted without a WDI error.So if you are gettign this error try removing all of the driveres from your boot wim and see if the virtual system still boots Chris Stauffer <><