Wednesday, April 27, 2011

Capture Windows 7 Failed with 00004005 Error Code

This is the first time I faced this error, searching in the internet and found the root cause of it. According this this site, this problem is due to too many times of sysprep, more than 3 times, which Windows Vista does not allow. This topic also discussed in technet forum, workaround is provided too. Here is another reference site.

Friday, April 22, 2011

CAMTProvisionEndpoint::GetProvisionSettings: GetObject() failed: 80041002

This error happened on some of my computers that I provisioning. According to this link, it says that this error is certificate related. But for my case, I personally think this can’t be certificate error because most of my machine are provisioned. Therefore I did some trial and error troubleshooting to solve this problem.
I manually unprovision the machine but still get the same error and then run this script to make it works. This script will clear the auto provision and then provision again. To make it works, you’ll need to unprovision the machine first and then run the script.
Before I made it happened, I also did try to use the Sendsched.vbs with {00000000-0000-0000-0000-000000000120} after I unprovision the machine manually but it is not working.

Thursday, April 21, 2011

Sendsched.vbs in SCCM Tools

This script helps us do our job faster!!! For example, you can trigger the AMT provision cycle instantly rather to wait the AMT provision schedule to run every hour. To operate this script, you just need to enter the correct key followed by the computer name. For instance to trigger the AMT cycle, c:\Windows\SCCMTools\sendsched.vbs {00000000-0000-0000-0000-000000000120} PC123. You can refer the key below to suit your need.

Hardware Inventory Collection Task

{00000000-0000-0000-0000-000000000001}

Software Inventory Collection Task

{00000000-0000-0000-0000-000000000002}

Heartbeat Discovery Cycle

{00000000-0000-0000-0000-000000000003}

Software Inventory File Collection Task

{00000000-0000-0000-0000-000000000010}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000021}

Evaluate Machine Policy Assignments

{00000000-0000-0000-0000-000000000022}

Refresh Default MP Task

{00000000-0000-0000-0000-000000000023}

Refresh Location Services Task

{00000000-0000-0000-0000-000000000024}

Location Services Cleanup Task

{00000000-0000-0000-0000-000000000025}

Software Metering Report Cycle

{00000000-0000-0000-0000-000000000031}

Source Update Manage Update Cycle

{00000000-0000-0000-0000-000000000032}

Policy Agent Cleanup Cycle

{00000000-0000-0000-0000-000000000040}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000042}

Certificate Maintenance Cycle

{00000000-0000-0000-0000-000000000051}

Peer Distribution Point Status Task

{00000000-0000-0000-0000-000000000061}

Peer Distribution Point Provisioning Status Task

{00000000-0000-0000-0000-000000000062}

Compliance Interval Enforcement

{00000000-0000-0000-0000-000000000071}

Software Updates Agent Assignment Evaluation Cycle

{00000000-0000-0000-0000-000000000108}

Send Unsent State Messages

{00000000-0000-0000-0000-000000000111}

State Message Manager Task

{00000000-0000-0000-0000-000000000112}

Force Update Scan

{00000000-0000-0000-0000-000000000113}

AMT Provision Cycle

{00000000-0000-0000-0000-000000000120}

For more information, you can refer to this link.

Monday, April 18, 2011

Un-provision Provisioned Intel vPro Machine in Enterprise Environment

How do you all un-provision provisioned machine? In lab environment, of course we can do it manually in the BIOS. How about enterprise environment? I was doing this research last week and found a tool to do it remotely. Unfortunately, this doesn’t works well. The tools prompt me an error like the picture below.

image

I confirmed that my machine is built with Vpro and it has been provisioned before. I have also tried to turn off the windows firewall and allow port 16992, but no luck.

Any other good method or workaround are most welcome. Thanks =)