Search the Community

Hello We recently moved our sccm on prem server to the azure cloud , since this move we are having issues with building devices. Basically we transferred the pxe from the main server as it is in the cloud to our on prem distribution point so we can now pxe boot and get the screen to kick of the task sequence , but now i am seeing it is missing so many applications and customizations i did, I already distributed all packages to the on prem distribution point. I have tried all sorts its been like this for a week now but i am not sure what else i can try next. Thank you tnt_115

Dear Admin, My Apologize - I feel to raise this Question separately to make myself clarity on asking question and getting answer, As per the previous post, Phase I : Upgrade from SCCM 2012 SP2 to SCCM CB V1606 At Present, the Environment is having as below and mentioned with To - BE State After Successful, Completion with Phase I - Progressing Phase II as follows (As-IS and To-BE Infra) Please Validate if the As-IS to Phase I, II (To-BE) is Okay / Please suggest if any changes Kindly suggest me, My Sincere sorry if there is any repeated questions. I feel to get some added advice from you for MDT, ADK. At Present, We are using AS-IS Infra (SCCM 2012 SP2) with Operating System Windows 7 SP1 1. Application Deployment 2. Patch Deployment 3. OS Deployment *With Windows 7 SP1* We Continue with the same for all 3 above, and added to that Windows 10 OS as well with New Infra (Phase II SCCM CB V1710) Looking for your response and mentorship Regards, Veera

Hello everyone, I am setting up IBCM and am looking at the DP cert requirements. In the TechNet documentation and walk throughs, this cert is often configured for auto enrollment from ADCS with private key marked exportable. There's no mention of Subject Alternative Names... but my spidey sense is that I need them to share the cert properly. My question is, if I have a primary site server and an Internet site server (for IBCM), would I need to request this cert with SANs? Would the SANs need to include the internal server name, the external server name, AND the Internet FQDN name? And then I would install this cert on both servers? (Update) I failed slightly at reading comprehension, a different TechNet page than I originally reviewed DOES at least say this about the DP cert: https://technet.microsoft.com/en-us/library/gg699362.aspx "There are no specific requirements for the certificate Subject or Subject Alternative Name (SAN), and you can use the same certificate for multiple distribution points. However, we recommend a different certificate for each distribution point." Interesting. So I can share the cert, but they suggest not to. And the SAN doesn't seem to matter. But is this really true? Anybody who's implemented can verify one way or the other how they did it? Thanks.

Hi, We are currently running SCCM 1606, and have a mix of Win7 and Win10 images. The probleme is the updated WIM file is not being updated on the DP, there is no error message, it shows up updated time stamp, however the image is not updated and keeps the same size. I'm thinking to delete the current image from the DP then distributing the new one Have you ever seen that before?

Hi, In my environment I have 3 locations for Operation System Deployments. Each one has its own DP and boundaries group. We have a very slow OSD process in one of them (3-4 for one deployment, other DPs take less than an hour) The only difference betwen the slow DP and the others DPs is that it's a VM with WS 2012. The other two DPs are WS 2008 and they are physical servers. We tried to change the NIC on VM Server with no luck. We also checked possible networking issues with the infraestructure team and we didn't notice any problem. Do you guys think that it could be a VM problem? Any help would be appreaciated Thanks and regards

Hi everyone, Currently, our company has 2 sites(Site A, site B)in different locations, and we already setup 1 SCCM 2012 R2 server in site A which as a primary server to deploy software, OS, patches to all PCs in 2 site. So my boss wanna build one more server to reduce its resource requirements and improve its performance as well as to load balance the potentially significant network traffic generated by clients downloading package source files. I found out 2 solutions: Solution 1. Setup one distribution point in Site B, so boundary group in site B will get applications, patches content from this new DP, and boundary group in site A still get a content from old one. So if I distribute 1 application contents from DP A to DP B, will PCs in site A will get software content from DP B? For example: In SCCMconsole, I select Winzip, click distribute content, then select DP B, so the PCs in site B can be deploy Winzip quickly right now, but how about PCs in site A, it will deploy from DP B as well, make it slowly, how can I get rid of this issue? Solution 2. Setup 1 secondary SCCM server in Site B, but with this solution, do I need to build 1 more server for central administration site(CAS), thus need 3 servers for SCCM(1 CAS, 1 primary, 1 secondary), is it possible if I just create secondary site without CAS? Actually we just have 400 PCs , no need to build hierarchy with CAS. I'm new in SCCM, so I don't know how to fulfill the requirement, pls advise Thanks so much.

