Archive for September, 2010


Moving On…..

 

So i have been quite on the blogging from recently as i am coming to the end of my current employment and moving on to a new company at the end of this week to which i will kick off blogging again, in the mean time i am busy handing over everything i can to the excellent support team…..

 

so i will be back in a week or so…. 🙂

 

So i have been quite on the blogging from recently as i am coming to the end of my current employment and moving on to a new company at the end of this week to which i will kick off blogging again, in the mean time i am busy handing over everything i can to the excellent support team…..

 

so i will be back in a week or so…. 🙂

30 things about lync

This is copy and pasted directory from the Technet Article found –>

http://blogs.technet.com/b/mbaher/archive/2010/09/17/the-30-interesting-info-about-lync.aspx

 

In this post I’ll list to you 30 fact and info about Lync which is totally new and different than OCS:

  1. You can virtualize all topologies and we support all workloads, including Enterprise Voice to be virtualized
  2. When you virtualize, Scalability is roughly 50% of the scalability offered by a Lync Server 2010 topology running only on physical servers
  3. In Microsoft Lync Server 2010, A/V Conferencing service functionality, which normally runs on the Front End Server, can also run in a standalone server role called A/V Conferencing Server
  4. If your site has more than 10,000 users, we recommend that you deploy a separate A/V Conferencing pool
  5. Lync introduced ‘Survivable Branch Appliance’, which is a new device introduced in Lync Server 2010 that combines a PSTN gateway with a Lync Server Registrar and Mediation Server. This appliance is targeting branch offices who require telephony services in case of WAN failures with the central site
  6. In the event a branch office’s WAN connection to a data center fails, the Survivable Branch Appliance provides the following voice features to users in that branch office:
    1. PSTN inbound and outbound calls
    2. Intra-site and inter-site calls
    3. Call hold, retrieve, and transfer
    4. User authentication and authorization
    5. Leaving and retrieving voicemail
    6. Call forwarding, simultaneous ringing, boss-administrator, and team calling
    7. Call Detail Recording (CDR).
    8. All two-party functionality, including instant messaging and audio-video conferencing
    9. PSTN dial-in conferencing with Conferencing Auto-Attendant
  7. In Lync Server 2010, the Director is now a unique server role which you cannot home users on it
  8. A Director is not designated as either a Standard Edition server or an Enterprise Edition server; it does not require any type of Microsoft Lync Server 2010 license (interesting huh)
  9. Collocation of mediation with FE is recommended if you are not using SIP trunking or Direct SIP
  10. New to Lync is the ‘Topology Builder’ which is a wizard-driven user interface that you use to create and edit your Microsoft Lync Server 2010 topology
  11. With Microsoft Lync Server 2010, configuration data about servers and services is moved to the Central Management store. Read-only copies of the data are replicated to all servers in the topology, including Edge Servers and survivable branch appliances
  12. Although most of the Lync configuration is stored in the central management store, the Active Directory Domain Services (AD DS) are still used to store basic Lync Server user information, such as the user’s SIP URI and phone number
  13. The Lync Server 2010 Management Shell is a new method of administration and management
  14. Lync introduces role-based access control (RBAC). Lync Server 2010 includes 11 predefined roles that cover many common administrative tasks
  15. Administration console is no longer using MMC, Lync Server Control Panel replaces the MMC administrative interfaces of previous releases
  16. Microsoft Lync Server 2010 introduces DNS load balancing for load balancing for SIP and media traffic (you will still need hardware LB for other traffic such as HTTP however this is the easiest part in configuring a HW load balancer)
  17. DNS load balancing is supported for Front End pools, Edge Server pools, Mediation Server pools, and Director pools
  18. Microsoft Lync 2010 Attendee is a new downloadable client that enables users without Microsoft Lync 2010 to attend meetings
  19. You manage Edge Servers from the internal network. All configuration data for servers and services resides in the Central Management database, which you can manage by using internal administrative tools
  20. Lync Server 2010 introduces support for integration with hosted Exchange UM
  21. Lync supports Enhanced 9-1-1 (E9-1-1) as part of your Enterprise Voice deployment
  22. New for the Mediation Server in Microsoft Lync Server 2010 is the ability for a single Mediation Server to route outbound calls through multiple gateways
  23. Also new for Lync Server 2010 is the ability for a Mediation Server to be deployed as a pool; this pool can be collocated with the Front End pool, or can be a standalone pool
  24. Malicious call tracing enables users to flag incoming calls which are harassing, threatening, or obscene. Immediately after hanging up, the user can select an option to report the call as malicious. If they do so, a trace request is sent to mark the record of the call, and an event is logged
  25. Lync introduced the concept of ‘Anonymous call’ in the Response Group feature, when a response group is so configured, agents can accept incoming and make outgoing calls on behalf of the response group without revealing their identity (Anonymous call). Anonymous calls do not support conferencing, application sharing and desktop sharing, file transfer, whiteboarding and data collaboration, or call recording
  26. Archiving policy settings for both IM and meetings are unified. The core archiving store contains both IM content and Web conferencing attendee entries and exits consolidated together
  27. You can do searchable transcript of archived information without the need for scripts
  28. In Microsoft Lync Server 2010, the Group Policy settings used in previous  Office Communications Server releases are now controlled by in-band provisioning client policies that are server-based.
  29. Lync 2010 clients can now receive updated software from Windows Server Update Service (WSUS) or Microsoft Update instead of from a location hosted on Lync Server 2010
  30. Lync Server 2010 provides support for analog devices. Specifically, the supported analog devices are analog audio phone and analog fax machines. Now you can configure the analog gateways and devices in your organization to use Lync Server 2010. After you do this, analog devices use Lync Server to make and receive calls, and Lync Server makes routing decisions and log calls in call detail records (CDRs) for analog devices, just as it does for any device

