Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

Token's Achievements


Newbie (1/14)



  1. Hi Peter, Thanks for the response. I have checked our DHCP server and we currently have 40% IP addresses left from our address pool. The machines are picking up a DHCP address during PXE boot and I can see this on the DHCP server. However, during the task sequence (during the Apply Network Settings stage...I assume) the build fails and resorts to the applied image but obviously not on the domain. Is there anywhere else that I should be checking?
  2. 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 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
  3. Hi, We have recently noticed that the client has stopped automatically installing onto laptop/desktops. We have had everything run successfully for over 6 months and I have spoken with other administrators and nothing appears to have changed on the domain. Once imaged you can see within C:\Windows that the 'ccmsetup' folder has been copied across but not further action has taken place. In order for the client to install correctly with Endpoint Protection I have to manually run the client.exe file. After this process Endpoint Protection is installed and I can see SCCM now states the machine has the client installed, allowing for remote control, deploying software etc etc. Post image I have noticed on Configuration Manager that the Client Certificate states 'None' rather than 'PKI'. Has anyone else experienced this problem and/or recommend the appropriate logs to be reviewing. Thanks
  4. Hi, I am currently trying to distribute content to one of our secondary servers that acts as a DP. The distribution fails to the server stating lack of free disk space. I have review the destination server and it has ample space on all drives. I have attached a photo with the exact error message I am receiving. Has anyone successfully resolved this issue or can someone guide me into the right path? Thanks
  5. Apologies for not returning with my solution. I resolved the problem by obtaining the drivers directly from the Intel website. Thanks Alewoodrum for the advice.
  6. Hi there. I am experiencing the same problem with a new batch of HP Probook 640 G1's. I have added all the network drivers from the HP website associated with that laptop and also added those drivers to the boot image (both x86 and x64). Does anyone have any other suggestions or a website in which I can download more drivers to throw into the boot image. I have updated the BIOS on the laptop to L77 Ver. 01.03 which is dated from 13th Feb 2014. I can confirm if I go into safe mode, I am able to obtain an IP Address. Thanks
  • Create New...