I have a single primary 1606 site, I went to configure the Site System Prerequisites on a new DP I was rolling out on Windows Server 2012 R2, I reviewed the following TechNet article https://technet.microsoft.com/en-us/library/mt752493.aspx, which was last updated 2016/07/22 there is a note that clearly states " The distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS." I'm confused, does SCCM Current Branch use BITS anymore?

Hi everyone, I am facing a strange issue. After distribution of 3 applications (not packages) failed on a DP, i decide to remove those from the DP by doing this trought the DP propertiets (content tab) Now i am trying to distribute again those application to the DP, but never distributed. The DP is always shown in available DP. Is somebody have an idea ? I can't recreate the applications because we have so many DP and PullDP. Thanks Gvlaarho

Our environment contains a CAS site and 3 Site servers. Currently each site server has 1 DP and 1 MP. Because of a firewall and various security limitations, we are setting up a new DP, MP and update point that reports to one of the existing site servers. We use SCCM for OS Deployments. We Use Site Based boot media today. I do not see the benefit of selecting dynamic Media option when creating a boot disk because I still have to enter in a DP. So in my existing setup, does it just make sense to still use Site base media but have 2 boot disks for my one sccm site that has 2 MP and DPs. All the computers that report to the 2nd MP/DP will in their own boundary I haven't investigated what I am going to do with DP groups. Currently we don't use them.

My task sequence fails with - "this task sequence cannot run because the program files for 00100002 cannot be located on a distribution point" (00100002 is config manager client). Does anyone have any idea why? I notice that my client package says 0 programs and has DEPLOY greyed out, so cant be deployed. Has anyone seen this before? the 'version' field is also blank

Hey Guys / Niall - I recently started in a new position to help implement and advise on SCCM 2012 (1511) as well as the setup of all features including converting them from using imaging to OSD, Application deployment, Software Updates, etc - at least all the basics except for Forefront. Quite a task, but sounds fun to me. I learned something today which I'm questioning so wanted to post and get opinions. I've implemented SCCM in about 5 production environments before and for each one; have had at least a distribution point at each local site. If a site didn't have one; it was understood that they would only experience limited support. Today, I found out that our multiple point site will only have a total of 3 DPs - and - they were told this would be ok by Microsoft - even for using OSD at each one. Microsoft's Recommended Plan The ~30 locations are spread out around the country. Each of these 30 locations connects to one of 3 datacenters via various speeds of connection like T1, 500k, (some fast, some really slow). I was told that "Microsoft advised" that it would be ok for them to create a distribution site (they are actually doing secondary sites) in each of the 3 datacenters. The primary server (4th site server) is offsite from the corporate office in a datacenter that we have a 100mb connection to. Overall I understand that having a 100mb connection to the primary may not be the worst thing ever for doing something like OSD if only running 1-2 at a time, but cannot imagine supporting OSD at all 30 of these locations with the setup above - even with BranchCache - not to mention all other services. So - what are your thoughts? Am I just crazy to think this or do you believe we have a problem on our hands? Thanks Guys!

I need help with Software Updates on SCCM 2012. Client machine has "Downloading (0% complete)" in the Software Center for every update. There are about thirty updates that apply to this client machine. What I have done: Created an Update List Created a Deployment Package with the Updates. Downloaded the Updates and distributed the content to a DP. Content status is success. A Boundary is defined for the client. The Boundary is in a Boundary Group. The Boundary Group is assigned to the DP. The Deployment for the Update List is targeted to a Collection with one machine in it. Updates are ​available as soon as possible. Updates are mandatory at a future date. Why are the updates all "Downloading (0% complete)" in the Software Center? Am I missing something? Thanks.

I have an SCCM 2012 R2 distribution point that was accidentally reinstalled (the DP role removed, then re-added - no content was deleted) the packages and content library are all still on the DP, is there any way to get the reinstalled DP to recognize and associate with the now old content? it seems like it should just be a matter of recreating the content mapping, but I have no Idea how to do that. Please help!

Hi! I have various computers in the correct bounderary (correct IP og AD), but connectingen to a DP outside that bounderary.... someone has an idea how to tackel this one ?

I have a 2012 R2 SP1 primary site that is servicing the main campus of the University I work at. All the site servers are located in the main campus data center. We also have a remote campus about 15 miles away from the main campus which utilizes the the servers in the main campus data center. For the most part this hasn't caused any issues, however when techs at the remote campus try to PXE boot and image a device, the TFTP portion of the boot process takes 10+ min to download the boot image as opposed to the 30 sec it takes on the main campus. Compounded when imaging multiple machines at once, 10 minutes turns into 20, 30, and so on, and is not feasible for the techs at the remote site. We have worked with our network engineers to verify that there were no problems on the network causing this difference and after A LOT of testing we determined that everything is working correctly as it is currently designed. The time difference comes from how TFTP works with the whole send 1 packet, receive 1 packet process. On the main campus, this isn't much of a problem but the minuscule bit of extra time between packets going back and forth from the main campus to the remote campus adds up to the extra time in the boot process (we actually drew out the math). So now, half of us are of the mind that we need to put a DP at the remote campus wants to start doing registry hacks and messing with DLLs to increase the TFTP window size. Is there any criteria (Physical distance, bandwidth, latency, clients managed, etc) on when it is appropriate to place a DP (or any other roles) at a remote site? Any documentation I can show about the matter would be helpful. Thanks!

