Heartbeat Discovery

Ok, so I know this isn't rocket science but dang it, I am having a hard time comprehending it. Can someone please tell me if I have this setup the best way?
I am seeing inactive clients in our SCCM database. I understand that is normal and so on, but what I am wanting to know is if I have my heartbeat discovery and the Clear Install flag maintenance task setup correctly, since I know they are somewhat connected
with each other.
My company works Monday through Friday with a few that work on weekends. I have my Heartbeat Discovery enabled and set to send every 3 days. We do have client push enabled. For my Clear Install Flag maintenance task, I have it enabled and the Client Rediscovery
period is set to 14 days and runs every Sunday. We want to be agrresive with keeping our client database current and up to date, but I don't want to be overly agressive either. I have a PC who is trying to get an application I am pushing out but SCCM
thinks the PC is "Inactive" since it has been turned off for 5 days now, but turned on today.
Any recommendations for changes?
Thank you!!

Honestly there are no changes needed.
However on a side note, I generally recommend that both heartbeat and hardware inventory be set to daily.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

Best practice - Heartbeat discovery and Clear Install Flag settings (SCCM client) - SCCM 2012 SP1 CU5

Dear All,
Is there any best practice to avoid having around 50 Clients, where the Client version number shows in the right side, but client doesn't show as installed, see attached screenshot.
SCCM version is 2012 SP1 CU5 (5.00.7804.1600), Server, Admin console have been upgraded, clients is being pushed to SP1 CU5.
Following settings is set:
Heartbeat Discovery every 2nd day
Clear Install Flag maintenance task is enabled - Client Rediscovery period is set to 21 days
Client Installation settings
Software Update-based client installation is not enabled
Automatic site-wide client push installation is enabled.
Any advise is appreciated

Hi,
I saw a similar case with yours. They clients were stuck in provisioning mode.
"we finally figured out that the clients were stuck in provisioning mode causing them to stop reporting. There are two registry entries we changed under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec]:
ProvisioningMode=false
SystemTaskExcludes=*blank*
When the clients were affected, ProvisioningMode was set to true and SystemTaskExcludes had several entries listed. After correcting those through a GPO and restarting the SMSAgentHost service the clients started reporting again."
https://social.technet.microsoft.com/Forums/en-US/6d20b5df-9f4a-47cd-bdc3-2082c1faff58/some-clients-have-suddenly-stopped-reporting?forum=configmanagerdeployment
Best Regards,
Joyce
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]

Active Directory Group Discovery not picking up Workstation OSs

We don't use the default 'workstation' container in AD. We have a OU called:i.e. 'contoso workstations'. Within 'contoso workstations are other OUs by location: i.e.: 'Bangalore'; 'Harare'; 'Bangkok': and 'Djibouti'. AD Group discovery dumps everything
into All Systems with no logical organization of locations. We need those location folders so we can throttle client deployment. How do I get Discovery to pick up OU 'locations' and populate those locations with workstations?

Are you talking about AD site? If so, that's collected by system discovery and heartbeat discovery. Thus, if you aren't using System Discovery, you'll have to wait until heartbeat discovery reports in for the client. Based on this info you can create
appropriate query based membership rules for collections that have you manually created. However, this is a bit of chicken and the egg if you want to use it for client agent installation since heartbeat discovery is only reported by client agents themselves.
Thus, you should either enabled AD System Discovery or choose an alternate deployment method like a startup script.
Jason | http://blog.configmgrftw.com

Double users after inter forest migration - sIDHistory in AD discovery

Hey,
we plan to perform an inter forest migration with ADMT.
There we will migrate about 6000 users.
Now we have the problem that after a user is migrated with ADMT the user account is not once but two times in SCCM.
One in old and one in new domain. In active directory the user is only one time (in new domain).
This causes the loose of all collection memberships and primary device assignments.
Having a look at the users we found that they have different SIDs.
In migration of sIDHistory is enable and we can see it successful in active directory.
It is not possible to include the sIDHistory propertiy in Active Directory User Discover of SCCM - or is this just a failure by our environment?
Does anyone have an idea or hint how to solve this or possible causes?
Thank you
mk-maddin

