Client Agent installation on SCCM Primary Site Server

Hello,
I Installed Client agent via Client push to my SCCM Primary Site. Installation was sucessfull (Return code 0 in ccmsetup.log). But in console still the client status shows 'NO'.
Is there any difference when installing Client agent on Primary Site or any other site server. Please advice.
Regards,
Vishnu
V I S H N U

Thank you Torsten, Got the log files.
ClientLocation.log: - All things seems fine here. Got assigned to correct Site code.
But found the below errors in other two logs.
ccmmessaging.log
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:BFD290FF-1A90-4863-8304-EAA205D6EC20";
DateTime = "20150128053734.123000+000";
HostName = "QVDCSCM01.QDOM.GLOBAL";
HRESULT = "0x00000000";
ProcessID = 9048;
StatusCode = 0;
ThreadID = 11052;
CcmMessaging 28/01/2015 05:37:34 11052 (0x2B2C)
No reply message from Server. Server may be temporarily down or a transient network error. CcmMessaging 28/01/2015 05:37:34 11052 (0x2B2C)
Post to http://QVDCSCM01.QDOM.GLOBAL/ccm_system/request failed with 0x8000000a. CcmMessaging 28/01/2015 05:37:34 11052 (0x2B2C)
LocationServices.log
Failed to send management point list Location Request Message to QVDCSCM01.QDOM.GLOBAL LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Persisted Default Management Point Locations locally LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Current AD site of machine is Default-First-Site-Name LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Failed to send management point list Location Request Message to QVDCSCM01.QDOM.GLOBAL LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Attempting to retrieve local MPs from the assigned MP LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Current AD site of machine is Default-First-Site-Name LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Failed to send management point list Location Request Message to QVDCSCM01.QDOM.GLOBAL LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Current AD site of machine is Default-First-Site-Name LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Current AD site of machine is Default-First-Site-Name LocationServices 28/01/2015 05:37:34 11052 (0x2B2C)
Executing Task LSRefreshDefaultMPTask LocationServices 28/01/2015 05:37:45 1188 (0x04A4)
V I S H N U