This is copy and pasted directory from the Technet Article found –>

http://blogs.technet.com/b/mbaher/archive/2010/09/17/the-30-interesting-info-about-lync.aspx

 

In this post I’ll list to you 30 fact and info about Lync which is totally new and different than OCS:

  1. You can virtualize all topologies and we support all workloads, including Enterprise Voice to be virtualized
  2. When you virtualize, Scalability is roughly 50% of the scalability offered by a Lync Server 2010 topology running only on physical servers
  3. In Microsoft Lync Server 2010, A/V Conferencing service functionality, which normally runs on the Front End Server, can also run in a standalone server role called A/V Conferencing Server
  4. If your site has more than 10,000 users, we recommend that you deploy a separate A/V Conferencing pool
  5. Lync introduced ‘Survivable Branch Appliance’, which is a new device introduced in Lync Server 2010 that combines a PSTN gateway with a Lync Server Registrar and Mediation Server. This appliance is targeting branch offices who require telephony services in case of WAN failures with the central site
  6. In the event a branch office’s WAN connection to a data center fails, the Survivable Branch Appliance provides the following voice features to users in that branch office:
    1. PSTN inbound and outbound calls
    2. Intra-site and inter-site calls
    3. Call hold, retrieve, and transfer
    4. User authentication and authorization
    5. Leaving and retrieving voicemail
    6. Call forwarding, simultaneous ringing, boss-administrator, and team calling
    7. Call Detail Recording (CDR).
    8. All two-party functionality, including instant messaging and audio-video conferencing
    9. PSTN dial-in conferencing with Conferencing Auto-Attendant
  7. In Lync Server 2010, the Director is now a unique server role which you cannot home users on it
  8. A Director is not designated as either a Standard Edition server or an Enterprise Edition server; it does not require any type of Microsoft Lync Server 2010 license (interesting huh)
  9. Collocation of mediation with FE is recommended if you are not using SIP trunking or Direct SIP
  10. New to Lync is the ‘Topology Builder’ which is a wizard-driven user interface that you use to create and edit your Microsoft Lync Server 2010 topology
  11. With Microsoft Lync Server 2010, configuration data about servers and services is moved to the Central Management store. Read-only copies of the data are replicated to all servers in the topology, including Edge Servers and survivable branch appliances
  12. Although most of the Lync configuration is stored in the central management store, the Active Directory Domain Services (AD DS) are still used to store basic Lync Server user information, such as the user’s SIP URI and phone number
  13. The Lync Server 2010 Management Shell is a new method of administration and management
  14. Lync introduces role-based access control (RBAC). Lync Server 2010 includes 11 predefined roles that cover many common administrative tasks
  15. Administration console is no longer using MMC, Lync Server Control Panel replaces the MMC administrative interfaces of previous releases
  16. Microsoft Lync Server 2010 introduces DNS load balancing for load balancing for SIP and media traffic (you will still need hardware LB for other traffic such as HTTP however this is the easiest part in configuring a HW load balancer)
  17. DNS load balancing is supported for Front End pools, Edge Server pools, Mediation Server pools, and Director pools
  18. Microsoft Lync 2010 Attendee is a new downloadable client that enables users without Microsoft Lync 2010 to attend meetings
  19. You manage Edge Servers from the internal network. All configuration data for servers and services resides in the Central Management database, which you can manage by using internal administrative tools
  20. Lync Server 2010 introduces support for integration with hosted Exchange UM
  21. Lync supports Enhanced 9-1-1 (E9-1-1) as part of your Enterprise Voice deployment
  22. New for the Mediation Server in Microsoft Lync Server 2010 is the ability for a single Mediation Server to route outbound calls through multiple gateways
  23. Also new for Lync Server 2010 is the ability for a Mediation Server to be deployed as a pool; this pool can be collocated with the Front End pool, or can be a standalone pool
  24. Malicious call tracing enables users to flag incoming calls which are harassing, threatening, or obscene. Immediately after hanging up, the user can select an option to report the call as malicious. If they do so, a trace request is sent to mark the record of the call, and an event is logged
  25. Lync introduced the concept of ‘Anonymous call’ in the Response Group feature, when a response group is so configured, agents can accept incoming and make outgoing calls on behalf of the response group without revealing their identity (Anonymous call). Anonymous calls do not support conferencing, application sharing and desktop sharing, file transfer, whiteboarding and data collaboration, or call recording
  26. Archiving policy settings for both IM and meetings are unified. The core archiving store contains both IM content and Web conferencing attendee entries and exits consolidated together
  27. You can do searchable transcript of archived information without the need for scripts
  28. In Microsoft Lync Server 2010, the Group Policy settings used in previous  Office Communications Server releases are now controlled by in-band provisioning client policies that are server-based.
  29. Lync 2010 clients can now receive updated software from Windows Server Update Service (WSUS) or Microsoft Update instead of from a location hosted on Lync Server 2010
  30. Lync Server 2010 provides support for analog devices. Specifically, the supported analog devices are analog audio phone and analog fax machines. Now you can configure the analog gateways and devices in your organization to use Lync Server 2010. After you do this, analog devices use Lync Server to make and receive calls, and Lync Server makes routing decisions and log calls in call detail records (CDRs) for analog devices, just as it does for any device

 

