Change to BITS-enabled Distribution Point

Hi guys,
Sub: Change to BITS-enabled Distribution Point
Let say the DP was not BIT-enabled, and I want to enabled BITS on that DP now.
Q: Do I need to refresh/update packages inside the DP?
OR do I need to clear cache content on client e.g C:\Windows\system32\CCM\cache?
Any concerns on changing to enabled BITS on DP that I should be aware of?
Many thanks in advanced!!
---Pat

Looks like i have found the answer at least i have got it to work.
Once i install .Net Framework 3.5.1 Feature on the server, i was able to boot succesfully into SCCM Task Sequence Wizard.
I also was successfull installing the the PXE DP role from the console succesfully without having to install WDS first.
So i guess that .Net Framework 3.5.1 is required for PXE DP role on Windows 2008 R2. (but i can't see that mentioned anywhere here http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SiteSystemRolePrereqs)

Similar Messages

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Issue setting up PXE Enabled Distribution point for SCCM 2012.

I'm trying to set up SCCM 2012 in my Lab Enviroment in order to plan for implmentation to production.
I have installed and Configure one Primary site which has a working DP role width PXE /WDS.
And i am able to successfully do and OS Deployment.
I want to setup an additional Distribution point with PXE, to simulate a branch Office.
Installation of the second Distribution point looks to be succesfull, but i'm not able to boot on PXE.
It allways gives me the error messeage "The Windows Boot Configuration Data file does not contain a vaild OS entry
The same error messeage is given before i distributed the boot images (both x86 and x64)
So my thougts are that he WDS dosn't find the bootable images somehow.
I can see that the images are added to the RemoteInstall\SMSImages directory, but i also see the following in smsdpprov.log
[83C][Mon 04/23/2012 15:43:26]:Conent 'PS100004.7' for package 'PS100004' has been added to content library successfully
[83C][Mon 04/23/2012 15:43:26]:Expanding \\?\E:\SCCMContentLib\FileLib\4ABE\4ABEBA3BB557A810CBCC8148BC70FE01349142EB1BCF1C1154216B77E3E22495 from package PS100004
[83C][Mon 04/23/2012 15:43:26]:Finding Wimgapi.Dll
[83C][Mon 04/23/2012 15:43:26]:MsiEnumRelatedProducts failed
[83C][Mon 04/23/2012 15:43:26]:FindProduct failed; 0x80070103
[83C][Mon 04/23/2012 15:43:26]:MsiEnumRelatedProducts failed
[83C][Mon 04/23/2012 15:43:26]:FindProduct failed; 0x80070103
[83C][Mon 04/23/2012 15:43:26]:Found C:\Windows\system32\wimgapi.dll
[83C][Mon 04/23/2012 15:43:26]:Expanding PS100004 to E:\RemoteInstall\SMSImages
[83C][Mon 04/23/2012 15:44:48]:Registry key creation successfull
[83C][Mon 04/23/2012 15:44:48]:Registry key creation successfull
[83C][Mon 04/23/2012 15:44:49]:Registry key creation successfull
[83C][Mon 04/23/2012 15:45:23]:Conent 'PS100001.5' for package 'PS100001' has been added to content library successfully
[83C][Mon 04/23/2012 15:45:23]:Expanding \\?\E:\SCCMContentLib\FileLib\5EFD\5EFD89A7C52739DC815393C586861AFB6664FD4F28726758D6A151722D160031 from package PS100001
[83C][Mon 04/23/2012 15:45:23]:Finding Wimgapi.Dll
[83C][Mon 04/23/2012 15:45:23]:MsiEnumRelatedProducts failed
[83C][Mon 04/23/2012 15:45:23]:FindProduct failed; 0x80070103
[83C][Mon 04/23/2012 15:45:23]:MsiEnumRelatedProducts failed
[83C][Mon 04/23/2012 15:45:23]:FindProduct failed; 0x80070103
[83C][Mon 04/23/2012 15:45:23]:Found C:\Windows\system32\wimgapi.dll
[83C][Mon 04/23/2012 15:45:23]:Expanding PS100001 to E:\RemoteInstall\SMSImages
Server is a clean installed Windows 2008 R2, only added to domain, added the primary SCCM server account as local Admin, added WDS Role and configured RemoteFolder before adding DP role from the SCCM Console. (So SCCM has installed and Configured IIS)

Looks like i have found the answer at least i have got it to work.
Once i install .Net Framework 3.5.1 Feature on the server, i was able to boot succesfully into SCCM Task Sequence Wizard.
I also was successfull installing the the PXE DP role from the console succesfully without having to install WDS first.
So i guess that .Net Framework 3.5.1 is required for PXE DP role on Windows 2008 R2. (but i can't see that mentioned anywhere here http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SiteSystemRolePrereqs)

Distribution-Point sharing (SCCM 2007 - SCCM 2012)

I've some problems by gathering data from a SCCM 2007 Hierarchy, into the SCCM 2012 environment.
Gathering Data without enable Distribution Point sharing is successful, enabling Distribution Point Sharing the Process always fail.
In migmctrl.log i recogniced that the process alway stucks on the following Row for about one hour:
[Worker]:                                 Query against Legacy Site , @SourceSiteCode=KR1,
@LastID=KR10001B:                       WITH Block AS
(                          SELECT TOP 2500 ID FROM PkgStatus WHERE ID > @LastID ORDER BY ID
)                      SELECT
ps.ID COLLATE SQL_Latin1_General_CP1_CI_AS AS ID,                          ps.Type AS Type,
ps.SiteCode COLLATE SQL_Latin1_General_CP1_CI_AS AS SiteCode,                          ps.PkgServer COLLATE SQL_Latin1_General_CP1_CI_AS
AS PkgServer,                          ps.Personality AS Personality,
ps.Status AS Status,                          ps.SourceVersion AS SourceVersion,
ps.UpdateTime AS UpdateTime,                          ps.Location COLLATE SQL_Latin1_General_CP1_CI_AS AS Location,
ps.SigLocation COLLATE SQL_Latin1_General_CP1_CI_AS AS SigLocation,                          ps.ShareName COLLATE SQL_Latin1_General_CP1_CI_AS
AS ShareName,                          ps.HTTPUrl COLLATE SQL_Latin1_General_CP1_CI_AS AS HTTPUrl,
ps.State AS State,                          ps.SigURL COLLATE SQL_Latin1_General_CP1_CI_AS AS SigURL
FROM dbo.PkgStatus ps                      JOIN (
SELECT d.ThisSiteCode COLLATE SQL_Latin1_General_CP1_CI_AS AS SiteCode FROM SMSData d                           UNION ALL
SELECT s.SiteCode FROM Sites s JOIN SMSData d ON s.ReportToSite = d.ThisSiteCode AND s.SiteType = 1) s2                      ON s2.SiteCode = ps.SiteCode
JOIN DistributionPoints dp ON ps.SiteCode = dp.SMSSiteCode                          AND ps.PkgServer = dp.NALPath collate SQL_Latin1_General_CP1_CI_AS
WHERE ps.Type != 1 AND dp.Action != 3                          AND ps.ID > @LastID
AND ps.ID <= (SELECT MAX(ID) FROM Block)
And after that this Errormessage appear:
ERROR: [Worker]:                                 Failed to execute:
WHILE (1 = 1)                      BEGIN
MERGE TOP (1000) PkgStatus AS target                          USING   (
SELECT                                ps.ID, ps.Type, SiteCode = @CurrentSiteCode, PkgServer = dps.PkgServerFQDN,
ps.Personality, ps.Status, ps.SourceVersion, ps.UpdateTime,                                ps.Location,
ps.SigLocation, ps.ShareName, ps.HTTPUrl, ps.State, ps.SigURL, SiteCode as SourceSiteCode
FROM #MIG_PkgStatus ps                              JOIN #MIG_DistributionPointSource dps ON ps.PkgServer = dps.PkgServer
WHERE ID in (SELECT PkgID collate SQL_Latin1_General_CP1_CI_AS from dbo.SMSPackages_L)                             )
AS src                          ON
(target.ID = src.ID AND target.Type = src.Type AND target.SiteCode = src.SiteCode AND target.PkgServer = src.PkgServer AND target.Personality = src.Personality) -- TODO: Ensure we match an index
WHEN NOT MATCHED THEN                              INSERT (ID, Type, SiteCode, PkgServer, Personality, Status,
SourceVersion, UpdateTime,                                      Location,
SigLocation, ShareName, HTTPUrl, State, SigURL)                              VALUES (src.ID, src.Type, src.SiteCode,
src.PkgServer, src.Personality, src.Status, src.SourceVersion, src.UpdateTime,
src.Location, src.SigLocation, src.ShareName, src.HTTPUrl, src.State, src.SigURL)                          WHEN MATCHED AND (
target.Status != src.Status                              OR target.SourceVersion != src.SourceVersion
OR target.UpdateTime != src.UpdateTime                              OR target.Location != src.Location
OR target.SigLocation != src.SigLocation                              OR target.ShareName != src.ShareName
OR target.HTTPUrl != src.HTTPUrl                              OR target.State != src.State
OR target.SigURL != src.SigURL                              ) THEN
UPDATE SET                                  target.Status = src.Status,
target.SourceVersion = src.SourceVersion,                                  target.UpdateTime
= src.UpdateTime,                                  target.Location = src.Location,
target.SigLocation = src.SigLocation,                                  target.ShareName = src.ShareName,
target.HTTPUrl = src.HTTPUrl,                                  target.State = src.State,
target.SigURL = src.SigURL                          WHEN NOT MATCHED BY SOURCE AND EXISTS(
SELECT * FROM MIG_Entity me WHERE me.Type = 2 AND me.ObjectKey = target.ID)                              AND EXISTS
(                                  SELECT * FROM MIG_DistributionPointSource dpsrc
WHERE dpsrc.PkgServerFQDN = target.PkgServer AND dpsrc.SourceSiteCode = @SourceSiteCode
)                              AND NOT EXISTS (
SELECT * FROM MIG_Job job                                  WHERE Type = 3 AND dbo.fn_GetNALPathFromMIGJobConfiguration(job.AdditionalConfiguration)
= target.PkgServer                              )
THEN DELETE ;                            IF @@ROWCOUNT = 0 BREAK
END SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]:                 End syncing Distribution Points related tables. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]:         ========== End syncing distribution points ========== SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
ERROR: [Worker]:         System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.     at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler,
SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior
runBehavior, Boolean returnStream, String method, DbAsyncResult result)     at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)     at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ConfigurationManagement.MigrationManager.MigrationRepository.BulkCopyData[T](Snapshot snapshot, LegacyRepository legacyRepository, IntlSqlFormatter formatter, Func`2 watermarkFunc, T lastMaxId, Boolean doNotDrop)     at Microsoft.ConfigurationManagement.MigrationManager.MigrationRepository.BulkCopyData[T](Snapshot
snapshot, LegacyRepository legacyRepository, IntlSqlFormatter formatter, Func`2 watermarkFunc, T lastMaxId)     at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<SyncDPSettings>d__5f.MoveNext()
at Microsoft.ConfigurationManagement.MigrationManager.ExtensionMethods.<AttachErrorHandler>d__6`1.MoveNext() SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
STATMSG: ID=8610 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS="<SourceSITESERVER>" SITE=CA1 PID=2348 TID=4516 GMTDATE=Do Nov 07 11:28:33.390 2013 ISTR0=""<SourceSITESERVER>" (CA1)"
ISTR1="<DestinationSITESERVER>" ISTR2="-2146232060" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33
4516 (0x11A4)
STATMSG: ID=8605 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS="<SourceSITESERVER>" SITE=CA1 PID=2348 TID=4516 GMTDATE=Do Nov 07 11:28:33.416 2013 ISTR0=""<SourceSITESERVER>" (CA1)"
ISTR1="<DestinationSITESERVER>" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516
(0x11A4)
[Worker]: ==================== Sync Agent Job 16 Ended ==================== SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
ERROR: [Worker]: Microsoft.ConfigurationManagement.Migration.MigrationException: 1 exceptions occurred during syncing.     at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJob.<get_ExecutionPlan>d__7.MoveNext()
at Microsoft.ConfigurationManagement.MigrationManager.Job`1.ExecuteNext() SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Start processing status changed event for MIG_SiteMapping.ID=16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]:         Set the schedule item 16 end time SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]:         Set the schedule item 16 status to Failed SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: End processing status changed event for MIG_SiteMapping.ID=16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Disposing Job 16 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Removing Job 16 from job manager. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Removing the Job with Id 16. SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Disposing worker SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
[Worker]: Disposing current site connection SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131500, 80131500 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
ERROR: [MigMCtrl]: FAILED to EXECUTE job. error = Unknown error 0x80131500, 80131500 SMS_MIGRATION_MANAGER 07.11.2013 12:28:33 4516 (0x11A4)
In the StatusMessages of Migration_Manager there are the following Errormessage:
The Migration Manager on Configuration Manager site server "<SourceSITESERVER>" was unable to complete the SQL operation on the SQL Server "<DestinationSITESERVER>" of Configuration Manager 2007 due to error "-2146232060".
Thanks in advance

