Collection Evaluation - multiple primary sites

Hello:
If I have a CAS and multiple primary sites and have a set of collections all created on the CAS, where is the collection evaluation done (I believe coll eval is done only on primary sites)? Is it done on each primary site independent of others?
And then they replicate to CAS and CAS sorts out possible conflicts/discrepancies?
So if I set the collection evaluation schedule, is that based on the local time of that particular primary site?
Thank you,
Mustafa Hamid, System Center Consultant

Thank you Jason,
I think I understand your comment about the managed systems - the systems that are assigned to that primary site. To take a simple case to help me understand - So if I have a device collection that has a query based on OU name=Dallas and that collection
evaluates on PS1 and also on PS2. Both will send their results to the CAS. Generally they should both evaluate to same result (maybe sometimes a bit different based on the DC they connect to). It seems in this case they are repeating the
same work since its all global data?
Thank you
Mustafa Hamid, System Center Consultant

Similar Messages

Unknown Computer collection with multiple Primary sites

Hi All,
We have a SCCM 2012 SP1 envionment with a CAS and 2 Primary sites in seperate countries. Last week the primary site server in site B was down, this affected PXE boot deployments to the Unknown Computers group across the whole environment eg: site A. PXE
booting to existing collections worked fine but PXE booting to unknown computers would time out, like the deployment server was waiting for a response from both Site A and Site B site servers.
Now my question is this expected behaviour? Do the primary site servers across the whole environment need to be up for the Unknown Computers collection to work properly?
Another thing I noticed is that the admins for Site B have created their own site specific Unknown Computers collection so i'm wondering if this is getting referenced when Unknown Computers PXE boot in Site A.

I doubt that there's something happening cross-sites, but - as Jason said - logs would be helpful.
Torsten Meringer | http://www.mssccmfaq.de

Do I need multiple primary sites? Some design questions..

I have about a thousand users & devices, across two sites. Setting up SCCM 2012 R2 and wondering if I need to have multiple primary sites?
From everything I've read so far, it seems that a single standalone site will handle tens of thousands of users/devices or some very large number, so I'm not sure if I'd ever need a secondary site or what it's function would be - failover, backup, or is
it just best practice to have different roles spread across multiple servers?
I was originally thinking of just doing a single primary site on a single server. But then I'm not sure if my DP should be separate.
Can someone point me the the right direction to a high level planning document or blog?
Thanks
Nathan

How many clients are there in total? How many at each location? What's the WAN speed in between?
Multiple primaries are only needed for scale out purposes (>100k clients)!
Torsten Meringer | http://www.mssccmfaq.de
About 500 at each, T1 speeds connect the sites, so I want to enable software metering I think.
Also - if I have a single server with DP role installed, what kind of RAM/HD requirements are needed? I know this probably varies with the install/features, but are there any ballpark estimates/starting points posted? Sorry I know this is probably
on the MS site somewhere, the the volume of information is hard to weed through. Update, I found some good guidelines here:
http://myitforum.com/myitforumwp/2012/06/27/sccm-2012-site-hardware-requirements/
For 1000 or less users, is a single Gb NIC sufficient? Sounds like it might be? Also, when using a virtual machine, do you need to still somehow separate SQL logs & data from OS?
Update #2, looks like that above post answered that question too:
If you’re in a VM, it’s not sufficient to have a single VHD file, and having the roles split among 4 virtual drives inside that file. It’s not sufficient to have that single file on a shared set of remote disks. It’s not sufficient to have that
single file on a dedicated set of disks, regardless of the number and size of those disks. Any VM should be configured to only run the OS, and the 3 other spindles should be dedicated sets of disks, attached to the VM. Otherwise, it’s like painting
with watercolors in a hurricane…you’re spending a lot of time, looking creative, with zero value.
But I'll take any follow up comments or recommendations if you have them on proper VM setup.
Thanks
Nathan

Multiple Primary Sites connected to a CAS

On a global deployment of SCCM 2012 we are planning on deploying a CAS in the global domain and Primary Sites in the sub domains and Secondary Site in the smaller subsidiaries where needed.
I understand that all collections, clients and packages come through to the CAS but could an administrator connected to Primary Site A see the collections and packages in Primary Site B? Are they independent of each other with the exception of the CAS or
do all sites in the hierarchy show everything from all sites?
If that is the case then ideally we would want administrators of Site A to not even be able to connect to Site B but am struggling to understand how this could be achieved?