Major problem today last day of the project and couldnt get group chat installed it was right to the wire…

 

all we were getting was Error 121 after the setup was ran for the group chat server and it invoked the configuration tool…

now we rechecked the database permissions , accounts, membership everything

reviewed various technet documentation and blogs and nothing at all!

anyway…. sql and kerberos turned out to be our problem and we exposed it with UAC in windows

basically when the installer was invoking the configuration tool it was doing under system and tried to authenticate to the sql server (as kerberos is in use) with the machine account and not the account we invoked the installer under!

very annoying! so the obvious thing was to add the machine account to sql 2008 but guess what you cant!…. well not directly! 🙂

to get around the problem we created a group, added the machine account to the group and then added it to the sql security and gave it SA permissions with DBO on the relevant database…

after this group chat installed with no errors……

 

Major problem today last day of the project and couldnt get group chat installed it was right to the wire…

all we were getting was Error 121 after the setup was ran for the group chat server and it invoked the configuration tool…

now we rechecked the database permissions , accounts, membership everything

reviewed various technet documentation and blogs and nothing at all!

anyway…. sql and kerberos turned out to be our problem and we exposed it with UAC in windows

basically when the installer was invoking the configuration tool it was doing under system and tried to authenticate to the sql server (as kerberos is in use) with the machine account and not the account we invoked the installer under!

