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

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

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

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.

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

Yeah, CPU usage drops immediately after IPCONFIG /release

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

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

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.

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.

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.

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.

Hi,

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

Rgrds,
SAM

Upgrading to ru5 solves many problem so do upgrade to it