FubsyGamer

I ended up getting this resolved. I re-added the MP and DP, and then changed the command I run to this, based on the website below: ccmsetup.exe CCMHTTPPORT=80 SMSMP=sccmserver SMSSLP=sccmserver SMSSITECODE=XXX SMSCACHESIZE=1000 http://www.myitforum.com/forums/m225419-print.aspx

[RESOLVED, SEE POST BELOW] Hello, I am having an issue manually installing the SCCM Client on a handful of workstations. I have it pushing out via GPO, as well as installing during my PXE task sequence. The GPO worked for about 90% of the workstations in my environment, but it didn't for a handful, so I decided to just go do it manually on those workstations. It worked for me perfectly on the first one I tried. However, every one after that, it will not install. Please see my attached log files to see if you can help me out. I get the same errors at the bottom of each one. This is an excerpt from the bottom of the log: <![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="ccmsetup.cpp:6814"> <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="state.cpp:171"> <![LOG[Params to send '5.0.8412.1004 Deployment Error 0x800704dd. Path http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002']LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="0" thread="192" file="state.cpp:208"> <![LOG[A Fallback Status Point has not been specified and no client was installed. Message with STATEID='309' will not be sent.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="state.cpp:222"> <![LOG[Failed to send status 309. Error (87D00215)]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="state.cpp:235"> <![LOG[Failed to download from DP 'http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002', error 0x800704dd.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="ccmsetup.cpp:1388"> <![LOG[Enumerated all 1 DP locations but none of them is good. Fallback to MP.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="ccmsetup.cpp:11481"> <![LOG[Cost settings successfully set on '{E2CD69D0-4F42-4D47-BE77-0D7E1D24EF81}'.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="0" thread="192" file="ccmutillib.cpp:5781"> <![LOG[Using branch cache option.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:6639"> <![LOG[Adding file 'HTTP://cbsCM01:80/CCM_Client/i386/vcredist_x86.exe' to BITS job, saving as 'C:\Windows\ccmsetup\vcredist_x86.exe'.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:6670"> <![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="ccmsetup.cpp:6814"> <![LOG[Failed to connect to policy namespace. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="localpolicy.cpp:367"> <![LOG[Failed to revoke client upgrade local policy. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="localpolicy.cpp:394"> <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:9772"> <![LOG[CcmSetup failed with error code 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:10927"> I worked with my network engineer, who tells me the workstations have full access to this server. I even tried putting a workstation on the same VLAN as the server, and still get the same error. Timeline is: 0. The GPO for Client deployment worked for ~90% of the workstations in my environment. 1. I try to manually install the client on my own workstation. It works without a problem. 2. I try to manually install the client on another workstation where it is missing. I get the error as shown in the log below. 3. I try 3 other workstations that don't have the client, they all give the same error as the 'FAILED' log 4. I move the workstation to the same VLAN as the SCCM server, and still get the same error Any assistance would be greatly appreciated. FAILED-ccmsetup.log SUCCESS-ccmsetup.log

One more update...we got it! I was using the wrong .msi I was using the msi from \\sccm_server\SMS_sitename\Client\i386\client.msi I should have been going to \\sccm_server\SMS_sitename\bin\i386\ccmsetup.msi Yay!!!

Just to update my own post, in case someone googles and finds this, I also posted on reddit.com/r/sccm. Over there, someone recommended I check C:\Windows\Temp for any MSI logs, and I found a BUNCH of them, that all say: I'm now working on this, but at least it's a point in the right direction.

Server details: Windows Server 2012 R2 - fully updated SCCM v 1606 Console version: 5.0.8412.1205 Site version: 5.0.8412.1000 Deploy workstation: Windows 10 Enterprise v1607 Hello, I have been trying to install the SCCM Client onto my workstations for the better part of two days now, attempting to deploy it via GPO. No matter what I try, I always get the same four errors in my Windows Logs/System. They come in a list of 4 entries, right in a row At this point I'm ready to pull my hair out. I'm really really unsure what my settings should really look like. I've googled and googled these errors, and I've tried every configuration change that I can see being recommended, and I don't get any changes at all. Right now, here's how I have it set up: Group Policy with Computer Configuration-Policies-Software Settings-Software installation package that has my client.msi for the source. I have tried the client.msi file from two different locations: \\sccm_server\SMS_mysite\Client\i386\client.msi and \\domain.local\NETLOGON\. For the first one (from my sccm_server), at first there were no read permissions to the Client folder (for Everyone, or Authenticated Users, or any other blanket group), so I granted them. I got that idea from this technet discussion. I tried NETLOGON because that's how I install LAPS (which works great). Figure I might as well give it a shot. I imported both templates into the group policy. Site Assignment has my site code, retry interval set to 5, retry duration set to 1. Client Deployment Settings, I've tried LOTS of things here. I've tried leaving it not configured, I've tried different variations on CCMSetup.exe with different switches like /logon, SMSSITECODE=mysitecode, MP=sccm_server, etc. I'm very unconfident on what should ACTUALLY be here. In SCCM, under Software Update-Based Client Installation Properties, I have check marked the box for 'Enable software update-based client installation'. I have extended my AD Schema as suggested in step 14 of this guide. In fact, I followed this guide for setting up my SCCM and deploying W10 via PXE. My setup should be nearly identitcal. When I try to check my workstation for C:\Windows\system32\CCM\ for logs, the CCM folder does not exist. I've searched all over C:\Windows for any CCM files or folders, and I find none. Please, help me here. Thank you.

Sure that's fair. I guess I should have been more specific, because you are right I don't need to re-install MDT for Windows 7. My question really should have been "what (if anything) should I change when creating a deployment task sequence for Windows 7x64?"

I have been asked to set up a Windows 7 image as well as a Windows 10. Will these same steps work for Windows 7x64 Enterprise, or are other steps needed?

Hey guys, So I am rolling out SCCM and OSD. I am learning this totally from scratch, so it's kind of a long road. The tutorials and help guides in this forum have been a HUGE benefit, so let me thank you for that. My questions are more procedural at this point. I have SCCM set up, and I've followed every step in the SCCM 1511 deployment guides on the forum. I have my Windows 10 x64 image set up and have tested PXE booting, which works perfectly. So now...how do I go about this whole process for my help desk guys? I'm thinking right now I'm able to tell my help desk guys that I have deployed a clean image of Windows 10 x64, that will do some basic tasks (add to the domain, add to correct OU, enable .NET 3.5). They could start using this tomorrow. In the mean time, I will continue to work in the background on deploying each application we use. I envision that I can slowly roll out each one as I test it. Office 365 tomorrow, then our Loan Ops app, then another, etc. Is there a 'best practice' for setting up a build lab environment to test with, then migrate it to production once I'm happy? I have to imagine it's setting up a Device Collection specifically for testing, then create a test Task Sequence that I can use. Once I'm happy, is there a best way to push the new task sequence to production? Or do I just un-distribute the old Task Sequence to OSD Deploy and then distribute the new one? Sorry if I'm all over the place, I'm having a hard time knowing even exactly what I'm asking for. tl,dr: I want my help desk guys to be able to use what I've got ready so far with SCCM and OSD, and then push out new configurations as I test/implement them. Thanks in advance.