SCCM 2012: OSD to VHDX, deploy VHDX bare metal via TS?

Hi,
I wonder what your point of view is on the following scenario:
1.Deploy ts to vhdx
2.Deploy this vhdx to pc (bare metal) via another ts, this ts would then:
-wipe the disk
-make bootpartition
-add vdisk via bcdboot
It would give a lot of flexibility in terms of deployment speed (only 1 file to deploy, not that many reboots)backup (mount vhd to recover data),adding extra os, running clients vhd on hyperv host ...
Only issue would be how to add machine specific drivers.
Please advise.
J.
Jan Hoedt

Hello,
Only issue would be how to add machine specific drivers.
The answer is to this question. And in order to deploy VHD, you can follow this blog:
SCCM 2012 R2 – Create Virtual Hard Disk (VHD)

Similar Messages

SCCM 2012 OSD Task Sequence - force Policy and SCEP update?

Hi,
How can I force a policy update to update machine policy and scep definitions at the end of
SCCM 2012 OSD Task Sequence,
Thanks,
Ward.

Hi,
I normally use this solution from Chris Nackers to deploy the latest EP definitions during OSD and deploy a custom EP policy, it works great. The policy will be downloaded when the client is registered.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 OSD task sequence condition

Is there a way to set a condition on a step that looks to see if the machine is already known to SCCM / Active Directory?
I have a step that names the PC using ITX Solutions AutoName function. I want to say only use this step if the machine is not known.

This is essentially a follow on to: http://social.technet.microsoft.com/Forums/en-US/3c6f37ad-b3dc-4219-ae7f-e6c51f05d5bf/sccm-2012-osd-retain-computer-name-on-reimage-rebuild?forum=configmanagerosd
To my knowledge, there is nothing explicitly built-in; however, you might be able to check _SMSTSMachineName to see if it matches the default WinPE naming convention of MINNIT_* or _SMSTSClientGUID to see if it has a value.
You could also put a task in before the format and partition step to check for an existing installation.
Jason | http://blog.configmgrftw.com

SCCM 2012 OSD; Not finding driver package during deployment

I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.

Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change.

SCCM 2012 OSD Retain Computer Name on re-image rebuild

I am migrating our PC workstation Windows 7 build process from MDT 2010 lite touch to SCCM 2012 zero touch. Everything is working expect
one thing.
When I re image a PC, if the PC is already known to AD I want it to keep the previous machine name, so that it retains its collection memberships
for software. If I put the PC into the collection that the OSD task sequence is advertised to, the machine successfully rebuilds with the same machine name. Starting from Windows - i.e the configuration manager client.
If I initiate the rebuild via PXE boot the machine gets a new name.
I have read that if the OS is booted from PXE or boot media then the deployment type is new computer. But if the TS is advertised to an
existing client and initiated from the config manager client, the deployment type is refresh.
I'm currently using itx-solutions.nl AutoNameControl to get RIS style naming i.e. PC-123, PC-124 etc.
When I used MDT and lite touch I used MaikKoster Deployment Webservice and obtained the machine name via the GetComputerNameByNetbootGuid
service. This worked perfectly. I don't know what exactly sets this in AD, but have noticed the PC's built with SCCM have no value for NetbootGuid so this doesn't work.
How do I always get the PC to retain the same name on rebuild?

Thank you are correct - It turns out it was the AutoNameControl. It creates a new name regardless.
I set a TS variable called ExisitngClient as the first step of my TS - but put a condition on it, to check for the existence of CcmExec.exe on the client. If it exists then I set the variable to TRUE.
Then later on when the AutoNameControl runs, I put a condition of IF ExistingCient not equals TRUE.
Meaning it only runs if it didn't have Config Manager on before the format.
It seems to work.
Thanks for the help

Helix gen.2 very slow with USB 3.0 and SCCM 2012 OSD

Hello there, i have a problem with our Helix gen.2. i would like deploy the OSD with SCCM 2012 and so i insert the USB 3.0 Dongle driver in WinPE. The Download and WIM installation is very fast but slows down after the OSD TS insert all Drivers for the system an makes a reboot. After the reboot the machine runs very slow over the network (1GB) and over 20 Hours and breaks down with a unsigned Error Message 80004005. i change the driver to an old version for the UBS 3.0 but it doesn´t helps so i need help from you. with best regards andré

