Chris Stauffer at myITForum.com

SP2 also includes a Service Pack Clean-up tool (Compcln.exe) which helps recover the hard disk space by permanently deleting previous versions of files (RTM and SP1) that are being serviced by SP2. The Service Pack Clean up tool can also be run offline while creating slipstream images to reduce the size of the image.

Running this compcln.exe tool is pretty simple:
1. Click Start>All Programs>Accessories>Command Prompt or click Start>Run and type cmd to open Command Prompt Windows.

2. Execute the command “Compcln.exe”. The path is “c:\Windows\System32 \compcln.exe”.

3. Users will be prompted with a question whether to keep Vista SP2 permanently in the system.

This operation will make all service packs and other packages permanent on this computer.

Upon completion you will not be able to remove any cleaned packages from this system.

Would you like to continue? (Y/N):

4. Once users types “Y” and presses enter, the system will start performing the windows components clean.

After the cleansing process, users will notice the free hard disk space has increased substantially.

This tool would be good to run if you are building a WIM.

I will look into adding this to a TS in ConfigMgr later this week.

Looks like Vista SP2 is now available in Windows/Microsoft Updates.

http://technet.microsoft.com/en-us/windows/dd262148.aspx

Download types

Deployment Guide

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

As you can see by my posts lately i have been doing a lot with OSD and MDT.

Well here is the latest error I've come across.

OSDDiskPart.exe failed: 0x80070490

Turns out the tech replaced the SCSI hard drive but didn't reconfigure the RAID settings. I had to clear the settings then reconfigure the raid array.

Then do the following:

Enable the F8 Diagnostic (cmd prompt by pressing f8 key) in your Boot Image.

Then boot your win PE image.

1. press F8 for the command prompt
1. execute diskpart.exe
1. select disk 0
1. Choose clean

Sometimes the disk is badly formatted or messed up from being replaced.

==============================[ OSDDiskPart.exe ]============================== Command line: "osddiskpart.exe" Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' FALSE, HRESULT=80070490 (e:\nts_sms_fre\sms\framework\tscore\diskutils.cpp,1386) CDisk::GetDiskSize(oDisk.getIndex(), cbDiskSize), HRESULT=80070490 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,691) LoadDiskConfiguration(oDisk), HRESULT=80070490 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,1412)Invalid disk number specified: 0 Invalid configuration specified.  Please ensure that the task sequence is properly configured. OSDDiskPart.exe failed: 0x80070490

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

Note: You may also get this error if WinPE cant find the hardrive. So you may need to add additional SCSI drivers to get the drive to appear.

If you are in a large site like me some queries will not show you what you need because you surpass the 2000 entries limit. The reg entry below will fix that.

Apparently they change the location for ConfigMgr. So if you are only running the ConfigMgr 2007 console you only need the second entry. but if you are using both like me you will need the whole works.

http://support.microsoft.com/kb/269201

APPLIES TO

• Microsoft Systems Management Server 2.0 Standard Edition
• Microsoft Systems Management Server 2.0 Service Pack 1
• Microsoft Systems Management Server 2.0 Service Pack 2
• Microsoft Systems Management Server 2.0 Service Pack 3
• Microsoft System Center Configuration Manager 2007
• Microsoft System Center Configuration Manager 2007 SP1
• Microsoft System Center Configuration Manager 2007 R2 with SP1

#################################################

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\AdminUI\QueryBuilder]

"ValueLimit"=dword:000124f8

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\AdminUI\QueryProcessors]

"ValueLimit"=dword:000124f8

#################################################

I have been able to successfully boot a test machine via PXE and install an OS (using the Task Sequencer) but after building the same machine a dozen or so times SCCM stops supplying the machine with the boot WIM.

This is my test machine  that i am using to to build my WIM’s with and play with other settings (thus why i am constantly rebuilding it). 

The PXE service point produces a status message stating "The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned."

But this statement is not correct.

I’ve tried the following:

• The device exists in a collection which has a TS advertisement assigned

• The advertisement is configured to "make this TS available to WINPE and PXE"

• I have attempted to re-run advertisement

• I’ve removed the machine altogether and tried to use the Unknown PC function.

The same advertisement works perfectly when run from "run advertised programs" if run from within the OS.

After searching the internet i found this:

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/55cbc072-4dd4-4c0f-a7eb-d3d505cb26d1

I tried both of these solutions and found that number 2 worked best.

1. The PXE flag is set on the computer resource to indicate that the computer was booted mandatory via PXE and prevents any further PXE boots until it is cleared (right click on the computer in the collection and select "Clear Last PXE Advertisement") [should only happen if the Task Sequence is advertised mandatory]

2. A caching issue: Occurs when the ResourceID of a computer changes but the MAC address stays the same. Happens if you delete and import a computer with the same MAC address after it was booted via PXE, then SCCM/PXE tries to lookup the advertisements for the old ResourceID. You can restart the Service WDSSERVER to clear the cache of the SCCM/PXE provider and see if the problem persists.

Hope this saves someone else time.

God knows I’ve wasted enough time on this issue.

Steps for getting PXE to work:

• Install all needed software on the SCCM server:
• WDS
• MDT
• SCCM with PXE role
• Vista WAIK 1.1
• All additional software to get OSD working

• Setup DHCP Helpers
• http://technet.microsoft.com/en-us/library/cc732351.aspx
• On the DHCP server
• 66 is ip address to SCCM server (you can use FQDN here if you choose)
• 67 is smsboot\x86\wdsnbp.com

• Uploaded Boot images to PXE DP
  • Then uploaded my custom x86 boot image
  • Then uploaded the out of box x64 boot image

Note: You need to upload the x64 boot image even if you are only using x86 because when the system boots if it sees that it is an x64 then it will just spin until an x64 file is found. As long as your TS is using the x86 boot image you will be fine.

Note: Make sure that you set a password on the PXE boot so that no unauthorized users can refresh there image.

As usual thanks to everybody on the MyITForum list for your assistance in getting this working.