Recent content by VictorySabre

Hi All, Our company is currently preparing for some reorganization/changes in the coming months (certain business units sold to another company), which includes changing the domain name. We're currently in just the planning/information gathering phase. Since I look after our SMS 2003 SP3...

I'm not familiar with the use of BDD 2007 (someone else in our dept is looking after it), but have you tried building a silent VSE 8.5i install package using the McAfee Installation Designer and use that custom package in BDD to install the client?

I hope that is a typo for Patch 4 in October. I hear Patch 2 was scrapped as it BSoDs PCs and they are now working on Patch 3. I hope they don't already know that Patch 4 is already required as Patch 3 doesn't fix all issues.

pytchley, Are you referring to your response regarding the On-Demand Scans running at 100% or are you referring to another message? I believe the 100% On-Demand Scan is different than the 100% McScript_InUse process which only occurs when AutoUpdate is running and not related to a full scan.

OK, fair enough. Not sure if you have ePO or not. I'm only familiar with ePO. If you don't have ePO, I know within the VirusScan Console, you can import an updated AutoUpdate Repository list, but I'm not sure how you can automate that across 200 PCs. Simplest way if you are using ePO (in case...

Is there a reason why your security people want to disable the NAIHttp entry? All of our clients are set to use our own internal repository, but in the event there is a peoblem with our ePO Server or I've taken the server offline to troubleshoot, clients will then get their latest DAT updates...

What I do is build a new Package, but leave my Source Directory field empty in the Data Source tab. You can enter the rest of the required info into the rest of the Package fields. I then create a new Program and call it Silent Uninstall. (You can call it whatever you like) In the Command Line...

I managed to get the answer from MyITForum.com. Turns out that I need to modify the AssessmentConfig.XML file located inside the PkgSource folder and add the MBSA 2.0.1 scanner info to get it to work. So if you look at the XML file, this is what I've updated: . . . <Scanners> <Tool>...

I'm currently testing the Vulnerability Assessment tool that comes with SMS 2003 R2 and it worked fine on my test PCs initially. Then when MBSA 2.0.1 came out, I upgraded some of my PCs manually to that new version and now the Vulnerability Assessment tool refuses to run on these test PC. I get...

Hi Mizzy, I'm not familiar (have not encountered it on my end) with the error you've reported in your log. Since I haven't experienced it on my end, I probably would perform the following actions to see if any of it helps: (Best to try it on one of the PCs you can easily access locally) Have...

Hi Mizzy, From within the ePO Console, select the name of one of the PCs that appears to be having problems with DAT updates, then select the Properties tab on the right hand side of the window, and then expand System Information. If you look at the Last Update entry, check and see if the...

The only thing that I had to do was get our firewall guy to allow our ePO Server access to http://myavert.avertlabs.com:8801. Once he opened that up, my server no longer showed Last Check: Failed. As for the Security Threads bulletin, so far it doesn't appear to be used by McAfee because I...

Hi SPV, I agree that the data should be stored on a file server and that should reduce the amount of data being scanned on the developers' PCs. I've suggested that over 2 years ago, but I've been told that won't fly because our culture/environment. Because of this, we've been forced to do...

That is very useful info indeed. We use SMS and whenever it runs its inventory, it is essentially forcing our clients to do a "scan". By putting that into the low risk process, that prevents the scan from running. I think this is something worth considering and testing in our environment to see...

Thank you for the feedback Terry712 and gdvissch! We used to get some moaning from our end users and we've always accepted it as part of the protection, but lately we've been getting more louder moaning, even from some high profiled employees in the company (Exec VPs, Project Managers, and even...