If the OP only wants to do single server configs (e.g. single edge, single frontend) standard is fine. You need Enterprise to go to a pool config. Enterprise CAL is required for the voice stuff in particular.
Definitely want to budget for certs - DigiCert is where I would go for that. Not sure offhand what the costs are to light up PIC - I didn't remember there being a turn-up fee. Thanks, Brian Desmond br...@briandesmond.com c - 312.731.3132 -----Original Message----- From: Steven Peck [mailto:sep...@gmail.com] Sent: Monday, May 10, 2010 5:40 PM To: NT System Admin Issues Subject: Re: log Windows Live Messenger conversations There is a charge for the initial PIC connectivity so don't forget to look that up too and you will need a cert for that. If you have an ISA server there are some scenerios that let you use that for a pass through edge server. We have the Enterprise version so I am vague on the differences in standard vs enterprise. On Mon, May 10, 2010 at 3:25 PM, Bill Songstad <bsongs...@gmail.com> wrote: > Thanks guys. I knew there was some sort of communications server. It > never occurred to me that it was an Office branded product. Looks > like cheap is not going to be in my solution. Not terribly expensive > either though. List is $700 +31 per user. > > > Thanks, > > Bill > > On Mon, May 10, 2010 at 2:58 PM, Steven Peck <sep...@gmail.com> wrote: >> >> OCS with Archiving and federation. Otherwise some network logging >> appliance but i fthe clients are using something like SimpLite then >> you are out of luck >> >> http://www.secway.fr/us/products/simplite_msn/home.php >> >> Get OCS2007r2. Connecting with MSN and Yahoo Public IM (PIC) >> networks now does not require a license. Just block AOL or pay for licenses. >> >> Steven >> >> On Mon, May 10, 2010 at 2:54 PM, Brian Desmond >> <br...@briandesmond.com> >> wrote: >> > Bill- >> > >> > >> > >> > You need an appliance. I know Symantec makes one as a previous >> > employer imposed this upon us. Depending on your FW/Proxy >> > environment that vendor might also make a plugin or have a 3rd party addin >> > to it for this. >> > >> > >> > >> > A better solution would be something like OCS with Archiving and >> > Federation w/ MSN, etc., IMO. >> > >> > >> > >> > Thanks, >> > >> > Brian Desmond >> > >> > br...@briandesmond.com >> > >> > >> > >> > c - 312.731.3132 >> > >> > >> > >> > From: Bill Songstad [mailto:bsongs...@gmail.com] >> > Sent: Monday, May 10, 2010 4:52 PM >> > To: NT System Admin Issues >> > Subject: log Windows Live Messenger conversations >> > >> > >> > >> > My office uses WLM for communication to supplement email and telephones. >> > That battle is lost. But the next battle is to log communications >> > through that medium for legal purposes. My Google Fu has been less >> > than encouraging as the popular opinion is that since there are no >> > GPOs for WLM and since the reg keys needed are encrypted and >> > unpredictably variable, it wouldn't be possible to turn on logging >> > with Group Policy. >> > >> > >> > >> > So what I am asking is: Does anybody know how to, or have a strategy to >> > administratively turn on logging for Windows Messenger? Or will I just >> > have to disable it if we ever become involved in a lawsuit? >> > >> > >> > >> > What I need to do is turn on message history and prevent users from >> > turning >> > it off. Ideally this would be something I could turn on or off as >> > needed. >> > >> > >> > >> > Any insight would be appreciated, >> > >> > >> > >> > -Bill >> > >> > >> > >> > >> > >> > >> > >> > >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
