SpecialK

Hello, I have installed a new DP on a remote location. There is still the old DP on site. So I activated the Pull DP feature for speeding up the package replication. It works like expected for round about the half of the packages. But suddenly, it stopped. So I looked up the pending packages in the console and removed the assignment from the new DP to have a "clean view". Now it looks like this in the console: So I tried to assign just one new package to the DP. This is what I get in the PkgXferMgr.log: I ask myself, why there is no sitesystem-specific sending capacity available (used 3 of 3). I would say there is no active sending to the specific DP according to the console. Is there some kind of possibility to reset the sending capacity for the DP? It's not possible for me at the moment to send any new package to the DP because of the error. Thanks and best regards SpecialK

Hello, thanks for your input. So the MP has an info about every single file in a package in the database? In my case, the package is already distributed to the DP. I just wand to add a little xml file in an (office) subfolder. But ok, if this a no go, I wait for the already scheduled deployment this weekend. Best regards

Hello, first, let me introduce myself: I'm a 30 year old IT Administrator from germany. I'm relatively new to SCCM. After a microsoft training and much testing in a test environment I'm now supporting our SCCM team. So there are SCCM related questions from time to time. Most of them I can solve with testing or looking for corresponding articles. But now there is one where I need your help: We have a big Office 2010 multilingual package deployed through all the sites. Now I had to change one little xml file in the package. But for some reasons, I can't schedule a redeploy to all DPs before the weekend. But it would be great If I could have the file at least on one DP before the weekend. So apart from scheduling, I thought, that I can cop the file manually directly to the right folder on the DP in the SMSPKGR share. But our concern is that this leads to unknown problems for example on the next planed redeploy on the weekend when SCCM tries to copy the file to the share. Has anyone of you any experiences (good or bad) with copying files manually to the share? Is this a "no go" or an acceptable way for what I want? Best regards