Failed to add drivers to package

Recently I bumped into this problem, I manage to import all the drivers but cannot add them to the package. After searching around the internet, I found out that this is a common issue and it is due to the drivers folder share and security settings. To confirm that, I try to set the driver folder share permission to Everyone – Full Control, security permission to Everyone – Full Control. The new settings solved the problem, and hence confirm that it is due to share and security settings. Due to security issue, it is not recommended to use the settings above.

According to this forum, we should set the driver folder share permission to, “Everyone – Read”, “SMSadmin – Full Control”, “SYSTEM – Full Control”. The security settings are “Everyone – Read & Execute, List Folder contents”, “SMSadmin – Full Control”, “SYSTEM – Full Control”. I have tested this settings and it is working. Enjoy~!!!

Exiting with code 0x80004005 Windows setup failed, code 31

I got this error during Windows 7 OSD, searching around the internet and finally found the solution. This error is due to the product key I entered in my task sequence doesn’t match with the OS version. After I removed the product key and let it blank, the OSD is running smoothly.

Lesson learned, make sure that the product key is match with the OS and also make sure that it can be activated before doing the OSD. =)

Launch Virtualized Application without AppV Management Server

This would be useful to do troubleshooting on the application. Without the AppV management server, we can still launch the virtualized application with the AppV client. Here is what you need to do,

1. Copy the whole virtualized application folder that includes all the sequenced files like Icons, .sft, .sprj, .xml, and .osd to local c:\
2. Edit the .osd file with notepad.
3. Look for this code, CODEBASE HREF
4. Replace the protocol to FILE, and hostname to C:
5. For example: <CODEBASE HREF=FILE://C:/Adobe.80/Adobe.80.sft
6. Save the .osd file
7. Right click the .osd file and open it with AppV Client

Are you getting the similar error like below???

Solution:
You are required to modify a registry key to solve this error. Go to HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration and change the value "AllowIndependentFileStreaming" value to 1.

Cheers again… You can now launch the virtualized application without the use of AppV management server. =)

OSD Experience | Dual boot Win XP / Win 7 & Fedora

Like what I mentioned above, this post is all about my OSD experience from my project on dual boot OS with either Windows XP or Windows 7 and Fedora. The machines of the existing environment has three partition, and we would like to maintain the settings. The first partition is Windows OS, second partition is the data for Windows, and the third partition is for Fedora. Besides that, all the machines are the same model and same specs.Our challenge here is to maintain the existing settings, the second partition and the third partition must be maintained.

First of all, we will need to capture a reference image for both Windows XP and Windows 7. Both Windows are loaded with drivers, patches, and also installed with applications needed. My advise to you is to prepare a checklist and you prepare the reference image accordingly.

After your reference image is ready, capture the reference image with the capture media. Remember that your reference image cannot joined to the domain, and if you’re capturing Windows XP, please place the sysprep folder to C:\. Add the reference image to your SCCM server, then update it to the desired DP.

Prepare a task sequence by selecting Install an existing image package. Remove the second task (Partition Disk) in the task sequence. This step is to avoid the existing partition settings from being deleted because we need to remain the Fedora partition. Advertise the task sequence to the desired collection after you finished edit the task sequence.

After the OSD completed, your machine now suppose to has a Windows OS in the first partition, followed by data for the Windows, and last partition is the Fedora OS. Cheers~!!!

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.

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.

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.