Loading Profile...
Recent activity
Subscribe to this feed
wquin1s replied on June 12, 2009 16:44 to the question "Does Deployment Package include McAfeee uninstallers?" in Sunbelt Software:
Nevermind, I had to call support to get the quick answer. No, it does not get packaged if you use the self-contained executable. Only works through automated deployment. I wonder why nobody replied.-
wquin1s asked a question in Sunbelt Software on June 03, 2009 17:16:
Does Deployment Package include McAfeee uninstallers?We have configured our VPE to include the uninstaller for McAfee. Does the uninstaller also get packaged when you create a Deployment Package (self-executing EXE) or does it only work when you deploy using Automated Push/Pull installation? The reason I'm asking is because we used a packaged executable but McAfee services restarted after the reboot so it basically locked up the computer after logging on to Windows. -
A comment on the problem "sbamoutlook.dll reenabled and causes Outlook 2007 to hang." in Sunbelt Software:
That is the problem, all of the new policies including the default policy was never set to enable email protection in the first place. At first we encountered the issue on our Terminal Server which was deployed using the default policy settings where Outlook 2003 hung for all TS users. And now we encountered it with Outlook 2007 on Vista. When I tried to unregister the DLL on this Vista PC with the correct path, it encountered an error saying "DLLUnregisterServer failed with error code 0x80070005." But somehow it still is disabled in Outlook add-ins so at least Outlook is no longer unresponsive. – wquin1s, on April 21, 2009 21:50 -
A comment on the problem "sbamoutlook.dll reenabled and causes Outlook 2007 to hang." in Sunbelt Software:
John, neither of those possibilities occurred on this Vista PC (at least, not that I am aware of and done it myself). As a matter of fact, I left it on in working order yesterday afternoon and "locked" my Windows session. After that, the only thing I can think of that would change is the DB version update early this morning. So right now, the only fix to this issue when deploying new agents to similar PC's is go and unregister the DLL after the agent installs? – wquin1s, on April 21, 2009 20:00 -
wquin1s reported a problem in Sunbelt Software on April 21, 2009 16:29:
sbamoutlook.dll reenabled and causes Outlook 2007 to hang.For the past 4 days all have been fine with a Vipre Enterprise Agent installed on a Vista Business SP1 using Outlook 2007. Today, Outlook hung 3 times having to end task via Task Manager before it prompted that Outlook crashed due to plug-in "sbamoutlook.dll" therefore it asked to disable it. I believe it was disabled when I first installed it on this Vista PC. So how come it was re-enabled? Is that due to threat db update? And according to the other posts here, there should be a fix in the next agent release? Is the option to disable Outlook plug-in from the console working? Obviously, the policy does not have email protection enabled so you would think the plug-in should be non-existent at the workstation it was deployed to.
The other thing I noticed in the console is that this Vista PC is reported as inactive but it normally stays on 24-hours and the vipre tray icon is visible on the Vista PC. I even opened the Vipre agent GUI and also pinged it using the option on the Enterprise console. -
A comment on the question "VPE Server & Console on VMWare Virtual Server?" in Sunbelt Software:
Yes, the virtual server guest OS basically was unstable. Just opening up the console took a very long time. There were times when I tried to deploy 2 to 5 agents from the console to remote physical (non-virtual) Windows XP workstations and it would use up at least 90% CPU and then eventually will lock up the console. When I try to run an agent scan on other workstations from the server console it would lock up because of high CPU. And the other times when I leave th Console running for a couple of days, it would just be unresponsive to mouse-clicks, task manager or even a safe reboot. So I would have to stop & start the virtual server manually. We also have encountered the error "Unable to start remote service" maybe a couple of times when trying to login to the console. Again, I suspect that the issues are due to a low spec allocated for the virtual guest OS since this is not happening to the new server currently in use right now. – wquin1s, on April 20, 2009 20:03 -
wquin1s asked a question in Sunbelt Software on April 20, 2009 18:45:
VPE Server & Console on VMWare Virtual Server?Has anyone successfully ran VPE + Console on a VMWare Virtual Server guest with Windows Server 2003 SP2? In our case, we tried running it on a Dell PowerEdge server and allocated 1 processor to the virtual server (Pentium III 1 GHz, 1 GB RAM and 70 GB HDD) which fairly exceeds the requirements of VPE but encountered numerous problems. At this time we are running it on a non-virtual server with Pentium 4 3.0 GHz and 2 GB of RAM. It has not locked up so far. So we are just wondering if there is a tried-and-true recommended specs for running it under a virtual environment. -
A comment on the question "Vipre Enterprise Agent inactive on Terminal Server" in Sunbelt Software:
Jason, setting install mode I am aware of. Thank you for pointing me to the right direction since I "pushed" the agent, I would have to treat it as any other install on a TS environment. I have already created a deployment package so I will try that after the restart since now the service is hung. Do you recommend running the removal tool instead or reinstalling should just overwrite the current install (in Install mode of course)? – wquin1s, on April 17, 2009 22:35 -
wquin1s asked a question in Sunbelt Software on April 17, 2009 21:58:
Vipre Enterprise Agent inactive on Terminal ServerIs Vipre Enterprise Agent fully supported on a Windows Server 2003 hosting Terminal Services? What happened is that it worked for a few days after remote deployment and then afterwards on the console, it says that the agent is "Inactive". However, this server is always on. I tried restarting the Vipre service on the Terminal Server but it got hung to "stopping". Looks like we may have to restart the server when given the chance. -
wquin1s replied on April 09, 2009 17:06 to the question "Why Vipre's definition files are so huge?" in Sunbelt Software:
Does this include changing the definition updates to be all-inclusive of the previous ones if you missed a couple of days connecting to the internet? I am evaluating the home version that missed 3 days worth of updates, and it took forever as it was downloading and then installing the update one at a time. -
A comment on the question "How can I push an agent to a Windows XP workstation on a different network/domain?" in Sunbelt Software:
John, as a matter of fact, I did that (save as IP) thinking it should eliminate the issue but it did not. I can telnet fine from the workstation to the server on port 18082 using the server IP address. When I try to reinstall the agent using a push deploy and select the computer (which it lists on the domain tree), it says "unable to resolve IP address for the selected computer". I get the same error as well even when I try to type in the target IP in the Manual Entry box. – wquin1s, on April 06, 2009 22:54 -
wquin1s started following the problem "Vipre hangs Outlook 2000 when closing" in Sunbelt Software.
-
wquin1s asked a question in Sunbelt Software on April 06, 2009 20:40:
How can I push an agent to a Windows XP workstation on a different network/domain?How can I push an agent to a Windows XP workstation on a different network/domain? I also tried using the Deployment Package option and manually executing the install at the remote workstation but after the restart, Vipre agent does not seem to start automatically.
