[Lync 2013] Response groups : description size

Hi.
I have difficulties to create or modify groups, queues or workflows with no descriptions.
In the web interface, I can set whatever I want as a description for these objects, including empty description, but when I try to do the same using the powershell commands, I have errors.
For example, I first create a queue with the following command :
New-CsRgsQueue -Name 'MyName' -Parent 'service:ApplicationServer:LYNC2013Finale.ciscoad.lab' -Description $Null
I then change the description with the following commands :
$KURMI_GETQUEUE = Get-CsRgsQueue -Identity 'service:ApplicationServer:LYNC2013Finale.ciscoad.lab/ba74e783-71b6-4952-ade7-4afbf2599653';
$KURMI_GETQUEUE.Description = 'MyDescription';
Set-CsRgsQueue -Instance $KURMI_GETQUEUE;
Once again, it works correctly, but if I try later to empty the description I have an error :
$KURMI_GETQUEUE = Get-CsRgsQueue -Identity 'service:ApplicationServer:LYNC2013Finale.ciscoad.lab/ba74e783-71b6-4952-ade7-4afbf2599653';
$KURMI_GETQUEUE.Description = $Null;
Set-CsRgsQueue -Instance $KURMI_GETQUEUE;
The error (SetValueInvocationException) tells me that the minimal length of description is 1.
Il also tried to use the '' value, but the error is the same.
How can I empty a description ?