Hi,
1.Please examine reports “All active package distributions” on SCCM 2007 to check whether have package is currently being installed or removed. Then refresh all DPs on SCCM 2007.
After completing these actions above, try to re-gather data.
2.If fail, please check the transaction log both on SCCM 2012 and SCCM 2007 SQL Server. Then, a SQL engineer should be involved in this case.(This forum do not support database issue)
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Migrate Secondary to Distribution Point - RTM

Hi,
quick question about a request made in my environment:
We have a huge number of useless secondaries (< 100 clients) over the infrastructure. I would like to change that and use Distribution Points instead of Secondaries.
What i'm looking to do is transform the secondary to a distribution point (easily / scripted).
2 blocking points:
- Server must remain the same and formating is not an option
- RTM Version of SCCM 2012 (doing this to prepare the update this summer and avoid migrating too many secondaries).
If not possible easily then the only option i see is to fetch the list of packages on the DP (All content on a specific distribution point) and create manually the prestage content for each package. But that would take so long that i want to avoid it.

You'll need to test -- as I never have explicitly -- but as long as the long sccmcontentlib folder remains in place and unchanged, a simple uninstall of the secondary and deployment of the DP role *should* (to my knowledge) re-utilize the content (this
isn't explicitly by design either, it's an artifact of the repair process so may not be esxplicitly supported, but it is just content after all). You'll of course have to reassign the content to the DP (which would be really easy if you're using DP groups
or could also be done with PowerShell).
Jason | http://blog.configmgrftw.com