very annoying! so the obvious thing was to add the machine account to sql 2008 but guess what you cant!…. well not directly! 🙂

to get around the problem we created a group, added the machine account to the group and then added it to the sql security and gave it SA permissions with DBO on the relevant database…

after this group chat installed with no errors……

over the past few days i have done a few migrations from beta to rc

and other bits in between….

the move-csmanagementstore cmdlet kept failing saying the sql server was not accessible but it was and no firewall was enabled and i could create an odbc connection to the DB and all was great HOWEVER i still could not move the CMS database master! (remember all servers host a copy of the database) anyway a quick ADSI edit os MS-RTCSIP-backendserver value in AD changing it to the server i want and off we go! refresh the topology builder and all done

one of the coolest commands i have come across when decommissioning a server is the bootstrapper.exe /scorch command

other commands i have had to use are

install-csdatabase –centralmanagementdata –clean –sqlserverfqdn server.contoso.com –sqlinstance rtc (this creates the CMS database)

install-csdatabase –localdatabases –clean (this creates the local database store)

disable-cscomputer (removes roles from the server based on the published topology)

enable-cscomputer (enables roles from the server based on the published topology)

get-csconferencedirectory (see what conference directories are published in the entire topology)

remove-csconferencedirectory (deletes a specific directory based on the identity you specify)

logging is excellent in every part of it and you can isolate problems very quickly which is a massive change from the previous versions…

and of course RBAC this to me is a god send!

for now on with the playing! 🙂

 

see this post from the LCSKID http://blogs.technet.com/b/toml/archive/2010/09/16/upgrading-lync-server-2010-release-candidate-to-rtm-no.aspx?utm_source=twitterfeed&utm_medium=twitter

now microsoft have said stuff like this before and allowed it to happen in some format and i reckon we might see the same…

the beta to rc was a little bit mucky (you have to modify an AD attribute to move the CMS) but it was possible…

so lets watch this space!

over the past few days i have done a few migrations from beta to rc

and other bits in between….

the move-csmanagementstore cmdlet kept failing saying the sql server was not accessible but it was and no firewall was enabled and i could create an odbc connection to the DB and all was great HOWEVER i still could not move the CMS database master! (remember all servers host a copy of the database) anyway a quick ADSI edit os MS-RTCSIP-backendserver value in AD changing it to the server i want and off we go! refresh the topology builder and all done

one of the coolest commands i have come across when decommissioning a server is the bootstrapper.exe /scorch command

other commands i have had to use are

install-csdatabase –centralmanagementdata –clean –sqlserverfqdn server.contoso.com –sqlinstance rtc (this creates the CMS database)

install-csdatabase –localdatabases –clean (this creates the local database store)

disable-cscomputer (removes roles from the server based on the published topology)

enable-cscomputer (enables roles from the server based on the published topology)

get-csconferencedirectory (see what conference directories are published in the entire topology)

remove-csconferencedirectory (deletes a specific directory based on the identity you specify)

logging is excellent in every part of it and you can isolate problems very quickly which is a massive change from the previous versions…

and of course RBAC this to me is a god send!

for now on with the playing! 🙂

 

see this post from the LCSKID http://blogs.technet.com/b/toml/archive/2010/09/16/upgrading-lync-server-2010-release-candidate-to-rtm-no.aspx?utm_source=twitterfeed&utm_medium=twitter

now microsoft have said stuff like this before and allowed it to happen in some format and i reckon we might see the same…

the beta to rc was a little bit mucky (you have to modify an AD attribute to move the CMS) but it was possible…

so lets watch this space!