Or for short use [NullString]::Value
$KURMI_GETQUEUE.Description = [NullString]::Value;
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Similar Messages

  • Lync 2013 Response Group - timeout issues

    I have an Lync 2013 Enterprise Pool deployment with three FE servers.  For the Response Group configuration, the Group is setup as Informal, Alert Time 20 seconds, Routing method as Attendant with a single agent in it.  The Queue is setup
    with the Enable queue time out set to 20 seconds and forward call to voicemail to a sip user.  The workflow is huntgroup with routing to Queue during business hours.
    when I call from inside or outside, Lync call or PSTN call, the agent gets alerted for 20 seconds while the external caller hears music on hold, but after the 20 seconds, instead of going to voicemail, the call comes back to the agent and the caller hears
    nothing for the next 20 seconds.  after two separate 20 second ring cycles for the agent and 20 seconds of music and 20 seconds of dead air for the caller, the call is routed to Exchange UM. 
    Changing Alert Time or Queue Timeout has no impact on the above behavior (except for the amount of time a call rings during each cycle).  Routing on queue timeout to another user or a number instead of voicemail also results in the same behavior. 
    I have tested the exact configuration on Lync 2013 Standard Edition and it works fine.
    Anyone ran into similar issues with Lync 2013 Enterprise pool?

    We just experienced the same issue today on a Lync 2013 Standard Edition server. I originally had the Agents set for Informal Participation, 10 second alert, and Attendant Routing method. The call would come in to the Response Group (either PSTN or internal...same
    behavior) and ring all the users. The caller would hear hold music for 10 seconds while all Agents rang. Then the caller would hear silence while the callee's end would stop ringing for a second and then start ringing again (caller's end remains silent).
    When I changed the routing method to Serial, I ended up with the same sort of function but broken down by user. So, the caller would hear hold music while the first Agent rang for 10 seconds. Then the caller would hear silence and the Agent's ringing would
    stop momentarily and start again. The Queue has a 15 second limit before timeout, so it would timeout to an IVR (as configured) at that time. Because it is in production, I couldn't mess with things too much but I hope to test and make changes this evening
    if needed.

  • How can I get Lync 2013 to "remember" the size of my conversation window

    Each time I open a Lync conversation, the window size always reverts to a default that is too small.  With Lync 2010, a new conversation remembered the size of the window from a previous conversation.  How can I get Lync 2013 to remember the
    size from a previous conversation?  I have a multi-monitor setup and would also like for Lync to remember the location of the last conversation window.  Lync 2010 remembered both the size and location.  I have Lync 2013 and Windows 7.

    I believe what you're seeing is expected behaviour. The Lync 2013 client appears to remember the position of the conversation window relative to the Lync client itself. It seems like it is noting it's screen co-ordinates based on the clients location. This
    works fine for single monitor, but ultimately means that a conversation window cannot remember it' location if it is on a different screen to the Lync client itself.
    Regarding the window size - I believe this has come up before and is not something you can change either natively in Lync, or through registry manipulation.
    Kind regards
    Ben
    Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you've asked, please mark the thread as answered to aid others when they're looking for solutions to similar problems or queries.

  • Uninstall Lync 2010 client, Install Lync 2013 using Group Policy/VB/MS Customisation Tool

    Hi, I am using Group Policy/vb/Lync customization tools to deploy 2013 and remove 2010. The machines have Office 2010. The vb script is as below:
    Dim objShell 'As Object
    Dim objFSO 'As FileSystemObject
    '-- SET OBJECTS
    Set objFSO = CreateObject("Scripting.FileSystemObject")
    Set objShell = CreateObject("WScript.Shell")
    strComputerName = objShell.ExpandEnvironmentStrings("%COMPUTERNAME%")
    Dim WshNetwork : Set WshNetwork = WScript.CreateObject("WScript.Network")
    objShell.Run """\\xxxxxxxxx - Do not Remove\Lync Install 2013 2010\Lync 2013 Outlook 2010\setup.exe"""
    I have amended the OCT with relevant settings, Lync 2013 installs but Lync 2010 does not uninstall. Here is how i have it set:
    In the Office Customization Tool - Set-up - Add Installation and Run Programs,
    In target - pointing to the Lync2010 exe file (on above share)
    In Arguments - /silent /uninstall
    Is this correct?
    Also, i would have thought that, Remove Previous Installations, it would have an option to remove Lync2010?
    Anyway..pulling my hair out here!
    Hope you can help.

    Hi,
    Based on your description, we can refer to the following threads for help.
    Slient Unninstall of Lync 2010 on client machines script required
    http://social.technet.microsoft.com/Forums/lync/en-US/69e32128-4581-4be5-9a44-b5d133e1f480/slient-unninstall-of-lync-2010-on-client-machines-script-required
    Scripting a Lync 2010 client Uninstall
    http://social.technet.microsoft.com/Forums/en-US/a65bd0d0-daa1-4616-8725-63f349fdde86/scripting-a-lync-2010-client-uninstall?forum=lyncconferencing
    For this issue is more related to Lync, in order to get better help, we can ask the question in the following TechNet dedicated Lync forum.
    Lync 2010 and OCS - Lync Clients and Devices
    http://social.technet.microsoft.com/Forums/lync/en-US/home?forum=ocsclients&filter=alltypes&sort=lastpostdesc
    In addition, for it also involves scripts, we can also ask for help in the following scripting forum.
    The Official Scripting Guys Forum
    https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG&filter=alltypes&sort=lastpostdesc
    Hope it helps.
    Best regards,
    Frank Shen

  • Lync SBA & Response Groups

    Hi
    I have a SE Lync deployment with Enterprise voice.
    All Lync services are in the primary site.
    I am adding a SBA to the primary site for resilience and all users use this as their primary registrar and the FE as their backup registrar.
    Inbound calls come in via ISDN cards on the SBA and go to response groups on the FE.
    My question is that if the Lync FE server goes down and the SBA kicks in with limited Lync functionality how can I continue to process inbound calls that were going to the response groups?
    Its my understanding that response groups don't survive a FE Lync outage.
    My design goals must have the inbound numbers continue to work in the event of a FE failure
    Thanks
    Alan

    Hi,
    Response Group would not be available if branch site’s WAN connection to a central site fails or if the central site is unreachable. It will be available only if your resiliency solution is a full-scale Microsoft Lync Server 2010 deployment at the
    branch site.
    For details:
    http://technet.microsoft.com/en-us/library/gg398715.aspx
    Regards,
    Kent Huang
    TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a
    marked post does not actually answer your question.

  • Unable to connect as a formal agent to a Response Group after Migration to Lync 2013

    We are in the process of migrating our Lync 2010 servers to Lync 2013. Everything seems to go well, but problems started to appear after we migrated the Lync 2010 response groups to Lync 2013. Now only those groups with informal agents work. All the groups
    with formal agent, when they try select their group through the web page, they all get the error:
    You are not a member of any group. For assistance, contact your support team"
    Did anyone experience such an issue ?
    Thanks,
    Antonio

    We had this problem with our recent migration of c. 350 response groups, many of which had formal agent groups. The cause appears to be that after the migration, the formal agent registration screen sees both the 'old' and the 'new' formal agent groups of
    which the current user is a member and resolves these to only one entry on the registration screen (which is understandable). But the entry seems to be connected to the 'old' and not the 'new' agent group. We were able to verify this by checking in the old
    and new pool database (rgsdyn) and seeing that even after the migration the formal agents were signing in to the old pool and not the new one. One solution is to delete the members from the old formal agent groups so that future registrations are forced to
    take place  in the new pool database. However, if you do this, bear in mind that if you have to back out the migration, you have to restore these.
    We were also had to abandon one migration attempt because of another problem where the migration tool does not support the migration of agents who are defined indirectly in the agent group through a mail distribution group.
    tags: Move-CsRgsConfiguration ; formal agent groups ; lync2013 ;

  • Response Groups not working

    Hi there
    My environment is a single Lync 2013 Front End Server installed on Server 2012.
    It works since a year and now we want to use some response groups. I created 2 of them and everything seems fine but i cant call these groups. Not from internal and also not from external.
    The clients shows an 500 internal server error with ID 26017.
    So i traced the whole thing on the Front End Server. It seems the Response Group Service cant work with the local SQL Server. I see three error messages.
    1. TL_ERROR(TF_COMPONENT) [2]0B90.37A8::07/23/2014-06:38:39.119.000002fb (RgsClientsLib,MatchMakingLocator.GetActiveInstanceFromDB:683.idx(479))
    (0000000000150BA8)No instance registered as the active instance!
    2. TL_ERROR(TF_COMPONENT) [1]1E08.2910::07/23/2014-06:38:42.462.00000a34 (RgsHostingFramework,CallControlManager.HandleAudioVideoCall:2049.idx(619))
    (000000000362D054)Call is declined because Call Control is not started.
    3. TL_WARN(TF_COMPONENT) [1]0B90.0B7C::07/23/2014-06:38:48.053.00000f2d (RgsClientsLib,MatchMakingLocator.GetActiveMatchMakingInstance:683.idx(301))
    (0000000000150BA8)There is currently no active MatchMaking instance in the pool.
    The Lync Server Event Log shows this error when the Response Group Service starts:
    LS Response Group Service ID 31067
    Lync Server 2013, Response Group Service Match Making could not find the Contact object used for subscribing to agents' presence.
    Cause: The application has not been properly activated or the Contact object was deleted.
    Resolution:
    Deactivate and then activate the application for this pool.
    Is there a way to reinstall / reconfigure the whole response group service incl. the active directory objects?
    I hope somebody could help
    Regards
    Andreas

    Have you seen this thread:
    http://social.technet.microsoft.com/Forums/lync/en-US/cd25ddec-6e1e-4d58-9a9a-a530abfa82e3/response-groups-not-working?forum=ocsclients ?
    He ran Get-CsApplicationEndpoint and received a warning that let him to a resolution.
    Short of that, I'd rerun step 2 in the deployment wizard and restart services when you can to see if I could jog anything loose.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Response Groups - Duplicate "Built In" Services - Multiple Default Routing Endpoints

    Hello,
    I have a Lync 2013 deployment that has been migrated from OCS 2007, to OCS 2007 R2, to Lync 2010, and now to Lync 2013. I am including that information as that may be important for the following discussion.
    When the Response Group Service starts, it logs four error messages which I will place at the bottom of this post. The error messages point to duplicate routing endpoints for the same service. Upon review, it appears to me that I have duplicates of the following
    two services, when I look up the below SIP addresses with Get-CSApplicationEndpoint.
    Announcement Service
    RGS Presence Watcher
    My guess is that during one of these migrations, we ended up with a duplicate service. The problem is - how do I get rid of the duplicate, and how do I know which is the duplicate and which I want to keep? Error messages below.
    Lync Server 2013, Response Group Service was not able to establish the application endpoint.
    The following exception occurred when establishing application endpoint associated with 'sip:RtcApplication-9ebda80c-12e1-4db6-b5f3-f0dc9585ad4d@<scrubbed>.com': System.InvalidOperationException - The ChannelDispatcher at 'net.tcp://<server scrubbed>:8404/'
    with contract(s) '"IAgentSignInOut", "IMatchMaking"' is unable to open its IChannelListener..
    Cause: Failed to connect to Front End server or the Front End server is misconfigured.
    Resolution:
    Check the Front End server for errors.
    Application endpoint for Contact object cannot be created.
    The following exception was thrown during application endpoint creation for Contact object 'sip:RtcApplication-8e1e15ac-09d4-4271-b961-6757feabd621@<scrubbed>.com'. The Response Group associated with this endpoint will not be available.
    Exception: System.ArgumentException - Only one default routing endpoint is allowed per platform. The platform already contains a default routing Endpoint.
    Inner Exception: ~
    Cause: Networking problems with the Front End server, or Front End server configuration problems.
    Resolution:
    Check for eventual SIP errors on the Front End servers.
    Lync Server 2013, Response Group Service was not able to establish the application endpoint.
    The following exception occurred when establishing application endpoint associated with 'sip:RtcApplication-11e8fb5c-9847-460c-9e60-0f34834f8b37@<scrubbed>.com': System.InvalidOperationException - The ChannelDispatcher at 'net.tcp://<scrubbed>:8404/'
    with contract(s) '"IAgentSignInOut", "IMatchMaking"' is unable to open its IChannelListener..
    Cause: Failed to connect to Front End server or the Front End server is misconfigured.
    Resolution:
    Check the Front End server for errors.
    Application endpoint for Contact object cannot be created.
    The following exception was thrown during application endpoint creation for Contact object 'sip:RtcApplication-1c871209-add1-40a6-87bb-07884eb879b5@<scrubbed>.com'. The Response Group associated with this endpoint will not be available.
    Exception: System.ArgumentException - Only one default routing endpoint is allowed per platform. The platform already contains a default routing Endpoint.
    Inner Exception: ~
    Cause: Networking problems with the Front End server, or Front End server configuration problems.
    Resolution:
    Check for eventual SIP errors on the Front End servers.

    Hi,
    Have you reviewed this blog? You may check the ownerpoolID in rgsconfig database.
    http://blog.lync2013.org/tag/lync/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Response Group problems

    For the past few weeks I have been struggling with launching response groups and I am hoping someone might be able to help.
    Little background on my config –
    2 – Frontend 2013 servers (5.0.8308.556)
    Sonus SBC1000 voice gateway, 1 PRI
    Stuff that works – Direct calling inbound to end users works great!
    So here is my problem.  I set up a response group with a direct dial number to the outside and assign my people to the group and everything is good. 
    For about 15mins response groups work great! After about 15mins response groups stop working and calls to response groups are no longer picked up. This also affects chat with response groups.
    When I turn on the logging software inside Lync I get these messages when the calls are dropped;
    TL_INFO(TF_COMPONENT) [1]3784.356C::04/14/2014-14:24:54.627.018e2f49 (RgsCommonLibrary,RgsLogMessage.ReportMessage:2111.idx(227))
    _rgs_message_begin_
    Direction: Incoming
    From: tel:+15555555555
    To: sip:[email protected]
    Message: CALLCONTROL: Call declined because CallControl is not started
    WorkflowId: 08d328a20de8419caad0dee898586051
    TL_ERROR(TF_COMPONENT) [1]3784.356C::04/14/2014-14:24:54.627.018e2f4a (RgsHostingFramework,CallControlManager.HandleAudioVideoCall:2049.idx(619))
    (0000000000C9D21E)Call is declined because Call Control is not started.
    I then simply restart response groups on one of the FE servers and they come back (for a short time) -
    Here some interesting events logged in the Lync Server event logs after Response Group Service is restarted –
    LS Response Group Service – 31028 - A WorkflowRuntime cannot be started.
    Lync Server 2013, Response Group Service Match Making could not find the Contact object used for subscribing to agents' presence. Cause: The application has not been properly activated or the Contact object was deleted. Resolution: Deactivate and then activate
    the application for this pool.
    I am willing to try just about anything to get this to work.  Any ideas out there? Thanks for all your help! 

    Please check if the application server is active(lync control panel--Topology--status--double click your FE SERVER--applicationserver).
    If the application server is not started, please start it. If it is started, restart it.
    If issue still exist, use following steps:
    use following command Get-CsApplicationEndpoint
    And check for messages in "Yellow"
    Locate the Identity in Active Directory using ADSIEdit
    And Delete the "CN" located at the end of the Identity String
    And try and add your Line URI or Response Group SIP Address.
    Also you can refer below link
    http://social.technet.microsoft.com/Forums/lync/en-US/cd25ddec-6e1e-4d58-9a9a-a530abfa82e3/response-groups-not-working
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

  • Lync 2013 Crashes When Transferring From Response Group

    Hello,
    Seeing a very strange issue on a couple of our clients running Lync 2013.  Whenever they transfer a call from their response group Lync will crash.  Calls into their direct line will transfer just fine.  Here are two of the event logs we have
    seen from this.
    Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0bd5c
    Faulting module name: mso.dll, version: 15.0.4569.1506, time stamp: 0x52e0dcca
    Exception code: 0xc0000005
    Fault offset: 0x0000000001828520
    Faulting process id: 0x1550
    Faulting application start time: 0x01cf4766655f5ead
    Faulting application path: C:\Program Files\Microsoft Office\Office15\lync.exe
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office15\mso.dll
    Report Id: cbd75420-b38c-11e3-ae5c-0026b9dd72ee
    Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0bd5c
    Faulting module name: LyncDesktopViewModel.dll, version: 15.0.4569.1503, time stamp: 0x52b0c3a2
    Exception code: 0xc0000005
    Fault offset: 0x0000000000119795
    Faulting process id: 0xee0
    Faulting application start time: 0x01cf4757f9b12418
    Faulting application path: C:\Program Files\Microsoft Office\Office15\lync.exe
    Faulting module path: C:\Program Files\Microsoft Office\Office15\LyncDesktopViewModel.dll
    Report Id: 9db0d18d-b359-11e3-ae5c-0026b9dd72ee
    We have tried a number of things this to get this working, but nothing has worked.
    Installed Office 2013 SP1
    Completely re imaged the client's computers
    Deployed new Polycom Lync phones
    Completely removed clients from their response group and the Lync server and added them back
    I'm not sure where to go from here or what might be causing this.  I would appreciate any thoughts you might have.  Thank you!

    By default, calls from Response Groups ignore call forwarding or simultaneous ring settings.
    Lisa Zheng
    TechNet Community Support

  • Lync 2013 Attendant Response Group - Long Delay - Error ID 45019 LS Inbound Routing

    Hello,
    We have a customer who's using Lync Server 2013 with Response Groups and the SamRoxx Attendant Client. They are getting an error whereby calls made directly to users come through instantly, however attendants who take a call via the Response Group
    get a 10 second delay. We are seeing 
    Error ID 45019 LS Inbound Routing
    User ***@***.com provided a routing document with errors.
    Default call handling was applied instead. Merge conflict. Wait total present in both preambles.
    Problems with this user's routing documents will not be reported again for another hour.
    Cause: A new or experimental user agent my have published a routing document with errors.
    Resolution:
    Replace the user agent that published the defective configuration.
    Has anyone seen this before??
    Thanks
    Lync Tips Blog - [email protected] - If this post has been useful please click the green arrow to the left or click 'Propose as answer'

    Hi tomcotton,
    You can try steps below to troubleshoot the problem.
    1. Remove the affected Lync user from the Response Group and test whether the error persists.
    2. I’m not aware of
     the SamRoxx Attendant Client, can you use Lync 2013 client to test and check ?
    Best regards,
    Eric
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Update response group membership on Lync.

    Hi guys! Short question. I've updated the list of members in my AD group, which is used for calls routing. At about 10 minutes after the calls still flow to excluded members. How to force this update on Lync server?
    Thank you!

    Hi,
    I have tried both commands, but my response Group using a Distribution List does not update.
    I have found this in my event viewer:
    Log Name:      Lync Server
    Source:        LS Response Group Service
    Date:          05-04-2013 12:57:56
    Event ID:      31128
    Task Category: (2001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      LYNC-FE1.xxxx.dk
    Description:
    Data synchronization from Active Directory failed.
    The following exception was thrown during the synchronization process:
    Exception: System.Data.SqlClient.SqlException - Cannot insert duplicate key row in object 'dbo.Agents' with unique index 'IX_Agents_UserSid'.
    The statement has been terminated.
    Inner Exception: ~
    The next synchronization attempt will be in 480 minutes.
    Cause: Unhandled exception.
    Resolution:
    Verify the connectivity with the domain controller or if the Active Directory schema was properly applied and all user attributes are present.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Response Group Service" />
        <EventID Qualifiers="51153">31128</EventID>
        <Level>2</Level>
        <Task>2001</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-05T10:57:56.000000000Z" />
        <EventRecordID>155606</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>LYNC-FE1.xxxx.dk</Computer>
        <Security />
      </System>
      <EventData>
        <Data>System.Data.SqlClient.SqlException - Cannot insert duplicate key row in object 'dbo.Agents' with unique index 'IX_Agents_UserSid'.
    The statement has been terminated.</Data>
        <Data>~</Data>
        <Data>480</Data>
      </EventData>
    </Event>
    Any help would be much appreciated.

  • Lync Response Group Manager - cannot change opening hours

    Hi all
    I've run into an odd problem with Lync Response Groups with Lync 2013 Server. Just wondering if anyone has seen this before or knows of a solution. I've searched around but can't find any reference to this particular problem.
    Response supervisors who are defined in the workflow and are a member of the AD group CSResponseGroupManager cannot change working hours for their response group from a custom schedule to a preset in the web interface.
    If the workflow is already set to preset they can switch between existing presets, and they can switch from preset to custom. But once it has been set to custom they cannot change it back to preset.
    They can select to do so but when they click Save they receive an error on the page saying "The term 'Remove-CsRgsHoursOfBusiness' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name,
    or if a path was included, verify that the path is correct and try again."
    I don't believe this is by design, why would you want a workflow manager to be able to switch between presets or to custom but not back again?
    If they are a member of CSResponseGroupAdministrator this works, however this is not really a solution as members of this group can edit all workflows and we don't want the managers of a workflow for one department able to access the workflows of another.
    Any information greatly appreciated.

    Hi
    I had to abondon working on this for a while as we only had 1 Response Group in place, it wasn't too much hassle for me to do these changes myself.
    However we now have about 6 Response Groups. All are managed and have a user listed as manager in the workflow, that user is also in the CSResponseGroupManager AD user group.
    As previously described they can change the opening hours from between existing presets, and from preset to custom, but attempting to change back to preset from custom causes the error given previously.
    This does not occur if the user is a member of CSResponseGroupAdministrator, however putting our Response Group managers in this group is not appropriate as it gives them access to all Response Groups not just their own.
    Is it possible the error is due to the fact that the CSResponseGroupManager group is not giving them permission to the Remove-CSRGSHoursofBusiness cmdlet, I think PowerShell tells you a cmdlet doesn't exist if you don't have permissions to use it?

  • LYNC 2013 mobility clients disconnect and AAR bad response time

    Good day,
    I'm new to this, but have to implement LYNC 2013 for our company.
    I have implemented Lync 2013 by following various instructions and all seems fine... apart from all mobile clients (internal/external - Andoid/IOS). They get disconnected after a few minutes. On Android the error is "unknown error" (very useful)
    and on IOPS it's "unhandeled alert type 302 E_Badgateway (E2-3-35).
    What I have noticed is that on AAR, on the LYNCWEB server farm  (under " Monitoring and Management") the response time is huge (10000 + ms) and when the errors come up on the clients I get a "failed request".
    I can not think what may be wrong but all is pointing to AAR?
    AAR is version 3 running on 2021 R2
    any ideas? been stuck for a week on this now.
    Many thanks
    DD

    Hi,
    From your description above, it seems to be the issue with IIS ARR.
    You can check with the following steps:
    Check if DNS records and certificate were appropriate.
    Check if ExposedWebURL set to External.
    Try to increase the time out value from 200 to 1800
    More details:
    http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • How to change the default window size display font size on Lync 2013 main window?

    Hi champs,
    Just a simple non-technical question: How to change the default window size display font size on Lync 2013 main window on Windows 7 desktop?
    Thanks,

    Hi,
    Did you mean change the Lync: Change the Default Font and Color of Instant Messages just as Edwin said above?
    If not, as I know, there is no natural way to change it.
    If yes, on the latest version of Lync 2013 client, there is a new option “IM” on Lync client “Options” list. And you need to change the default Font and Color of IM in the interface of “IM”.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

Maybe you are looking for