"The use of a CAS was made due to the scale of the deployment."
So you mean you have more than 100k devices. Regardless of having a CAS and multiple primaries or having only 1 primary, if you have (let's say) a total of 3,000 devices; split up into 1k silos of responsibility.
you Essentially create 3 Collections, and those 3 silos get rights to their collection of devices. Connecting to the primary sites' for the console really isn't "normal" in CM12--it's called the Central Administration Site for a
reason--it really makes it less confusing for those people that need to use the console. You may not think so initially (coming from a CM07 point of view); but it really is the best in a CM12 world. If you have people in different locations which
need console rights, the easiest, IMO, is to have a Citrix-hosted console; and people just connect to that console remotely; where the citrix host is in the same data center as the Central Administration Site.
Now, if you do NOT have 100k devices, or you are nowhere near that number, please please please, I beg you, PLEASE rethink your perceived need for a cas and primary sites. T-shooting replication issues is no fun, no joy to be had there at ALL.
you need to setup RBA correctly regardless of a CAS and primaries, or just 1 primary--so having a CAS and primaries when there is ZERO NEED for it due to scale--well, all I can say is I sincerely hope you are a contractor, and are just setting this up and
then bailing never ever to return, and leaving the mess behind for the poor day to day admins to deal with.
Standardize. Simplify. Automate.

Multiple primary site - Discovery issue

Hi,
I am working on a scenario where there is 1 CAS and 3 Primary sites(PS1,PS2,PS3). At PS1 site, Active directory system Discovery is only configured and all the OU for all the sites are added. On the other two Primary sites this discovery was not configured.
Now I wanted to ask is there any issue due to this , or should I have to configure this discovery on both sites??
Thanks
Pallavi

no, you can still control that. Site Assignment is either based on an AD Query or you hard coding the site code during the install process. Client deployment depends on the method, in this process content boundary Groups and DP's are being used.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

Can we assign 2 IPs for a SCCM 2012 primary site server and use 1 IP for communicating with its 2 DPs and 2nd one for communicating with its upper hierarchy CAS which is in a different .Domain

Hi,
Can we assign 2 IPs for a SCCM 2012 primary site server and use 1 Ip for communicating with its 2 DPs and 2nd one for communicating with its upper hierarchy CAS . ?
Scenario: We are building 1 SCCM 2012 primary site and 2 DPs in one domain . In future this will attach to a CAS server which is in different domain. Can we assign 2 IPs in Primary site server , one IP will use to communicate with its 2 DPs and second
IP for communicating with the CAS server which is in a different domain.?
Details:
1)Server : Windows 2012 R2 Std , VM environment .2) SCCM : SCCM 2012 R2 .3)SQL: SQL 2012 Std
Thanks
Rajesh Vasudevan

First, it's not possible. You cannot attach a primary site to an existing CAS.
Primary sites in 2012 are *not* the same as primary sites in 2007 and a CAS is 2012 is completely different from a central primary site in 2007.
CASes cannot manage clients. Also, primary sites are *not* used for delegation in 2012. As Torsten points out, multiple primary sites are used for scale-out (in terms of client count) only. Placing primary sites for different organizational units provides
no functional differences but does add complexity, latency, and additional failure points.
Thus, as the others have pointed out, your premise for doing this is completely incorrect. What are your actual business goals?
As for the IP Addressing, that depends upon your networking infrastructure. There is no way to configure ConfigMgr to use different interfaces for different types of traffic. You could potentially manipulate the routing tables in Windows but that's asking
for trouble IMO.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM Primary Site installation fails

Hello!
In my organization we have two domain/forests. DomainA.local and DomainB.local
in one forest (DomainA.local) we have sccm 2012 sp1 CAS site. with dedicated database server on sql 2012 sp1 cu5
in other forest (DomainB.local) we want to setup primary site on sccm 2012 sp1 with dedicated database server on sql 2012 sp1 cu5
forests have trust both sided.
all installation accounts have administrative rights on all SC servers. in both domains.
when i try to install SCCM 2012 primary site in the hierarchy,
i receiving the errors:
INFO: Created SQL Server machine certificate for Server [S-SCDB-02.DomainB.local] successfully.
ERROR: Failed to open certificate store (HRESULT=0x35) Configuration Manager Setup 9/3/2013 11:56:19 AM 3268 (0x0CC4)
ERROR: Failed to write S-SCDB-02.DomainB.local SQL Server certificate to store (TrustedPeople) on site server (S-SCDB-01.DomainA.local).
ERROR: Failed to write certificate of primary site's SQL Server [S-SCDB-02.DomainB.local] to CAS SQL Server [S-SCDB-01.DomainA.local].
Install user from domainB.local has administrative rights on S-SCDB-01.DomainA.local and sysadmin rights in sql server.
Also, it has full administrator role on CAS.Of course, it has administrative rights on primary site server and sql server S-SCDB-02.DomainB.local and sysadmin rights.
WHY????

