Client configuration Manager Dissapears

We have approx. 1000 laptops that we manage with System Center 2012 and about 3-4% of our laptops have been experiencing Domain Trust Relationship issues. We think it is due to the kids repeatedly shutting down the laptops with the power button and
rebooting in recover mode. The issue that this has triggered is that when we run the Network ID under System Properties to rejoin the domain, they never come back up in the System Center Console. They show up as inactive. Also the configuration
manager is missing from the control panel and any Applications that were deployed are now missing. All logs under the c:\windows\ccm also dissapear. It's as if the configuration manager gets uninstalled.
Pushing the client via the Console does not work. It's as if the console is holding on to the old SID and the laptop is now assigned a new sid and communication is no longer existent. Has anyone been experiencing those issues? If so, what
is the remedy?
thanks -Marc

Why does pushing them not work? Any errors in ccm.log on the site server? Have you already examined the eventlog on affected clients in order to get an idea what might have happened?
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

How to deploy Client Configuration Manager on 400 workstations step by step

Hi to all,
I would like to know how to install SCCM Clients on 400 Workstations which no longer have it.Our netwok have 2250 workstations and 400 workstations don't have the SCCM client installed.How to create the deployment package?Or where to find it?
I tried to deploy it using the pushing methods.I've created a collection of workstations which don't have the client installed.theni tredthe pushing methods but no workstations received the clients.
Can i create a package on software distribution then deploy it to the collection?I know that it is not good for the network to deploy 400 workstations at once.
Thanks in advance for your suggestion.
Regards,

Can i create a package on software distribution then deploy it to the collection?I know that it is not good for the network to deploy 400 workstations at once.
If the systems don't have the agent already, a package can't reach them as software distribution requires the agent first.
Here's a very nice and detailed article on troubleshooting client push: https://support.microsoft.com/en-us/kb/925282
Remember though, it's not magic. Certain pre-requisites must be in place like permissions and firewall ports. ConfigMgr can't just conjure some voodoo to make these go away.
Jason | http://blog.configmgrftw.com | @jasonsandys

Customizing the "Configuration Manager" client found under Control Panel

Running: SCCM 2012 R2
How can you customize what an end user can see in the client "Configuration Manager" tool under Control Panel?
I saw this in an environment where certain parts were greyed out or where the action list was only limited to a few entries. How was this accomplished?

That's related to the level of permissions that the user has on the local system and UAC. The tabs of
Cache, Network and Site require UAC elevation before those settings can be adjusted and those tabs will be grayed-out without.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

AW client configuration updates

Hi,
Any updates done from AW client (configuration manager) will be updated in Logger database. Right.?
So is there a way to backup the configuration data before user make any configuration changes.? So that we can backup the configuration data and restore in case of mishap by the ldap user.
Also please let me know what all the configuration changes an AW client can make.? (I mean to say what all the components an AW client can access.)
Thanks and Regards,
Karthik U R

With all due respect....
"AW client is nothing but AW Distributor in which you can restrict different admin access. Basically the access of AW client is subset of the access of AW distributor. It is done during the setup."
and...
"OK, So we can set the access level during client AW installation.
Also can we restrict the access,Right.?
like should not be able to access script editor, Instead can access only Agent list, Skill groups, team list .etc.. "
These statements are NOT accurate.
A client AW has all the ability to make configuration and script inserts, updates, or deletes as any other AW. You cannot set any such access during installation. It depends on who the USER is who's logged in to the machine, versus what the machine itself can or cannot do.
In order to restrict access, you'd need to create a read-only user, or use Feature Control Sets to limit what individuals can insert, modify, or delete.
As indicated though, you can use ICMDBA to export your known good, working configuration, such that if something catastrophic occurs, you can then re-import that data. This is non-trivial, however! You would need to bring your entire ICM/UCCE system down, import the config into the loggers and AWs, and then re-initialize it so the callrouter would come up with the 'old' copy of the configuration.

SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"

