Tuesday, July 24, 2012

OCS R2 July 2012 Updates Released

Microsoft has released a few updates for OCS 2007 R2 Group Chat Server.

Here are the components that were updated for this round of updates:

Group Chat (6907.258)

Monday, July 16, 2012

Big Wave (15) Rolling In…

When Microsoft decided to roll-out (preview) the next collaboration wave, they did it with fireworks.  Today marks the day that Microsoft has released all “Wave 15” products to the public in “Preview” (beta) format.

Obviously, this is going to generate lots of great blog posts which I am really excited about.  There is going to be much more information releasing about this “Wave” in the coming days, but here are some links to get you started.

Lync Server 2013

  • Download –> HERE
  • Documentation –> HERE
  • What’s New –> HERE

Exchange Server 2013

  • Download –> HERE
  • Documentation –> HERE
  • CHM File –> HERE
  • What’s New –> HERE

SharePoint Server 2013

  • Download –> HERE
  • Documentation –> HERE
  • What’s New –> HERE
  • Deployment Guide eBook –> HERE

Office ProPlus 2013

    • Download –> HERE
    • Documentation –> HERE
    • CHM File –> HERE
    • Deployment Guide eBook –> HERE

    Other Miscellaneous Downloads –> HERE

    There is a lot to get through here, and I will be working on bringing you up to date articles explaining the new 2013 features and providing configuration and implementation help.

    What a great day!

    Monday, July 2, 2012

    Configuring Location Information in Lync Without E911

    One of the most underutilized features in Lync is the Location Information Server (LIS) database.  This is due usually to the following:

    • LIS is marketed in the same discussion as E911, which only North America (really US and Canada) can use
    • The configuration is completely performed in powershell

    The LIS can also be very helpful for an organization (no matter what country you are in) for publishing…well, location information.  If a company is very spread-out, either regionally with many campuses or globally with many offices, wouldn’t it be great to auto-populate a user’s location information based on where they are actually sitting that day?  I mean Lync unleashes us from our cubicle and now it is hard to know if someone is actually in the office or working from another company location.

    Lync Loc - client before - markup

    LIS can be configured to do just that, publish location information for your users based on where their Lync client is connecting from.  This post will step you through the minimum requirements to make that happen.

    Location information is based off of network components, such as subnets, switches, etc.  When looking at Lync configuration options for network components, it might be a little confusing.  Lync will use network information (subnets) for four different uses and understanding what the authoritative source is crucial.

    Lync Functionality Subnet Definition Location
    Determining Location LIS Subnets (powershell)
    Determining Location Policy (used in E911 config) Lync Subnets defined in Lync Control Panel
    Call Admissions Control (CAC) Lync Subnets defined in Lync Control Panel
    Media Bypass Lync Subnets defined in Lync Control Panel

    If we are just interested in determining our location and publishing the information, only the LIS subnets need to be defined.  Subnets (including location information) will be configured using the Set-CsLisSubnet cmdlet.

    In our example, we will be creating two different locations.  If you are only interested in publishing location information into the Lync client and do not care about E911 configuration, only the “Location” and “City” field are used to populate the client.  You can use both or either for your configuration.  The following commands are used in my environment:

    Set-CsLisSubnet –Subnet –Location “Building 40” –City “Redmond”

    Lync Loc - set-subnet1

    Set-CsLisSubnet –Subnet –Location “Home Office” –City “Texas”

    Lync Loc - set-subnet2

    Once we have our subnets defined, we need to publish the information to the LIS database.  The can be achieved by running: Publish-CsLisConfiguration cmdlet:

    Lync Loc - publish

    Once everything has been replicated, we can log-off of our client and back in.  The location information is now published into the client depending on what subnet the user sign’s in from.

    Lync Loc - client after1 - markup

    You will also notice that others users will see this information about other user’s presence within their client:

    Lync Loc - client after2 - markup

    Note that we did not have to configure anything in the Lync Control Panel for Network Sites and Subnets:

    Lync Loc - control panel

    This post showed how to configure location information and publish that information in the Lync client.