Summary: DLP causing the system to become unresponsive
Description: DLP 18.104.22.1682 , Agent 22.214.171.1249, ePO 4.5 Patch 4 with Hotfix for EEPC 6 , VirusScan 8.7
Have DLP installed on 15,000 xp SP3 machines with no issues.
Testing a new Windows 7 Enterprise SP1 build on WYSE Z90Thin Client 4GB Ram, 80GB SSD, AMD 1.60GHz Processor. Dual Core. Run through the base install and install VirusScan 8.7 with Agent 126.96.36.1999. Reboot and machine functions normally. Install DLP Agent manually and reboot. Login and enforce policies and the machine beocmes unresposnive. I can type in the run command but not press enter. Cannot open Control panel of any MMC s. Cannot start task manager. The machien just hangs trying ever action. In the event log I can see many errors relating to computer browser service unable to start due to dependencies.
I have tried a SATA drive in the same WYSe client as I thought it may be solid state drives but have the same issue. Have also tried Vase Win7 and Win XP.
The issue occurs as soon as the agent pulls done the DLP policy for the first time.
Help ! What can be causing this.
Is this actually a thin client, or is it thin client hardware with local OS etc? If it's the former, I don't believe DLP is supported over thin client due to the way it has to hook into the OS?
Thanks for the quick response. It is Thin Client hardware with local OS.
I am out of ideas on what to try next. The only thing I can think of is to try and find the latest drivers for all components.
how does the hardware compare with a typical modern laptop? Maybe it's just not got the horsepower to run something as complex as DLP?
WYSE Z90Thin Client 4GB Ram, 80GB SSD, AMD 1.60GHz Processor. Dual Core
The issue only starts once the policy is enforced for the first time.
Must be a conflict of some sort - In Agent Configuration under the Miscellaneous tab deselect everything and Apply the policy (assuming you're on a non-production test network) and push that policy to the client.
If that resolves it then enable the modules till you find the offending item. If that doesn't help disable File Tracking under the 'File Tracking' tab and repeat.
Next, do you have very broad tagging/category settings? Is the system really hung or just so overloaded it's running really slowly?
Otherwise use support.microsoft.com/kb/927069 to generate a full memory dump and get it escalated to TierIII for analysis.
McAfee Tier III Support Engineer
Data Loss Prevention