What OS are you deploying on the box, 7 or 8.1?
Did you import the drivers from the Helix2 SCCM driver pack for the appropriate OS into a Driver Package?
Did you also add the USB 3.0 drivers specific to the OS being deployed into that same Driver Package?
Do you have an Apply Drivers task that references this driver package in the task sequence? If so, you should be able to find the task ID in the SMSTS.log file and verfiy it is running.

SCCM 2012 OSD - unattended XML problem?

Hi,
I am having an issue with SCCM 2012 SP1 / MDT OSD task sequence. The issue is
with the Apply Operating system step. It applies the OS reboots and boots into
the new OS. We are trying to install Windows 2008 R2.
The first dialog I see is:
"Windows could not parse or process the unattende answer file for pass [specialize].
The settings epcified in the answer file cannot be applied. The
error was detected while processing for component [Microsoft-Windows-Shell-Setup]"
Then in the black background under the dialog".
"Setup is applying system settings"
-- So I click "OK" the computer reboots..
Then I get
"The computer restarted unexpectedly or encounted an
unexpected error. Windows Installation cannot proceeed. To install
Windows, click "OK" to restart the computer, and then restart the
installation.
The in the black background see:
"Setup is preparing your computer for first use"
If I click on "OK" here it reboots and presents the same dialog again - so it gets stuck and loops
around and does not progress.
Questions
1. So from the "Apply OS step" I can see you can see you can specify a specific "unattended.xml" file.
Is there a log file I can look at that can give me more specific detail on what the exact setting it does
not like in that XML file so I can correct it?
2. If I don't specicy anything how is that XML generated and where would its log file be? I assume the same
as question 1?
3. For question 2 - where can I find the unattended XML on the target OS.
4. Since I am not in PE anymore and F8 does not work is there anyway I can bring up a command prompt?
Thanks,
Ward.

1. You'll have to check the Windows setup logs files because at this point, that's what's running.
2. There is a default XML file generated/used.
3. You will only find the file on deployed systems and I think you can traditionally find it under the panther folder.
4. Actually, you can use F8 to launch a command-prompt in the target OS during the TS as long as you enabled it in the boot image. However, as mentioned, you are in Windows setup at this point (which is actually another instance of WinPE) and so F8 doesn't
work here. Shift-F10 should though.
Jason | http://blog.configmgrftw.com

SCCM 2012 R2 - Management Point deployment to untrusted domain

Hi all,
we've got two domains in our environment which have no trust relationship. I have sccm 2012 r2 installed on a Windows 2012 R2 server in the larger domain
and have just installed a DP and MP on a Windows 2008 R2 server in the second, smaller domain. The Management Point installed ok according to mpmsi.log but the problem i'm having is that the mpcontrol.log is now repeatedly throwing up the following message:
Call to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error
On the dp/mp server in the smaller domain i can browse to http://sccm-dp1/ ok. I can also browse to http://sccm-dp1/sms_mp/.sms_aut?MPCert ok. I cannot
browse to http://sccm-dp1/sms_mp/.sms_aut?MPList (receive a HTTP 500 error).
In additon to this, every now and again the MP tries to connect to the SQL DB in the other domain. This fails with the following errors:
MPStart(): RegisterWithWINS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
CMPControlManager::PublishInDNS: DnsReplaceRecordsInSet() failed with status 9002.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): PublishInDNS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
EnableBranchCache(): configuration has not been changed.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): EnableBranchCache() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Successfully Registered for IP Address Change notifications.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): RegisterForIPAddressChangeNotification() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to register the SQL connection type for the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Registered connection type for SQL Server 'xxxxxxxxx' and database 'xxxx\xxx_xxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): RegisterSqlDatabaseConnectionType() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Checking the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Getting the CLR Enabled value from the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Impersonating using the SQL connection account; user name is now 'xxxxxxxxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to
respond.        SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more information see SQL Server Books Online.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** Failed to connect to the SQL Server, connection type: MP_CONTROL_ACCESS.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get connection to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Reverting back from using the SQL connection account.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CheckSqlDatabaseClrEnabled() returned 0x800720d9
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Waiting up to 300 seconds for the SMS Agent Host service to be running.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Stopped waiting for the SMS Agent Host service to be running; Result = 0x0.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): WaitOnSmsAgentHostRunning() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CreateThread() succeeded with id 0x2fc.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
SMS_MP_CONTROL_MANAGER successfully STARTED.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
Can anyone provide any suggestions as to where i should begin troubleshooting this issue? When i deployed the MP to the smaller domain i ensured it
had a Management Point Connection Account which could access the SQL DB in the larger domain. I'm wondering if the two error messages i'm receiving are related or whether i have two separate issues here?
Thanks for the help!

