jrekkedal

Ok everyone, I am being a good forum member and looping back with a resolution. Long story short, I had to engage Microsoft directly to resolve the issue. We checked everything from IIS setup, to permissions on the source directories, so permissions/setups of the content library/package library and signatures... you name it. Here is the resolution that finally got things rolling: RESOLUTION: · opened the below path in WMI: 1. Run “wbemtest” with administrator account. 2. Connect to root\sms\site_ <SITECODE>. For example: root\sms\site_PS1 3. Run the query select * from sms_sci_component where componentname=SMS_DISTRIBUTION_MANAGER 4. Double-click the object. 5. Double-click the “Props” properties. 6. Click View Embedded 7. Double-click the query result to find the Property where PropertyName is “Package Root Directory”. 8. Double-click Value1. Remove E: 9. Click “Save Property” 10. Click “Save Object” 11. Click “Close” and click Save Property 12. Click “Save Object” 13. Restarted the SCCM services.

Wished this worked for me... ugh. All boundaries are setup correctly. Worked before "something" happened, but I checked just to make sure. I am running SCCM SP1 CU4, so maybe that is my rub? I'll look at what it takes to get on R2. Do you know if that is another purchase of if I am guaranteed an upgrade with my current SP1 license?

Thanks, but those address a 401 (unauthorized) issue rather than the 404 I see above.

So I have a meeting later this afternoon to train our Service Desk on how they should be imaging machines in our environment and being the good engineer I am I setup a test yesterday to just "make sure" things were still working. As you can tell, they aren't... I noticed my task sequence was hanging on installing an application that normally installed without issue... Frustration to say the least. So, I tried to see if I could just deploy the application, like I did when I originally created it and it worked, but it would stay stuck at "Downloading 0%" Long story short and after some digging, I took a look at the ContentTransferManager.log and see the following entries: CAS logs shows this: The application source files live on another NAS/storage server, and I've checked the permissions so that Everyone has access to them just to get that out of the way but I need to stress that it was working and now its not... No idea when it could have broke either. I have validated the application, I have removed it and re-added it, and I have even removed the distribution point role from the server and re-added it to no avail (pain in the but btw). Distmgr.log shows the application as being successfully distributed and GUI shows that application in the green. I can still deploy updates and I can deploy packages, but NOT applications now. Maddening!

It looks like I finally figured it out as an application successfully installed and I'm watching the image capture as I write this. I'm doing my part in making sure I update the thread so in the case some other poor soul finds his/her way here they might get an answer faster than I did. I did some research over the weekend (i.e. Google) and start broadening my search terms a bit from failing to run applications to also Software Updates. Long story short, on the Distribution point Properties page (Administration > Site Configuration > Servers and Site System Roles > Highlight the DP > Right-click DP role > Properties) you need to check the box "Allow clients to connect anonymously" on the General tab in order for things to fully work. I'm guessing this is because a workgroup machine not only uses the NAA, but the DP has to also be prepared to get requests from anonymous machines. Granted, that sounds like a no-brainer but I never found that setting in any of the guides posted on this site, or others, so it was a lucky hit as far as I am concerned. Thanks to conorofarrell and Edenost for the replies as I know taking time out of your day for a random forum posting can be a big deal.

I am at my wits end on troubleshooting this issue. I am trying to do a simple build and capture of Windows 7 SP1 x64 and can't seem to install even one application (let alone get to the part where I can install updates). If this is a simple deploy/build of a workstation that joins the domain then the applications install without any problem at all; however, I really want to build/capture that doesn't require me to join the domain then join a workgroup just to prep the OS/install apps. I am running SCCM 2012 SP1 CU3 on my server with is pulling the duty of a DP, MP and a host of others. The task sequence was built using the wizard, so nothing too outrageous there. The sequence goes normally and IMMEDIATELY bombs out when it gets to "Install Applications". Things I have checked/verified already: The application does have the checkbox enabled for "Allow this application to be installed from the ...." Boundary is setup for the machine I am working on via an IP address range that covers my entire subnet. Checked that SMSMP=myserver.mydomain.com is set for my Management Point in the TS for "Setup Windows and Configuration Manager" I read a blog posting that mentioned installing a hotfix in the task sequence, rebooting and then it should work, but I get the same error even on a package. My Network Access Account does have permissions to the applications share (I even temporarily changed it to my own account as I am a domain admin) Checking in my smsts.log file doesn't yield much either (I'll post it later because I want to completely delete SCCM from my server/memory over this), but I at least wanted to get a thread going to see if anyone had any other ideas to check?

Thanks h4x0r, for the prompt reply and the info. Unfortunately, I can't seem to find it in my volume licensing site. Nothing can be easy can it? Microsoft really sold us up the river on this one when they didn't realize that some organizations are non-profit and have tight budgets that don't allow hardware refreshes on a regular basis. Let me know if you find it suitable to share out the correct file.

Anyone know where I can get a copy of the non-SP1 SCCM download? Or perhaps someone just nice enough to shoot me a generic boot.wim from theirs?