Hi,
Based on my experience, the maintenance tasks will delete the aged Discovery Data.
Delete Aged Discovery Data
Use this task to delete aged discovery data from the database. This data can include records resulting from heartbeat discovery, network discovery, and Active Directory Domain Services discovery methods (System, User, and Group).
Planning for Maintenance Tasks for Configuration Manager
http://technet.microsoft.com/en-us/library/e555d7e3-3681-440a-82d0-319d2b4bdd08#BKMK_PlanMaintenanceTasks
You can view the default list of object attributes returned by Active Directory User Discovery, and configure additional attributes to be discovered in the
Active Directory User Discovery Properties dialog box on the
Active Directory Attributes tab.
In addition to the basic information, you can configure the discovery of extended attributes from Active Directory Domain Services.
Active Directory User Discovery
http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_ADUserDisc
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.

Difference between delete aged discovery data and delete inactive client discovery data maintenance tasks

I'm setting up a new CM12 site and one issue with our current CM2007 site that I'm trying to minimise in this new site is the discovery and retention of dead clients.
I think the new options as part of the system and group discoveries to only discover systems that have logged on to a domain/updated their password in a set period will resolve the majority of the problems we have here. I've set both of these to 30 days.
Management are keen to be pretty aggressive with the retention period so we're looking to only keep computers in the database that have heartbeated within 30 days. I've set the heartbeat discovery to 8 hours and now I'm looking at the maintenance tasks.
The task I think I need to configure is 'delete inactive client discovery data'. I've set this to 30 days and to run every Saturday. If I look at the 'delete aged discovery data' task it's set to 90 days every Saturday. How will that affect things?
Do I need to make both tasks match?
P.S. Thoughts on the retention period...is 30 days too aggressive? My original design was 60 days.

I do have question about this and more related to "Delete Aged Discovery Data". I've got following configured in my environment for AD Discovery (Development environment)
do not discover machine not logged on for 80 days | do not discover machines not changed password for 80 days.
if I run the query select * from v_r_system (nolock) where datediff("dd", last_logon_date0, getdate()) > 80
it returns about 600 devices.
The task "Delete Aged Discovery Data" is also configured to remove anything that has not been discovered in last 80 days. When this task run I would expect that the 600 devices should be removed from the db, however it only removed 1 device ???
question I have
do you know which other criteria is taken into consideration for this to work. I'm currently using SQL Profiler to determine which StoredProcedure/Function is used to remove these devices.
this is my development environment I only have 2-3 clients all the other devices are just discovered with no SCCM Client installed.
do the devices have to be discovered as part of AD Device discovery or is it sufficient that they get discovered through AD Group membership, in our environment AD Device discovery will not work as we don't have WINS/ DDNS enabled.
thx for any help.

Client "discoverying" SCCM Server?

Hi,
I got a strange problem, we are in the process of implementing the SCCM 2012 R2 into our company, and for testing purposes i designated only one OU to be discoverable by our new SCCM 2012 R2 server, but every now and then another computer is discovered randomly.
How can that be when those computers which are discovered are nowhere near the OU in which SCCM is setup to discover computer objects. Right now I only have one test computer object inside.
Only two discovery methods i have enabled in this moment are heartbeat discovery and AD system discovery.
Thanks,

Look at the client version. It's a down-level client left over from a previous 2007 installation.
It's not truly manageable from the 2012 site, but the client doesn't know that so its sending its info up and because the discovery format hasn't changed, the 2012 site is still creating a resource for it.
Jason | http://blog.configmgrftw.com | @jasonsandys

System Discovery Issues in SCCM 2012

SCCM is not discovering all resources from AD OU. What could be the reason for this. This is not happening for all OU's but randomly for some of them.
Is there a method to force the system discovery to run instantly ?

