Jump to content


hynesy

Established Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hynesy

  • Rank
    Member

Profile Information

  • Gender
    Male
  1. Hi all, I just wanted to ping back with another cause that produces this issue to help anyone else. So basically after installing SCCM 1610 build it hosed our DP, I had to recreate the DP to get Application deployments working. Even after this Software Updates were not downloading, they would hang at 0% and would leave the following errors in DataTransferService.log: "Error sending DAV request. HTTP code 404, status 'Not Found'" "GetDirectoryList_HTTP('http://dp:port/SMS_DP_SMSPKG$/Content_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.x') failed with code 0x87d0027e." "Non-recoverable error retrieving manifest (0x87d0027e)." Cause For us, the cause was the "Authenticated Users" group had been removed (or not added when the DP was recreated) from the security permissions on the SMS_DP_SMSPKG$ and SMS_DP_SMSSIG$ IIS websites. Resolution If your Authenticated Users is missing from your SMS_DP_SMSPKG$ and SMS_DP_SMSSIG$ IIS websites, do the following to add the group back in: 1. Open IIS Manager 2. Under your server expand Site 3. Expand Default Web Site 4. Right click on SMS_DP_SMSPKG$ and select Edit Permissions, select the Security Tab and select Edit 5. Click Add... and enter Authenticated Users then select OK, OK, OK (if you get access denied error you will need to take ownership first). 6. Repeat steps 4 and 5 for SMS_DP_SMSSIG$ Cheers, Hynesy
  2. If you're running updates to match patch Tuesday why not have the schedule set to run every second Tuesday of the month after MS releases the patches? Just remember to adjust to your time zone, I'm in Australia so I have it set to run at 6pm on every second Wednesday which is about 2 hours after MS releases the patches IIRC. With that said there is nothing terribly wrong here that I can see. If you log onto one of the servers/computers not getting the updates and open software centre are the updates listed at all? Trying to troubleshoot these issues are always going to be hard when you don't have complete understanding of the process involved. I'd probably start by creating a very small pilot group and follow the guide here so you can walk yourself through the entire process to get a better understanding of the whole thing. If the pilot group works you know its nothing more than a misconfigured ADR. Windows-Noob is a great site for SCCM 2012 resources, I would also have a look here as they list of great resources. Cheers, Hynesy
  3. If it's just that enabled and you're not using internet based client management you should be good on that front. Did the previous SCCM admin not utilise automatic deployment rules? (unless I'm reading this wrong?)
  4. You're most welcome. Basically with the group policy you want to make sure the policies under Computer Configurations > Policies > Administrative Templates > Windows Components Windows Update are left as "Not configured" or at the most if you only have one SUP and IBCM (internet based client management) you can probably enable "Allow signed updates from an intranet Microsoft update service location". The reason for this AFAIK is when the software update cycle is ran it updates the local group policy settings according to the local of the device. For instance we utilise IBCM to ensure the compliance for our devices to the latest MS critical and security updates, when the software update cycle is run while on the intranet it sets the SUP as the server name however if the update cycle is run while connected via the internet it will change the SUP to the public hostname for the server and connect via SSL and validate via certs. Long story short, the less configuration on these group policy settings the better haha. Cheers, Hynesy PS: I didn't proof read so I hope it makes sense/reads ok.
  5. I would check group policy to ensure the correct policy settings for SCCM are being applied.
  6. Hi lost_jedi14, AFAIK there is no way to deployment software via the application catalogue without having the ccm client installed. If you already have IBCM enabled why not install the client and allow the client be set as internet-based. Cheers, Hynesy
  7. Hi Spelaben, Are there any logs located in the C:\Windows\ccmsetup\Logs folder of the affected (but not fixed) systems? Perhaps the ccmsetup.log, client.msi.log and client.msi_uninstall.log's might should why it was uninstalled, or at the very least when. Cheers, Hynesy
  8. Hey commissar117, I solved this issue on my infrastructure, all that was required was to uninstall the reporting services point and reinstall and BAM, all green ticks. I'd seen this mentioned on various forums and posts below but I was hesitate to make the change but ultimately it was a painless and effective way of fixing the issue. Cheers, Hynesy
  9. At least I'm not the only one!!! It's been like this for close to 12 months so its very annoying but I have seen a post on answers.microsoft.com saying it was a known bug to be fixed in R2 SP1 but haven't seen anything else since. I guess I was hoping that some folks on here may have found a solution. Cheers, Hynes
  10. Hi All, I am currently managing a production SCCM R2 CU2 server with an SQL 2012 site database server and reporting services point and I have the Site System status for the SQL component server role listed as critical under System Status\Site Status. I suspect its a bug but I just want to get some confirmation. There are no errors or warnings going back weeks when view the "Messages" associated with it. I've also checked the sitestat and statesys logs and the ONLY errors I have are listed below: sitestat.log ---->: Unable to get the file system information for: \\DP1\E$\; error = 67. Not adding this volume to site object list. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 29/09/2014 9:00:00 AM 4664 (0x1238) ---->: Unable to get the file system information for: \\DP2\E$\; error = 67. Not adding this volume to site object list. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 29/09/2014 9:00:01 AM 4664 (0x1238) ---->: Unable to get the file system information for: \\DP3\D$\; error = 67. Not adding this volume to site object list. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 29/09/2014 9:00:02 AM 4664 (0x1238) ---->: Unable to get the file system information for: \\DP4\A$\; error = 67. Not adding this volume to site object list. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 29/09/2014 9:00:02 AM 4664 (0x1238) ---->: Unable to get the file system information for: \\DP4\D$\; error = 67. Not adding this volume to site object list. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 29/09/2014 9:00:02 AM 4664 (0x1238) These are just SCCM looking for drives on the DP and not finding it. sitesys.log Started task 'Update NAP Restriction Error Summary' SMS_STATE_SYSTEM 29/09/2014 8:06:20 AM 8336 (0x2090) Task 'Update NAP Restriction Error Summary' completed successfully after running for 15 seconds, with status 0. SMS_STATE_SYSTEM 29/09/2014 8:06:35 AM 8336 (0x2090) We don't use NAP. Can anyone shed some light on this, its not effecting performance or usability but it would be nice not having the component always listed as critical so when something does go wrong it's immediately obvious. Cheers, Hynesy
×
×
  • Create New...