I've just received a proposal to install some calendaring software on one of our exchange servers that requires a lot of things I'm pretty uncomfortable with.... without divulging too much about the software (I'm not under non-disclosure--but I'm not under disclosure either!). This software requires:
Installing Outlook 2000 client on server Installing Visual Basic (yes the development platform--why not just the dll type libraries? I don't know) Setting up a profile on Outlook using the "administrator" inbox for security purposes A dll COM object that has a sink to catch calendar items All this goes on the server--and this isn't just throw-away server. This is a critical box with 2000 users and a 55 gig store. It will be Ex2k at install--so I may split the store at that point. I can see maybe installing a com object--if you want to use object event sinks that seems logical but the other stuff just makes me question the whole project and the knowledge behind the development... but I'm not a developer. Any thoughts? I've read that putting outlook on your exchange server isn't a great idea because they share dll's. But I've done it and test before and never seen a real problem... Installing VB on a production exchange box, though, just seems silly! I'm uncomfortable installing in VB dlls on the box--as many unstable VB apps as I've seen, but I'm looking around for a little more teeth to my argument. Josh Harmon Server Admin and now external program analyst _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