Hi Everyone Strange problem we seem to be getting - wonder if anyone else has found the same issue... Standard task sequence for deploying Windows 7 x86 and some standard software, used on 7 remote sites each using a local distribution point One site seems to keep failing, on installing a custom application. Same task sequence works on other sites without issue on same make and model of machine Rebuilt the distribution point onto the same hardware, from Svr2008 up to Svr2012R2 - still failed task sequence Built a new DP as a virtual machine for testing - distributed content needed - failed the task sequence Convert the application to a package and it works fine! - but that seems to be a step backwards, and the TS works without issue at all other sites! Anyone have any ideas on what to look at or try? Thanks John

Hi All, Has anyone ever written a script or report to pull out packages and applications which are not distributed to any DPs? We are wanting to do some cleaning up of our source folder... Thanks John

Hello, I recently installed CM 2012R2 as a single site with SQL server and 7 disk drives on the same machine. Now when I'm checking site system status, the distribution point Site system role is installed on all disks. Is it normal?

We are having a very difficult time locating any posts, forum topics, or ms bulletins in regards to the attached distmgr.log file. If anybody of you knowledgeable helpful users on the forum can assist in ANY way, please feel free to offer any suggestions. We currently are unable to distribute any new data, sync dp's, etc... We have performed a site reset. We have removed MP role. We have removed and replaced the mentioned file. Kind of at a loss. Short of rebuilding the main site server, I'm not too sure as to our next step. Any assistance would be greatly appreciated. Thank you in advance for your time and assistance. distmgr.log mpcontrol.log

Hi i have struggling with some of my distribution points, when i look at the \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status it reports as my DP all green and fine. but i had some of our engineers complaining applications were not downloading. When i looked into it the content was missing. so I used the SCCM toolkit, and the content library explorer, i noticed there were many packaged greyed out with a (PENDING) at the end. but when i checked the DP List there was no distribution happening. so i have to basically go back to the application and redistribute them. why is it miss reporting ??? any pointers appreciated

Hi all, Background We’re running SCCM 2012 R2 CU1. It’s a single primary site with a physical Site Server, six virtual distribution points, and a physical SQL cluster. Our physical site server hosts, among other things, the distribution point role and has a 600GB drive for packages and the content library. It’s in a distribution point group with the six other DPs and customers distribute content to that group rather than to the DPs individually. Question Recently we started getting close to the hard 600GB limit on our primary site server, so we started thinking through our options. Buy more drives? Can’t, we’re maxed out. Buy bigger drives? We can, but how big should we get and is that the best option for us? It seems like the best option would be to remove the DP role from our physical site server and just let that role live on the virtual servers with drives that can be grown easily. Our thoughts were to Perform our maintenance in the off-hours and apply a maintenance window to keep people from doingthings. Pull the physical site server from the DP group Remove the DP role from the physical site server Lift the maintenance window so people can do things again Does that plan seem sufficient? Are there any gotchas to look out for? How does this affect any active or ongoing deployments that may be out there? If a computer is stuck waiting for content from our physical site server, how can we tell it to move on to the next available DP? All the documentation out there says how to remove the role, which isn't hard, but doesn't really go into any detail. So either it's very easy and we're over complicating things or you're just not supposed to do it. Thanks in advance for your help and thoughts!

Recently a new drive was installed on my remote SCCM 2007 distribution point. This new drive (F:) was larger and had more space on it than my previous drive designated to be used for my packages (D:). After distributing and updating a few packages, I realized (too late) that these files were being copied to drive "F:". I tried to reverse this process by creating a "NO_SMS_ON_DRIVE.SMS" file on drive "F:", but apparently this is not how this works. I now have these issues: The SMSPKGD$ share no longer exists In the database packages that have not been added or updated since the new drive was added still point to SMSPKGD$ for this DP and now do not work Packages that existed before the new drive was added that have been updated since the new drive installation now have package files on both "D:" and "F:" and will not install on clients properly. I believe this is because the SMSSIG$ directory on the original drive "D:" still holds the package signatures for these packages and there is not a matching package signature in the new SMSSIG$ directory on "F:". I would like to be able to do the following (if possible): Change the drive that SCCM uses on this distribution point server from "F:" to "D:" Prevent the "F:" drive from being used for SCCM packages Copy the packages and signatures from "F:" back to "D:" Update the database pointers for these packages on this DP to "SMSPKGD$" instead of "SMSPKGF$" Perform these steps without having to purge the files from this DP. I believe this last point is the biggest sticking point as this DP is remote and it would take a large amount of bandwidth and time to re-copy these packages back to this DP. It also seems silly to have to remove and re-copy files over the WAN that are already on that server to begin with. Any guidance or assistance that leads me to be able to fix this "in-place" would be a godsend and a huge time saver.

