Thursday, November 17, 2011

SCCM Capture Image Failed – WinPE Boot Failed

Today I bumped into the silly error below. Failed to boot into WinPE after the sysprep due to winload.exe file missing or corrupted. I’ve never seen this error since the first day I start to learn SCCM (scratching my head).

IMG_20111117_152833I read somewhere stated this error might due to burning process not good or file transferred is not complete. Therefore, I transfer the file to an USB drive rather than network transfer. And then tuned the burning speed to lower speed.

Guess what, it is working after that!!! No harm to give it a try as long as it is working at the end… =)

Monday, November 14, 2011

Error "0xc0190036" Whilst Upgrade To Windows Vista SP1

Today this patch has scared the shit out of me!!! I’ve deployed this patch via SCCM to the users and some of machine can’t even start the Windows after the patched. The installation stuck on a black screen after the system restarted. I found this is a common error for Windows Vista, and there are plenty of resolutions and guides. Below is the resolution:

Renaming the problem file allows the update package to replace that file during installation. To rename the problem file, follow these steps.
Important Record the file name in the error message. This is the file that will be renamed in the following steps.

  1. Insert the Windows Vista installation DVD and restart the computer from the DVD.
    Note During the startup process, when you are prompted to Press any Key to restart from the CD or DVD, press a key.
  2. Select your language settings, and then click Next.
  3. In the Setup window, click Repair your computer.
    Note If you are asked whether you want to do a system restore, click No.
  4. Select Microsoft Windows Vista to repair, and then click Next.
  5. In the System Recovery Options window, click Command Prompt.
    Note If the repair process detects problems starting Vista, it runs Startup Repair to automatically fix the problems. If this occurs, click Cancel, and then click View advanced options for system recovery and support.
  6. Type the following commands and press ENTER after each command:

    C:
    cd windows
    cd system32
    ren myfile.xxx myfile.xxx.old

    NoteMyfile.xxx represents the file name that was listed in the error message.

  7. Type Exit, and then press ENTER.
  8. In the System Recovery Options window, click Restart.

Note If you still see the black screen with a similar error and a different file name, record the file name. Repeat the steps from 1 to 7 and type the recorded problem file name in step 5. The restart might take more time than usual and may ask you to log on to the desktop.

This guide is taken from here. I read from this article that the root cause could be the hard disk file system is inconsistent or automatic defragmentation has corrupted the system file(s). The answer of the forum also mentioned it too. Bravo Vista~!!!

Thursday, November 10, 2011

Failed to send HTTP request. (Error at WinHttpSendRequest: 12007)

During my SCCM agents deployment in my new project, I got this error from a couple of dozen computers. This happened because those computers couldn’t resolve the SCCM server name. I’ve checked the DNS IP and it is configured correctly. For temporary solution, I included the SCCM server and IP in to the host list located at C:\Windows\System32\drivers\etc\hosts. After that, the SCCM agents deployed smoothly without any issue.

More troubleshooting will be done as the solution above is just temporary. Stay tuned!!!