Similar Messages

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((((

Using a custom certificate store for SCCM 2012 clients and primary site server

I have read what seems to be all the pki related documentation out there for SCCM 2012. I have a PKI infrastructure up and running issueing certificates with an offline root through group policy autoenrollment. The problem that i'm faced with is we are migrating
from SCCM 2007 that was in native mode and we chose not to use the CA that we used for the old SCCM environment. When the clients attempt to communicate with the M.P. it runs through all of the different certificates and adds a tremendous amount of overhead
to the M.P. We will have ten's of thousands of clients by migration end. Could someone please point me to a document that goes over how to leverage a custom certificate store that I could then tell the new 2012 environment to use? I know that it's in there,
I've seen it in the console. The setup is one primary site server with SQL on box and the pki I just mentioned as well as the old 2007 environment that is still live.
I read that you can try and use SAN as a method of identifying the new certs but I haven't found a good document covering exactly how that works. Any info you could provide I would be very grateful for. Thanks.

Jason, thank you for your reply. I'm getting the impression that you have never been in the situation where you had to deal with 2 different PKI environments. Let me state that I understand what your saying about trust. We have to configure the trusted root
CA via GPO. That simply isn't enough, and I have a valid example to backup this claim. When the new clients got the advertisement and began the ccmsetup process I used the /pki switch among others. What the client end up doing was selecting a certificate that
had the longest validity period which was issued by our old CA. It checked the authentication chain, found it to be valid and selected it for communication. At that point the installation failed, period, no caveats as you say. The reason the install failed
because the new PKI infrastructure is integrated into the new environment, and the old is not. So when you said " that
are trusted and they can use *any* cert that is trusted because at the end of the day, there is no
difference between two valid certs that have the same purpose as long as they are trusted. "
that is not correct. Both certs are trusted, and use the same certificate template, but only one certificate would allow the install to complete successfully.
Once I started using the CCMCERTISSUERS
switch the client install went swimmingly. The only reason I'm still debating this point is because someone might read this thread see your comments and assume "well I've got my new PKI configured as a trusted root CA, I should be all set" and their
deployment will fail, just as my pilot did.
About Intune I'm looking forward to doing a POC in the lab i built with my Note 3. I'm hoping it goes well as I really want to have our MDM migrated into ConfigMgr... I think the
biggest obstacle outside of selling it to management will be the actual device migration from the current MDM solution. From what I understand of the enrollment process manual install and config is the only path forward.
Thanks Jason for your post and discussion.

SCCM 2012 Primary Site server is piling up so huge

Hello Folks,
We recently implemented SCCM in our environment for a month ago. Its a stand-alone primary site model running DB on the primary site server itself. But, have segregated the drives for content, DB, and C drive for holding up the SCCM server related
installations. I haven't noticed the data growth on the server, as a result the C drive ran out of space yesterday and increased 40 GB more than the earlier. As of now, C drive has about 120 gb in total and there is only 25% left on whereas it had 33%
after expanding to 120 GB. When digging through the blogs, I doubted it could be BAD MIF inbox folder(screenshot attached), so went ahead and ran space check on the server, and looks like the major % of drive space is being occupied by the inbox folder and
also it is increasing day by day. I need further more directions on how this can be monitored to find out growth % and fix this.
I checked basic stuffs like clearing up profile & recycle bin data and any of this kind.
Step by step guide in detail should be more helpful in this regard. And, I hope this should be helpful for a larger SCCM admin crowd like me in the universe.
I also want to know what are the settings in SCCM console associates with these folders so that the settings can be streamlined to match the best practices (like inventory schedule for every 1 week & software inventory best practices) if at all, if we
have enabled in the implementation phase to receive fast & large results.
Thanks, V@s!m

We are seeing a stable disk size nowadays.
With that hopefully, this is a time to sum up the actions taken.
1. SCCM 2012 implemented a couple of months ago.
2. During the implementation phase, Client & Discovery settings were enabled to be quite an aggressive schedules to get good amount of results in a short period.
3. Implementation had been successfully completed and the system was running just fine until I noticed the space crunch
4. I thought it was normal and increased the disk space by 50% which got ate up in a couple of days and that's when I started suspecting about something is going wrong
5. As an interim solution, have increased the disk space by 70% and started troubleshooting the SCCM buddy.
6. Discovery settings were brought down to not to be aggressive (but this wasn't the issue) - still the issue was going on
7. Inventory settings were too brought down to be nominal (Useful :
http://www.informit.com/articles/article.aspx?p=1912064&seqNum=8)
8. By this time, I brought my colleague who was involved during the Implementation. We did the clean-up on server, went through the Inbox\Auth folders and were trying to figure out still what is going wrong.
9. We couldn't notice much improvement about the situation though we gave enough time for each and every fix that we applied.
10. Through some warnings and errors in the site system status, remembered that the 'Configuration.mof' was modified for testing some customized inventory classes, during the implementation phase which was getting mismatched data from lot of different clients.
- "Potential cause figured out"
11. Replaced the original Configuration.mof, and we started noticing big differences - the space was no more increasing.
12. Still we could see lot of old files in sub-folders of Inbox\Auth folder, we hope all these files would try to process for the information that we added in the 'Configuration.mof' > will fail > will go to respective 'Bad/Corrupt' folders and
eventually will be removed as per the clean-up cycle.
I will update the thread if anything goes wrong beyond this point. But, we believe it wouldn't as we have found the culprit and fixed.
**** I appreciate all your responses to help me with this situation. Happy SCCMing..!
Thanks, V@s!m

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

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

Configure SUSDB_log.ldf Autogrowth Size on SCCM 2012 Standalone Primary Site Server

I have configured the rest of my .ldf log files for SCCM use according to best practices by SCCM MVPs, but I have not read anywhere that states how I should go about configuring the auto growth for the WSUS database log file (susdb_log.ldf) itself.
If someone can offer some guidance here, I would greatly appreciate it.
Thanks

Thanks Torsten.
So after I run the first full sync, I can just use that value to set the initial size like you stated and then use some other value to set the growth rate? There is only about 1,000 clients in this organization and I want to get this WSUS db log file configured
prior to installing the SCCM primary site on the server. I have used Kent Agerlund's instructions on pre-configuring the SCCM 2012 R2 database and everything looks good there, but just wanted to know how to go about NOT using that 2TB default limit on the
SUSDB_log. What is a good rule of thumb to use to determine the file growth value? Like 2x or 3x the initial value size?
Thanks

Client Upgrade on Primary Site Server

This should be an easy question but I really want confirmation.
When you perform a Cumulative Update does the Update upgrade the client also on your primary site server? If so do when you create a device collection for x86/x64 clients do you exclude the site server from getting push?

Hi,
No the SCCM Client stays at version 5.00.7958.1000 on the primary site.
If you wanted you could upgrade the SCCM client on the primary manually by running.
C:\Program Files\Microsoft Configuration Manager\hotfix\KB2970177\Client\x64\configmgr2012ac-r2-kb2970177-x64.msp and then exclude it from the below collection or let it go out automatically.
This is from an older version but the principle is still the same.
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
You can go straight from R2 to CU2. You do not need to install CU1 first.

SCCM CAS & Primary Site Server - Same SQL Database and Reporting Instance

Hi Fellows,
I need to know whether, for SCCM CAS, a dedicated/seperate SQL instance for SCCM CAS a mendatory requirement or recommendation?
Or we can use the same SQL instance used by Primary Site Server?
J.A

There no technical reason not to have the CAS and Primary database in separate instances of the same remote SQL server. However if you are going to deploy a CAS that would suggest a very large number of clients and a very busy infrastructure. In that case
I would RECOMMEND separate SQL servers.
This is a good guide for SQL sizing (but it is only a guide)
http://blog.coretech.dk/kea/system-center-2012-configuration-manager-sql-recommendations/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Replacing the primary site server, SCCM 2012 R2

Hi,
Setup is currently SCCM 2012 R2 with the primary site server on Windows 2008 R2 on a Hyper-V VM with a separate physical SQL server on 2008 R2 (Windows and SQL). I'm not making any changes to the SQL server at this stage.
I want to completely replace the primary site server VM completely with a brand new VM using Windows 2012 R2.
I was looking to run the SCCM setup and using the Expand an existing stand-alone primary into a hierarchy option but it wont let me do that due to "The site code you specified should not be the same as the primary site's site code".
So seems this Expand an existing option isn't the right option for me?
Do I just add the new server in the SCCM console and add all roles and test and then delete the roles from the old server?
Thanks
EDIT: I have 7 Secondary sites, so I dont want to just start over by doing some sort of backup and restore to the new server unless someone can tell me that wont break my hierarchy.

a backup and recovery is the correct way to do this, but there are a few things you should keep in mind.
Do a backup of your current environment and shut everything down.
install new vm, ensure the configuration is identical, (dns, hostname, etc...); install the same software and pre-requisites,
do a recovery
check the following links on how to do a backup and restore:
http://www.windows-noob.com/forums/index.php?/topic/7403-how-can-i-backup-system-center-2012-configuration-manager/
and
http://technet.microsoft.com/en-us/library/gg712697.aspx

Running WMI repair script on SCCM 2012 primary site server

Hi,
running WMI rebuilding repository script on SCCM 2012 primary site server. Any idea what kind of issue on SCCM environment it will cause.
Regards,
Gopi

Gah! did you already do so? I hope your resume is up to date. As to what kind of issues: it'll break everything, and nothing will ever work right ever again. Ever. Again.
Standardize. Simplify. Automate.

SCCM - Uninstalling Primary site server

Hi All,
After we uninstall a primary site server from SCCM architecture, are there any changes that we need to make in AD, so that there should be no junk entry objects in AD that are related to this primary site server.
Rgs,

Hi,
Clear up all the objects in System\System Management that points to the Primary site you are uninstalling and it roles.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SMS Agent Host Service requirement for Site Server or Site Systems

Is the SCCM Client a requirement on the SCCM 2012 Site Server or Site Systems or is it possible to disable SMS Agent Host Service or uninstall the client without affecting any of the Site roles? I have actually done that and everything
is working as expected but I wanted to make sure that none of the site roles are dependent on the client agent.

Hi,
Only need to install client when you want to manage the servers by Configuration Manager client.
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.

Is the distribution point role required on an SCCM 2012 site server?

I am wondering if the distribution point role is required on an SCCM 2012 site server.
We have an installation of SCCM 2012 SP1 with a site server, and two remote DPs.
I would like to remove the DP role from the site server, and stand up another server (2012) at the same location, making it a DP and also have it hold the WSUS content.
I was successful in creating the DP on the new server. I distributed all of our packages to the new server.
I then removed the packages from the DP on the site server, and removed the DP role from the site server.
After making these changes, we lost the ability to deploy packages, either from the new DP server, or from the previously existing DPs that were at other locations.
Deployment status in the SCCM console showed that clients were “waiting for content”.
I found that adding the DP role back to the site server, and distributing packages to it corrected the problem.
Deployment resumed after doing that. Is it necessary to have packages on a DP on the site server?
We want to virtualize the server, and would like to make it as small as possible to facility restores.

Hi,
Have you checked the log file distmgr.log? Maybe it can give us some clues.
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.

Is there a way to change an existing SCCM 2012 site server intranet FQDN name to lowercase?

Does anyone know if there is a way to change the intranet (not internet) FQDN name of an existing SCCM 2012 site server to all lowercase letters? You used to be able to do this in SCCM 2007.

I had a problem with WSUS updates not working via SCCM 2012 R2 during an operating system deployment. When examining the c:\Windows\WindowsUpdate.log I found the following errors:
WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <****:8080;****:8080> Bypass List used : <(null)> Auth Schemes used : <>
+ Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
After a LONG time researching this error I found it was related to the fact we were using a WPAD proxy implementation and apparently this doesnt cope well with uppercase characters for the WSUS server URL. I changed our GPO to be using lowercase lettering
but when examining the WindowsUpdate log again it still showed as being in uppercase. In the end I found that despite what your GPO setting says, this can get over written by the SCCM site server's own published WSUS location. You can check this by entering
the following command:
wmic /namespace:"\\root\CCM\SoftwareUpdates\WUAHandler" PATH CCM_UpdateSource
Unfortunatelty in SCCM 2012 there is no GUI way to amend the intranet FQDN used for the WSUS location so I then turned to directly editing the database (which anyone will tell you is not recommended, but by this point i was DESPERATE!).
In the end it solved all my troubles so if anyone finds themselves in this situation, you can fix it by going to the SCCM database and within the table 'WSUSServerLocations', change the WSUSServerName to be in lowercase letters.

Client Agent installation on SCCM Primary Site Server

Similar Messages

Maybe you are looking for