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

Similar Messages

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

Configuration Manager Client Retry Scheduled Task not removed

I have had several clients where the “Configuration Manager Client Retry” scheduled task is not removed after a successful install. The task will run daily and reinstall the client
over and over until someone notices and we delete the task. So far I have only seen this happen on R2 clients (5.00.7958.1000). Has anyone ever run into this before? Thanks!

Hi,
Has this client installed successfully during the reinstall process?(ccmsetup.log and Client.msi.log)
Please check ccrretry.box in Program Files->Microsoft Configuration Manager->inboxes and Ccm.log on the site server to get more information. SCCM might cannot detect the SMS Agent Host is running.
Best Regards,
Joyce
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.

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

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

Trying to download icloud control panel - only getting so far. Got message: The installer encountered errors before iCloud Control Panel 2.1.2 could be configured. Your system has not been modified. To retry these operations at ltr time, pls run again.

First time on here... so not sure if doing correctly.
I'm tryng to download icloud control panel to my PC (have Windows 7 - so should be ok). I only get so far - 2 times I've tried it. Keep getting message:
The installer encountered errors before iCloud Control Panel 2.1.2 could be configured.
Your system has not been modified. To retry these operations at a later time, please run the installer again.
huh?

As I mentioned before you need to start the iTunes installation, then do NOT allow it to complete. In other words go all the way to the point that the installer extract the installation files, then STOP right there.
Now look for the temp folder and the files I mentioned in my initial posting. If you don't find the temp folder it may be because you have "Do not show hidden files and folder" selected under "View Tab" in the "Folder Options". You may need to unselec it. If you don't know about hidden files and folders in Windows XP take a look here: http://txpress.blogspot.com/2007/05/show-hidden-filesfolders-in-windows.html
Another possibility is that you may have a different path for your temp folders. To find out where you temp folders are located please do the following:
- Right click on "my computer"
- Select the "Advanced" tab
- Click on "Environment Variables"
Then look for the path for both variables "TEMP" and "TMP" take note of the path and check them out.
Or you may just go to a DOS Prompt and type the following commands:
1 - %temp% and hit enter
2 - %tmp% and hit enter
to both of these commands you will get a reply such as:
'c:\temp' is not recognized as an internal or external command, operable program or bath files.
So by looking at the reply you can see that my temp folder is c:\temp
The above is the temp folder on my machine which I've customized to my own use. Your machine may be different.
I suggest you check for the iTunes temp folder inside both your temp folders locations "TEMP" and "TMP" as they may be in different locations.
IMPORTANT NOTE: If you allow the iTunes installation to complete you will NOT SEE the iTunes temp folder and files because it will be deleted as soon as iTunes processes the installation.
Hope it helps.

Message (on one account) when logging in: The user account running the Configuration Manager console has insufficient permissions to read information from the Configuration Manager site database.

After installing the reportservice/database i cannot use the Configuration Manager Console 2012 anymore with my own AD account. (The accounts of my colleagues are stil working)
When i login i get the following message:
The user account running the Configuration Manager console has insufficient permissions to read information from the Configuration Manager site database. The account must belong to a security role in Configuration Manager. The account must also have
the Windows Server Distributed Component Object Model (DCOM) Remote Activation permission for the computer running the Configuration Manager site server and the SMS Provider.
I checked the following:
I am a administrative user in SCCM (Full Administrator)
I am a member of the administrator group on the server
Deleted HKEY_CURRENT_USER\Software\Microsoft\ConfigMgr10
I tried to start it on multiple workstations and deleted my roaming profile
Any more suggestions?

Hi,
Maybe you could have a look on the below blog.
http://blog.nimbo.com/how-to-disable-user-account-control-in-windows-server-2012/
(Note: Microsoft provides third-party contact information to help you find technical support. This contact information
may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
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.

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".

OSD with Configuration Manager Clients and PKI certifications

My team and I had just set up PKI Certs on our System Center 2012 R2 Server. We want the opportunity to utilize Out Of Band Management, but we also would like to make our OSD available to the following "Only Configuration Manager Clients." I have
done some testing and have found that without PKI enabled we have been able to use this feature. Once we enabled PKI we could only perform OSD through PXE or Boot Media.
Is there a way to have PKI enabled but also allow OSD's to be available through "Only Configuration Manager Clients"?

Thanks for the reply, I will relay the info concerning OOB. It is not necessarily a technical problem we are running into, more of an inconvenience. OSD works great as long as you make your TS deployment available through Boot media or PXE. Our end goal
is to create a zero touch environment. To do this I was thinking of making the TS available only configuration manager clients. With PKI I loose that capability and it forces me to use boot media or PXE.
Is there a way to have PKI enabled and still be able to deploy TS with only configuration manager clients, and no other deployment method?
Thank you again.

Multiple duplicate Configuration Manager Client (Upgrade) Packages

We have 14x Configuration Manager Client Package / Configuration Manager Client Upgrade Packages in our SCCM2012R2cu1 environment.
We tried deleting all of the packages that were not linked to deployments/task sequences, but a few days later these were re-created with new PackageIDs.
Any ideas what could be causing this? are there some logs we should be checking?
http://oi61.tinypic.com/5nx4.jpg
Thanks!

FROM hman.log:
CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Handle auto-upgrade client configuration changes   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Update auto-upgrade client configurations   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
INFO: Full client package id XX1001EB exists.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade package id XX1001EC exists and upgrade package flag is set to 1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade program Configuration Manager Client Upgrade Program in package id XX1001EC exists and its currently disabled.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade advertisement id XX1203B8 exists for package XX1001EC and program Configuration Manager Client Upgrade Program. Deployment is targeted to collection SMS00001.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM
1936 (0x0790)
INFO: All client auto upgrade related objects exists. No objects are to be created.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Successfully added client upgrade packages XX1001EC and XX1001EB to all 31 distribution points from site XX1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
Wait for site control changes for maximum 3600 seconds...   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)

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

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

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.

Installation turnkey error verifying JBoss during the configuration manager setup

LiveCycle seems to install fine, then immediately after install, the Configuration Manager runs and I get an error "Failed on 'Verifying JBoss for Adobe LiveCycle ES v8.0 service is installed' Windows turnkey service JBoss for Adobe LiveCycle ES v8.0 does not exist".
I received the error in both the "express mode" and "custom mode" within the "turnkey mode" step of the configuration manager.
Has anyone seen this error before or know what causes this? We have tried installing on three different PC computers with the same error. The latest JDK1.6 is installed and environment variables created before install of LiveCycle.
Any ideas? Am I doing something wrong? Th installer seems pretty straight forward.

Before re-installing LiveCycle, ensure that:
1) the JBoss and MySQL services are removed
sc delete "JBoss for Adobe LiveCycle ES v8.0"
sc delete "MySQLfor Adobe LiveCycle ES v8.0"
2) Delete the \Gen1 folder from C:\Program Files\Common Files\Install Shield\Universal\Adobe\LC8

Customizing the "Configuration Manager" client found under Control Panel

Similar Messages

Maybe you are looking for