What and Where you can control the Network Bandwidth

Ok.. Now you want to know here are all the bandwidth can be controlled in SCCM

 

Package Movement	Bandwidth Control	Uses Binary Differential Replication?
From package source directory to site server	None.	No
From site server to standard distribution point	None.	Yes
From parent site server to child site server	Bandwidth controlled by Address settings on the sender between sites.	Yes
From child site server to child standard distribution point	None.	Yes
From standard distribution point to branch distribution point	BITS or manually pre-staged on the branch distribution point. For more information	Yes
From standard distribution point to client	BITS, if BITS-enabled distribution point is available and advertisement is configured to download and run locally.	No
From branch distribution point to client	None.	No

SCCM Senders End to End

Senders can be configured on only Primary and Secondary sites, the use of senders are instead, senders use existing network connectivity to manage the connection, ensure the integrity of transferred data, recover from errors, and close the connection when it is no longer needed.

Types of Senders : 6 types

1) Standard Sender

The standard sender is installed and configured by default on all primary and secondary sites. If your site-to-site communications occur over a LAN that uses a supported protocol, you do not need to install another sender.

if you want to apply some bandwidth restrictions between site to site communication. here are the options for Standard Sender.

 

 

2) Courier Sender

The courier sender is installed and configured by default on all primary and secondary sites. It is not displayed, and cannot be created, in the Configuration Manager console because it must be manually started from the Configuration Manager programs folder on the Start menu. Courier senders are used only for software distribution to send package data to other sites by using physical media instead of sending data over the network. To use the courier sender, you must first create a standard sender connection between the parent site and the child site. Once the standard sender is created, you then create a courier sender address for each site to use the courier sender functionality.

When you have large packages that require excessive time or bandwidth to be sent over the network, this sender can be useful. You can use courier sender at the source Configuration Manager 2007 site to create a parcel (that is, a collection of files transferred from one site to another using courier sender); write the parcel to a tape, CD, or other physical medium; and then ship the tape or CD to the destination site by mail or a courier service. At the destination site, you can then use courier sender at that site to receive the parcel and import the package data into the site.

Note :- The courier sender is installed and configured by default on all primary and secondary sites. It is not displayed in the results pane because it must be manually started from the Configuration Manager 2007 program files on the start menu.

3) Asynchronous RAS Sender

Used for communication over an asynchronous line.

4) ISDN RAS Sender

Used for communication over an ISDN line.

5) X25 RAS Sender

For RAS communication over an X.25 line.

6) SNA RAS Sender

For RAS communication over an SNA link.

Ok.. Now if you in confuse what to use in your network after reading the above, Just check the below table you will get some more clarity where what type of sender you can use

Existing network connectivity between sites	Sender
LAN or WAN	Use Standard Sender, the most commonly used sender, for sending to other sites on the same LAN, or on a WAN using routers, switches, or bridges.
Asynchronous line	Use Asynchronous RAS Sender for RAS communications over an asynchronous line.
ISDN line	Use ISDN RAS Sender for RAS communications over an ISDN line.
X.25 line	Use X25 RAS Sender for RAS communications over an X.25 line.
SNA	Use Systems Network Architecture (SNA) RAS Sender in RAS communications over an SNA link.
No Connectivity to your office or None	Use Courier Sender to send packages between the sites by using removable media instead of network wiring and protocols if you have a slow or unreliable link between a site and its parent. Courier Sender is used only for package distribution, not site-to-site communications.

For my all Primary Site i have open the communication to be open all the time however for secondary sites i have done below recommendation based on the bandwidth and  clients size : this is again for Standard Sender

WAN Link Speed	Time (Local time)	Monday – Friday	Saturday	Sunday	% of Available Bandwidth	Pulse Mode Settings
64Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		20KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		20KB every 5 seconds
128Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		40KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		40KB every 5 seconds
256Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		80KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		80KB every 5 seconds
384Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		100KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		100KB every 5 seconds
512Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
1024Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
1536Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
2045Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
3072Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
5464Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%

 

Pulse mode configure options

In real World :- You will use only Standard Sender

What is SMS_SiteSystemToSiteServerConnection & SMS_SiteSystemToSiteServerConnection group

Site System to Site Server Connection Group:

 

The Site System to Site Server Connection (SMS_SiteSystemToSiteServerConnection_sitecode) group grants the necessary permissions for Microsoft System Center Configuration Manager 2007 services running on remote site systems (such as management points) to connect to the site server to access the Configuration Manager 2007 registry keys and directories on the site server. if you are runing any below role this group should be part of remote site

