brand

When running the Deploy Windows 7 x64 - New Computer task sequence the Install Updates action just seems to hang at 100%. I am testing it in a VM and it has been on this screen for several days. I am not sure what logs to look at or what to look for. Any help would be greatly appeciated.

The two packages created by default are named specifically: "Configuration Manager Client Package" with no version specified "Configuration Manager Client Upgrade Package" with no version specified The package that is created when creating a MDT task sequence is named: "Configuration Manager Client Upgrade" with a version of 5.0 GIven that they are not named exactly the same I wonder if there might be other settings.

Snapshots and the ability to have multiple computers running on a single host for testing purposes.

Can someone plese check their "Configuration Manager Client Upgrade Package" Package and see what it does and what the settinfs are so I can rebuild mine?

I basically did what you are describing and just used client push to deploy the client to the computers.

I accidentally deleted the "Configuration Manager Client Upgrade Package" Package while trying to get things working. I believe that this package came pre-created as part of the installation but am not positive. If it did come as part of the initial installation how can I get it back and what is it used for?

I have also downloaded the SCCM 2012 install ISO twice and compared the MD5 hash and they are both the same so I am not sure why it says file hash check failed.

I installed SCCM 2012 RTM on a Server 2008 R2 SP1 Hyper-V virtual machine following the Release Candidate install guide here. During the install several errors showed up in the ConfigMgrSetup.log file and I am concerned that the errors may be something to worry about. INFO: Executing SQL Server script: Create foreign key ci_currenterrordetails_ciid_fk Configuration Manager Setup 4/17/2012 11:38:08 PM 3060 (0x0BF4) INFO: Executing SQL Server script: Create foreign key ci_currenterrordetails_currentcompliancestatus_fk Configuration Manager Setup 4/17/2012 11:38:08 PM 3060 (0x0BF4) INFO: Executing SQL Server script: Create foreign key ci_currenterrordetails_settingid_fk Configuration Manager Setup 4/17/2012 11:38:08 PM 3060 (0x0BF4) INFO: Adding Permission: IF OBJECT_ID('EN_SetEnrollmentError') IS NOT NULL GRANT EXECUTE ON [EN_SetEnrollmentError] TO [smsdbrole_EnrollSvr] Configuration Manager Setup 4/17/2012 11:38:17 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\msrdcoob_amd64.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\wic_x64_enu.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\WindowsUpdateAgent30-x64.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\msrdcoob_x86.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\WindowsUpdateAgent30-x86.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\Silverlight.exe Configuration Manager Setup 4/17/2012 11:39:05 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\wic_x86_enu.exe Configuration Manager Setup 4/17/2012 11:39:06 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\dotNetFx40_Client_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:06 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\dotNetFx40_Full_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:10 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\sqlncli.msi Configuration Manager Setup 4/17/2012 11:39:38 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\dotNetFx40_Full_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:38 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\msrdcoob_amd64.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\wic_x64_enu.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\x64\WindowsUpdateAgent30-x64.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\msrdcoob_x86.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\WindowsUpdateAgent30-x86.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\Silverlight.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\wic_x86_enu.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\Client\i386\dotNetFx40_Client_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:40 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\sqlncli.msi Configuration Manager Setup 4/17/2012 11:39:41 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\sqlncli.msi Configuration Manager Setup 4/17/2012 11:39:41 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\msrdcoob_amd64.exe Configuration Manager Setup 4/17/2012 11:39:42 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\dotNetFx40_Full_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:44 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\SQLEXPR_x64_ENU.exe Configuration Manager Setup 4/17/2012 11:39:45 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\SQLSysClrTypes.msi Configuration Manager Setup 4/17/2012 11:39:47 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\SharedManagementObjects.msi Configuration Manager Setup 4/17/2012 11:39:47 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\sqlncli.msi Configuration Manager Setup 4/17/2012 11:39:47 PM 3060 (0x0BF4) ERROR: File hash check failed for D:\SMSSETUP\bin\x64\dotNetFx40_Full_x86_x64.exe Configuration Manager Setup 4/17/2012 11:39:48 PM 3060 (0x0BF4) omGetServerRoleAvailabilityState could not read from the registry on vNext.brazos-ra.dst.tx.us; error = 5: Configuration Manager Setup 4/17/2012 11:40:47 PM 3840 (0x0F00) omGetServerRoleAvailabilityState could not read from the registry on vNext.brazos-ra.dst.tx.us; error = 5: Configuration Manager Setup 4/17/2012 11:41:19 PM 3840 (0x0F00) omGetServerRoleAvailabilityState could not read from the registry on vNext.brazos-ra.dst.tx.us; error = 5: Configuration Manager Setup 4/17/2012 11:41:51 PM 3840 (0x0F00) omGetServerRoleAvailabilityState could not read from the registry on vNext.brazos-ra.dst.tx.us; error = 5: Configuration Manager Setup 4/17/2012 11:42:23 PM 3840 (0x0F00)

The name of our SCCM 2007 server is "SCCM" is it possible to keep that same name for a SCCM 2012 server or would it need to be different?