Change "Update distribution points on a schedule" in SCCM 2007 via powershell script

Hi
I would like to change the Custom Schedule start time in the "Update distribution points on a schedule" on a package in SCCM 2007 with out logging into the SCCM console.
I have following line code to query the package.
Get-WmiObject
-Namespace
"Root\SMS\Site_$sitecode"
-Query
"SELECT * FROM SMS_PackageBaseclass WHERE PackageID='$PackageID'"
-ComputerName $ServerName
The problem is I only get the "SourceDate" and "LastRefreshedTime" from the query. I am not sure if I change the "LastRefreshTime" that it would change the start time in the Custom Schedule

Hi Jason
I progressed a little bit with you help. I now have the following bit of code.
$Package = Get-WmiObject -class SMS_Package -Namespace "Root\SMS\Site_$sitecode" -Filter "PackageID='$PackageID'" -ComputerName $ServerName
$RefreshPkg = $Package.RefreshSchedule()
$RefreshPkg.RefreshSchedule
I get the following error:
Method invocation failed because [System.Management.ManagementObject] doesn't contain a method named 'RefreshSchedule'.
At line:7 char:1
+ $RefreshPkg = $Package.RefreshSchedule()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (RefreshSchedule:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

Enable PreStaged content on a distribution point.

I would like to enable Prestaged content on two current distribution points that already have content on them. I am assuming after I enable them I will still be able to use the option to Automatically download content to the distribution without presaging
it? (When a distribution point is not configured for prestaged content the content is automatically set to download when the package is assigned to a distribution point?)
Also if I have some packages that are set to Manually copy content do a distribution point (I don't know why this was set since our distribution points were not enabled for prestaged content yet) will they still work?
Is there a way to query for packages that have the distribution settings set to Manually copy?

So essentially if "Enable this distribution point for prestaged content."
is not selected on a distribution point, the content behavior for all packages is "Automatically download content when packages are assigned to distribution
points"?
If "Enable this distribution point for prestaged content."
is selected on a distribution point, and the distribution settings for a package is set to "Download only content changes to the distribution point". Does
the first time the package get deployed it need to be prestaged or will it fully copy the content the first time and then just update the changes?
My distribution points are not really network resource constrained but I would like to be able update images and software update packages with just updated content. I won't necessarily ever need to prestage content.

SCCM 2012 - Change Distribution Point's Site System Properties Site Code

Hello All,
I'm hoping someone can help me out. Here's what I have and here's what I'm trying to do.
SCCM 2012 R1
Each of our offices has a Windows 7 SP1 Ent PC that is a distribution point for that office's 10-20 machines. A number of these offices and their DPs were setup prior to me setting up a number of Secondary Site Servers. So right now, these DPs' site codes
are the primary site server's. I'd like to change these to one of the Secondary Site Servers.
When I go to the Site System properties of one of these Win7 distribution points, the Site Code is grayed out.
So, the question is, how can I change one of these DPs' site codes?
Thanks in advance to whomever helps!!
Bill

That's a strange reason for using Secondary Sites. How many clients are you managing? Have you good WAN links?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Distribution Points properties changing permissions

Hi everybody!
How can we use RBA to lock down branch's admins DP properties changing permission....?
Branch admin's could change PXE properties and etc.....Could we let them work with DP object only in read mode?
In their role permission properties there are only "Read" and "Copy to DP" mark above "Distribution Point" object, but they still could change assigned to their scope DP's properties((

You've got to remove the Modify permission on the Site
object. In case you do want them to be able to modify other site settings, you can also create an additional scope configured to the specific distribution point. Then combine that scope and the role with less permissions on the site object together
on the administrative user and you achieved your goal.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Problem with option: enable this distribution point for prestaged content

Hi, for past few days I have been focused on application deployment with SCCM 2012 R2 (I am learning SCCM 2012 R2 reading books, watching video trainings . . .). Having followed allong book Mastering System Center 2012 R2 Configuration Manager I also did
deployment of Microsoft Office 2013, Adobe Reader 11, Foxit Reader 4.2 and Notepad ++ to test collection containing one Windows 7 computer. In one of examples prestaged content file is created for Foxit Reader application. In order to do so, if I am
right, option Enable this distribution point for prestaged content
has to be checked on distribution point and I did that.
Problem is that I noticed deployment of any application to test collection failed every time - system waits for prestaged content file if this option is selected. Then I have to delete deployment of given application, application itself, deselect option
Enable this distribution point for prestaged content and create app, distribute it to DP and deploy to test collection - then everything works well.
To make things worse, having deselect option Enable this distribution point for prestaged content (I did it yesterday and I checked that several times) this morning I checked again and this option is selected again. What might be the cause
of this behaviour? I expected this option to be deselected - this is weird to say at least.

When you enable the option "Enable this distribution
point for prestaged content" on a DP, it causes newly created applications/packages to default to "Manually copy the content in this package to the distribution point"... This would then cause the deployments on the clients to remain
at 'waiting for content' - unless if you manually prestage the content, as this option requires it.
If you enable the option "Enable this distribution
point for prestaged content" on the DP, but want to automatically have CM distribute the content, then configure the app/package to do so,
before distributing the content: Distribution Settings tab > Prestaged distribution point settings > Automatically download content when packages are assign to distribution points.

Server 2012 Distribution Point - Is BITS Required ?

Hi All,
I have deployed a Distribution Point on Server 2012, i went through the documentation and there was no mention of BITS being a prerequsite...
So my Question is - Do we still need to install BITS as a prereq for the Distribution Point Role on a Server 2012 box.
Cheers

There still seems to be some contradictions on whether you are supposed to install BITS or not when setting up a Distribution Point.
http://technet.microsoft.com/en-us/library/gg712264.aspx under the section
"To install Internet Information Services (IIS) on Windows Server 2008 and Windows Server 2008 R2 computers"
clearly shows for Windows Server 2008 R2, select the
Background Intelligent Transfer Services (BITS) check box.
If you look at http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs under the Distribution Point prerequisites, there
is no mention of installing BITS unless we are to assume the statement "You can use the default IIS configuration" means to select BITS as described above?
Plus the following note under Additional prerequisites is as clear as mud.
Note
With System Center 2012 Configuration Manager, 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.
Most of us understand the client facilitates the BITS downloads but is there still a need for the
BITS Server Extensions and the only way to get those on a Server 2008 R2 box is to select the
Background Intelligent Transfer Services (BITS) check box?

Pull Distribution Point Requirements (BITS?)

We have recently migrated to all SCCM 2012 infrastructure. All of our recent deployments are Server 2012 but we have a lot of Server 2008 R2 64bit. There is a lot of documentation online and some say BITS is required for DPs and some say not. Our packages
have been struggling to reach our DPs and Pull DPs. Does anyone have any opinion if BITS should be installed on DPs or Pull DPs. I know I have read that BITS is not required on Server 2012 however it states nothing about Server 2008 R2 64bit. Any opinion or
experience would be helpful.

Nothing specific to Pull DP...
Windows Server 2012 or Windows Server 2012 R2:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_Win2k12SiteSystemPrereqs
With System Center 2012 Configuration Manager, 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
A pull-distribution point is considered to be a client when it accesses another distribution point to obtain content.

Question about locking down IIS on an SCCM 2012 distribution point on a Windows Server 2003

Hello. My environment is SCCM 2012 SP1. I will be setting up several distribution points on Windows Server 2003 machines. This summer I have a project to configure SCCM to use our PKI infrastructure. Unfortunately, this will not be in place before I need
to set the Windows Server 2003 machines up as distribution points. I am not an IIS expert. When I set the DPs up, I am only 1)Installing IIS, 2)Enabling BITS extensions, and 3)Enabling WebDav. Is there anything I should do to ensure they are as secured as
possible?