Servers hosting the following site system roles should be members of this group, unless they are in a remote, untrusted forest:

• Management points - MP
• System Health Validator points – SHV
• State migration points 
• Fallback status points
• Software update points
• PXE service points
• SMS Provider computers
• Asset Intelligence synchronization point (Configuration Manager 2007 R2)
• Out of band management point (Configuration Manager 2007 SP1)

 

Site to Site Connection Group

This group has the necessary permissions for a sender to connect from one Microsoft System Center Configuration Manager 2007 site to another.

 

Note both should be local /Domain Local Group membership only

You need to know this by end –to end

 

below is a sample and I am making up this for final Just pushing out from my inbox that’s alll

Hierarchy

Limitation of SCCM

http://configmgr2oo7.blogspot.com/2010/08/limitations-of-sccm-2007.html

Adding a secondary site to a primary site

Sender limitations for packages

SCCM Console Not connection
SCCM Services
SCCM Client Services
Discovery – DDR record

Boundary – IP Subnets vs AD Site name
Site to Site communications

MP Problem

DP Problem

RP Problem

OSD Problem
WOL Problem
WOL Configuration

WOL Unicast Vs SubNet broad Cast methods

Native Mode Configuration

Installing SCCM on Windows Server 2008
Office 2007 Deployment With SCCM
MSI packaging Story
Inboxes Checks
Daily Checks
Weekly Checks
Backup and Recovery

Multicasting on

DP

OSD Advantages

SMS 2003 to SCCM 2007 Migration

1) In place

2) Side by side

3) In place upgrade on new Hardware

Site Code auto detect problem

Schema extending and publishing

IE Important products

Branch Distribution Point Vs Nomand Branch DP

Night Watchman Vs SCCM R3 Power management or WOL

SCCM WOL Vs IE WOL

Client Installation Methods

Site Maintenance

Obsolete Clients

Delete Old H/w and S/w or S/w Metering Inventory date

Backup Configure

After backup

no_sms_on_drive.sms file

Collections:-

Software Distribution:-

Program

Package

Distribution Points

Software Updates:-

Search Folder

Update List

Severity

Required

Installed

Suppressed

Expired

Every month releases

License review

Review and accept

Update List merge or Master Update List / Cleaning up Update List

Deployment Templates

Deployment Management

Deployment Packages

Sync Software update:-

OSD:

Boot Images:-

Computer Association

Reference Computer

WIM

Install packages

Operating system Images

Task Sequences

Drivers

Driver packages

Unprovisioned Computers
Task Sequence

MDT Integration

AI:-

How to enable AI

What are the Catalogs?

Software metering

Reports

SQL Web Based Reports

SQL Reporting Service point

Limitation of Reporting Point

WQL Vs SQL

DCM

CI Types

Base Lines

Remediation

Collections Query(s)

Site Status

Components status

Auditing for modification on the console by user / team / group /site

View audit messages based on Packages and Advertisements

Security Delegation for Users & Groups

User /Groups Accounts used in SCCM/SMS

Using the Site ConfigMgr Service manager and starting and stopping the components

Client Issues:

Client Supporting Third-party tools

Client Side log Files

General Reports:-

SMS_Def.MOF Vs Configuration.Mof

Scripts:-

Client Installation Scripts

Ping Scripts

Inboxes Checks Script

Inboxes Bad files delete Script
Uptime.exe
Fs.exe
Psexec.exe

Sample Ticketing Tool:-

IBM Maximo Link & User Name and Password

SMS / SCCM Site codes Names will not work

Be careful of reserved names for site codes

Suppose you've created a new site named 'CON' and are having trouble with it. The reason for this is that you've used a Windows reserved name for your SMS site code. The list of reserved name is fairly short and includes:

• CON
• PRN
• AUX
• NUL

The reason that these site codes are reserved is pretty simple. In some places, SMS creates folders using the site code. Since these names are reserved names in Windows and are used for other specific tasks, SMS can't create the site folder.

Limitations of SCCM 2007

Below are the Microsoft Recommendation as per MS Website

Maddy

Have you ever won a lottery or game show?
The only thing I have ever won was a water bottle at a school competition. But I have won a lot of

 

 

 

 

………………..will continue… .