Thanks Jason,
I think my query was mixed up.
2) Will the status be NO client ?, If yes, does that mean the complete
cycle will start again? Meaning as the client is already inactive, it will not send any more hearbeat and configmgr will again wait for the specified days before deleting it again ?
I know the difference between AD and Heartbeat discovery. I am trying to get a clear difference between
delete Inactive discovery data and delete
aged discovery data.
I checked a blog, I think this is from you http://www.myitforum.com/forums/Delete-aged-discovery-data-and-delete-inactive-client-discovery-data-m204924.aspx
, where it says "For the Delete Inactive Client Discovery
Data task, if you haven't cleaned up AD, the object will get recreated (without the client installed flag). If you auto client push enabled, ConfigMgr will try to push to the system again"
What I get from here is, client status will be NO when it is rediscovered from AD.
Now if the machine was already deleted with Delete Inactive discovery data maintenance task, and its rediscovered, the client will again become Inactive as the machine is
not in use. Will the Inactive discovery maintenance task wait again for defined days before it deletes this machine from the database.

Admin Console displays wrong Hardware Scan and Heartbeat DDR times

When we open up our collections to "Show Members" and add the Hardware Scan and Heartbeat DDR display columns, we notice those times do not reflect the actual times of the last Hardware Scan listed in the Resource Explorer or
the Heartbeat Discovery time shown in the properties of the DDR. Is there an evaluation rule that I am forgetting about?

I believe that information is summarized every hour rather than displaying live info. You may have to close the node or refresh the resource to get it to update after being summarized.
I'm not finding any specific information in the documentation or anywhere in the console that this is controlled. Maybe someone else has more concrete info.
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
<-- If this post was helpful, please click "Vote as Helpful".

New SCCM Discovery with existing Device

Sorry for the English, but I have a existing installation of SCCM 2012 SP1 in productino enviroment. I have just noted that a client with windows 7 was formated and installed with windows 8 Enterprise. The client of SCCM was manually reinstalled and the
client come backup with activity in SCCM, but some data records was not updated. I noticed that the version of Operating System was Updated to 6.2 (Windows 8) But the description continued showing "Windows 7 Enteprise Edition", that was the description
of the device before formatted. The name of Windows 8 Enterprise Edition only appeared after we deleted the device object and waited for the device to be automatically recreated. Then, the description of Operating System was informed correctly.
How can i be able to confirm that formatted machine has a full update in database?
Cláudio Costa - http://claudio-costa.blogspot.com

Information changes like operating system will be reported/updated when the client runs a heartbeat discovery. You can force that in control panel/configuration manager icon, on the actions tab run the Data discovery cycle.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

AD System Group Discovery not updating System OU Name on computer object when computer moves OU

2 related questions.
1. We have noticed that computer objects (active clients) in ConfigMgr are not getting their System OU Name discovery data updated when a computer account is moved from one OU to another, and AD System Group Discovery runs. Since we are basing some of our Software Updates collections on AD OU name, these systems are not falling into their required collections.
2. On a few occasions we are also seeing duplicate computer objects being created. One new record from AD System Discovery, which contains the correct 'new' System OU Name, and one 'old' computer object from before the computer account was moved to a different OU in AD. The heartbeat discovery of this second object is still updating e.g. showing new heartbeats, but the computer object still shows the old System OU Name from before the computer account was moved in AD. If we delete both objects and run a Discovery Data Collection Cycle from the client, and AD System Group Discovery, then we get one new record with the correct 'new' set of System OU names.
This duplicates issue is happening in both our Central Primary Site and our other child Primary site. Both sites are set to create new client records for duplicate hardware IDs, and there is a possibility we're seeing the duplicate records on machines that have been re-imaged and redeployed at some point.
It's my understanding that it is AD System Group Discovery that updates the System OU Name property on client objects. We have this set to run every 4 hours. I'm not seeing any errors in the adsysgrp.log. Any idea why discovery is not updating the System OU Name information when a computer account moves OU? As far as I understand it, nothing additional is required to happen from the client end for this property to get updated.