Hi Team; I’m having 2 issues with SCCM 2012 R2:
Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
distmgr.log file.
~Package BDC00002 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~SourceVersion (1) of package BDC00002. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~Package BDC00003 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002"
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
~SourceVersion (1) of package BDC00003. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
AVAL0="BDC00003" $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
the status is packages deployment compliance stuck at 0%
Infrastructure:
3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
server is configured for each group respectively.
A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
is that I can't deploy the packages to production PCs in the Office subnet!
Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
I tried configuring IP Subnet Boundaries, still no luck!!
Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
<![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
thread="4884" file="lsad.cpp:770">
And here are the last 4 lines in the ClientLocation.log
<![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
<![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
<![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
While on the PC that the application was installed on I see the folowing in the LocationService.log:
<![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
Is there something wrong with the Distribution point on the Secondary Site server?
Please help…
Thanks..

Update:
I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
However; the second issue is still unsolved...
Please help..

When converting over to HTTPS and PKI for clients, not all actions are available in configuration manager cpl

I'm not exactly sure which forum heading this should go under so if this isn't correct please let me know or move it on my behalf.
So I am trying to setup Internet Based Client Management in SCCM 2012 R2 and have come across a few articles on how to do so. I think I have mostly gotten it to work but I seem to be having a client issue when deploying new machines. My already
deployed servers seem to have picked up the PKI setting no problem. In the past when I would deploy a new windows client everything would be fine. When i converted over to PKI in my test environment I am now having issues when I go to deploy a
new windows client. I don't get all of the Actions listed in the Configuration Manager control panel. All I have are Discovery Data Collection, Machine Policy Retrieval and Eval, User Policy Retrieval and Eval, and Windows Installer Source list Update
Cycles, before all of them would populate no problem. I have let this machine sit here for several hours and nothing has changed yet. It does say PKI for client certificate. Sometimes when I would deploy new machines it would say NONE for
Client certificate. In my production environment it says self-signed. I have found if i uninstall the client and re-install the client it does populate all of the cycles but I don't understand why it is not working on deployment.
Ok so maybe not all the time that when i reinstall the client it fixes it. I just did an uninstall and reinstall on a test client and all it has under actions are machine and user policy cycles.
Does anyone have any ideas?

Hi,
I think SCCM client installed before the GPO applied, so you don't a certificate available when it is required.
You can export and import the certificate by using MDT integration, try this blog for PKI part:
How To: Build and Capture in Configuration Manager 2012 using HTTPS
And in addition, you can upload the log to your onedrive so you can share with us.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Unable to copy hidden package "Configuration Manager Client Package" to local DP

Content status lists it as successfully distributed to all DPs (including the local site server)
However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
NOTE: It appears to not be any of these causes.
If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
Intializing DP Monitoring Manager...    SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
distmgr.log shows the following:
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Retrying package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
No action specified for the package CDW00001.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Updating package info for package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Exiting package processing thread.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Used 0 out of 3 allowed processing threads.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)
Sleep 1825 seconds...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
http://support.microsoft.com/kb/811833) being enabled?
Nothing special with certificates; I've used the basic stuff for intranet management of clients.
The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
(as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

How do you set up your Configuration Manager client when Imaging?

OK everyone we got an issue that we need to take care of sorry if this seems like a dumb question but we cant seem to make this work. How do you set your configuration manager client when you deploy your image(s)? I created package and pointed
it right to the config manager install directory just like the recommended one for USMT but it does not seem to work. I also tried to leave it blank but it appears to be mandatory.. So my question how do YOU get it to work for your areas?
Thanks

that might be the problem I dont see a "Microsoft Configuration Manager Client 5.0 All" anywhere. We threw something together that points to:
\\Server.Domain.com\SCCM_Install\SMSSETUP\CLIENT
What is happening is this.
Have a task to deploy Windows natively to the workstation
Drop applications to the workstation
do updates
capture back to server
All it does is
Drop the OS down
copy the Agent files
join to the domain
reboot
sit
sit
and sit

Communication lost - Same installation, same version of client (.exe), but client has different configuration in Configuration Manager properties

Hi, I can't understand how I get the following different between old and newly installed client. On the left side it is the original client configuration and on the right side it is what client gets after installing the same version of CCMSETUP.EXE (5.00.7958.1000)
with SCCM 2012 R2.
Differences noticed:
-Catalog's name (in Software center) are different. New client has "IT Ogarnization" as name for their catalog.
-Configuration Manager Properties for new client doesn't have "Configurations" Tab.
-Many Components status in the components tab are different: CCM Notification Agent, Compliance and Settings Managment, Hardware Inventory Agent, Out of Band Mangement Agent...
With all this, I can't send Windows updates or any applications to ANY clients. The client status in the monitoring deployment always shows "Unknown".
I don't think it is on the client side, because I return to older VMware snapshot and see the different, after uninstalled and re-installed the SCCM agent, I get the new "problematic" client configuration.
Any suggestion to resolve my problem? Thank you in advance.
bsuperkid

Here the all three logs. Sorry to give them like that but I think it is best way to let you take a look. I did change some name and reference to hide my environment.
Also, I don't know if there a link with my problem, but I guess so.
- I noticed in Monitoring\System Status\Components Status\"Warning SMS_WSUS_SYNC_MANAGER", the following message (ID 6703):
WSUS Synchronization failed.
Message: Thread was being aborted.
Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS.
- I noticed in Monitoring\System Status\Components Status\ "Warning SMS_AD_SYSTEM_DISCOVERY_AGENT", the following message (ID 5203):
Active Directory System Discovery Agent reported errors for 2074 objects. DDRs were generated for 0 objects that had errors while reading non-critical properties. DDRs were not generated for 2074 objects that had errors while reading
critical properties.
Possible cause: The site server might not have access to some properties of this object. The container specified might not have the properties available.
Solution: Please verify the Active Directory schema for properties that are not replicated or locked.
Refer to the discovery logs for more information.
I'll upload a print screen of all three logs files. If you need it in text format, I'll upload them as the code Block.
Thank you again!
bsuperkid

Configuration Manager client upgrade package failing to download to DPs

Hello,
I am receiving the following error in distmgr.log "Failed to get RDC signature path for for package SF100004 version 1. Error = 2"
"SF100004" is the "Configuration Manager client upgrade package"
Is there a way to rebuild/repair this package?

Yes, I did find out how to fix the problem. I had to use a power shell script to call WMI on the site server to manually force a refresh of the package having problems.
$SiteCode = "SF1"
$PackageID = "SF100004"
$distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
foreach ($dp in $distpoints)
$dp.RefreshNow = $true
$dp.Put()

Build and Capture TS fails in "Prepare Configuration Manager Client" task

I have a ConfigMgr 2012 R2 + CU1 I use for Windows 7 deployment.
I have made a "build and Capture" TS in ConfigMgr that I use to build my reference image.
When I run the TS it fails at the "Prepare Configuration Manager Client" step where I get the following error:
The task sequence execution engine failed executing the action (Prepare Configuration Manager Client) in the group (Capture the Reference Machine) with the error code 2147749938
Action output: ... 1 instance(s) of 'SMS_MaintenanceTaskRequests' successful
Successfully reset Registration status flag to "not registered"
Successfully disabled provisioning mode.
Start to cleanup TS policy
getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=80041032 (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,463)
ns.Query(sQuery, &spEnum), HRESULT=80041032 (e:\qfe\nts\sms\framework\tscore\utils.cpp,3666)
End TS policy cleanup
TS::Utility::CleanupPolicyEx(false), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,564)
pCmd->Execute(), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)
Wmi query 'select *from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0x80041032
Failed to delete policies compiled by TaskSequence (0x80041032)
Failed to prepare SMS Client for capture, hr=80041032
Failed to prepare SMS Client for capture, hr=80041032. The operating system reported error 2147942402: The system cannot find the file specified.
If I disable the "Install Software Updates" part of my TS it will run without probems. It installs 154 updates during the build.
I have seen another reference to this problem on this forum but why should the large number of the updates be the reason why the task sequcens cannot prepare the SCCM client for capture.
Sounds to me that it's a BUG :-(
Thomas Forsmark Soerensen

I'm glad I'm not the only one running into this. I've been racking my brain for the past few days trying to figure out where I went wrong.
SCCM 2012 R2 CU1
Installation properties in TS: SMSMP=mp.f.q.d.n FSP=mp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp"
Drop Windows 7 WIM that has all the updates Schedule Updates (offline servicing) installed (169 of 277)
Apply several updates offline (the dual-reboot Windows 7 updates among others)
Run Windows Updates more than once to be sure I get everything
Breaks at the preparing client for capture step
Is this:
a bug?
a known issue
something that's just frowned upon for no technical reason?
I'd love to hear from an SCCM guru [at Microsoft] on what the heck is going on here.

Streamlined Client Management and VDI with Configuration Manager 2012

Hi,
There is an interesting blog about managing ConfigMgr 2012 Clients in a VDI environment.
http://blogs.technet.com/b/server-cloud/archive/2011/11/15/streamlined-client-management-and-vdi-with-configuration-manager-2012.aspx
But I didn't find any way or description in the blog on how to prepare the client in the base image used for VDI. Do we still have to make the client unique before shutting down the base image? Or will this be done automatically?
Are these new attributes (IsVirtual, IsMachineChangesPersistent ...) enabled by default?
Thanks!
Gr. Cédric.

No this is handled by ConfigMgr post SP1
Are these new attributes (IsVirtual, IsMachineChangesPersistent ...) enabled by default?
For XenDesktop -no you will need to enable them in the client settings (not sure for other virtual
solutions)
In the SCCM Console go to the Administration workspace; click Client Settings. Right click the Default Client Settings and choose Properties
Choose Hardware Inventory and click Set Classes.
Click the Add button and then click Connect.
Enter the computer name of a master image device that has the SCCM client installed.
Enter root\ccmvdi as the WMI namespace and click Connect.
Select CCM_DesktopMachine. Click Ok.
Cheers
Paul | sccmentor.wordpress.com

How to deploy configuration manager client package to a query based collection

Hi
I have created one OU based collection.Now i wants to deploy client package to this collection so that the client automatically get installed,whenever a new machine added to the OU and so on to the collection.
But the issue is with configuration manager client package deployment,as we can't deploy the default configuration package to the collection(Deploy option is grayed out). For this i created a new configuration manager client package and deployed this package
to the query based collection.
Now when a new machine added to this collection,the client did not appear to deploy on this machine. Please help

If you want all the devices in the OU to get the client, you can use a Computer Startup Script to deploy it. Everybody just uses Jason's since it does everything and is well documented.
http://blog.configmgrftw.com/configmgr-client-startup-script/
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Fail on windowsupdate because of Configuration Manager Client

Hello everbody,
I have setup a Build and Capture task and this works ok until i enable the windowsupdate post application installation.
It looks good but it then stumbles on installing the Configuration Manager Client. Our WSUS server is also our SCCM server.
Googled arround but not much to be found other then one suggestion to exclude it using the KB number.
This is what the log is saying:
<![LOG[Scan complete, ready to install updates. Count = 1]LOG]!><time="11:05:51.000+000" date="02-05-2015" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Begin Downloading...]LOG]!><time="11:05:51.000+000" date="02-05-2015" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Begin Installation...]LOG]!><time="11:06:06.000+000" date="02-05-2015" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ 8427071a-da80-48c3-97de-c9c528f73a2d result(4 / HR = 80070643 ) : Configuration Manager Client (5.00.7958.1000)]LOG]!><time="11:06:07.000+000" date="02-05-2015" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Failure, Please run again!]LOG]!><time="11:06:07.000+000" date="02-05-2015" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
Regards,
Francis

