SCCM 2012 R2 C2 OSD deployments no logs when Applications fail

Hello,
Have Task Sequences with the Install Application step {as well as other steps for packages, etc.} that installs Applications when one of the Applications fail I usually see exactly what Application fails through the Console Status Message Query "All
Status Messages for a Specific Package at a Specific Site".
Troubleshooting: When I look in C:\Windows\CCM\logs. I see none of the logs: AppDiscovery.log(s), AppEnforce.log(s), AppIntentEval.log (s)?
Note: This only happens if there is an error in the Install Application step...normally the logs are there. Any ideas on how to fix this?
Thanks!

Here is a snippet of smsts.log There are 2 Install Applications steps the first one has 9 applications the 2nd has 1 application.
<![LOG[
Parsing step node: CCL Shipboard Applications]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_75fb5490-a490-4e64-9545-fcd0429bc135,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_848807ff-6527-4984-b789-315489b5d8fb,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_275df3b1-48df-49dd-8f4d-e739352e9da5,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_a5e881ca-e355-4119-ae4c-ecb0b809da1d,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b4ade0f0-0801-4772-a1b1-2f07b9e774d9,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_c57aedb5-5a8a-49a7-98ed-89b48fe78d12,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_01266b3d-f6cb-4dc4-b255-36c3244b998f,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b5d3c8f3-cb78-4e1a-8796-f8285128e315,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_83d05a3c-a613-40d7-88da-ceb0a07ef60e
/basevar: /continueOnError:True]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 56]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">
<![LOG[
Parsing step node: CCL Shipboard Application Part 2]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_cdad2a4f-c0cc-4fd5-9833-0b273c8dca01 /basevar: /continueOnError:False]LOG]!><time="09:30:41.517+240" date="04-10-2015"
component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 57]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">

Similar Messages

SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends

Hi
Configmgr 2007 sp2
Client versions : 4.00.6487.2000
On many of our servers (2003 SP2, 2008 R2 SP1) the SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends. The log gets full in
less then a second then another log opens and so on!
Here is an example of a small part of the log file:
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 06:00:00 6988 (0x1B4C)
Thanks for any help!
Daniel

Yes, I know this is an old post, but I’m trying to clean them up.
This is not normal, I would check the health of the server and I would also use WMIdiag to see if WMI is healthy.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 - Windows 7 OSD wrong driver letter?

Hi,
I am having issues with SCCM 2012 OSD / MSD 2012 and deploying Windows 7
I am using a captured WIM and I have noticed that on a machine it deploys
to the E: drive even if I have not data on the hard disk (I have cleaned it
with diskpart). So when the task Sequence is finished it the Windows
directory is E:\Windows which is not what I want.
Now what I thought I would try is moving the CD-ROM drive to a different
SATA controller from AHCI port 2 to AHCI Port 3.
Now this made the OS deploy correctly to C: with the final state being C:\Windows
1. So my questions are "How" does SCCM determine what the final logical drive that
windows will be put on?
2. Is there a way I can force it to be C: drive no matter what port my CD-ROM is on?
3. Also if I am using UEFI and Bitlocker is the logic the same?
4. I have noticed when I run diskpart and do list volumes the CD-ROM drive appears?
in the list is this normal?
It seems very bizzare the way it works.
Thanks,
Ward.

Hi,
Thanks for your response actually we are already doing that. :)
Sorry I will re-correct my original post something I did not point out - opps - is we are trying to build these by USB.
It seems that if there is a clean partition and the system boots and happens to choose allocate either the USB key or DVD rom to C: drive then the OS will install on the wrong drive.
So my idea of moving it to another controller seems to make it better but not consistently reliable.
It seems to work if the following conditions are true - need to do a more testing to confirm:
The DVD rom shows up and USB not using the C: so it seems the it will work.
If there is already a partition on the drive called C: and it is already allocated then all seems ok as well
So can I get some more clarity on this - I would like to be able to control it better :)
Thanks,
Ward

SCCM 2012 with MDT: osd, apply wim captured with CM task sequence in MDT task sequence: "cannot find the file specified"