The only thing I can think of would be ad sys group discovery not running at the site where the client is assigned to?
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
HI Everyone..
ANy reply or correct answer to this question???
Same problem even i have. Duplicate machine names created when machine moved to different sites.
And also, AD sys group discovery running on all the sites (i have 4 sites).
System Security analyst at CapG

Generating a report for clients that are not registered

Hi - Hopefully someone can assist. We are looking to generate a report in SCCM 2012 that will tell us if a client is properly registered, and most recent scan.
I can't seem to find a generic report for this task, so does anyone know if one exists - or how to create a custom one?
Thanks!

what means "properly registered" in your eyes? To me, if it was able to communicate at all--heartbeat; that means it had to have registered. But maybe you have a different criterion.
So I think what you want is simply something like...
select s.Netbios_Name0, max(disc.AgentTime) as LastHeartbeat
from v_r_system s
left join v_agentDiscoveries disc on s.resourceid=disc.resourceid
and disc.AgentName = 'Heartbeat Discovery'
Group by s.Netbios_Name0
order by LastHeartbeat desc
where the most recent heartbeat at the top; and boxes with no heartbeat reported will be null at the bottom. If you don't want to even "see" the boxes that have never reported a heartbeat successfully, then don't left join, use just Join
You could also use v_r_system_valid, instead of v_r_system. As you can tell by the name, _valid means that CM itself has determined those are valid clients; so that might be what you think of as "properly registered".
It all boils down to what means "properly registered" to you, and what you mean by "recent scan". is a recent scan a heartbeat? a software update scan? hardware inventory reported? and what means "recent". the sample above is
reporting on anything and everything regardless of date.
As for default reports, you're saying that the default reports in "Client Status" don't fit your criteria?
Standardize. Simplify. Automate.

Request for info regarding MAC address population in computer objects

Hi,
I am trying to determine how MAC address information is populated in computer objects. I had assumed initially that the hardware scan would be used, but observation shows this information
to be obtained prior to any hardware inventory.
I have laptops that are primarily connected via VPN, and before long their objects lose the internal network interface's MAC address. When I try to rebuild them, they fail to PXE boot. I have
found that importing a CSV of host / MAC / SMBIOD GUID will update the object (rather than having to delete and recreate it) which works temporarily. The MAC will eventually disappear, and the device fail to PXE boot.
I have thousands of these devices to manage, and it is already difficult enough having a CAS and two primaries (the windows Deployment Service on a DP only cares about devices in the DPs primary
site, and so devices that move site are a real pain already, try finding that anywhere in the OSD reference documents!)
I'm assuming now that this information is pulled from the actual client-server connection, and therefore is dynamic(ish), like IP information. If this is the case, more detail around that process,
where to find evidence of that process occurring would be very useful.

The MAC is updated by hardware inventory and heartbeat discovery.
Torsten Meringer | http://www.mssccmfaq.de

Problems (?) with install CU4 on SCCM 2012 R2

Hi,
Today I have installed CU4 on my test SCCM enviroment (before I will install it on production). My test lab is:
1. One Primary Site server
2. One Secondary Site server
3. One server with Distribution Point role installed
First I have installed CU4 on Primary site server - without any issues.
Next I have done that same on Secondary site server - no problems also.
As final step I have use "Install Client" option with "Uninstall prevoius version". It has also was done with success.
After that I decided to check test infrastructure has been really updated to CU4. In distmgr.log, PkgXFer.log there was no errors. On ccmsetup.log there was info SCCm Client instalaltion has been done without errors also.
When I click RMB on distmgr.dll located on SMS\bin\x64 and choose Propoerties, there was info on "Detail" tab - file version 5.0.7958.1501. But when I do that same on smsexec.exe on "Details" tab there was file version 5.0.7958.1000 (that
situation is on all servers - PS, SS and DP as well..). It is normal? If not why it has been happened and how can I fix it?
I have next checked in SCCM console, on Asset & Complilance-->Devices all three servers in column "Client version" still has 5.00.7958.100 instead CU4... - I suppose it is not normal also...
Thank you for any suggestions and explanations.

