SMC.exe takes 99% CPU.

SAM_SHAIKH's picture

Hi,

We are using SEP 11.0 MR4 MP2 on the below config machine.

After the deployment we did found SMC.exe uses 99% of CPU.

We have installed all the component on the client

Dell Optiplex 755
Intel Core 2 Duo 2.33 Ghz
1GB RAM

Do let me know if its a known issue.

Rgrds,
SAM

Samuels's picture

same issue already discu

 http://www.symantec.com/connect/forums/smcexe-high-cpu-usage

same issue is already discussed in above link....just refer to it.....hope you will get some idea about your issue......

Suren Gundumalla's picture

 Do you have any VPN client

 Do you have any VPN client software installed? Are you seeing on all the machines? Are you logged into this machine remotely?

SAM_SHAIKH's picture

HI Suren, There are no VPN

HI Suren,

There are no VPN software installed on the user machine. We are currently facing this issue on a single user. We are not logging into the machine remotely.

There are 5 machines and we are facing issue on only 1 machine.

We did the re-installation but still the problem persist.

Rgrds,
SAM

Ajitjha's picture

Recreate a pakage nd

Recreate a pakage nd re-deploy.it shld fix it

Regards'
Ajit Jha
TechSuport Engineer
STS

Chris V's picture

Resolution?

I'm facing the same issue as described here. Was there a resolution for this?
I have SEP 11 MR 4 MP 2 - its an entirely new installation.

kavin's picture

Try to do an IP release &

Try to do an IP release & dont renew it & see if it reduces the CPU usage?
Let me know.

Bijay.Swain's picture

Hi kevin I tried this and yes

Hi kevin I tried this and yes it reduces cpu uses . so what could be the problem. and what to do.

Chris V's picture

Yeah, CPU usage drops

Yeah, CPU usage drops immediately after IPCONFIG /release

MKN's picture

Does it goes high after that

Does it goes high after that and after how much time. Any specific thing after which it goes high(If it goes high)

Chris V's picture

It remains low, until

It remains low, until renewing IP at which point it consumes 1 CPU again.

MKN's picture

These are few thing those you

These are few thing those you can try

-- Display the routing table with "route print" and identify the route that shows the local subnet with the gateway set to an ip other than the local machine.
-- Disable the network adaptor or release the IP and re-check the routing table for persistent entries.
-- Remove the bad routing table entry with "route delete".
-- Re-enable the network adaptor or renew your IP.
-- Request a policy update from the SEP client and it gives a green dot.

Chris V's picture

I'm not sure what we're

I'm not sure what we're trying here.  I have no persistant routes, and only one external gateway route which points to our WAN (The Management server is at another site).
If I RELEASE the IP I lose all routes, which renders the 3rd step invalid.  As soon as i RENEW all original routes are restored.

SV's picture

upgrade to MP5 it will work

upgrade to MP5 it will work

Please see note below on how stop SMC service on a desktop if its going through the roof

• Open regedit
• HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SYMANTEC ENDPOINT PROTECTION\SMC\smc_exit_test 1 to 0

Then from the Symantec installed DIR etc c:\program files\symantec\symantec endpoint protection\

Then run.

• SMC –STOP

Then run an upgrade.

Then run.

• SMC –START

Then all done !!!

Enjoy.

AravindKM's picture

Try buy upgrading to RU5 From

Try buy upgrading to RU5

From RU5 relese note
Fix ID 174134
■ Symptom: After upgrading a Symantec Endpoint Protection client,
communication with the Symantec Endpoint Protection Manager fails because
the default gateway is not in the same subnet.
■ Solution: Enhanced the process to find the best route to the server after the
gateway IP address changes.

 

SAM_SHAIKH's picture

Hi, Will be going to upgrade

Hi,

Will be going to upgrade to MR5 next week. Will update the same here in forum.

Rgrds,
SAM