Installing Visual Studio runtimes on Build and Captures

Greetings,
I was just wondering how many of you out there install all Visual Studio runtimes in your base OS builds as part of you build and capture process. This would be the following four:
VC2005, VC2008, VC2010, VC2012 Update 4.
I'm thinking that there are so many apps these days that tend to use one or other of these versions that you might as well include them all. Is there a downside to doing this (apart from the increased OS build file size?).
Thanks
David Z

Yes. The Microsoft Visual C++ Runtime redistributable package install runtime components of Visual C++ Libraries required to run applications developed with Visual C++. They are not related to Windows.
If you deploy a x86 application on Windows 7 x64, it will require the x86 of Visual C++ Runtime.
If you deploy a x64 application on Windows 7 x64, it will require the x64 of Visual C++ Runtime.
A x86 application cannot use a x64 runtime. So yes you may need them in your image
/ Yannick Plavonil
blog: Deploiement Windows
twitter: @yplavonil
facebook:
www.facebook.com/deploiementwindows

Similar Messages

Trying to install visual studio on my mac and it is freezing during the install and I have to reboot, I have run out of ideas as to why it will not install. amy help with this would be greatly appreciated

Trying to install visual studio on my mac and it is freezing during the install and I have to reboot, I have run out of ideas as to why it will not install. amy help with this would be greatly appreciated

maybe something is wrong with your install or your computers hardware as in a periodic defect
or the cd is dodgy
installed
vs express 2013 for desktop
vs express 2013 for windows (metro)
vs express for windows phone
on my windows 8.1 think I installed them when I was still using win8 though
without problems
when the same bootcamp partition was windows 7 ultimate 64bit
I was running
vs 2010 pro
and vs 2008 (for winCE)
without problems

Install Updates step fails in Build and Capture (error code 87D00272)

Hello,
I was really hoping someone could help me with this.
Background information:
- We have a CM07 server in a production environment.
- I've set up a CM12 RTM server, following the guides in this forum, with the hopes of migrating soon.
- I wanted to do OSD from scratch to learn more and to take advantage of new features in CM12.
- I have a few virtual machines running for testing OSD/apps (these are the only clients managed by my CM12 server).
- Since it's not possible to have two WDS servers running at the same time AFAIK (without using registry tweaks, the F11 trick, that by the
way doesn't work for me) I have created a bootable TS media that I mount on the virtual machines whenever I want to test OSD.
Now, to my problem:
I can't figure out why my Build and Capture TS is failing on the Install Software Updates step. smsts.log file says: Failed
to RefreshUpdates, hr=087d00272, followed by: Failed to run the action: Install Software Updates. Component is disabled (Error: 87D00272; Source: CCM).
I have read about similar issues occurring in CM07 capture task sequences since the machine is joined to a Workgroup. The proposed solution was adding SMSSLP=FQDN to the client installation properties, but since that functionality is moved to the MP in CM12,
it should be enough to specify SMSMP=FQDN in my case. It's not working anyway. Tried it to a Deploy TS also, where the machine is domain joined, but I got the same error.
The error code 87D00272 returns no results on Google. This stumps me, as someone surely has had the same problem? Here are the relevant portions
of the smsts.log file
If someone had the chance to look at this, I would greatly appreciate it. Thank you!
Refreshing Updates InstallSWUpdate 2012-06-13 10:15:33 228 (0x00E4)
spInstall->RefreshTargetedUpdates( spCallback, &bAlreadyCompleted ),
HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
\installswupdate.cpp,467) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
Failed to RefreshUpdates, hr=0x87d00272 InstallSWUpdate 2012-06-13 10:15:34 228
(0x00E4)
RefreshTargetedUpdates(spInstall, spCallback, bAlreadyCompleted), HRESULT=87d00272
(e:\nts_sccm_release\sms\client\osdeployment\installswupdate
\installswupdate.cpp,1295) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
RefreshUpdates(), HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment
\installswupdate\installswupdate.cpp,906) InstallSWUpdate 2012-06-13 10:15:34
228 (0x00E4)
InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle),
HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
\main.cpp,248) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 2012-06-13
10:15:34 228 (0x00E4)
Process(pInstallUpdate, tType), HRESULT=87d00272 (e:\nts_sccm_release\sms\client
\osdeployment\installswupdate\main.cpp,304) InstallSWUpdate 2012-06-13 10:15:34
228 (0x00E4)
Process completed with exit code 2278556274 TSManager 2012-06-13 10:15:34
912 (0x0390)
---------! TSManager 2012-06-13 10:15:34 912 (0x0390)
Failed to run the action: Install Software Updates.
Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
10:15:34 912 (0x0390)
MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
2012-06-13 10:15:34 912 (0x0390)
Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
/ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
Set a global environment variable _SMSTSLastActionRetCode=-2016411022 TSManager
2012-06-13 10:15:35 912 (0x0390)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager
2012-06-13 10:15:35 912 (0x0390)
Clear local default environment TSManager 2012-06-13 10:15:35 912 (0x0390)
Let the parent group (Setup Operating System) decides whether to continue execution
TSManager 2012-06-13 10:15:35 912 (0x0390)
The execution of the group (Setup Operating System) has failed and the execution has
been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 2012-06-13
10:15:35 912 (0x0390)
Failed to run the last action: Install Software Updates. Execution of task sequence
failed.
Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
10:15:35 912 (0x0390)
MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
2012-06-13 10:15:35 912 (0x0390)
Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
/ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
Launching command shell. OSDSetupHook 2012-06-13 10:15:45 1932
(0x078C)
executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
10:15:45 1932 (0x078C)
executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
10:15:45 1932 (0x078C)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:
\nts_sccm_release\sms\client    asksequence    smanager    smanager.cpp,756) TSManager
2012-06-13 10:16:57 912 (0x0390)
Task Sequence Engine failed! Code: enExecutionFail TSManager 2012-06-13
10:16:57 912 (0x0390)
TSManager 2012-06-13 10:16:57 912 (0x0390)
Task sequence execution failed with error code 80004005 TSManager 2012-06-13
10:16:57 912 (0x0390)