>Taking a step back: why? Are you using a CAS and multiple primary sites at all? Do you have 100,000+ clients to manage?
we need CAS due to our network infrastructure.
thank you for you help.
we solved problem today.
it was need to open "windows" ports on the firewall between SCCM Primary Site server and CAS SQL server to give SCCM
primary site installation process the ability to install the primary site's sql-server's self-signed certificate to CAS sql-server trusted people local store.
i did not remember this point in deploying documentation((((

Primary site server a single point of failure?

I'm installing ConfigMgr 2012 R2, and employing a redundant design as much as possible. I have 2 servers, call them CM01,CM02, in a single primary site, and on each server I have installed the following roles: Management Point, Distribution Point, Software
Update Point, as well as the installing the SMS Provider on both servers. SQL is on a 3rd box.
I am now testing failover from a client perspective by powering down CM01 and querying the current management point on the client: (get-wmiobject -namespace root\ccm -class ccm_authority).CurrentManagementPoint . The management point assigned to
the client flips to the the 2nd server, CM02, as expected. However, when I try to open the CM management console, I cannot connect to the Site, and reading SMSAdminUI log reveals this error: "Provider machine not found".
Is the Primary site server a single point of failure?
Why can't I point the console to a secondary SMS provider?
If this just isn't possible, what is the course of action to restore console access once the Primary Site server is down?
Many Thanks

Yes, that is a completely false statement. Using a CAS and multiple primaries in fact will introduce multiple single points of failure. The only technical Eason for a CAD a multiple primary sites is for scale out; i.e., supporting 100,000+ managed systems.
HA is achieved from a client perspective by adding multiple site systems hosting the client facing roles: MP, DP, SUP, App Catalog.
Beyond that, all other roles are non-critical to client operations and thus have no built-in HA mechanism. This includes the site server itself also.
The real question is what service that ConfigMgr provides do you need HA for?
Jason | http://blog.configmgrftw.com

Is 100K devices a hard cap for a Primary Site (or a guideline)?

Hi,
I'd like to know if the 'supports up to 100,000 devices' per Primary Site is a hard cap on the number of devices that SCCM 2012 R2 can handle or if it is a recommendation?
We are using SCCM 2012 R2 and currently have a single Primary Site with about 90K devices. Very soon, we will be looking at adding a CAS (with multiple Primary Sites) to support our ever growing number of devices.
Until we get there with the CAS, I'd like to know what to expect if we get over 100K devices.
Will we break SCCM?
Will any devices over 100K not be added (and therefore not be managed)?
Nothing much, but the system may perform more slowly?
Results will be unpredictable?
Something else?
Thanks, Joe.

Actually, it's not really a guideline either, it's an official statement of support from Microsoft meaning that if you go over this number, you may have issues that Microsoft will not provide support for.
This is officially documented at https://technet.microsoft.com/en-us/library/gg682077.aspx under the Clients per Hierarchy section.
Is your org simply close to this number or fearful of going over in the future?
Remember that a primary site can be expanded into a CAS with multiple primary sites under it if need be in the future.
Also note that the although the 100,000 client limit has been there since the launch of 2012, that was over three years ago and there are some upcoming releases.
Jason | http://blog.configmgrftw.com | @jasonsandys

How to set security group as primary site collection admin and secondary site collection admin using powershell in sharepoint online site - office 365?

How to set security group as primary site collection admin and secondary site collection admin using powershell in sharepoint online site - office 365?

Hi,
According to your description, my understanding is that you want to set security group as admin of primary and secondary site collection using PowerShell command in office 365.
I suggest you can use the command below to set the group to site owner, then it will have the site collection admin permission.
Set-SPOSite -Identity https://contoso.sharepoint.com/sites/site1 -Owner [email protected] -NoWait
Here are some detailed articles for your reference:
https://technet.microsoft.com/en-us/library/fp161394(v=office.15)
http://blogs.realdolmen.com/experts/2013/08/16/managing-sharepoint-online-with-powershell/
Thanks
Best Regards
Jerry Guo
TechNet Community Support

SCCM 2007 - All clients from primary site have vanished from central site collections

Hi all,
we have a SCCM 2007 R2 setup with one central site, one Primary Site (A) with a secondary site hanging off it and another Primary Site (B). Suddenly all the clients from the Primary Site A (and also it's Secondary Site) have vanished from the central
site. All the clients are still present when we check Collections from the admin console on Primary Site A site server - they have simply disappeared when we check Collections from the Central Site admin console.
Can anyone provide any info on a good starting point for troubleshooting this issue? As a sidenote, we can still push packages out to the Primary Site A distribution point and both the Primary and Central site can communicate/ping each other.
Any help/info would be much appreciated!
Thanks

Check the
site replication on central site, is that SQL is working fine, and also see the
inbox folder in central site, might be there is backlog and those DDR files are
not processing, and after maintenance they got deleted.<o:p></o:p>
please run
the heartbeat discovery by hour or day, and once the clients will sent all the
DDR files then they will appears again.<o:p></o:p>
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

Single Primary Site with CAS

Hello,
I have a client with a single primary site server and a CAS. It was installed for some reason, doesn't really matter now why.
They have two options, leave it up or migrate to a new Primary Site server.
The questions is, if they leave it up (It's not needed or used), what harm will it do?
Yes, I know it will make the site simpler to manage but other than that? What would compel them to go through the hassle of a migration to a new server?
Thanks!
John

Short answer: get rid of it.
There are a host of complications introduced by having a CAS and it should really only be done if the environment demands it (massive device management count for example).
In addition to patching complication increase and SQL replication monitoring you now have to do:
1. Many roles will need to be installed multiple times. Example WSUS will be required to be installed on the CAS with a secondary on the Primary for proper functionality.
2. Some roles will be required on the CAS, some will be required on the Primary site. If you aren't well-versed in your SCCM this can be a frustrating path of discovery.
3. Then there are roles that _can_ be installed in both locations but don't have to be ... like the reporting server. This one comes down to login policies and if people will ever log directly into the PRI or just CAS box.
All these architectural complications come before the "why" is asked ... which is usually driven by one of two things:
1. In SCCM 2012 RTM, the CAS had to be installed first or you could never use it. Some clients did this to avoid potential problems. This requirement has sense changed.
2. In 2007, people used to use multiple primaries as security boundaries. With SQL replication, collections being uniform across all sites, and the general inclusion of RBAC .... this is now moot.
Basically don't use CAS unless it absolutely fits the company. It's a lot more pain than just "one more VM".

Effect on OSD if remove primary site from SCCM heirarchy

Wanna ask, just a theory question, im currently planning to decommission and upgrade my current primary site server. The process will take roughly a few days. At the same time, I also have other site system server that also acts as an MP (has MP role). So,
for the time being I would not have an active primary site for a couple of days.
Question is, during that timeframe (when primary site not available), am I able to still do OSD? Was thinking the only issue of not having a primary site at that time, my user client machine will not be able to get the latest policy
cause any new policy will be push down from the primary site right...but the client will only be able to get the old TS advertisement correct... Question as below
Does the client machine still able to run the old advert advertised to it?
Does the client machine cache the TS advert and store it locally on their machine?
All the OSD content (boot image, OS image etc) is available in the DP, so it should be able to PXE boot and execute the TS correct if the primary site is not available?
Read the net on PXE boot flow at
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx. Its says as below. What I don't understand is isn't the primary server is the only one that can access the DB? Don't quite get it when it says
WDS can also access the DB....?
WDS/PXE sever runs a stored procedure, LOOKUPDEVICE for the client machine against SCCM DB. If the machine is found in the DB or If there is an advert for Unknown collection, WDS signals client to proceed with the PXE
boot.

Which roles are installed on the site server?
Torsten Meringer | http://www.mssccmfaq.de
Roles installed on my primary site is
Management point
SUP
Site System
Component Server
Site Server

SCCM 2012 hierarchy CAS is down will primary sites work

hi all
SCCM 2012 hierarchy CAS is down will primary sites work and if primary site down will secondary sites work
can anyone explain this, how CAS Down will affect the functionality of other primary sites or we can still manage the clients with primary site without any problem.

Hi,
if your CAS is down, you can still work with your primary site. You will get into replication trouble and even loose data after an offline time longer than 14 days. If you know that your offline time will be shorter than those 14 days, you will not get into
trouble. This 14 day duration needs to be configured, I think the default value was 5 days.
if you have a secondary sites and loose the connection to the primary, you are not able to manage the secondary sites since the SCCM console is only connectable to primary sites and CAS. The MP on your secondary will still collect client data which will
be transmitted to the primary after an reconnect.
Regards
Thomas

Customer reference has two identical primary site uses

This customer reference has two identical primary site uses
defined in RA_CUSTOMERS_INTERFACE. Please update the SITE_USE_CODE
field or the PRIMARY_SITE_USE_FLAG so that only one primary site use exists per customer and site use code.
Thanks in advance

Check Note: 181622.1 - Customer Interface Imports Multiple Shiptos For A Customer With No Site Use Code
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=181622.1

Collection Evaluation - multiple primary sites

Similar Messages

Maybe you are looking for