Thursday, July 29, 2010

SCCM Right Click Tools Error -2147217405

I am trying to run some client action from SCCM console but there is an error like the picture below. I had been googled around and found solution 1 which listed below but sad that it is not working for me! After troubleshooting for while, I found myself a solution which listed below as solution 2. And now I manage to run the client action from my SCCM console.
Solution 1:
At your SCCM Server
  1. Search for wmimgmt.msc
  2. Right click WMI control (Local)
  3. Click on properties
  4. Click on the security tab
  5. Expand Root
  6. Select SMS and then click the security button
  7. Select SMS Admin, and Allow Enable Account and Remote Enable
  8. Click OK to exit.
If the solution above doesn't work, you may need to follow the next solution.

Solution 2:
At the PC that you want to connect
  1. Right Click on Computer, Click on Manage
  2. Expand System Tools
  3. Expand Local Users and Groups, Click on Groups
  4. Right Click Administrators Group, Click on Properties
  5. Click Add to add the desired user the group.
It should be working now. =) 

Friday, July 16, 2010

MDT 2010 failure during sysprep and capturing

I am using MDT 2010 to do a sysprep and capturing task sequence on the Windows 7 reference machine.
First of all, I mapped the deploymentshare$ to drive Z. After that, I execute the Litetouch.wsf file under the deploymentshare$\script and then go thru the wizard. Everything run smooth until the sysprep finished, a failure occur like the screenshot below.
This failure happened due to the registry key CloneTag under HKLM\SYSTEM\Setup is deleted during the start of the sysprep. There are few ways to counter this failure:
  • Go to your sysprep and capturing task sequence, Execute Sysprep, Options tab, Add, Registry Setting. Enter SYSTEM\Setup in the key box, and enter CloneTag in the value name box and leave the value box blank. This whole step is to add the registry key back to HKLM\SYSTEM\Setup after the sysprep completed.
  • You can also modify the script to prevent the registry key from being deleted. Go to your deploymentshare folder and look for a script named LITSysprep inside the scripts folder. Right click, edit to do modification in the script. You can either remove the oShell.RegDelete "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" or you might want to add .// infront to turn it into a comment.
Both ways stated above can resolve the failure occur during sysprep and capturing. This topic also discussed in technet forum, and here's the link.