Hi,
Please see titlte. When I try to apply an CM captured WIM via an MDT task sequence, it starts, applies but stops after 15 minutes.
Logfile says it "cannot find the file specified".
Full error: "Installation of image 3 in package mypackage failed to complete. . The system cannot find the file specified. (Error: 80070002, Source: Windows).
Though the image IS there, redistributed it (if it wouldn't be there the task sequence would not start).
Please advise.
J
Update: could it be the fact I'm using an old (SCCM 2012) MDT wim? If I need to recreate the WIM boot image, where do I get the SCCM 2012 R2 boot wims?
Jan Hoedt

See how to manually re-create your boot images
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Sccm 2012 simulate deployment for task sequence / OS or applications

Hi
I have been getting a lot of problems with Os/Application Task Sequences and have been asked a few questions.
I cannot find anything on the Web about Limitations for a simulated deployment in SCCM 2012.
I know SCCM allows you to create them but does it work/Are the results accurate?
I need to know the following:
Can you simulate an OS Deployment Task Sequence?
Can you simulate an Application Deployment Task Sequence?
Are there limitations to Simulated Deployments?
Thanks guys Hope this makes sense and you can help.
Regards
Anthony

If you have the MDT integration with SCCM 2012 you can simulate the settings used by the task sequence, but not the actual task sequence deployment. However, seeing the settings is often enough.
Check this post:
Save time (and avoid pain) - Create a MDT simulation environment
http://www.deploymentresearch.com/Research/tabid/62/EntryId/155/Save-time-and-avoid-pain-Create-a-MDT-simulation-environment.aspx
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Orchestrator and SCCM 2012 integration: run task sequence and install assigned applications/packages?

Dear,
We do not have Orchestrator running in our SCCM 2012 R2 environment. Though I wonder if we could accomplish the following scenario with it:
Task sequence Windows 7 => Orchestrator step which queries assigned installations to the computer object and installs them one by one.
Could you advise?
Kind regards,
Stev.
SteveWonB

> > Define "assigned to computer objects". How is this done technically?
Well, computer objects are members of collections via AD memberships, like the collection "W7-Google-Chrome" (exists of 100 computer objects).
Deploy of packages is done to these collections. So a computer member of "W7-Google-Chrome" will automatically get Google Chrome.
Some computers are member of 30 collections, some of 80.
Goal is to have the task sequence run all applications/packages assigned (with their reboots if needed).
Kind regards,
Steven
SteveWonB

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

Trouble shooting BOOT issue in SCCM 2012 but I cant find SMSPXE.log in the logfolder

Hi,
Is there an change in PXE troubleshooting PXE PE boot issue, in 2012?
I cant find wat I am used to...
/SaiTech

Hi,
One of our PXE point get some issue, I could not set my finger on it.
I could not find any log file and I expect an smspxe.log in D:\Program Files\SMS_CCM\Logs (Primary site server) so I think something is wrong. The PXE worked after I put .Net 4 on the server.
Is it a secret what you're missing? How should we help you if you don't tell the exact problem?
No secret but I am not sure by my self what state the DP server have.
/SaiTech

SCCM 2012 - SUP - updates not showing as downloaded when they actualy are

Hello. I have a strange problem.
I have collected my updates by year to have an overview of what is still updates..
In the console I have 4 updates showing as not downloaded.
If I highlight these and choose to download I get this
So appearantly it works. However these continue to show as not downloaded. R
My WSUS installation uses a SQL database on a proper sql server.
Help needed

Nothing happened in the logfile. I have no clue to what is happening. What I ended up doing was that I recreated the Software Update Group with the exact same updates and downloaded it again. Problem solved. The views in the console are made from SQL
queries. Guess the download process just didnt finish its sql job.
Old log history is of course gone but I will post the logfile here if/when it happens again.

No event logs when RAID fails in Server 2008 and R2

From what I'm finding out (by web searching) they forgot to include event logging in Server 2008 for when a Windows software RAID fails in some way such as missing disk, failed redundancy, etc. This is REALLY annoying as I was trying to setup email notifications
for when this happens so I can fix it. I'm just using this on my servers at home, so I'm not big on the idea of spending a lot of money on a hardware RAID, it just does some simple network file sharing and streaming and software RAID is fine. Is there anyway
to get this to work properly, like it used to?! Hotfix? Sacrifice a small animal? Free third-party tools that would work if nothing else? Would a MOM server be able to notify me? (been considering setting up one of those and SCCM to mess with)

Thanks guys for chiming in. The only way Microsoft will know this is a big deal (you would think they would, but apparently not), is for people to complain. I found this out myself when I was trying to set up event triggered tasks to email on low disk space
and RAID failure, only to find no events are created on RAID failures!
I have setup a SCOM 2007 R2 server in my testing environment. It registers and alerts me for low disk space just fine, but the availability monitor is not tripped when I break a RAID volume. I have tried offlining a disk, which results in failed redundancy,
and also shutting down the VM and removing a drive, and neither seems to trip an alert. Do I have to do something to get it to monitor correctly?

Latitude E6330 BSOD via SCCM 2012 R2 OSD

Hi All,
I'm currently struggling to build some Latitude E6330 laptops via SCCM 2012 R2 CU3 OSD . I'm getting a BSOD with error code 0000007E after the drivers are applied and the laptop reboots.
I've built nearly 100 OptiPlex desktops without issue from the same server. I've tried both the A09 and A10 E6330 driver CABs, and both have the same issue. I was having an issue even building the boot image with these drivers, but removed a faulty driver
before importing them into SCCM (Conexant USB Modem driver) which resolved that issue. I'm assuming that the removal of this driver wouldn't be causing the BSOD - but I'm currently trying to find a replacement driver to see if that resolves it anyway.
I've tried using 'Auto Apply Drivers' and 'Apply Driver Package' in the task sequence, using a WMI query and also without a WMI query to no avail. I've blown away all previous drivers, imported only the A09 and then blew away + imported only the A10
drivers, rebuilt the driver packages and re-added to the boot image numerous times. Yep I've been distributing/updating distribution points each time too :)
Unfortunately I can't get onto the laptop to check the smsts/setupact/etc etc logs because it blue screens even in safe mode.
My last resort will be to add just the network+HDD drivers, and then slowly add drivers until I figure out what driver is causing the BSOD. Unfortunately this would be quite a lengthy procedure, so I'm hoping that someone has had a similar problem and
may know which driver could be causing me this grief.. Or perhaps could point me in a different direction as to what may be causing this issue....
Thanks for your time.

Are you trying to deploying Windows 7 to the laptops?
If so does your WIM file include the platform update (how long has it been since you created / updated it)? If not then you may need to update / capture a new wim and try again.
A lot of newer drivers will cause this sort of problem if you try and inject them into an older wim file.
If this isn't the case, then I have had this happen to me a long time ago with a webcam driver so maybe exclude these drivers first? A long shot though.
Cheers
Damon

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 NO SP - Reporting for application deployments not up to date

Hello,
We have a problem when deploying applications with our SCCM 2012 NO SP.
The reports for the application deployments and sup deployment are not up to date.
The applications have been deployed on the clients but the information is not in sccm servers.
The reporting for the package deployment are working correctly.
Do you have an idea ?
Thanks

Hi,
How are things going? Please let us know if there is any progress.
Regards.
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.

Strange problem - app install failed randomly - OSD SCCM 2012 R2

Hi,
We have this problem for a few weeks and despite various test the problem persists. I hope the community can help me on this problem.
Problem : During TS New computer Win 7 x64 or X86 OSD, app failed to install randomly. Some example
: on the same model, morning OSD test, all app located on TS will be installed, then test the afternoon and no application is here. Sometimes, it works during 4 days and after doesn't work during 1 week / 2 day, it's very randomly. Problem is here for all
models.
Test made :
Add reboot step in TS just before install app > Not ok
Change deployment option app TS to : "Download content and run locally" > Not ok
Add following properties to the client agent in TS : SMSMP=SCCMSRV.domain.lan DNSSUFIX=Domain.lan > Not ok
Enable anonymous mode > Not ok
Informations :
App concerned : Adobe flash, google chrome etc...
Domain integration : OK
App installation tested across software center : OK
Account service for distribution app : OK
Some errors that i've notice :
Policy Evaluation failed, hr=0x80004005 (smsts.log)
Install application failed: 'Adobe Shockware Player'. Error Code 0x80004005 InstallApplication
(smsts.log)
Policy prevents failover to WINS for lookup (LocationServices.log)
Error sending HEAD request. HTTP code 401, status 'Unauthorized' (LocationServices.log)
No error in AppEnforce.log
Do you have an idea ? Thank you in advance.

Finally the pause Works and all app was installed after 8 test on different models.
For my case I following this order :
- 1 Before install app: Put a pause (3m) with this script
Set fso = CreateObject("Scripting.FileSystemObject")
Wscript.Sleep 180000
And this command line : %SYSTEMROOT%\System32\wscript.exe Pause_TS_3m.vbs
- 2 Then put a pause ( about 30s) before each app with a run command line ping :
cmd.exe /c "ping -n 30 localhost" > NUL
As Damon
A. Johns say "At the very least it can result in unreliable results."
Well I hope i'll find a reliable solution, thanks a lot all for help me it was a long time to test.
These topic help me :
http://social.technet.microsoft.com/Forums/en-US/221bcfe8-4c1e-4766-be5b-fbf54fe0e66c/specific-model-suddenly-fails-on-any-application-install-packages-work-fine?forum=configmanagerosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/17cc2c51-2769-4a43-b456-570373b24643/pausing-the-sccm-osd-task-sequence?forum=configmgrosd

SCCM 2012: PXE deploy: import boot images?

Hi,
We fully configured sccm 2012 and did osd via bootable media. Now we want to configure PXE.
We enabled it (http://prajwaldesai.com/deploying-sccm-2012-part-14-build-and-capture-windows-7-64-bit/).
My questions:
*Is that all that needs to be done?
*It seems to me we need to import boot images in WDS?
*If we do, which to import then (both x86 and x64 probably) + there is a winpe and a winpe.....wim made by sccm, which one to import then?
*on DHCP we change the boot server hostname but what about the bootfile name, what is the path of that? \boot\x64\wdsnbp.com?
Please advise.
J.
Jan Hoedt

I keep on getting TFTP open timeout
I find in smspxe.log that it reaches to the SCCM-server but then something goes wrong. Not sure what.
How can I troubleshoot find more info, please advise?
00:51:55:2A:5C:C5, 0A190A42-FFDe6-5e69-9e41-70e481B852E3: device is not in the database.   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Getting boot action for unknown machine: item key: 2046820352   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 CCM_POST /ccm_system/request   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Jan Hoedt
Note: what I also can see:
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 000.000.000.000

SCCM 2012 R2 C2 OSD deployments no logs when Applications fail

Similar Messages

Maybe you are looking for