I would say that installing Windows Server 2003 is not "as secure as possible" due to it's end of support coming soon.
http://support.microsoft.com/lifecycle/default.aspx?LN=en-us&p1=3198&x=10&y=12
And I would say that we need more information about your scenario to tell you how it is as secure "as possible". Since that would be shutoff at the bottom of the ocean. But that wouldn't be that useful server.
Im guessing that you will run these servers for internal
clients ONLY. And that you have a decent edge protection as well as physical protection. Then I would start by having the lastest secrutiy patches, running antivirus software and having the firewall turned ON. I would make sure that
only necessary logons would be possible and that the servers wouldn't cache any credentials. Typically a DP NEVER holds sensitive data so no real need to secure them more than that in a normal scenario if you ask me.
A final notice, this is a baseline
for a common scenario. You would need to scale and change that
in order to apply for your scenario.
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Critical Errors SCCM 2012 (Distribution Point and Reporting services point)

Hello,
We are getting errors under the Site Status for the Distribution Point and Reporting services point. Was running fine and have not really made any changes but all of a sudden we have these critical errors.
The report server service is not running on Reporting Service Point server "XXXXXXXXXXX"; start the service to enable reporting.
We have stopped and restarted the SQL 2012 reporting service point with no errors. What else should we look at for this error? And are these related?
Thanks,
Bobby

