Config_Mgr_noob Posted June 6, 2014 Report post Posted June 6, 2014 Hi, I keep receiving the below error message during OSD when it hits the Install application step. We just received the new X1 Carbon laptops and have imported the NIC drivers from Lenovo's website. Earlier model of the X1 Carbon are able to successfully image without any errors. Not sure if this is related to the NIC drivers or any other drivers that I imported for this model. It says it can't find the Management Point but it clearly indicates the management point site below the error message. So im not sure why it can't find it when every other PC here can detect it and complete the installation. I've tried manually inputting the MP in the Setup Config Mgr step but the PC does not get added to the domain. Has anyone else here encountered this issue before? Any suggestion or assistance would be greatly appreciated it. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 6, 2014 Report post Posted June 6, 2014 Did it by any change restart before the application installations and do those devices contain SSD drives? Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted June 6, 2014 Report post Posted June 6, 2014 It did restart during the 'Setup Windows and ConfigMgr' step but then continues the same step after the restart. And yes, all of the X1 carbons here have SSD drives; including the new X1 carbon. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 7, 2014 Report post Posted June 7, 2014 That sounds a lot like a "known" timings issue with SSD drives in combination with Applications. A workarround is a new variable, named SMSTSMPListRequestTimeout, that is introduced since R2 (see also: http://technet.microsoft.com/en-us/library/hh273375.aspx). Make this timeout higher and you should be OK. 1 Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted June 9, 2014 Report post Posted June 9, 2014 Thanks Peter I will attempt this today. However, I also notice that the PC does not get joined to the domain when it reboots into Windows. So not sure if this variable will assist me with that issue? Also where in my TS should I place this variable? Quote Share this post Link to post Share on other sites More sharing options...
Jorgen Nilsson Posted June 9, 2014 Report post Posted June 9, 2014 Hi, If it didn't join the domain, check the Netsetup.log file on the client as well to start with. It will give you an indication on why it wasn't joined to the domain. Regards,Jörgen Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 9, 2014 Report post Posted June 9, 2014 The location of the variable doesn't matter, as long as it's in front of the Install applications step. Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted June 9, 2014 Report post Posted June 9, 2014 Thanks Jorgen, the netsetup.log indicated that the issue I was experiencing was that I was selecting 'Computer' AD group, during the OSD, to place my PC in but this process is not possible. It was telling me that the OU does not exist since Computer is not an OU. Once I selected a different OU, the computer was joined and all the applications were installed, thanks Peter and Jorgen. Is there a way to select the Computers "OU" to add newly joined PCs during the OSD process? Not sure if leaving a selecting in the UDI Wizard blank will it know to join it to the default Computer "OU" Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted June 10, 2014 Report post Posted June 10, 2014 Nevermind got it to work. It is possible to indicate an entry within UDI Wizard to point to no OU and it will default to the Computer group..Thanks all for you input! Quote Share this post Link to post Share on other sites More sharing options...
Joe Posted June 27, 2014 Report post Posted June 27, 2014 That sounds a lot like a "known" timings issue with SSD drives in combination with Applications. A workarround is a new variable, named SMSTSMPListRequestTimeout, that is introduced since R2 (see also: http://technet.microsoft.com/en-us/library/hh273375.aspx). Make this timeout higher and you should be OK. Thanks for this note. I was having this problem and just implemented it. I'll know in 20 minutes if it worked! EDIT: Fixed my issue! Thanks again!! Quote Share this post Link to post Share on other sites More sharing options...