Hi Nick,
No it does not have to be into the image, i just wanted to use the WSUS to update more quickly instead of downloading it using the internet.
Small update, i excluded the Configuration manager client to install during update, that works but no othe updates gets installed. It is finishing the deployment succesfuly without any update installed.
Somehow i thing it needs Configuration Manager Client to be installed to install other updates.....
When i do not point the deployment to the wsus server (i comment out the wsus server in customsettings) it start downloading and installing updates as it should.
Regards,
Francis

Please clarify license about server managed and configuration manager client ML system center 2012

Could clarify why managed servers License required ,already we bought the configuration manager client ML License ? We are planing to buy system center operation manager 2012

Hello,
if you wants planing to Monitoring your AD with Exchange Server and you have only one physical Server with for example 2 CPUs and 2 VMs, you need to purchase the System Center Standard 2012 R2 SML for Monitoring your Server environement. However, if
your AD is a datacenter or for example 4 x Windows Server Standard with 8 VMs than, you need to purchase the System Center datacenter SML.
the System Center SML is licensed per physical Server: one license up to two physical CPUs. if you have for 2 physical Hosts with 2 CPUs each, you need to purchase two System Center licenses.
the only difference between Standard and datacenter is only about virtualization rights
for System Center Operation Manager for your Clients Desktop, you need to purchase the System Center Client Management Suite includes: Operation Manager; Services Manager; Data Protection Manager and Orchestrator.
thanks
diramoh

Client configuration Manager Dissapears

Similar Messages

Maybe you are looking for