Jump to content


alewoodrum

Established Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

0 Neutral

About alewoodrum

  • Rank
    Advanced Member

Profile Information

  • Gender
    Female
  • Location
    USA
  1. i haven't done that, but sometimes adding a restart after the system is built helps, before adding an application. I think i had to do that when deploying flashplayer or something like that. just an idea.
  2. i just had some issues capturing an image from win 10 1709 and turned out to be the computer name was longer than 15 characters. when i changed the name to something shorter it worked.
  3. i had the same error : Failed to send HTTP request. (Error at WinHttpSendRequest: 0x80072ee2) ccmsetup 1/18/2018 2:59:24 PM 5776 (0x1690)Next retry in 10 minute(s)... it really means a server time out. After further checking it turned out to be Endpoint (antivirus) installed on the host server. My SCCM server is also a VM.
  4. thank you, i finally found the program that was blocking it. It was McAfee endpoint security installed on the host where i have sccm as a VM. I didn't think that would affect the VM but it did.
  5. i am getting similar messages but using only http: Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 1/18/2018 2:53:01 PM 14988 (0x3A8C) [] Params to send '5.0.8577.1000 Deployment Error: 0x80004004, ' ccmsetup 1/18/2018 2:53:01 PM 14988 (0x3A8C) Sending Fallback Status Point message to xxxxxxxxxxx', STATEID='306'. ccmsetup 1/18/2018 2:53:01 PM 14988 (0x3A8C) <ClientDeploymentMessage ErrorCode="-2147467260"><Client Baseline="1" BaselineCookie="" Platform="2" Langs=""/></ClientDeploymentMessage> c
  6. We are part of a bigger forest on ADUC and central offices have their own WSUS, could I skip the WSUS installation on my sccm standalone server?
  7. I am experiencing the same problem now. I am running SCCM 2012 SP2 CU3 and it just fails loading the network drivers. I have been reading and it seems i need to uptade ADK. I am running windows boot 10.0.10586 and deploying windows 10 for education 1511. I am not sure if i need to update adk first and then apply a hotfix 3143760 or not.
  8. I am pretty sure it is the right one. I was also running ADK 8.1 and it had been working but today I updated to ADK 10.0 and hope that will help.
  9. i am having the same issue here with DELL optiplex 5040, it is not installing the network drivers during OSD. After bringing the system up i can put the same drivers on a stick and it will install them and work, but fails on deployment. I have injected the DELL drivers for boot image also. At the beginning it wouldn't start the task sequence because of drivers, so i injected them on the boot.wim but now it is not installing them on OSD. I have also extracted a newer version from intel prowim64 and put them on a package and send them for OSD and still nothing :-( very frustaded. Forgot
  10. i used the Nic drivers from intel. check the nic manufacturer. But in my case, the workstation didn't have an IP. Check on storage drivers.
  11. I deploy windows 7 sp1 and windows 8, as Jorgen said, you don't need to put a key for the operating system, by default if is doesn't have a key, the KMS server will activate it. However you could put the default KMS client key on your Task sequence, on windows settings: Operating system edition KMS Client Setup Key Windows 7 Professional FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 Windows 7 Professional N MRPKT-YTG23-K7D7T-X2JMM-QY7MG Windows 7 Professional E W82YF-2Q76Y-63HXB-FGJG9-GF7QX Windows 7 Enterprise 33PXH-7Y6K
  12. I think i have seen that message too. And it might very well happened with the Dell optiplex 7010. we deployed a bunch on them with windows 7 32bit. However i don't remember how we solved it. Almost every time we deploy a new model we face some troubles. I would check on your 64bit boot image, even if you are deploying x86, the 64bit needs to be distributed as well.
  13. Yes indeed it was the drivers. I did the F8 and it didn't have an IP. So after downloading all kind of drivers from DELL and INTEL , it finally worked. It didn't work with DELL drivers, I ended up downloading the intel PROWIN64 and updloading all drivers on SCCM and then select the one for the specific NIC I217 and added it to the boot file and voila!
×
×
  • Create New...