I can add that I've looked at the Site Status in the Monitoring tab, and everything looks green apart from some Warnings about User and System Discovery. In Component Status, I have a warning about the Distribution Point on C$. I thought placing a NO_SMS_ON_DRIVE.SMS
file in the root of C: would mean no stuff was placed there? I can't see anything SCCM related, but it seems that it has placed a DP on C:?
The error message about DP is:
Distribution Manager has not tried to install IIS component of operating system to distribution point "["Display=\\CFGMGR-SRV.zenit.brummer.se\"]MSWNET:["SMS_SITE=PS1"]\\CFGMGR-SRV.zenit.brummer.se\". You should install and configure IIS manually. Please
ensure RDC is also enabled.

Known Issue: How to Install Visual Studio Tools for Universal Windows App Development (Windows 10 Insider Preview SDK and tools, April 2015 release)

The Visual Studio Tools for Universal Windows App Development are not installed by default. If they are not installed, in the New Project dialog in Visual Studio 2015, you will see only a template “Download Windows Universal Tools”.
For additional known issues with using Visual Studio 2015 RC, see
https://support.microsoft.com/kb/3025133/

Additional Installation Known issues:
Visual Studio Tools for Universal Windows Apps Requires Windows 10 Build 10074 or later
https://social.msdn.microsoft.com/Forums/en-US/de06c7c0-4248-4d68-bfcb-4b9a23fae1c0
You cannot install the Visual Studio Tools for Universal Windows Apps on a pre-RC build of Visual Studio 2015
https://social.msdn.microsoft.com/Forums/en-US/25d0b000-3ebb-4032-a786-99caf0390e9b
Emulators for Windows Mobile 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294
https://social.msdn.microsoft.com/Forums/en-US/17bc9d5e-2ea7-4149-bb75-23997db8bd25/
Setup warnings for Windows 10 SDK, Emulators for Windows Mobile, and Tools for Windows 10 Universal Apps
https://social.msdn.microsoft.com/Forums/en-US/bfc4fcc0-cb48-4bb0-aab3-5797e31b08e0
Fatal error when installing the Windows emulators: 2147023293
https://social.msdn.microsoft.com/Forums/en-US/5485554c-e7e8-414e-a542-d1f7c0b6291c
Do not install Visual Studio Express 2015 for Windows 10 on a Machine with Visual Studio Community, Professional, or Enterprise
https://social.msdn.microsoft.com/Forums/en-US/94a29b17-baaf-4318-98ff-1cfc90a54bad/
How to enable your Windows 10 device for development
https://social.msdn.microsoft.com/Forums/en-US/6e34c9f0-5e3a-4b44-9aae-586ba94f8a28/

