shifty Posted August 1, 2012 Report post Posted August 1, 2012 Hey guys, I've visited this site a lot for the guides and its been a huge help throughout our SCCM 2012 install and setup. Unfortunately, while I had our implementation of it working (pretty well) at one point - I've had to go through the setup process again on another server and am running into some issues I haven't seen before. So, I'm hoping someone here can give me some guidance. I'm basically running a build and capture for Windows 7 x64 on a Hyper-V VM, once it hits the Configure OS / Setup Windows and Configuration Manager client task the sequence errors out. An investigation of the SMSTS log yields hundreds of lines with the following error: "Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type" I've found a couple of online topics referencing a problem with it pulling/applying an activation key - however, every time I've run this task I have not embedded an activation key. Not 100% sure where to go from here, first time I've seen an error like this while running a TS, really. For everyone's convenience, I've attached the full SMSTS.log. Let me know if I need to provide any more detail Thanks in advance! smsts-20120801-024746.log Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted August 2, 2012 Report post Posted August 2, 2012 hmm does it actually pop up an error at this point or does it just sit there forever logging the same line ? do you also have a copy of any other logs ? check x:\windows\temp\smstslog\ Quote Share this post Link to post Share on other sites More sharing options...
shifty Posted August 3, 2012 Report post Posted August 3, 2012 Yeah, I guess that wasn't quite the right log file I posted originally. This one actually shows a proper error (attached). But again, I haven't been using an activate key in any of my task sequences (which is the common solution to the error being thrown, it seems). Anyway, I've also attached a screenshot of the failed sequence and its relatively generic error code. smsts.log Quote Share this post Link to post Share on other sites More sharing options...
AdminSccm Posted February 27, 2013 Report post Posted February 27, 2013 Did you ever find a solution to this? Quote Share this post Link to post Share on other sites More sharing options...
Oneone Posted February 27, 2013 Report post Posted February 27, 2013 Seems to me it cant access the sourcefiles for the config mgr client. Is the client a member or the right boundary group? and try to make a new package "from definition" for the client package. Dont forget to update DPs Quote Share this post Link to post Share on other sites More sharing options...
inzandity Posted April 1, 2013 Report post Posted April 1, 2013 I was so excited to see someone finally have the same error as me. I have ripped through permissions, logs, set up all new packages, and even started from scratch and followed the guide here step by step (with some slight adjusting for the official release). I just can't seem to get past this though! I have three smsts.log files that I found on the PC (C:\SMSTSLog (2), X:\SMSTSLog) that I have attached. I have as well tried applying a serial key, and toying with the drivers (although I don't think this is an issue in hyper-v?). Hyper-V Environment SCCM 2012 SP1 with all updates SQL 2008 R2 SP2 Build and Capture Windows 7 x64 Enterprise Any help would be greatly appreciated! smsts_c.log smsts_x.log smsts-20130401-230057.log Quote Share this post Link to post Share on other sites More sharing options...
sakpasepj Posted April 29, 2013 Report post Posted April 29, 2013 Same error, I have to remove the Apply Driver Package step. Same to be relate to some unsigned drivers. Quote Share this post Link to post Share on other sites More sharing options...
