IME, the Vipre Console is a bit of a resource hog.  I only run it when I
need to run a one off report or manually deploy an agent.

On Tue, Jul 26, 2011 at 1:27 PM, <[email protected]> wrote:

> I have loads of consoles and no slowdown. I use a virtual desktop too. I
> have loads of RAM, and very occasionally an MMC will eat loads of memory,
> but that's usually when I haven't rebooted for weeks
>
> Sent from my POS BlackBerry wireless device, which may wipe itself at any
> moment
> ------------------------------
> *From: * David Lum <[email protected]>
> *Date: *Tue, 26 Jul 2011 17:21:57 +0000
> *To: *NT System Admin Issues<[email protected]>
> *ReplyTo: * "NT System Admin Issues" <
> [email protected]>
> *Subject: *mgmt consoles (was RE: Vipre console hangs server on reboot)
>
> Exchange is not dissimilar. I don’t know if it loads the mgmt console by
> default but it always seemed weird to me that the full installer interface
> was presented when all you wanted was the console.****
>
> ** **
>
> Which brings me to a Q: I have what is effectively my “management” server
> (a VM) that has most of the consoles on it (Exchange, Shavlik, vSphere
> client, etc). I simply RDP to it when I need to administer something (unless
> it’s a web-based tool like PGP or McAfee ePO). Saves me the trouble of
> moving those around when I change PC’s. If I need a hardware upgrade I move
> the VM. ****
>
> ** **
>
> In general I don’t like consoles on my personal machine because they seem
> to load way more services and crap than you really want and once you have a
> few of them your machine becomes slow just doing e-mail and browsing, etc.
> ****
>
> ** **
>
> Is this an unusual setup? I seem to recall reading (years ago)  that this
> was a good idea but didn’t know if many people actually did this.****
>
> ** **
>
> Dave****
>
> ** **
>
> *From:* Andrew S. Baker [mailto:[email protected]]
> *Sent:* Tuesday, July 26, 2011 9:22 AM
> *To:* NT System Admin Issues
> *Subject:* Re: Vipre console hangs server on reboot****
>
> ** **
>
> It also allows you to install the console elsewhere...
>
> Just because SQL server installs a local console by default doesn't mean
> that this is the best place to run it for day to day administration...
> ****
>
> *ASB*****
>
> *http://about.me/Andrew.S.Baker*****
>
> *Harnessing the Advantages of Technology for the SMB market…*****
>
>
>
> ****
>
> On Tue, Jul 26, 2011 at 12:12 PM, John Aldrich <
> [email protected]> wrote:****
>
> I won't swear to it, but I'm pretty sure that the console is designed to
> run
> on the server. I mean it installs the console when you install the server.
> :D
>
>
>
> From: Gasper, Rick [mailto:[email protected]]
> Sent: Tuesday, July 26, 2011 11:59 AM****
>
> To: NT System Admin Issues
> Subject: RE: Vipre console hangs server on reboot
>
> A lot of today’s software is designed to run on a local desktop and then it
> connect back to a server.
>
> For example:  You can administer active directory from your local desktop
> and not log into the server (though I wouldn’t recommend this to a someone
> who doesn’t have any clue about security.)
>
> I am not familiar with the product you  mentioned but sometimes running
> from
> a server is a bad thing.™
>
> From: John Aldrich [mailto:[email protected]]
> Sent: Tuesday, July 26, 2011 11:45 AM
> To: NT System Admin Issues
> Subject: RE: Vipre console hangs server on reboot
>
> I suppose there’s no real reason to reboot the server on a scheduled basis…
> THAT server has never had any real issues… As for not running the Console
> remotely, I really don’t wish to install it on another machine as it’s a
> bit
> of a resource hog. As far as taskkill, I just don’t like killing off a
> process “just because”, and that’s what that seems like to me.
>
>
> ****
>
> From: Andrew S. Baker [mailto:[email protected]]
> Sent: Tuesday, July 26, 2011 11:25 AM
> To: NT System Admin Issues
> Subject: Re: Vipre console hangs server on reboot
>
> A - Why are you rebooting the server on a scheduled basis?
>
>
> B - Why are you not running the Vipre console remotely?
>
> C - What's wrong with Taskkill (assuming you don't wish to address the
> previous two issues)?
> ASB
> http://about.me/Andrew.S.Baker
> Harnessing the Advantages of Technology for the SMB market…
>
> On Tue, Jul 26, 2011 at 11:14 AM, John Aldrich
> <[email protected]> wrote:
> I have to manually shut down Vipre Enterprise Console if I want the server
> to come up on a scheduled reboot, otherwise it hangs the server and I have
> to manually power-cycle the server to get it to work. I checked with
> Sunbelt
> support and they said there is no way to *programmatically* close the
> console when I reboot the server (scheduled task, so it's non-interactive.)
> They suggested using Microsoft's TaskKill. Anyone got any better
> suggestions? Server is Windows 2003R2 standard.****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to