Hi Bartas!
>here was file version 5.0.7958.1000
Not all files are modified by each CU. This is normal - smsexec.exe should still be at .1000 after applying CU4.
>"Client version" still has 5.00.7958.100 instead CU4... - I suppose it is not normal also...
This column will not be updated until the next Heartbeat discovery happens. You can force this by triggering the "Discovery Data Collection Cycle" client action on the device, waiting a few minutes, and then refreshing the record in the console.
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Last Logon User name query attribute not populating

I have created a query that looks for all desktops in my environment and returns the hostname of the PC, the computer system model, and the last logon user name of each machine. The problem is about 200 PCs do not have the last logon user name field
populated. The remaining 350 desktops and all laptops are reporting this. I have been looking at this for the last several days but cannot find a reason why. I verifed the PC have had at least one person log into them. I thought maybe
it is an issue with the SCCM client on the PCs so I have tried unistalling/reinstalling the client on a few machines. After the reinstall is complete, the query shows my domain account as last logged into that PC, as I would expect. However, no
matter how many times I log into and out of the same PC with a different domain account, the query doesn't show this. Can anyone help with some direction with this? I am running Config Manager 2012 SP1 CU2.
Thanks in advance.
Mike G

Audit logon events it set to capture success and failures. The Heartbeat Discovery is set to send every week.
Check your DDM log on site server and look for any error messages.
I personally run my heartbeat discovery every day.
You can try to adjust your discovery interval and see if that helps. If you can run it manually and it works, I can't think of anything that it would prevent it from working site wide with currently scheduled interval.
Also, if you have adjusted your aged data maintenance tasks, this is something worth noting:
The default schedule for Heartbeat Discovery is set to every 7 days. If you change the heartbeat discovery interval, ensure that it runs more frequently than the site maintenance task Delete
Aged Discovery Data, which deletes inactive client records from the site database. You can configure the Delete Aged Discovery Data task
only for primary sites.
http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_HeartbeatDisc

SCCM 2012 client not being reinstalled after OS re-image

So last spring I rolled out SCCM 2012 and set up the whole boundary group/discovery thing so that it automatically populated my device and user collections based upon Active Directory. All of my computers (app. 750) have been available in SCCM for
a year now. All was good - I was interacting with my comptuers and deploying software through SCCM with no issues. Now I'm doing OS re-installs (the OS image does not have the SCCM client pre-installed) on computers. These are computers that
were previously known to SCCM, but after restarting them with a fresh version of Windows, the SCCM client software does not get re-deployed to them. I've let them sit for hours, days, even a week. I have Client Push Installation configured for
the site with an account that has both rights to the SCCM server as well as local admin rights on each machine. If I browse to that machine in its device collection (where it remains listed), I can right-click it and manually install the client.
That works just fine. But I don't want to do that for 750 machines. Can someone please tell me what I'm missing? Thanks!

No I am not deleting old computer records. I'm the only one who administers the SCCM site but we have many technicians who go out and repair computers that may involve re-imaging. They don't always take the time to communicate each one to me.
As for using SCCM for OS deployment, we're currently using WDS because that's what we had first. I put SCCM in place just to have a flexible way to deploy software. My next step - probably later this summer - will be to find a way to move
imaging over to SCCM as well. However, this is not an immediate need. What is immediate is that we're about to re-install our Windows image on hundreds of computers starting in a week or so and none of them are getting a client after the fact.
I have client push, heartbeat discovery, and clear install flag all configured but these clients just don't get reinstalled. If I go to their device collection and tell SCCM to manually push the client to that device, it fires right off. So I
know it isn't an issue with admin rights within the client push settings.

Heartbeat Discovery

Similar Messages

Maybe you are looking for