Install Updates task not working during Build and Capture in SCCM 2012

Working with a new SCCM 2012 installation.
We are trying to get a Build and Capture TS to install all updates for Win7SP1.
All packages are deployed to DP, build and cap machine is in a collection with all updates deployed to it. Agent installation parameters include "SMSMP" "SMSSLP" parameters. Machine is not being attached to the domain during OS install.
Updates can be pushed to existing domain machines, so obviously the updates themselves are working.
The task sequence works correctly to install the image, but "Install Updates" task just sits there and eventually times out. (No indication of updates being installed.) If this task is working, shouldn't I see a Downloading Updates progress bar, or was that
eliminated from 2012?

Same issue for me except I'm running 2012 R2 my B&C runs forever on Install Software Updates, eventually just rebooting and coming back to the login screen of Windows 7 without ever finishing the Install Updates.
Been working on it litteraly for weeks.
1- Tried adding .Net 4.52 as an application installation thinking maybe it would resolve the issue
2- Tried installing via Run Command Line + DISM all hotfixes that require 2 reboots as per (https://support.microsoft.com/en-us/kb/2894518)
3- Tried to simply REMOVE the same hotfixes from my Software Update Groups alltogether.
4- Injected all applicable software updates through Offline Servicing in the SCCM Console (Schedule Updates) on the Windows 7 DVD wim file. That way my logic was that once it would hit the Software Updates, there would be a lot less to install.
I'm at the point where I had to open a case with Microsoft Premier Support as of yesterday. So, nothing new to report yet. But yes, this is a true pain in the ***.
For the sake of comparison, I am running 4 Update Groups: one containing patches up to 2012. Another one for 2013, 2014 and 2015. I have patches for Windows 7 + Office of all categories except Service Packs.
If someone has any ideas, feel free to chime in.

Build and Capture - waiting to install

I am using SCCM 2012 RTM and have started seeing an issue with our Build and Capture Task Sequence. When performing a build and capture the system will not install anything for a day or so and anything that is advertised to it gets stuck in a "Waiting
to Install..." status in the Software Center UI.
When looking at the execmgr log for the client I see the following items that stick out to me:
<![LOG[On policy activation ignore disabled policy Configuration Manager Client Upgrade Program]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="2" thread="3956"
file="execreqmgr.cpp:7489">
<![LOG[Mandatory execution requested for program Configuration Manager Client Upgrade Program and advertisement CM120000]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="1"
thread="2512" file="execreqmgr.cpp:3533">
<![LOG[Creating mandatory request for advert CM120000, program Configuration Manager Client Upgrade Program, package CM100003]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="2512" file="execreqmgr.cpp:3658">
<![LOG[Program Configuration Manager Client Upgrade Program change to state WAITING_ENABLED]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512"
file="executionrequest.cpp:4618">
<![LOG[Execution Request for advert CM120000 package CM100003 program Configuration Manager Client Upgrade Program state change from NotExist to WaitingDisabled]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr"
context="" type="1" thread="2512" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM100003",ProgramID="Configuration Manager Client Upgrade Program", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:53:36.979+300"
date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="event.cpp:410">
<![LOG[Policy arrived for child program insNCR-MPOSUIControls-1.0]LOG]!><time="10:57:50.240+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:50.287+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="3956" file="event.cpp:410">
<![LOG[Mandatory execution requested for program * and advertisement CM120006]LOG]!><time="10:57:50.865+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:3533">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.037+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="3996" file="event.cpp:410">
<![LOG[Creating mandatory request for advert CM120006, program *, package CM10001F]LOG]!><time="10:57:51.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956"
file="execreqmgr.cpp:3658">
<![LOG[Policy arrived for child program insRCS-FLIB_2_PlatformRuntime-5.5.5007]LOG]!><time="10:57:51.084+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
<![LOG[The created request is a Task Sequence request]LOG]!><time="10:57:51.115+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:1065">
<![LOG[Execution Request for advert CM120006 package CM10001F program * state change from NotExist to WaitingDependency]LOG]!><time="10:57:51.678+300" date="01-23-2013" component="execmgr" context="" type="1"
thread="3956" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.678+300"
date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
<![LOG[An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task.]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr"
context="" type="1" thread="3956" file="executionrequest.cpp:8829">
<![LOG[Request a MTC task for execution request of package CM10001F, program * with request id: {7BCB5674-DC91-49D8-9C52-0765E9D86984}]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="3956" file="executionrequest.cpp:8848">
<![LOG[Execution Request for advert CM120006 package CM10001F program * state change from WaitingDependency to Ready]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1"
thread="3956" file="executionrequest.cpp:503">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.443+300"
date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
<![LOG[MTC task with id {7BCB5674-DC91-49D8-9C52-0765E9D86984}, changed state from 0 to 1]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2932"
file="execreqmgr.cpp:6268">
<![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.959+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="3996" file="event.cpp:410">
<![LOG[Policy arrived for child program insRCS-Software_Retrieval_Agent_TAB-5.4.1]LOG]!><time="10:57:53.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996"
file="execreqmgr.cpp:6847">
<![LOG[MTC queeued a task for SWD execution request with program id: *, package id: CM10001F for execution.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context="" type="1"
thread="2932" file="execreqmgr.cpp:6481">
<![LOG[Package CM10001F, program * is ready but can not be started because package , program is currently running.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context=""
type="1" thread="2932" file="executionrequest.cpp:9083">
When I use the same Task Sequence (or any other deployment) on a system built from our old .WIM created with the same Build and Capture Task Sequence they always install immediately. I am thinking it has something to do with the default SCCM Client
upgrade package available by default, but I had our SCCM owner verify that has been disabled in the hierarchy.
The deployments are set to ignore maintenance windows and things of that nature. It appears to be an issue with the agents state when it comes up out of the build process. It checks in with the Site and processes assignments for Compliance (DCM)
without issues as well. The build and capture new WIM/System builds just seem to not want to install anything.
What makes this issue even more odd is that if I leave the system on for several days sitting at the "Waiting to Install..." state, the agent finally works out whatever issue it is stuck on and begins to work without issues. If I don't use
the WIM for several days after it was created, the WIM will also stop experiencing the issue too.
Has anyone else run into this too? This was working a couple months back and I went to create a new WIM in December and it hasn't work correctly since.
Thanks..Jon
Jon Kaloz

I have identified the source of the problem, but no solution yet. The blocking program is found under SMS_MaintenanceTaskRequests in the local client WMI Namespace Root\CCM\SMS_MaintenanceTaskRequests. The GUID that is found in there has
a matching TaskID to a TaskID found in the SMSTS from the Build and Capture Task Sequence logs.
This is found in the SMSTSLog from the Build and Capture process showing the same Task GUID referenced (followed by a failure I cannot find good info on). C:\SMSTSLog\SMSTS.log
<![LOG[Set command line: "C:\_SMSTaskSequence\OSD\CM100035\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\CM100035 /config:MobileClient.TCF /status:644]LOG]!><time="14:21:37.225+300" date="01-24-2013" component="OSDSetupHook"
context="" type="0" thread="2132" file="commandline.cpp:705">
<![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\CM100035\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\CM100035 /config:MobileClient.TCF /status:644]LOG]!><time="14:21:37.225+300" date="01-24-2013"
component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:801">
<![LOG[Process completed with exit code 0]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:1098">
<![LOG[Install succeeded. Blocking other instances of ccmsetup.]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1215">
<![LOG[Installed Client]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1273">
<![LOG[Start to cleanup TS policy]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2773">
<![LOG[TS Deleted 0 instances]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2816">
<![LOG[TS Policy cleanup done]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2817">
<![LOG[End TS policy cleanup]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2821">
<![LOG[Setting variable to indicate a client installation was done]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1284">
<![LOG[Registering the task sequence with the execution manager in the newly installed operating system.]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook" context="" type="0"
thread="2132" file="installclient.cpp:915">
<![LOG[Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE.]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook"
context="" type="2" thread="2132" file="installclient.cpp:918">
<![LOG[Saving the new active request handle for the task sequence: {01DE9356-CDBD-4051-B465-F87886A61BF5}]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook" context="" type="1"
thread="2132" file="installclient.cpp:931">
<![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG]!><time="14:23:30.662+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132"
file="installclient.cpp:949">
<![LOG[Waiting for ccmexec process to start]LOG]!><time="14:23:30.662+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:950">
<![LOG[CoCreateInstance succeeded]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:961">
<![LOG[Succesfully registered the tasksequence with the execution manager]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="installclient.cpp:994">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="commandline.cpp:228">
<![LOG[Set command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132"
file="commandline.cpp:705">
<![LOG[Executing command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="1"
thread="2132" file="commandline.cpp:801">
<![LOG[==========[ TsProgressUI started in process 3912 ]==========]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:329">
<![LOG[Unregistering COM classes]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:204">
<![LOG[Shutdown complete.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:1098">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="utils.cpp:2075">
<![LOG[Moving logs to SMS client directory]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="basesetuphook.cpp:1356">
<![LOG[LOGGING: Resetting log path.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="tslogging.cpp:1803">
These are the contents of the maintenancecoordinator.log showing the Task with the same GUID starting, but never registering a completion. After 12 hours (43200 second timeout) it will finally continue on and work as it should.
<![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:23:46.662+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="536" file="taskqueue.cpp:727">
<![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:23:55.912+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="4084" file="taskqueue.cpp:727">
<![LOG[Adding task for client "tasksequence": id - "{01DE9356-CDBD-4051-B465-F87886A61BF5}", pri - 0, service window - 0, max time for sw - 43200.]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator"
context="" type="1" thread="2556" file="taskqueue.cpp:259">
<![LOG[Signaled task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence').]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="2556"
file="taskqueue.cpp:1344">
<![LOG[Done scheduling task. Winning task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence')]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1"
thread="2556" file="taskqueue.cpp:1261">
<![LOG[Task "{01DE9356-CDBD-4051-B465-F87886A61BF5}" (agent 'tasksequence') is reporting back on starting.]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context=""
type="1" thread="2556" file="taskqueue.cpp:399">
<![LOG[Successfully started task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence').]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1"
thread="2556" file="taskqueue.cpp:1517">
<![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:27:36.544+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="2464" file="taskqueue.cpp:727">
<![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:53:27.219+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="3820" file="taskqueue.cpp:727">
I am not sure why the task is still hanging around on the system after the build and capture sequence completes. There are no errors during the B&C TS and I have removed everything from it as well to only be an OS install with no changes.
Jon Kaloz

Client with Patch fails to install - Build and Capture

Hi,
We recently hit an issue where our Build and Capture task sequence, previously fully working, was deleted. As such I've had to rebuild it from documentation. So far so good. However when I now test it out, the sequence fails during the installation of the client.
It appears to be due to access to the patch, however I can't work out why. The installation flags are:
/mp:sccmpri01.domain.com CCMLOGMAXHISTORY=4 PATCH=\\SCCMPRI01.domain.com\HotFixes\KB2938441\Client\i386\configmgr2012ac-r2-kb2938441-i386.msp
And the share is set for the network access account to have read/write/execute, and everyone to have read access. As it's a build and capture the machine is in a workgroup not the domain.
The error I'm getting is most detailed in the ccmsetup folder under the client.msi.log
MSI (s) (EC:4C) [15:51:37:441]: Unable to create a temp copy of patch '\\SCCMPRI01.DOMAIN.COM\HOTFIXES\KB2938441\CLIENT\I386\CONFIGMGR2012AC-R2-KB2938441-I386.MSP'.
MSI (s) (EC:4C) [15:51:37:441]: Note: 1: 1708
MSI (s) (EC:4C) [15:51:37:441]: Product: Configuration Manager Client -- Installation failed.
MSI (s) (EC:4C) [15:51:37:441]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1635.
I'm a little lost as to what to try next. If I install without the patch it's alright but then fails as soon as it hits the next step in the sequence.
Any help would be great!

You can use a UNC path in the PATCH command (but I would not recommend it) but i expect that the process above evidently does not have share or file permissions to the msp file.
The way I do it is simply to copy the 32 and 64 bit msp's into the folder that is created by default:
\\Server\SMS_sitecode\Client
That way, all you need to do is update your client package, and then change the command line so that it references the local msp file instead of UNC path.

Install Software Updates in a WIndows 7 build and capture shooses wrong SUP

Hi,
My environment is the following.
One SCCM 2012 R2 Primary site server in a trusted domain, MP, DP and SUP. This site is reachable from the clients on the internal network.
One SCCM 2012 R2 server in an untrusted forest, MP, DP and SUP. This server is NOT reachable from clients on the internal nrowotk.
I am doing a build and capture of Windows 7 using a SCCM TS on a VM on the internal network.
When the Install Updates task Is running the SCCM client is trying to use the SUP in the untrusted forest instead of the one in the local trusted forest.
How do I force the SCCM client to use the local SUP instead of the one in the untrusted forest.
According to
http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx it should prioritize the one in the local forest, but the build and capture PC is not member of the AD so it looks like it just uses the SUP that is
first in the list from the MP.
The blog also states that the SUP will not be shifted to the next one in the list before 4 failed scans at 30 minutes intervals so it will take more than 4 hours before the SCCM client will try the next SUP. At that time the TS has long finished the
Software Update task.
I thought about creating an entry in the hosts file on the capture PC with the name of the untrusted SUP and the IP of the trusted SUP to redirect the client to use the trusted SUP. I solution that might work but that I find very ugly.
What can I do to force the SCCM client on the build and capture PC to us the internal trusted SUP?
Thomas Forsmark Soerensen

The SUP info cannot be got from the Internal MP. Please review the Smsts.log file.
Juke Chou
TechNet Community Support

Workgroup Installing Client Fails (Build and Capture) - Windows 7 x64

Hi, I'm trying to configure a Build and Capture TS for Windows 7 x64 but the client always fails to find my site during installation, which means I can't install updates and applications. I'm running SCCM 2012 SP1 and the ConfigMgr2012-SP1-KB2801987-X64-ENU
hotfix has already been installed.
I'm using the SMSMP=XX.XX (and SMSSITECODE=XXX) options but the log always says "No MPs were specified from commandline..."
I've done a huge amount of searching and it seems like it should be possible to end up with a client installed on a workgroup computer with the correct side code (and displaying "Currently Internet"), which should allow updates to be installed
during the TS, but I can't get it to work! Any help would be greatly appreciated.
Here's part of my ccmsetup.log file :
==========[ ccmsetup started in process 2332 ]========== ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Running on platform X64 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Launch from folder D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CcmSetup version: 5.0.7804.1500 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Running on OS (6.1.7600). Service Pack (0.0). SuiteMask = 256. Product Type = 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Ccmsetup command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Copying config file from D:\_SMSTaskSequence\OSD\XXX00034\MobileClient.TCF to folder D:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
SslState value: 224 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CCMHTTPPORT: 80 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CCMHTTPSPORT: 443 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CCMHTTPSSTATE: 0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CCMHTTPSCERTNAME: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
FSP: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
CCMFIRSTCERT: 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Config file: D:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Retry time: 10 minute(s) ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
MSI log file: D:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="XXX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
Source List: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
MPs: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
None ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
No version of the client is currently detected. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
Updated security on object D:\WINDOWS\ccmsetup\. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
Downloading file D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe to D:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 17% complete (262144 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 35% complete (524288 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 53% complete (786432 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 71% complete (1048576 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 89% complete (1310720 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
File download 100% complete (1457840 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.cab to D:\WINDOWS\ccmsetup\ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
File download 100% complete (9613 of 9613 bytes). ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Download complete. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)

Thanks for the reply. You're right, I'm setting the SMSMP and SMSSITECODE in the command line of the package itself, not the TS properties box. I have tried both ways, in fact every combination I could think of and nothing seems to produce an installed client
which knows its site (and both ways produce almost identical logs, which makes me think the properties are being ignored from either location).
The log doesn't actually contain any error messages which seem relevant at all, but here's some chunks with all of the errors (the log was too big to post in its entirety) :
Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Couldn't find a product with MSI upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}' in the MSI database. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Item x64/MicrosoftPolicyPlatformSetup.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
File 'D:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Item x64/WindowsFirewallConfigurationProvider.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Discovering whether item 'i386/Silverlight.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
32-bit Hive selected ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Item i386/Silverlight.exe has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Detected item 'i386/dotNetFx40_Client_x86_x64.exe' ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Discovering whether item 'SCEPInstall.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
Couldn't determine site version for site 'XXX'. Let client deployment continue. ccmsetup 6/06/2014 10:58:16 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterEndpointsInit. Gathers information such as log file name on each endpoint to be registered on the system. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterSystemTasksInit. Processes the CcmSystemTask table and passes this information to CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:01: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
MSI: Action 11:01:02: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
MSI: Action 11:01:02: CcmRegisterComponentsInit. Generates the list of components for CcmRegisterComponets action to register. ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
MSI: Action 11:01:03: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
MSI: Action 11:01:03: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
MSI: Action 11:01:03: SmsMigrateSwDistHistory. Migrate software distribution history. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
MSI: Action 11:01:03: CcmInstallUtilInit. Initializing InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
MSI: Action 11:01:04: CcmStopService. Stops the ccmexec service. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:04: StopServices. Stopping services ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:04: SmsUninstallPrepDrvr. Uninstalling Software Metering PREP Driver ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:04: SmsStopUIComponents. This custom action forces all open client UI components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:04: SmsStopUserComponents. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:04: CcmUnloadWmiProviders. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterHostedApplicationsRollback. Rollback the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:22: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
MSI: Action 11:01:26: CcmRegisterPerfCountersRollback. Rolls back any changes made by CcmRegisterPerfCounters if install fails. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
MSI: Action 11:01:26: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
MSI: Action 11:01:26: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
MSI: Action 11:01:26: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
MSI: Action 11:01:26: CcmInstallUtil. Calling InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
MSI: Action 11:01:33: SmsSetLUAAccessPermissions. >Gets permission for evelation on Vista and grants each COM object permission. ccmsetup 6/06/2014 11:01:33 AM 2336 (0x0920)

Install Software Updates Step fails during Build and Capture

I have run into a problem while attempting to use the Install Software Update task during a build and capture task sequence. I have MDT 2012U1 integrated into SCCM 2012.
The Install Software steps find and use the Deployment Points fine and the Use Toolkit steps similarly are able to download their source files from the distribution points using the Network Access account. The Install Software Updates step, however
fails with an access denied error in the CAS.log.
I have found that I can work around this problem by setting the DP to allow anonymous access. After checking this box, the software updates install during the build and capture task sequence. Unchecking the Allow anoymous makes the problem recur.
I would like to not have to have the "allow anonymous access" enabled on the DPs for obvious reasons. Other packages download correctly from the DP with anonymous access disabled - they use the network access account. Install Software Updates
is the only step that seems unable to use that account to talk with the DP.
Is this a known issue? Is there a work around?

Thanks for the information. I will give that a try. I do have the SMSMP & SMSSLP (not sure I need this one in 2012) filled in in the Configmgr client install settings. Before I did that, it couldn't even find the SUP.
I am a little skeptical that the hotfix will fix my problem since most packages are downloading from the DP fine - it is only Software Updates that are failing to download. On the other hand, it is clearly a permissions issue since allowing anonymous
on the DP resolves the issue, all be it in a way I am uncomfortable maintaining in the long run.
That KB replaces a lot of key Windows system files. Hopefully, it won't cause more problems than it solves.
---additional thought
I wonder, could it be that Packages that work without this KB have package share settings with "Copy the content in this package to a packages share on Distribution Points" cleared/unchecked? This setting is not available for patch packages
- so I wonder if it is enabled by default behind the scenes. That could explain why the patch packages are affected and not the other regular application packages I have are not. All my regular packages so far do not have the
"Copy the content" box checked. Clients would be accessing the packages differently I suppose based on whether it was through a packages share or through the new SCCM 2012 package storage thing with the hashing.

Build and Capture - How to install software updates without joining domain

Due to security policy, can't join domain before the patch installation.
I want to know the detail steps. I only set SMSMP when install Configuration Manager, but in the end, NO updates are installed.
Do I miss some steps? what are the detail steps?

HI Jorgen
Sorry for my poor English!
You mean I should create two new collections, one is X86,
another is X64.
Add the "Unknow Computer"
object,
that I want to build and capture, into the two collections
Deploy the patches to the two collections
Do I correct?

Known Issue: Do not install Visual Studio Express 2015 for Windows 10 on a Machine with Visual Studio Community, Professional, or Enterprise (Windows 10 Insider Preview SDK and tools, April 2015 release)

If you install Visual Studio Express 2015 for Windows 10 on a machine with Visual Studio 2015 Community, Professional, or Enterprise, these editions will not work as expected.

To resolve this, uninstall Visual Studio Express 2015 for Windows 10. Then, repair Visual Studio Community, Professional, or Enterprise.

Problem with installing Visual Studio on Windows 8

Hi
I am disappointed to buy windows 8 based machine. I installed visual studio 2013 on Windows 7 machine and it was compiling well
But i installed same on my windows 8 machine. But i am not able to compile simple program
Below is program
#include<stdio.h>
int main()
printf("Hello World");
return 0;
I am getting below error
Error 1
error MSB4018: The "CL" task failed unexpectedly.
System.TypeInitializationException: The type initializer for 'Microsoft.Build.Utilities.FileTracker' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Build.Utilities.FileTracker..cctor()
--- End of inner exception stack trace ---
at Microsoft.Build.CPPTasks.CL.ComputeOutOfDateSources()
at Microsoft.Build.CPPTasks.TrackedVCToolTask.SkipTaskExecution()
at Microsoft.Build.Utilities.ToolTask.Execute()
at Microsoft.Build.CPPTasks.TrackedVCToolTask.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets
341 5
ConsoleApplication1
This is strange.
Please help here
thanks
regards
Sobin

Error 1 error MSB4018: The "CL" task failed unexpectedly.
System.TypeInitializationException: The type initializer for 'Microsoft.Build.Utilities.FileTracker' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
See if this thread helps:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/bbe9aa98-42de-4bf8-bce8-8b2ab4fd16ad/msbuild-error-msb4018-with-vs2012-update-1?forum=msbuild
When in doubt, put some of the key words from the error into your
favourite search engine.
Dave

Launching VB6 Editor after installing Visual Studio 2013 results in "Please wait while Windows configures Microsoft Visual Studio..."

I have had various versions of Visual Studio installed beside Visual Basic 6.0 Enterprise for some time with no problems, most recently Visual Studio 2012 Premium.
I recently installed Visual Studio 2013 Premium, and now every time I open VB6 I get a dialog that says "Please wait while Windows configures Microsoft Visual Studio Professional 2013" that shows a progress bar. After it finishes (30 seconds or
so), it launches again and again and finally VB6 will open. This happens with each instance of VB6, regardless if I've already done it once and never run VS2013 in between.
If I cancel the dialog, I get this error message in a dialog: "Error 1712. One or more of the files required to restore your computer to its previous state could not be found. Restoration will not be possible." Several more "Please wait"...
dialogs will appear and if I continue to cancel, eventually I'll get the VB6 editor. It appear to work fine despite the error messages.
It seems to me that the VS2013 installer flagged some dll's or other files to be rolled back whenever starting VB6. It doesn't appear to be necessary, and I'd like to avoid playing the "Please wait" wack-a-cancel-button game before launching each
instance of VB6 (or waiting several minutes for no reason). So how do I fix this?
Note: I've seen something similar happen in Outlook on a different PC when upgrading from 2010 to 2013. The same sort of "Please wait"... dialog would appear each time I opened Outlook. Judging by the "similar" questions that popped up when
entering this forum post, I'd say this is a general problem with upgrading older versions or installing newer versions of major Microsoft software side-by-side.
/* Don Reynolds */

I found the answer!
I was having the exact same issue, and I was search for a solution and I happened across the following thread: http://social.msdn.microsoft.com/Forums/en-US/f4b0fd38-f4f9-41ea-bd8d-834203a175d2/building-visual-studio-2010-project-triggers-please-wait-while-windows-configures-visual-studio?forum=vssetup&prof=required
Scroll a small bit down, and there is a post by Barry Wang explaining that you need to use event viewer to find out what is missing. Anyway, I opened event viewer, then open VS 6, then hit refresh in the event viewer (under Windows Logs -> Application)
and saw a warning message from MsiInstaller. It gave me the following message:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does
not exist.
I opened an elevated command prompt, I navigated to the C:\WINDOWS\Microsoft.NET\Framework folder and verified that 'URTInstallPath_GAC' didn't exist, and then I did "md URTInstallPath_GAC".
Closed and reopened VS 6, and it instantly opened - no "Please wait" message.
Now this may or may not be the same problem you are having (problem is - I have had it happen on two separate computers now with VS 6 and VS 2013 installed), but it should point you in the right direction. In fact, you should be able to use the Event Viewer
for anytime the "Please wait" message shows up for any application, and then once there find out what is really missing.

Can't install Visual Studio 2013 on Windows 8.1

When i want to install Visual Studio 2013, an error message appear :
Setup Blocked
Correct the following problems and then run setup again. To learn more, you can review the lis of common issues and workarounds or examine the log file
This version of Visual Studio is not compatible with Windows 8.1 Preview
I am using Windows 8.1, and i checked Visual Studio 2013 system requirement, it should run on Windows 8.1, but i can't install it on my PC.
What should i do?
sorry for my bad english

IAA
You do know that win 8.1 preview will expire on Jan 15th right? Preview is a beta build and if I were you I wouldn't worry about VS not installing until you upgrade to the released build of 8.1
This version of Visual Studio is not compatible with Windows 8.1 Preview
Wanikiya and Dyami--Team Zigzag

Installing Visual Studio runtimes on Build and Captures

Similar Messages

Maybe you are looking for