Hi Paul,
thanks for taking the time to help. I registered asp.net v4 with IIS as per your suggestion, unfortunately it hasn't made much difference and i'm still seeing the "Call
to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error"
message repeating in mpcontrol.log. Have you got any further suggestions of things
to try? Seems like an error message i really need to fix!
As far as the MP to SQL issue goes, the network team assured me the connection is allowed
but i might get them to double check this just in case.
Thanks

SCCM 2012 - Project 2010 Standard deployment failed with error 1603

Hi everyone,
I’m in the progress to roll out a software deployment via SCCM 2012, it’s to remove the current Project 2010 Professional we installed and reinstall the Standard version. We got a task sequence for the job, which is Reboot>Un-install Project 2010 Pro>Reboot>Install
Project 2010 Std.
The Un-installation process uses this command: setup.exe /uninstall PrjPro /config "PrjPro.WW\uninstall.xml"
The Installation process uses this command: setup.exe /adminfile project_silent_install.MSP
But the deployment result is quite random, some of the PCs would succeed without any issue, some of them with fail at the installation process with 1708/1603 error. As far as I know we use standard Win 7 64bits SOE across the environment, so everyone should
have same system baseline.
I reviewed some of the failed Project 2010 Standard installation logs as it shows the following:
Executing chained package: PrjStdWW
05/09/2014 20:16:14 Installing chained package: PrjStdWW
PERF: TickCount=530512 Name=Verify MSI local install source Description=Begin function
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
LIS: wait for package "{90140000-003A-0000-0000-0000000FF1CE}" to complete caching
LIS: package "{90140000-003A-0000-0000-0000000FF1CE}" caching completed
PERF: TickCount=530528 Name=Completed verify local install source Description=End function
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Use Shell UI transform : LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
Current transform is at path: LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
Using transform at path: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST
Catalyst Package Install...
Package: PrjStdWW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
Command Line: PATCH="\\SCCM2012\SMSPKGE$\PC100139\project_silent_install.MSP" ADDLOCAL=C.35347883.0E64.45B4.88A0.1881DE05E259,OSpp_Core,Project_PIA,SetupExeArpEntry,Office10Fix1,ProductFiles,InternationalSupportFiles_JPN,AceFiles,IMNFiles,OfficeIntlRDC,AceOdbc,OArt_DocTheme,OSetupController,WISPFiles,TCDRegistration,SetLanguageFiles,TCWorks7Files,ClviewFiles,VBAFiles,OfficeAppSupport,TextConverters,ProductNonBootFiles,dummy_Office_PIA,CAGOffice10,VSCommonPIAHidden,WebDiscussFiles,CAGCat10,CAGCat10Clips,MsoInstalledPackagesScoped,WxpFiles,SetupControllerFiles,Forms_PIA,dummy_MSCOMCTL_PIA,AlwaysInstalled,Gimme_OnDemandData,AceRepl,OISFiles,OfficeOLESupport,OfficeMSProof6,CAGFiles,InternationalSupportFiles_ArialUni,OSpp,Ace_PIA,GraphicsFiltersFile,WebDriveFiles,PROJECTFiles,ProductFiles_B2TR,SetupXmlFiles,OfficePostBoot,DocumentImagingUtils,VSTOCLR35,CAGCategoryFiles,ProjectCommon,VSTO,ProofingParent,MsoCommonShellHandler,OfficeDigitalSFiles,CARegistryFeature,OfficeCoreRDC,SetupExeAddRegistry,NonC2R_ProductFiles,MSSOAP3,TranslationCore,CAGOffice10Clips REMOVE=WISPHidden ARPENTRY_NOMODIFY="#0" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /modify PRJSTD /dll OSETUP.DLL" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_OEMPIDKEY="0" ARPENTRY_NOELEVATEONMODIFY="#0" SETUP_REBOOT="never" COMPANYNAME=" " ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Project.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office64.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\PRJSTD\setup.xml[~]" ARPENTRY_HELPLINK="" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\OSETUP.DLL,1" ARPENTRY_DISPLAYNAME="Microsoft Project Standard 2010" ACCEPTEDEULA="1" ARPENTRY_DISPLAYVERSION="14.0.4763.1000" BRANDING_XML="C:\Windows\TEMP\Setup00001048\BRANDING.XML" SLD_SUPPORTSBYPASS="0" SLD_ACID="5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE" SLD_TRIALTYPE="0" ARPENTRY_PACKAGEREFS="[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.es-es[~]Office64MUISet.en-us[~]PrjStdWW[~]Office64WW[~]Office64MUI.en-us[~]ProjectMUI.en-us[~]Proof.fr-fr[~]" SLD_DPID="#xF804000004000000380032003500300033002D00300030003000390038002D003000300031002D003000300030003000310030002D00300033002D0031003000330033002D0037003600300031002E0030003000300030002D0031003200390032003000310034000000000000000000000000000000000000000000000000000000000000000000350064006300370062006600360031002D0035006500630039002D0034003900390036002D0039006300630062002D00640066003800300036006100320064003000650066006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500072006F006A0065006300740053007400640056004C00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A09E4657B64703B2F32E339838F004006FE4EEC0394DE6AB2D77DCABCBC8F1C3B8B617EF54ACB52805F38EE560D0B738230977F4AB92430B37CBF02B49DB7636DCF15CE7E175CCF354E009C7A02432315800310036002D0030003800300035003100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056006F006C0075006D0065003A00470056004C004B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C0074004B004D00530000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" REMOVESAMEVERSION="" SLD_LICENSETYPE="6" SETUPEXEINSTALLUICULTURE="en-US" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" USERNAME=" " ARPENTRY_CONTACT="" ARPENTRY_HELPTELEPHONE="" ARPENTRY_PRODUCTCODES="[~]{90140000-00B4-0409-0000-0000000FF1CE}[~]{90140000-002C-0409-0000-0000000FF1CE}[~]{90140000-003A-0000-0000-0000000FF1CE}[~]{90140000-002A-0000-1000-0000000FF1CE}[~]{90140000-001F-0C0A-0000-0000000FF1CE}[~]{90140000-001F-0409-0000-0000000FF1CE}[~]{90140000-001F-040C-0000-0000000FF1CE}[~]{90140000-0115-0409-0000-0000000FF1CE}[~]{90140000-006E-0409-0000-0000000FF1CE}[~]{90140000-002A-0409-1000-0000000FF1CE}[~]{90140000-0116-0409-1000-0000000FF1CE}[~]" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SETUPEXE_DOARPWRITE="1" ACIDS="11B39439-6B93-4642-9570-F2EB81BE2238;5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE;B6E9FAE1-1A0E-4C61-99D0-4AF068915378" ARPENTRY_SPPSKUID="[~]5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE[~]" ARPENTRY_NOREMOVE="#0" SLD_PKU="0" SLD_PID="82503-001-0000106-49615" LICTYPE="ltKMS" ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /uninstall PRJSTD /dll OSETUP.DLL" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_URLINFOABOUT="" REMOVEPREVIOUS="" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\" ARPSYSTEMCOMPONENT=1 TRANSFORMS="C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST" ALLUSERS="1"
PERF: TickCount=530543 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Error: Failed to install product: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi ErrorCode: 1603(0x643).
Log level changed from: Standard to: Verbose
Rolling back chain
05/09/2014 20:18:47 Rolling back package: PrjStdWW
There appears to be no rollback work to do for package: PrjStdWW path: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
05/09/2014 20:18:47 Rolling back package: Office64WW
Package Office64WW was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64WW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\Office64WW.msi
Command Line: ADDLOCAL=AcePiaReg64,VSTO64,WordXmlEditVerb64,ExcelXmlEditVerb64,GrooveShellIntegration64,Project64Files,OSpp64_Core,ExcelPiaReg64,GraphPiaReg64,FormsPiaReg64,SmartTagPiaReg64,PPTXmlEditVerb64,MsoInstalledPackagesScoped,OfficeExample64bitFilesA,WAC_XmlEditVerb64SPD,SetupXmlFiles,WordPiaReg64,Outlook64Files,AlwaysInstalled64,VBEPiaReg64,VisioPiaReg64,Outlook64SearchShellReg,OneNote64Files,SetupControllerFiles,ProjectPiaReg64,SearchFilters64Files,OutlookPiaReg64,Gimme_OnDemandData,Visio64ShapeSearch,WAC_PIARegSPD64,ProductNonBootFiles64,XDocsPiaReg64,PublisherPiaReg64,OneNotePIAReg64,ProductFiles64,OfficeExample64bitFilesB,OfficePiaReg64,Visio64Files,TCDRegistration64,OSpp64,XDOCSFiles64,XDocsXmlEditVerb64,MsoCommonShellHandler64bit,AccessPiaReg64,PowerPointPiaReg64 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64WW ProductCode:{90140000-002A-0000-1000-0000000FF1CE}
05/09/2014 20:18:56 Rolling back package: ProjectMUI.en-us
Package ProjectMUI.en-us was installed in the chain... uninstalling as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Install Rollback (uninstall)...
Package: ProjectMUI.en-us
Product Code: {90140000-00B4-0409-0000-0000000FF1CE}
Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back install of package: ProjectMUI.en-us path:C:\MSOCache\All Users\{90140000-00B4-0409-0000-0000000FF1CE}-C\ProjectMUI.msi
05/09/2014 20:19:00 Rolling back package: Proofing.en-us
Package Proofing.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proofing.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proofing.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proofing.en-us ProductCode:{90140000-002C-0409-0000-0000000FF1CE}
05/09/2014 20:19:04 Rolling back package: Proof.en-us
Package Proof.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.en\Proof.msi
Command Line: ADDLOCAL=FindAllWordFormsFiles_1033,Gimme_OnDemandData,SpellingAndGrammarFiles_1033,ThesaurusFiles_1033,MsoInstalledPackagesScopedIntl_1033,HyphenationFiles_1033,OCR_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.en-us ProductCode:{90140000-001F-0409-0000-0000000FF1CE}
05/09/2014 20:19:05 Rolling back package: Proof.fr-fr
Package Proof.fr-fr was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.fr-fr
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.fr\Proof.msi
Command Line: ADDLOCAL=MsoInstalledPackagesScopedIntl_1036,Gimme_OnDemandData,SpellingAndGrammarFiles_1036,SetupControllerFiles,FindAllWordFormsFiles_1036,TranslationFiles_1036,ThesaurusFiles_1036,HyphenationFiles_1036,SetupXmlFiles,OCR_1036 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.fr-fr ProductCode:{90140000-001F-040C-0000-0000000FF1CE}
05/09/2014 20:19:11 Rolling back package: Proof.es-es
Package Proof.es-es was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.es-es
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.es\Proof.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SpellingAndGrammarFiles_3082,OCR_3082,FindAllWordFormsFiles_3082,HyphenationFiles_3082,ThesaurusFiles_3082,MsoInstalledPackagesScopedIntl_3082,SetupControllerFiles,SetupXmlFiles,TranslationFiles_3082 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.es-es ProductCode:{90140000-001F-0C0A-0000-0000000FF1CE}
05/09/2014 20:19:12 Rolling back package: Office64MUISet.en-us
Package Office64MUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUISet.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUISet.en-us ProductCode:{90140000-0116-0409-1000-0000000FF1CE}
05/09/2014 20:19:19 Rolling back package: Office64MUI.en-us
Package Office64MUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUI.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi
Command Line: ADDLOCAL=OfficeExample64bitFilesBIntl_1033,OfficeExample64bitFilesAIntl_1033,Gimme_OnDemandData,Outlook64SearchShellRegIntl_1033,ProductFilesIntl64_1033,MsoInstalledPackagesScopedIntl_1033,OneNoteToLinkedNotesIEAddin64Intl_1033,GrooveFiles64Intl_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUI.en-us ProductCode:{90140000-002A-0409-1000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUISet.en-us
Package OfficeMUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUISet.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUISet.en-us ProductCode:{90140000-0115-0409-0000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUI.en-us
Package OfficeMUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUI.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi
Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,WebDiscussFilesIntl_1033,GraphicsFiltersPNGFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,MSTagPluginNamesFilesIntl_1033,TCWP5FilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,WxpFilesIntl_1033,XDOCSEditorFilesIntl_1033,CAGFilesIntl_1033,WISPHiddenIntl_1033,CAGCat10Intl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,MsoInstalledPackagesScopedIntl_1033,TCRecoverFilesIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,GraphHelpFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,VisioPreviewerIntl_1033,ProductFilesIntl_1033,AceReplIntl_1033,GraphicsFiltersCGMFilesIntl_1033,GraphicsFiltersWPGFilesIntl_1033,Gimme_OnDemandData,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LOBiFilesIntl_1033,LISTFilesIntl_1033,UICaptionsCompanionIntl_1033,SetupXmlFiles,AceFilesIntl_1033,TOOLSFilesIntl_1033,MSSOAP3Intl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUI.en-us ProductCode:{90140000-006E-0409-0000-0000000FF1CE}
Error attaching to OSE, error 0x00000000
Stopping running ose
LIS: start uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
Error attaching to OSE, error 0x00000000
Stopping running ose
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
Not showing completion dialog because it was not requested.
Catalyst execution finished: 05/09/2014 20:19:25. Return code: 1603.
PERF: TickCount=722128 Name=RunSetup Description=End function
Can onyone enlighten me what's went wrong, and why did I get this inconsitent installation behaviour?
Thank you very much!!!

1603 means there is a fatal error during installation process.
Take a look at the article below. It may help on finding cause.
Hi Juke,
I did do fair a bit of Googling before I started the post. I have increased the logging level on one of the machines failed on the installation. Apparently Project installation log doesn't throw the "return value 3", I think it's pointing to a particular
updating item, anyone knows what is it?
Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed.
The following is the detailed installation log.
MSI (s) (8C:B4) [20:31:33:122]: Executing op: SetTargetFolder()
MSI (s) (8C:B4) [20:31:33:122]: Executing op: FontRegister(Title=Arial Unicode MS (TrueType),File=ARIALUNI.TTF)
MSI (s) (8C:B4) [20:31:33:122]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (8C:B4) [20:31:33:122]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (8C:B4) [20:31:33:122]: Error in rollback skipped. Return: 5
MSI (s) (8C:B4) [20:31:33:746]: Entering MsiProvideAssembly. AssemblyName: Policy.12.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:746]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:777]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:777]: Entering MsiProvideAssembly. AssemblyName: Policy.11.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:777]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:808]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:808]: Entering MsiProvideAssembly. AssemblyName: Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:808]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:840]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:840]: Note: 1: 2318 2:
MSI (s) (8C:B4) [20:31:33:840]: No System Restore sequence number for this installation.
MSI (s) (8C:B4) [20:31:33:840]: Unlocking Server
MSI (s) (8C:B4) [20:31:33:980]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\TEMP\MSI1f79e.LOG.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed an update. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: {35347883-0E64-45B4-88A0-1881DE05E259}. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Note: 1: 1708
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 -- Installation operation failed.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed the product. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Deferring clean up of packages/files, if any exist
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: MainEngineThread is returning 1603
MSI (s) (8C:24) [20:31:34:011]: No System Restore sequence number for this installation.
MSI (s) (8C:24) [20:31:34:011]: User policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (8C:24) [20:31:34:027]: Restoring environment variables
MSI (s) (8C:24) [20:31:34:027]: Destroying RemoteAPI object.
MSI (s) (8C:48) [20:31:34:027]: Custom Action Manager thread ending.
MSI (c) (F4:1C) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:1C) [20:31:34:027]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/05/2014 20:31:34 ===

