Search the Community

Good morning, Long time reader, first time poster. I have an issue with SCCM and clients already added to ADUC. If i build a computer with a name not already in ADUC the task sequence executes correctlt and the machine joins the domain for example KS-Win10-V5. If i use the exact same task sequence and attempt to build a machine already in ADUC (for example ks-wk-adm-01) it executes the task sequence but fails to join the domain... I have added the netbootguid to the machine in ADUC and updated the System discovery in SCCM and this has made no difference. Does anyone have any idea what i could try? I've got a site with 500 devices to rebuild next week. Thank you in advance. If you need any more info let me know. Mark

Hi, we're looking the possibility to request Username and Password ( so the HD staff can specify while we deploy a OS Task sequence (windows 7 standard image)). I saw the possibility to add a Variable to the device collection for request the computer name while the OSD start so i belive that if i add OSD varialble (OSDJoinAccount, OSDJoinDomainName, OSDJoinPassword, OSDJoinType) to the collection (and i specify the data request during the deployment ) the sccm join the client on domain with this credential but it doesn't work. what'is wrong ? Thank's in Advance. SCCM 2012 R2 Sp1 on windows 2012 server.

Afternoon, Recently, I have noticed that some our machines are not consistantly joining the domain as part of the task sequence. I find the issue is very strange, for example the same laptop can take multiple attempts before finally going through and completing the task sequence. The issue occurs with different laptop/desktop manufacturers and models. It also occurs with machines that have previously been sucessful through the task sequence. Our setup has been in place for 18 months and the task sequence has not been altered. The boot image has also not been altered and the correct network drivers are present. I have read that the network drivers in the driver package may need updating, however as the machines will occasionally work I am unsure as to whether that is the correct answer. Within the task sequence I have checked that the user account used to join the machine is correct and it has appropriate permissions. After reviewing the SMSTS logs I have noticed the following: Found network adapter "Intel® Ethernet Connection I217-V" with IP Address 169.254.101.136. TSMBootstrap 04/06/2015 12:32:50 2920 (0x0B68) So I think it must be failing due to the IP address. I am unsure as to why a 169.254 address would be issued. Can anyone explain why it picks up this address during the image build? Towards the end of the SMSTS log I can see the following: Retrying... TSManager 04/06/2015 12:47:36 2972 (0x0B9C) CLibSMSMessageWinHttpTransport::Send: URL: sccm-vm-wm1.XXXX.co.uk:443 CCM_POST /ccm_system_AltAuth/request TSManager 04/06/2015 12:47:36 2972 (0x0B9C) In SSL, but with no client cert TSManager 04/06/2015 12:47:36 2972 (0x0B9C) Error. Received 0x80072ee7 from WinHttpSendRequest. TSManager 04/06/2015 12:47:36 2972 (0x0B9C) unknown host (gethostbyname failed) TSManager 04/06/2015 12:47:36 2972 (0x0B9C) hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8936) TSManager 04/06/2015 12:47:36 2972 (0x0B9C) sending with winhttp failed; 80072ee7 TSManager 04/06/2015 12:47:36 2972 (0x0B9C) So I google'd the above and it is effectively telling me that machine can not speak to the DC in order to join the domain. Which makes sense as it has a 169.254 network. Hopefully someone may have seen something like this before. It is starting to cripple our productivity. Please let me know if any further information. Thanks in advance. Stephen

Hello, I have a problem with trying to join a domain and name the PC as part of a UDI task sequence using standalone media. The task sequence works just fine when PXE booting, but it will not do either task when using a USB drive. Do the task sequence variables that are set by the UDI somehow get reset before the domain join step when not connected to the SCCM server? If so, is there a way to get around this? Maybe using an unattend.xml file? I would appreciate any insight on this. Thanks. TheWes

Hi, after exhausting all of my options once again I need help. My test VM wont join a domain, and I don't know why. Environment: SCCM 2012 R2 MDT 2013 Wmware Workstation VM OSDJoinAccount and OSDJoinPassword variables set in all Unknown Computers collection and they prepopulate in UDI wizard. Account for adding to domain is Domain Admin/Enterprise Admin. Customsettings.ini [settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES Is Customsettings.ini missing some values? Lot of unnecessary steps disabled on purpose to fast up the process. Sales OU created by "Search by domain OUs" not manually(!) Drivers maybe not applying? What I have tried: 1. Disable step in TS Apply Network settings and remove check marks in UDI Wizard for checking AD credential check on both section (User and password) - no go. 2. Tried adding without and OU, so OU blank, and only domain - no go. 3. Tried leaving default computer name, yes I get the famous MININT predefined name (maybe leftovers from some script?, need help with that also) 4. Many other things that I cannot remember right now. Please help, Thank you, UDIWizard_Config.xml smsts-20140918-010624.log