Task sequence error 0x80070032 - System partition not set

Uninstalling and Re-Installing SCCM 2007 Client

When you have few hundred machines with no client or with broken client it is hard to re-mediate them manually visiting each and every machine. It is worst when the client push from the console not doing anything. In this scenario SCCM right click tool and ccmclean.exe comes to the rescue.

Considering admin share is configured, WMI is healthy, SCCM Right client tool installed on your machine and you have ccmclen.exe file downloaded, and we can install SCCM Client on no client machines or machines with the broken client.

Step 1: create a collection and add all the machines with no client and broken client machines to this collection.

Step 2: Next ping the collection using the right click tool ping command. It will produce two lists one is Successful and second one is Failed.

Step 3: Create a sub collection for No Client but online machines. Add all the successful ping machines to this collection in one go using right click tool.

Step 4: Now, go to the each and every machine on the sub collection and right click on the machines individually then click on Client Tools, then choose Remove ConfigMgr option. In few seconds it will show a successfully initiated pop-up message. We can open the log file on C:\Windows\System32\ccmsetup\ccmserup.log file for the progress of the un-installation. The uninstallation will take less than a minute.

Step 5: Once the uninstall is complete, right click on the machine then click on Client Tools then choose Install SCCM Client. It will take some time based on the network speed and computer performance. Again we can check the C:\Windows\System32\ccmsetup\ccmserup.log for the installation status.

Step 6: once the installation is successful, update the memberships then refresh. Wait for 20-30 min to console to update the status from no client to client installed.

Uninstall using ccmcleanup.exe:

If the Right click tool fails to un-install a broken client then we need to use ccmclean to do the job.

Step 1: Get the ccmclean.exe and psexec.exe and copy them to the computer we will send the uninstall command from

Step 2: Launch the command prompt with administrator rights, then browse to the location where psexec.exe then run the ccmclean.exe as below.

Psexec.exe –s \\clientcomputerhostname \\Location-of_the_ccmclean\ccmclean.exe /client /Q

That’s it. This will remove the client. Once the client is uninstalled, re-install the SCCM Client following the above method.

Windows 7 - KMS activation error 0xC004F035

Error: Activating Windows 7 using KMS activation failes with error code 0xC004F035.

Issue:
According to Microsoft:
"This error code equates to “The Software Protection Service reported that the computer could not be activated with a Volume license product key...” The error text is correct, but is ambiguous. This error indicates that the computer is missing a Windows marker in the BIOS – provided on OEM systems to indicate computers shipping with qualifying editions of Windows, which is a requirement for KMS client activation. Error: Invalid Volume License Key In order to activate, you need to change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source. ANY OTHER INSTALLATION OF THIS SOFTWARE IS IN VIOLATION OF YOUR AGREEMENT AND APPLICABLE COPYRIGHT LAW."

Solution:
Use valid MAK key to activate the windows.

Report Builder 2.0 is not installed as a click-once application on report server - SCCM 2012

Error: Report Builder 2.0 is not installed as a click-once application on report server - SCCM 2012



When trying to create custom report in SCCM 2012 the above error msg will display in first instance.

Reason: If you have installed SQL Server 2012 R2, by default it installs Report Builder 3.0.

But SCCM adds a registry to check for Report Builder 2.0

Solution:

Modifying the Report Builder version check from 2.0.0.0 to 3.0.0.0 will fix the issue.

Apply following registry key to remove the error:[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Reporting]

"ReportBuilderApplicationManifestName"="ReportBuilder_3_0_0_0.application"