SCCM 2012 OSD Task Sequence Fails "An error occurred while retrieving policy for this computer"

We have SCCM 2012 R2. I amm trying to start OSD task sequence from bootable media.
Hyper-v client gets DHCP ip and starts MDT bootable media, but could not find policy.
From F8 I can ping SCCM/DP/MP server.
What could be the cause?

Yes, this DHCP client is in the same subnet as other working clients.
smsts.log from client
Request was successful. TSPxe
21.03.2014 14:14:14 324 (0x0144)
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1970)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
reply has no message header marker TSPxe
21.03.2014 14:14:14 324 (0x0144)
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Failed to get client identity (80004005)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1113)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
failed to request for client
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Exiting TSMediaWizardControl::GetPolicy. TSPxe
21.03.2014 14:14:14 324 (0x0144)

SCCM 2012 OSD/MDT TS: Can I set the ComputerBackupLocation to d: (local) durin wim capture

Hi,
SCCM 2012 SP1 OSD w MDT 2012 /MDT TS:
Can I set the ComputerBackupLocation to d: (local drive) durin OS wim capture?
/SaiTech

Hi,
Please see if the article below helps:
Understanding How MDT 2010 Automatically Determines a Backup
http://www.migee.com/2011/03/10/understanding-how-mdt-2010-automatically-determines-a-backup-location/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 OSD PXE, OS System disk is D:/ !

