No, they’re all default.

Regards,
Freddy

From: [email protected] [mailto:[email protected]] On 
Behalf Of Duncan McAlynn
Sent: Monday, 28 December 2015 8:14 AM
To: [email protected]
Subject: [mssms] RE: Constant Client Activity on Non-Domain Network

Are you using custom ports for client communication?

[cid:[email protected]]

Duncan McAlynn, Sr. Solutions Specialist, Americas
HEAT Software
M: +1.512.391.9111 | 
[email protected]<mailto:[email protected]>
HEAT Software<http://www.heatsoftware.com/> |  490 N McCarthy Blvd. Suite 100 | 
Milpitas, CA 95035

Ask 
me<mailto:[email protected]?subject=Why%20are%20you%20THE%20leader%20in%203rd%20party%20patching%20for%20Microsoft%20System%20Center?>
 why we’re THE leader in 3rd party patch management for System Center

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Freddy Grande
Sent: Saturday, December 26, 2015 6:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Constant Client Activity on Non-Domain Network

Hi All,
I’ve been trying to figure out what could be causing this but I’m not sure 
where to start looking and can’t see anything obvious online.
Basically we have a single server ConfigMgr environment (2012 R2 SP1 CU1 (or 
CU2?)), clients are intranet only. I only noticed lately (because I seldom take 
my computer home until now) that at home the fan is usually running at near 
full blast and task manager shows Host Process for Configuration Manager using 
up ~100% disk. This kills the battery life on my Surface Book and I’ve been 
resorting to stopping the SMS Agent Host service which alleviates the issue.

The only two logs that get written to during this time are the 
LocationServices.log and StatusAgent.log files.
At work we have multiple boundaries linked to AD sites linked to specific 
subnets (192.168.1.0/24 … 192.168.9.0/24 and a few other different ones) and at 
home my network is on the 192.168.250.0/24 subnet.

Does anyone have any idea why this occurs or how I can stop it? See attachments 
for logs.
It seems to be related to the client trying to reach our server 
BNE-SC-01.marsys.com.au but it can’t resolve it, surely it should stop and only 
try intermittently??

Thanks,
Freddy



Reply via email to