I implemented Lync back in December, having done a few OCS installs.. Lync
was much better by far; highly recommend it. I too looked into the schema
changes, and found them to be benign should we want to back out of it after
all.

-B


On Wed, Jul 13, 2011 at 11:54 AM, Richard Stovall <[email protected]> wrote:

> I appreciate the heads up.  We're licensing per product at the moment.
>
> On Wed, Jul 13, 2011 at 2:36 PM, Paul Hutchings <[email protected]
> > wrote:
>
>>  FWIW if you’re on Core CAL you should see Lync Standard CAL’s added in
>> August leaving “only” the server to license.****
>>
>>
>>
>> ****
>>
>> *From:* Richard Stovall [mailto:[email protected]]
>> *Sent:* 13 July 2011 19:32
>> *To:* NT System Admin Issues
>> *Subject:* Lync 2010****
>>
>> ** **
>>
>> I've been asked to check out options for corralling / bringing IM
>> in-house.  Current policy allows employees to use AIM, etc. but that's going
>> to change.  If they want to use IM in the future, they'll have to use the
>> company-provided solution, whatever that turns out to be.****
>>
>> ** **
>>
>> Since we're a Microsoft shop, I started to install a trial of Lync 2010 on
>> a shiny new VM in our production domain, but stopped when the installer
>> said, "OK.  Let's extend your Active Directory schema."****
>>
>> ** **
>>
>> I can certainly build a test domain to play with, but the real test will
>> be getting the current IM users (we've only got about 10) to buy into the
>> new solution.  I was planning on setting it up and letting them run with it
>> during the trial period.****
>>
>> ** **
>>
>> My dilemma is that I hesitate to modify the schema if we might ultimately
>> decide against using the product, yet I need real people on the company
>> domain to use the software in a genuine work setting.****
>>
>> ** **
>>
>> Are the schema extensions 'benign' enough (for lack of a better word) to
>> not worry about in case we uninstall Lync after the demo and go with another
>> solution?****
>>
>> ** **
>>
>> Thanks for any input,****
>>
>>
>> RS****
>>
>> ** **
>>
>> Potentially relevant info:  Small shop with ~50 total users, AD = 2008 R2
>> DFL and FFL, Exchange 2010 with a few mailboxes yet to migrate from 2003.
>>  ShoreTel phone system.  Only looking for IM (Lync Standard CAL)****
>>
>> ~ 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****
>>  ------------------------------
>> *MIRA Ltd*
>>
>> Watling Street, Nuneaton, Warwickshire, CV10 0TU, England
>> Registered in England and Wales No. 402570
>> VAT Registration  GB 100 1464 84
>>
>> The contents of this e-mail are confidential and are solely for the use of
>> the intended recipient.  If you receive this e-mail in error, please delete
>> it and notify us either by e-mail, telephone or fax.  You should not copy,
>> forward or otherwise disclose the content of the e-mail as this is
>> prohibited.
>>
>> ~ 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