Hi,
Have you checked the log file SRSRP.log?
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)

Hello!
Scenario
Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
errors indicate that this software can'tbe downloaded.
In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
Problem
The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
were reinstalled. A fresh install didn't detect the NAA.
Solution
After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
domains aren't approved automatically (by default).
In this case something as simple as an Approving the client fixed these issues.
The DataTransferService.log highlights the issue:
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="1" thread="3136" file="dtsjob.cpp:3501">
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
<![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="3" thread="3136" file="dtsjob.cpp:3513">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.h:166">
<![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
{38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download. Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="2" thread="3136" file="dtsjob.cpp:3652">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.cpp:3205">
<![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
thread="3136" file="netaccessaccount.cpp:288">
<![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
type="1" thread="3136" file="netaccessaccount.cpp:858">
<![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
(0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
The IIS server logs u_ex150219.log captures the request:
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 2 5 1509 2
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 4
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 3
2 x Domains: DomainA and DomainX
- Single domain forests
- No trusts between domains/forests
DomainA\PRIMARYSERVER
- Primary Site Server, MP, DP, IIS, all roles
DomainX\DP1
- Distribution Point, IIS, etc
- CCM client installed

Based on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
Jason | http://blog.configmgrftw.com | @jasonsandys

Change to BITS-enabled Distribution Point

Similar Messages

Maybe you are looking for