HI !
SCCM 2012 st.OSD PXE, OS System disk is D:/ !
Deploing OS, resulting
in system drive
is D:/. How to achieve this
would be C :/?
cenubit

Ok.
What are the steps and conditions
are followed
to establish a
new Reference Image ?
cenubit

Create a prompt using MDT 2012 in SCCM 2012 OSD task sequence

Hi Experts,
I need some help with SCCM 2012 Task sequence using MDT 2012.
Here is the scenario:I want to build a task sequence where it will propmt whether the technican want to build a new build or refresh. Based on the technicians choice the task sequence will perform specific actions.
We can create the prompt using HTA or VBScript or some otherways.
But the requiremnt for us is to Use ONLY MDT 2012, not any other ways.
Is it possible to do like the above with UDI?
Please can someone shed some light how to do will be great.
Thanks in advance,

Hi,
UDI may achieve what you want. Take a look at the blogs below.
http://blogs.technet.com/b/anilm/archive/2012/06/01/integrating-mdt-2012-rtm-with-configuration-manager-2012-rtm-part-3-creating-and-deploying-a-udi-task-sequence.aspx
http://heinrichandsccm.blogspot.com/2013/04/how-to-setup-and-configure-sccm-2012.html
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Juke Chou
TechNet Community Support

SCCM 2012 - OSD - HAL.dll error (windows XP) using USB

Hi
SCCM 2012
I'm creating OSD for Windows XP and create .iso files
1. I create ISO files
2. make the USB bootable
3. Copy the ISO files in content in USB
4. Boot from USB, when it finish I;m getting the HAL.dll error
Please advise
Robert

The hal.dll is missing?
http://support.microsoft.com/kb/314477/en-gb
Juke Chou
TechNet Community Support

SCCM 2012 OSD and WinPE-StorageWMI?

Hi,
I am using SCCM 2012 SP1 OSD with MDT 2012. I am trying to work out how to use the command from the
WinPE-StorageWMI.
I have added them to my boot wim and am trying to invoke them from powershell from the F8 prompt first
then once I get them going in there put them in my task sequence.
However when I do not see them?
Am I not seeing any extra modules is there something basic I am missing? Am I meant to see a module
called WinPE-StorageWMI?
Thanks,
Ward.

The module is a part of Powershell. You need to enable WinPE-PowerShell.
http://technet.microsoft.com/en-us/library/hh824926.aspx
Juke Chou
TechNet Community Support

SCCM 2012: OSD to VHDX, deploy VHDX bare metal via TS?

Similar Messages

Maybe you are looking for