Nordland 1 Report post Posted January 6, 2014 I'm trying to set up a Windows 8.1 deployment TS using SCCM 2012 R2, MDT 2013 and UDI. The UDI is just there so that I will get the "deployment complete" message, no settings are changed in it. Now, since moving to R2, the deployment complete message doesn't always appear in the end and I have no idea why. The same latop is used Saturday, SUCCESS, Installed all software in the TS and got the deployment complete message Monday,First run. FAILED, Installed some of the software and actually got a deployment complete message. Monday, Second run. FAILED. Installed all software, but no deployment complete message. This isn't making any sense to me.... Quote Share this post Link to post Share on other sites
anyweb 477 Report post Posted January 7, 2014 without logs we can only guess. so post some logs (smsts*.log) Quote Share this post Link to post Share on other sites
Nordland 1 Report post Posted January 7, 2014 Here is the latest SMSTS.log file. This install ran today, finished but no complete message. OS is 8.1, that I think might have something to do with this... not sure though. smsts.log Quote Share this post Link to post Share on other sites
Nordland 1 Report post Posted January 7, 2014 As I understand it, "reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /v RunOSDResults /d %windir%\UDI\OSDResults.exe /f" is added from the "OSD_InstallOSDResults.vbs" to the registry of the machine. When things are working as they should, at least in my case, "Deployment Complete" pops up after the TS has completed and the computer has restarted, but before we log in. As it is now, it takes about 30 minutes to login after a deployment. Windows is showing the "Almost done. Taking care of a few things. Installing Apps. Don't turn off your PC." screen. After "Almost ready.." is done, the deployment complete pops up. Could it be that AppInstall.exe, which is added to "reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" in the registry, is some how causing this? thanks Quote Share this post Link to post Share on other sites
Nordland 1 Report post Posted January 9, 2014 So, it seems that this only happens on touch enabled laptops, in my case Latitude 7440. If I dock the laptop, close the screen and run the install from an external screen it works fine. Driver issue? Issue with SCCM and touch? Windows 8.1 Apps issue? Anyweb, any ideas? Quote Share this post Link to post Share on other sites
ggarman 0 Report post Posted January 29, 2014 Having the similar issue with Dell Venue Pro 11 7130. Windows 8.1 SCCM 2012 R2, MDT 2013 and UDI. Gives me login screen, I log in with account, takes approx. a minute to login in the first time then gives me deployment complete screen. I have no problems when installing on Optiplex 7010, goe right to the deployment complete screen, then allows me to login. Was guessing it has something to do with the touch screen Quote Share this post Link to post Share on other sites
jay 0 Report post Posted June 10, 2014 Happening here on certain models, I did remember it happening on win7 images but rarely. XT3 - touchscreen, but also happened on 990. Any updates? Quote Share this post Link to post Share on other sites
tttttttttt 0 Report post Posted July 29, 2014 It definitely is related to how 8.1 attempts to detect and treats differently tablets/touch screen computers. I'm working with two different touchscreen laptops, one that does it and another that works fine. Its the smaller screened of the two that has the issue. however if I plug in a USB keyboard it finishes fine. As I understand it the presence of a keyboard is one of the triggers that causes 8.1 to go straight to desktop at login. What I can't explain is why the built in keyboard isn't good enough for the smaller model I'm using sccm now but saw similar behavior with just MDT too. If I enabled the hideshell option it would hang for exactly 30 minutes "getting ready" but the ts was still running the whole time with the progress bar just hidden behind everything. So it like the os is waiting for the program to exit before you get past getting ready and when it doesn't it eventually timeout after 30 minutes. Quote Share this post Link to post Share on other sites