Injector

Yea I noticed that after some time, I ended up just pushing all the clients again.

So just for the hell of it (and because I wanted to see what was involved) I decided to go full worse case scenario on my 1511 SCCM lab (1 Pri, 2 Sec). I deleted one secondary VM to emulate a total loss, decommissioned the second secondary as well as the primary. Then I created a new VM where I installed a clean 1606. I got everything running (cleaned the schema as well) and all my content reloaded. My question is after enabling AD system discovery I see the systems again as expected but they state no client is installed, being they already have a client installed, should I just enable site wide client push/manual client push or would the clients see that the AD schema doesn't have the old server anymore and instead register to the new server in the System Manager container? Thanks.

ok so i'm clearly missing something here, I have ConfigMgr 2012 R2 SP1 running on Server 2012 R2, I installed ADK 10 after "removing" ADK 8.1 U (I quoted because i copied the whole 8 folder and restored it after the official uninstall so i could still use USMT) I took the W10 boot images and added them to ConfigMgr, now I happen to know what the wim PE images off the ADK don't come with any packages so in order for OSD to work ConfigMgr adds OCs upon distribution, for example this screenshot below is adding scripting, SecureStartup, WDS, and WMI However i know that DISM 6.3 which is what comes by default with Server 2012 R2 cannot modify Windows 10 images as it complains about upper level image or something or other. which is why the ADK installs DISM v10, in the screenshot below: On the left is DISM from start -> run -> CMD On the righ is DISM from ADK Now to the bread and butter of this post, even though SCCM has accepted the boot images and told me they were successfully imported when I do get-packages against it there is no packages, nor is there any drivers loaded.How are these images supposed to work when the server can't modify them? After i asked myself that question i went to look in the DISM log and noticed that it is version 10 that is being ran however after i mounted the image the server uses i noticed that none of the packages were loaded. So what I'm I missing here? the server said the images were imported fine however i'm sure that without scripting and WMI they're not going to work. Do i need to load those OC packages manually into the wim?

So I've been banging my head against this one, I have 5 machines out of 1k+ that when running a TS to deploy OS and software will fails to install 3 applications but all the other systems will install it fine. One of the apps happens to be Office 2013 so I'll concentrate on that one. on the SMSTS.Log file the only thing pertaining to this is: <![LOG[ Parsing step node: Install Office]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:459"> <![LOG[Description: ]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:463"> <![LOG[ContinueOnError: ]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:467"> <![LOG[SuccessCodeList: 0]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:475"> <![LOG[No condition is associated with the step.]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:670"> <![LOG[Disable: ]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:484"> <![LOG[Run in attribute: FullOS]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:492"> <![LOG[Timeout: ]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:496"> <![LOG[DefaultVarlist found]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:579"> <![LOG[Variable name: OSDApp0Description]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:620"> <![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:620"> <![LOG[Variable name: OSDApp0Name]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:620"> <![LOG[Variable name: OSDAppCount]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:620"> <![LOG[Action command line: smsappinstall.exe /app:ScopeId_EE508F4D-4716-4BDE-9DFE-0B9DA7F5B7B6/Application_0ac3c926-72e7-4ddf-8121-6d3eb58cbd08 /basevar: /continueOnError:True]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:522"> <![LOG[Adding instruction at 30]LOG]!><time="18:10:20.758+300" date="10-16-2015" component="TSManager" context="" type="1" thread="2928" file="tsxml.cpp:524"> When I do a normal deployment of the Office application after the TS has finished Office will install fine, it's only these 5 machines that refuse to do it when using the TS which also happens to report that all the machines in the collection finished successfully. Any ideas?