Hello, Im facing this log entries in DISTMGR.log file. Package 'PAK0002D' is found in active queue, will try it later Package 'PAK0002E' is found in active queue, will try it later Sleep 3600 seconds... Though these packages are not listed in Configmgr packages, i have searched individually in console also in WMI by using WMI query but there is no entry for this package file. But DistMgr.log file continuously prompt these logs. I have attached snapshot for furthure reference.

Hello All, My team lead wants to know from which DP client is downloading the package. As we are going to deploy DP on windows 7 computer in our site which is composed of approx 100 clients.

On my site distribution points, I am having an issue with after installing them that the SMS_MULTICAST_SERVICE_POINT comes up as critical under component status. This is because the mutli cast is not being installed for some reason. In teh status Message Details, i recieve this message, "Site Component Manager failed to install this component, because the Microsoft Installer File for this component (mcs.msi) could not install." in the mcsMSI.log.LastError I see these messages: Property(S): System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61 = C:\Windows\system32\ Property(S): SMSCACHEDIR = Default Property(S): SMSCACHEFLAGS = Default Property(S): DISABLESITEOPT = Default Property(S): DISABLECACHEOPT = Default Property(S): SMSCACHESIZE = 5120 Property(S): SmsShellNotify_ActionText = Notifies the shell for the file-association icon changes. Property(S): CcmInstallMCS = D:\SMS_CCM\ 0 Property(S): WDS_ActionData = WDS Property(S): WDS_UnregisterActionData = WDS_UNINST Property(S): SmsMCSDetectDowngrade_ErrorMessage = A newer version of the SCCM Multicast Service Point is already installed Property(S): ARPSYSTEMCOMPONENT = 1 Property(S): ARPNOREMOVE = 1 Property(S): ARPNOMODIFY = 1 Property(S): MCSENABLELOGGING_Default = TRUE Property(S): MCSLOGLEVEL_Default = 0 Property(S): MCSLOGMAXSIZE_Default = 2000000 Property(S): MCSLOGMAXHISTORY_Default = 1 In the MCSSetup.log I see this: <05/12/14 15:14:16> ======== Completed Installation of Pre Reqs for Role SMSMCS ======== <05/12/14 15:14:16> Installing the SMSMCS <05/12/14 15:14:16> Machine is running Windows Operating System or later. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> IIS Service is installed. <05/12/14 15:14:16> Created the DP mutex key for WDS. <05/12/14 15:14:16> Created the DP mutex value for WDS. <05/12/14 15:14:16> Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> WDS is INSTALLED <05/12/14 15:14:16> WDS Service is installed. <05/12/14 15:14:16> No versions of SMSMCS are installed. Installing new SMSMCS. <05/12/14 15:14:16> Enabling MSI logging. mcs.msi will log to D:\SMS\logs\mcsMSI.log <05/12/14 15:14:16> Installing D:\SMS\bin\x64\mcs.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 MCSENABLELOGGING=TRUE MCSLOGLEVEL=1 MCSLOGMAXSIZE=1000000 MCSLOGMAXHISTORY=1 <05/12/14 15:14:27> mcs.msi exited with return code: 1603 <05/12/14 15:14:27> Backing up D:\SMS\logs\mcsMSI.log to D:\SMS\logs\mcsMSI.log.LastError <05/12/14 15:14:27> Fatal MSI Error - mcs.msi could not be installed. <05/12/14 15:14:27> ~MCSRoleSetup(). <05/12/14 15:14:27> Stopping wdsserver service <05/12/14 15:14:32> Starting wdsserver service <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\McsIsapi <05/12/14 15:14:32> RegOpenKeyEx failed for Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegWriteDWord failed. 80070002. <05/12/14 15:14:32> ReleaseDpMutexForWDS: Deleting the DP mutex key for WDS. <05/12/14 15:14:32> ~MCSRoleSetup() - 00000000 <05/12/14 15:14:32> ~RoleSetup(). Any hep with this is greatly appreciated