Is it possible to connect to LYNC Server 2013 from outside without public certificate

Hello to everybody
I have a rather simple question but i cannot find a definite answer
I have installed Lync server for purely testing purposes on my work lab
I have internal communication ...even web based but i don't know how to get external communication
I have a domain with FQDN : domain.abc.com    .... please
take note that the FQDN is 3 part...my computer are registered under computer.domain.abc.com.....and my domain is presented as
abc
My lync server is lsvr.domain.abc.com
We also have DNS records to external.abc.gr pointing to my static IP
Is it possible to create a self signed certificate that will enable us to perform external communications...especially with the Lync Web app or i should
definitely get a public certificate.
The whole issue is that we wish to make a presentation to the company's owner in order to get the approval to buy Lync and the required infrastructure or will use some other way of communication like Skype
It seems i cannot get a definite answers if i can do it without paying the money for the certificate or we should bite the bullet and pay the certificate

Well i had a mistake in network configuration but now i have different issue and i can't find how to begin with this
Let me take it from the beginning ...
I am user :Tsuser
I connect internally to my Lync Server :lsvr.domain.abc.com
with internal IP 192.168.1.200
I use
the meet url : https://meet.domain.abc.com/Tsuser/randomnumbersletters
I connect
ok
I change
the meet url to : https://Internal IP of lsvr(192.168.1.200)/Tsuser/randomnumbersletters
i get 404  File or directory not found.
I change
the meet url to : https://lsvr.domain.abc.com/Tsuser/randomnumbersletters
i get 404  File or directory not found.
I port forward my public ip to lsvr.domain.abc.com
port 4443 the same 404
Something is wrong here but i can't figure it out
Can anyone give me a helping hand...i think this is the main obstacle

Similar Messages

  • Unable to Connect to Project Server 2013 from Project 2013

    Hello,
    I'm trying to connect to Project Server 2013 from Project 2013 but it is not working.
    I'm able to connect to the PWA from IE 10 on Windows 8 Enterprise
    On Project 2013, I configured account to connect to Project Server 2013 and I checked the "Log on to Project Server from Project Professional" global permission and it is on. 
    Any idea why it is not connecting?

    So you are using Project Online and not Project Server 2013? Can other users access Project Online from Project Pro successfully in your organisation? If it was an authentication issue, Project would prompt for credentials.
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Integrating Exchange 2013 & Lync Server 2013: can't use a certificate with Seth-AuthConfig

    I'm trying to integrate Exchange and Lyn Server. One of the first steps is to bind a correct certificate to IIS on all of the CAS servers and set it as a main certificate in the global AuthConfig object. The certificate must be the same on all of the
    CAS servers because the autodiscover.domain.local DNS record points to all of them, and Lync Server uses this FQDN to access Exchange servers. The thumbprint of this certificate must be specified in Set-AuthConfig command run on an Exchange server.
    We have an internal enterprise CA. I generated a certificate on one of the CAS servers and bound it to all of the Exchange services. Then I exported it, imported it on the second CAS server and bound it to all of the services as well. Now Exchange correctly uses
    it for OWA, for example, and IE gives no security warnings when I connect to OWA.
    However, whenever I run Set-AuthConfig command on any server, it keeps telling me that
    The certificate with thumbprint XXXX was found but is not valid for use with Exchange Server (reason: PrivateKeyNotAccessible).
    The key IS accessible - I can export the certificate along with its private key. What's wrong?

    Here's the answer.
    It seems that the -Server switch in the Set-AuthConfig command is only used to specify where you want to look for the certificate with the given thumbprint. However, it's impossible to predict which Exchange server will actually perform the operation
    (the Server switch doesn't influence it a bit). It could be ANY server, even a mailbox one with no CAS role at all. And, of course, another Exchange server has no access to the certificate store of the CAS server where the certificate is actually stored. It
    was exactly the case in my environment.
    So in order to enable this certificate you must import it on ALL of your Exchange servers. You need't (and even shouldn't) enable it for any services on your mailbox servers if you don't want to, just import it.

  • External users cannot connect to Lync Server 2013

    I everybody,
    The users inbound organizacion use lync 2013 good, i deploy a edge server for external connection but, when i try to connect, receive the next message: "can not log into lync because the server is temporarily unavailable".
    already test the certificate, ports and the cms replica. this components are good.
    i don´t know, what can i do.
    regards
     

    Hi JSanabria,
    Did you use single IP and FQDN for the SIP access, Web Conferencing service and A/V service?
    Did you use private IP with NAT or public IP directly on Edge external interface?
    Please tell us more detail about the configuration of Edge server.
    You can use Lync 2013 remote connectivity analyzer to check which step goes wrong.
    Here is the link of Lync 2013 remote connectivity analyzer:
    https://www.testexchangeconnectivity.com/
    http://www.insideocs.com/Tools/RUCT/RUCT.htm
    http://blogs.technet.com/b/nexthop/archive/2011/12/07/useful-tips-for-testing-your-lync-edge-server.aspx
    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.
    Best Regards,
    Eason Huang

  • Unable to establish AV call with Lync server 2013 from internal to external remote users

    Hi,
    Instant messaging is working fine
    When trying to video call from the internal Lan to an remote external user Video call connects for 10 seconds and then drops.
    This also happens between federated sites when we initiate the call
    Internal to internal video call works
    External to external video works
    Please see logs below, can anyone advise on this issue or point me in the direction
    The logs show trying to make a video call from user on the same domain, one user on the internal network and the other user is external
    08/08/2014|11:25:44.523 4024:4344 INFO  :: End of Sending Packet - 192.168.10.4:5061 (From Local Address: 192.168.11.77:62287) 1082 bytes
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 1082, BytesProcessed = 1082, cbDataCompressed = 465, psCompressedData = 16A01FD8
    08/08/2014|11:25:44.523 4024:4344 TRACE :: - encrypted buffer length: 533 bytes.  First 8 bytes:
    08/08/2014|11:25:44.523 4024:4344 TRACE ::  17 03 03 02 10 D0 D8 3D  :.....ÐØ=
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 465, BytesProcessed = 465, cbEncryptedBufSize = 533, spEncryptedBuff = 0C2B13C8
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::Send this 07B3B000, sending pbSendBuf 0C2B13C8, dwSendBufSize = 533
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::SendHelper - [0x07B3B000]
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CAsyncSocketWin32::Send this 0C47D5A0, pbSendBuf 0C2B13C8, dwSendBufSize = 533, dwBytesSent = 533
    08/08/2014|11:25:44.523 4024:4344 INFO  :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(2) at State (1)
    08/08/2014|11:25:44.523 4024:4344 INFO  :: REGISTER_CONTEXT:State (1) => (2)
    08/08/2014|11:25:44.523 4024:4344 INFO  :: UCCP:NegotiatedAuthProt0x8
    08/08/2014|11:25:44.523 4024:4344 INFO  :: Function: CUccPlatform::GetMetricsDataPoints
    08/08/2014|11:25:44.523 4024:4344 ERROR :: Failure condition: 'm_spMediaManage == NULL'
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 543 (first 8):
    08/08/2014|11:25:44.594 4024:4344 TRACE ::  17 03 03 00 E0 C4 48 8E  :....àÄHŽ
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.594 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.594 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="CEA1D9C7", snum="34", rspauth="040401ffffffffff000000000000000008fa065605ec8ffed4978ee2", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=e56751f845;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=EB010080
    Call-ID: aa4c7843a0c14678a03acc30a615c81b
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.594 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 314 (first 8):
    08/08/2014|11:25:44.594 4024:4344 TRACE ::  17 03 03 00 B0 42 E2 01  :....°Bâ.
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.595 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.595 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="A79E32E6", snum="35", rspauth="040401ffffffffff0000000000000000435392b30686e91dd20b3120", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=457d67e5ba;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=3D631C5A
    Call-ID: 7666f05a981c4eb28c8bd44d497382a2
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.595 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 133 (first 8):
    08/08/2014|11:25:44.595 4024:4344 TRACE ::  17 03 03 00 80 46 FC D6  :....€FüÖ
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.595 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.595 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="8FB2392C", snum="36", rspauth="040401ffffffffff00000000000000005c89df75c789bd815f2c87c7", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=b87f3eb341;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=447B0080
    Call-ID: 78fff0c6673c4c209914ba91221e7a71
    CSeq: 3 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.595 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.596 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCE28] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCEC8] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCC48] dtor
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E300
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E300
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [contactCard] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCCE8] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: ~Out trxn corr-id (18680A38)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><CEA1D9C7><34><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><aa4c7843a0c14678a03acc30a615c81b><2><SUBSCRIBE><sip:*****@*******.com><e56751f845><sip:*****@*******.com><EB010080><><><0><200>-length-238.
    signature:040401ffffffffff000000000000000008fa065605ec8ffed4978ee2
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (184AD1C8), SIP msg corr-id (b7eb295)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (184AD1C8)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><A79E32E6><35><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><7666f05a981c4eb28c8bd44d497382a2><2><SUBSCRIBE><sip:*****@*******.com><457d67e5ba><sip:*****@*******.com><3D631C5A><><><0><200>-length-238.
    signature:040401ffffffffff0000000000000000435392b30686e91dd20b3120
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (184AD2E0), SIP msg corr-id (e46ab49b)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (184AD2E0)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><8FB2392C><36><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><78fff0c6673c4c209914ba91221e7a71><3><SUBSCRIBE><sip:*****@*******.com><b87f3eb341><sip:*****@*******.com><447B0080><><><0><200>-length-238.
    signature:040401ffffffffff00000000000000005c89df75c789bd815f2c87c7
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (186E42C8), SIP msg corr-id (b03cc2c3)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (186E42C8)
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 373 (first 8):
    08/08/2014|11:25:44.757 4024:4344 TRACE ::  17 03 03 01 70 6D 6F B0  :....pmo°
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.757 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes:
    08/08/2014|11:25:44.757 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="FBA1D2E0", snum="37", rspauth="040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=50091c6b22;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=AC6EA9B1891BDC84CB8DED81E89D55FF
    Call-ID: 6f1ec22d6c96481093ebcdd126f5b255
    CSeq: 3 REGISTER
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft-provisioning-v2
    Supported: adhoclist
    Server: RTC/5.0
    Supported: msrtc-event-categories
    Supported: ms-keepalive-deregister
    Supported: ms-userservices-state-notification
    Content-Length: 0
    08/08/2014|11:25:44.757 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.758 4024:4344 TRACE :: verified buffer: <Kerberos><FBA1D2E0><37><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><6f1ec22d6c96481093ebcdd126f5b255><3><REGISTER><sip:*****@*******.com><50091c6b22><sip:*****@*******.com><AC6EA9B1891BDC84CB8DED81E89D55FF><><><0><200>-length-261.
    signature:040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd
    08/08/2014|11:25:44.758 4024:4344 INFO  :: Trxn corr-id (0C2E3618), SIP msg corr-id (67f10dc5)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(3) at State (2)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: REGISTER_CONTEXT:State (2) => (3)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: SIP_REGISTER:State (3) => (0)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: UCCP:NegotiatedAuthProt0x8
    08/08/2014|11:25:44.758 4024:4344 TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 3 to 4. Status 0. Status text (null).
    08/08/2014|11:25:44.758 4024:4344 INFO  :: CUccDnsResolverManager::Stop MR-INFO - [05026010] DNS resolver manager stopped
    08/08/2014|11:25:44.758 4024:4344 TRACE :: OUTGOING_REGISTER_TRANSACTION::ProcessSuccessfulResponse received 200 UnRegistration SUCCEEDED
    08/08/2014|11:25:44.758 4024:4344 INFO  :: ~Out trxn corr-id (0C2E3618)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: CUccPlatform::WriteStreamToLog:
    08/08/2014|11:25:44.758 4024:4344 INFO  :: <?xml version="1.0" encoding="UTF-8"?>
    <root>
      <Login>
        <Info><![CDATA[Executing wws method with windows auth auth, asyncContext=16C3E478,
     context: WebRequest context@ :415272512
      MethodType:10
      ExecutionComplete? :1
      Callback@ :07AB55A4
      AsyncHResult:3d0000
      TargetUri:https://owa.lon.*******.com/EWS/Exchange.asmx
    .]]></Info>
        <Info><![CDATA[Logon success state 1 reported by user id=EWS (adjusted=EWS) on CManagedCredential[DEFAULT this=01B6C988]]]></Info>
        <ExecuteWithWindowsOrNoAuthInternal>
          <SequenceID>1.1.1</SequenceID>
          <hr>0x0</hr>
        </ExecuteWithWindowsOrNoAuthInternal>
        <SequenceID>1.1</SequenceID>
        <hr>0x0</hr>
      </Login>
    </root>
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 1125 (first 8):
    08/08/2014|11:25:44.974 4024:4344 TRACE ::  17 03 03 04 60 1A 0C FC  :....`..ü
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.974 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes:
    08/08/2014|11:25:44.974 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="4C70707C", snum="38", rspauth="040401ffffffffff000000000000000023304d3690145c9d580a26a5", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
    From: <sip:*****@*******.com>;tag=4c49873a8c;epid=6969679f0b
    To: <sip:[email protected]>;tag=925E0080
    Call-ID: 612b2be69bbe45479e2676a9c89605a3
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bdBGMrXXhjLMmcJ4Ej8ReFZ_nqkUoCWKhFB19tji2ro5-_BAzrBqDJlQAA>
    Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
    Expires: 0
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
    Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bc4_1nrdDL4-KX7KrdReLOthlr4n7DTIcsDrkM0bP4gGNYk0BjUtG1CwAA>
    08/08/2014|11:25:44.974 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: verified buffer: <Kerberos><4C70707C><38><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><612b2be69bbe45479e2676a9c89605a3><2><SUBSCRIBE><sip:*****@*******.com><4c49873a8c><sip:[email protected]><925E0080><><><0><200>-length-233.
    signature:040401ffffffffff000000000000000023304d3690145c9d580a26a5
    08/08/2014|11:25:44.974 4024:4344 INFO  :: Trxn corr-id (184AD3F8), SIP msg corr-id (e3f780cb)
    08/08/2014|11:25:44.974 4024:4344 INFO  :: ~Out trxn corr-id (184AD3F8)
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 277 (first 8):
    08/08/2014|11:25:45.288 4024:4344 TRACE ::  17 03 03 01 10 3B 87 16  :.....;‡.
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:45.288 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes:
    08/08/2014|11:25:45.288 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="59667E0A", snum="39", rspauth="040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
    From: <sip:*****@*******.com>;tag=04814352f9;epid=6969679f0b
    To: <sip:[email protected]>;tag=3F0E0080
    Call-ID: 8115c934d1fd446eb7d034c4fc773ec0
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bd5A_eMqoaHs_fuYP-5aSBoYbANCe_p5RWv6n6yajgyfxebrRuBqDJlQAA>
    Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
    Expires: 0
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
    Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bcFuhIALmH85OaoJh25uPG5Y8-bgabM97QpJ5ypCK7x_cYXXQWUtG1CwAA>
    08/08/2014|11:25:45.288 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: verified buffer: <Kerberos><59667E0A><39><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><8115c934d1fd446eb7d034c4fc773ec0><2><SUBSCRIBE><sip:*****@*******.com><04814352f9><sip:[email protected]><3F0E0080><><><0><200>-length-230.
    signature:040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e
    08/08/2014|11:25:45.289 4024:4344 INFO  :: Trxn corr-id (184AD510), SIP msg corr-id (42a27507)
    08/08/2014|11:25:45.289 4024:4344 INFO  :: ~Out trxn corr-id (184AD510)
    08/08/2014|11:25:49.397 4024:4344 TRACE :: MULTIPARTY_SESSION::RemoveFromLinkedList[17060C50] removed from linked list

    As with the original issue, your problem is likely with the Edge server. The first thing I would do is check all of your ports and DNS settings.
    Remember that Edge may use somewhat unique ports for AV if you, or the federation target, used a single IP address. If you haven't, see if you have that unique port open on the firewall. If you used a single IP address, ensure that the federation target
    has the correct port open also.

  • How can I connect the phone network to LYNC Server 2013?

    Greetings,
    We have a working implementation of Lync Server 2013 (pc to pc), our objective is to connect lync to our phone central, receive and send calls from lync clients (pc, phone, etc), basically enterprise voice services.
    I would like to know the following:
    Hardware that I need for this beside the server.
    Extra configurations that must be done.
    If you could recommend me the hardware needed it would be helpful.

    You'll need a gateway typically. You can find a list of qualified IP gateways here: http://technet.microsoft.com/en-us/office/dn788945.aspx
    I typically lean towards the AudioCodes Mediant line, though many here love Sonus as well.  You'll need to pick a method to connect to your PBX before you begin, such as via a T1/E1 trunk, FXO ports, or a SIP trunk depending on what your PBX will
    support. 
    You'll need to configure the PBX to route calls through the T1 towards Lync and vice versa.  You'll also need to configure the gateway itself, so I'd go with a consultancy with experience here or purchase remote implementation support from the hardware
    manufacturer.
    On the Lync side, you'll need to configure dial plans, voice policies, usages, and routes:
    http://technet.microsoft.com/en-us/library/gg398272.aspx
    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
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Polycom CX600 "Signing in-" "Connecting to Lync Server"

    Hi,
    We have a customer who's using Lync 2013 and Polycom CX600 desk phones. They are getting a strange error where UserA can sign in to the phone, sign out, then back in again without error.
    If UserB tried to sign in to the that phone they would get the message “Signing in…” “Connecting to Lync Server” it never times out until you stop it!
    The only way to allow UserB to sign in is to perform a hard reset of the device. It's a single AD domain with a domain integrated ADCS deployment. They have tried two different levels of firmware with the same outcome. I setup the environment for
    Lync PE as per  Jeff Schertz's blog post.
    Anyone got ideas??
    http://lync2010tips.blogspot.com - [email protected] - If this post has been useful please click the green arrow to the left or click 'Propose as answer'

    Have you checked the logs on the Front End Server and if nothing is there, ran logging through Lync's Centralized Logging Service? Please keep in mind that the immediacy that was OCSLogger.exe does not seem to exist based on my experiences with
    CLS.
    For checking on what may be occurring, I would recommend the Authentication scenario as it checks the following:
    Scenario:  Authentication
    SipStack
    UserServices
    WebInfrastructure
    UserPinService
    CertProvisioning
    Start-CsClsLogging -Scenario Authentication
    Wait at least a minute, log in as the original user, then try to reproduce the issue, then wait a minute or two and stop the logging
    Stop-CsClsLogging -Scenario Authentication
    Give it a few minutes to compile a list then do a search of the CLS logs
    Search-CsClsLogging -OutputFilePath "C:\Users\Admin\Desktop\Auth.txt"
    Now, if you have the Lync 2013
    Debugging Tools installed, launch Snooper (The default path is 'C:\Program Files\Microsoft Lync Server 2013\Debugging Tools') and drag the Auth.txt file into it.
    With that said, you should be able to better decypher what is occurring based on what happens with the successful log on and cross referencing what happens with the failure.

  • What are the supported feature for LYNC Server 2013 WITHOUT Telephony

    Hi
    I have a new customer who is asking for LYNC Server 2013 without to use VoIP Support.
    The would like to use the LYNC-SKYPE connectivity but without LYNC calls.
    Most of their internal users are using SKYPE.
    The Question is now, what Features are possible for example:
    FEATURE-LIST
    See other’s presence
    Manage own presence
    See presence in Office
    Contact management
    Contact card
    PC-PC and multiparty IM
    PC-PC and multiparty file transfer
    Persistent Chat
    PC-to-PC computer audio calling
    PC-to-PC computer video calling
    PC-to-PC presence display, IM, audio, and video with Skype users
    But what of the above feature list is possible without using VoIP ??
    And how works that LYNC WebApp Client without VoIP? Is it possible to route Audio/Video over the internet by using that LYNC WebApp Client in LYNC 2013??
    Thanks in advance ;-)
    Kind regards
    Michael
    Kind regards Michael Damaschke

    All of that is possible without PSTN connectivity or the plus cal.
    When you say VoIP, do you mean audio chatting over TCP/IP in the purest form, or do you mean specifically telephone calls?
    Technially PC-to-PC computer audio calling is VoIP, or voice over IP, but if you're talking about connecting it to a PBX or the phone network, you don't need it for any of the above.  It works wonderfully and is quite a bit cheaper without it due to
    fact that you won't need to license the plus cal for enterprise voice or the Exchange enterprise cal for voicemail. 
    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

  • On-Site Conversation Translator and Lync Server 2013

    To Whom It May Concern,
    I'm looking into deploying Lync Server 2013 Standard and I was curious as to whether there is a way to install the Conversation Translator as a service on-site.  Meaning not using the service on the Internet.  Similar to IBM's Websphere Application
    Server where I can install a local instance on a closed network, have Sametime Connect point to that service, and translate the IM conversation.
    I remember talking to a few MS folks a couple years ago, and they mentioned that it was going to be available as an add-on (or component) of Lync Server.  Is this possible?
    Thanks,
    Brendan

    There is a Client side plugin, take a look at:
    http://channel9.msdn.com/posts/Lync-2013-Translate-a-conversation-from-one-language-to-another-in-real-time-part-one
    http://voipnorm.blogspot.ca/2012/11/lync-2013-enabling-conversation.html
    http://code.msdn.microsoft.com/office/Lync-2013-Translate-a-a849e513
    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.

  • Persistent Chat (Lync Server 2013) with Lync 2010 Group Chat

    I have successfully deployed Lync Server 2013 and both 2013 and 2010 desktop clients connect and function as expected.
    The problem is with Persistent Chat. It works perfectly with the 2013 desktop client but - whilst 2010 Group Chat connects - I receive the error message "The [LOGON_DOMAIN] is not available". No chat rooms are available and I am unable to search.
    I have been unable to locate anything on the web which discusses the problem.
    I do not know whether this makes a difference but the 2010 clients use terminals rather than dedicated workstations.
    Can anyone shed any light on what the problem may be?

    Have you created a CsPersistentChatEndpoint to allow the Group Chat client (2010) to connect to Persistent
    Chat server? Please take a look at: http://technet.microsoft.com/en-us/library/jj204901.aspx
    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.

  • Office Web Apps server / Lync server 2013

    Hi I have installed a Lync 2013 Server and Office Web Apps Server. Configured Lync topology, Office Web Apps farm and certificates.
    However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
    Event ID:      41033
    Description:
    Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
    Attempted Office Web Apps Server discovery Url:
    Received error message: Invalid Uri syntax for WAC configuration
    The number of retries: 1,
    Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
    Resolution:
    Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
    I can access the OWAS server Url from Lync Server
    Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
    The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
    Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
    http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
    He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
    Regards
    Sverre A. Veel

    Hi,
    In addition, please make sure you have restarted front end and office web apps server after reissuing the certificate.
    Kent Huang
    TechNet Community Support

  • Please help me resolve the Lync server 2013 deployment error: "An error occurred while applying SQL script for the feature BackendStore."

    I am getting an error in "Step 2 - Setup or Remove Lync Server Components" of "Install or Update Lync Server System" step.
    "An error occured while applying SQL script for the feature BackendStore. For details, see the log file...."
    Additionally, all previous steps such as: Prepare Active Directory, Prepare first Standard Edition server, Install Administrative Tools, Create and publish topology are done without any errors. The user that I used to setup the Lync server is member of:
    Administrators
    CSAdministrator
    Domain Admins
    Domain Users
    Enterprise Admins
    Group Policy Creator Owners
    RTCComponentUniversalServices
    RTCHSUniversalServices
    RTCUniversalConfigReplicator
    RTCUniversalServerAdmins
    Schema Admins
    I have tried to re-install all the things and started to setup a new one many times but the same error still occurred. Please see the log below and give me any ideas/solutions to tackle this problem.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
    Initializing DbSetupBase
    Parsing parameters...
    Found Parameter: SqlServer Value lync.lctbu.com\rtc.
    Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Found Parameter: Publisheracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group;RTC Local Administrators;LCTBU\RTCUniversalServerAdmins.
    Found Parameter: Replicatoracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group.
    Found Parameter: Consumeracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group;RTC Local Read-only Administrators;LCTBU\RTCUniversalReadOnlyAdmins.
    Found Parameter: DbPath Value D:\CsData\BackendStore\rtc\DbPath.
    Found Parameter: LogPath Value D:\CsData\BackendStore\rtc\LogPath.
    Found Parameter: Role Value master.
    Trying to connect to Sql Server lync.lctbu.com\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 2100.
    Sql version is acceptable.
    Validating parameters...
    DbName rtcxds validated.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup validated.
    DbFileBase rtcxds validated.
    DbPath D:\CsData\BackendStore\rtc\DbPath validated.
    Effective database Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath.
    LogPath D:\CsData\BackendStore\rtc\LogPath validated.
    Effective Log Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    Checking state for database rtcxds.
    Checking state for database rtcxds.
    State of database rtcxds is detached.
    Attaching database rtcxds from Data Path \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath, Log Path \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    The operation failed because of missing file '\\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath\rtcxds.mdf'
    Attaching database failed because one of the files not found. The database will be created.
    State of database rtcxds is DbState_DoesNotExist.
    Creating database rtcxds from scratch. Data File Path = D:\CsData\BackendStore\rtc\DbPath, Log File Path= D:\CsData\BackendStore\rtc\LogPath.
    Clean installing database rtcxds.
    Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
    Initializing DbSetupBase
    Parsing parameters...
    Found Parameter: SqlServer Value lync.lctbu.com\rtc.
    Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Found Parameter: Serveracct Value LCTBU\RTCHSUniversalServices;RTC Server Local Group.
    Found Parameter: DbPath Value D:\CsData\BackendStore\rtc\DbPath.
    Found Parameter: LogPath Value D:\CsData\BackendStore\rtc\LogPath.
    Trying to connect to Sql Server lync.lctbu.com\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 2100.
    Sql version is acceptable.
    Validating parameters...
    DbName rtcshared validated.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup validated.
    DbFileBase rtcshared validated.
    DbPath D:\CsData\BackendStore\rtc\DbPath validated.
    Effective database Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\DbPath.
    LogPath D:\CsData\BackendStore\rtc\LogPath validated.
    Effective Log Path: \\lync.lctbu.com\D$\CsData\BackendStore\rtc\LogPath.
    Checking state for database rtcshared.
    Reading database version for database rtcshared.
    Database version for database rtcshared - Schema Version5, Sproc Version 0, Update Version 1.
    Thanks and Regards,
    Thanh Le

    Thanks Lạc
    Phạm 2
    I Had similar issue i end up uninstalling and reinstallting but same issue, then i change the drive but same issue. It was I/O issue. After adjusting my I/O it fix our issue and installation went on without any issue. 
    If any one using KVM here is detail article 
    We just  give this option cache=‘writeback
    using this article http://www.ducea.com/2011/07/06/howto-improve-io-performance-for-kvm-guests/ and http://itscblog.tamu.edu/improve-disk-io-performance-in-kvm/ this fix my issue thanks 

  • Lync HP 4120 Sign in problems with Lync Server 2013

    Hi, this is my second request for help, this with more information...
    I`ll ready install the follow infrastructure:  (I change the name of my organization for contoso)
    Lync Server 2013 Installation with Enterprise mode with 1 front end :  Pool: lync.contoso.com  Front End: lyncfe01.contoso.com     Back End: lyncsql01.contoso.com
    I`ll ready install a PKI infrastructure with two tiers, the root offline and the subordnate ac.contoso.com
    This with the defailt algorithm configuration RSA SHA1
    My phones are HP 4120 
    In the Front End Server i configured the SCHANNEL registers:
    EnableSessionTicket in 2
    Send..etc in 0
    Ok, the installation is ok, services are OK, Client login trough PC its OK, PSTN Configuration... (I can make a phonecall with the lync client of Office 365)
    Commnd Checks:  
    When i run the command Test-CsPhoneBootstrap -PhoneOrExt 12345 -PIN 123456 -TargetFqdn lync.contoso.com
    The result is:
    Target Fqdn   : lync.contoso.com
    Target Uri    : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
    Result        : Success
    Latency       : 00:00:09.0559615
    Error Message :
    Diagnosis     :
    When i run the command Test-CsPhoneBootstrap -PhoneOrExt 12345 -PIN 123456 for
    check the DHCP the result is:
    Target Fqdn   : lync.contoso.com
    Target Uri    : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
    Result        : Success
    Latency       : 00:00:09.0559615
    Error Message :
    Diagnosis     :
    When i run the follow command 
    PS C:\Users\Administrator> $cred = Get-Credential
    cmdlet Get-Credential at command pipeline position 1
    Supply values for the following parameters:
    Credential
    PS C:\Users\Administrator> Test-CsClientAuth -TargetFqdn lync.contoso.com -UserSipAddress "sip:[email protected]" -UserCredential $cred
    I got this:
    Target Fqdn   : lync.contoso.com
    Target Uri    : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
    Result        : Success
    Latency       : 00:00:00.3431783
    Error Message :
    Diagnosis     :
    But.. when i use the same command but i remove the -targetFqdn for check the Dhcp i got this:
    VERBOSE: Workflow Instance Id 'bca95636-af7b-4b0a-b43d-dba259294b2d', started.
    VERBOSE: Command line executed is 'Test-CsClientAuth -UserSipAddress "sip:[email protected]" -UserCredential $cred
     -Verbose'.
    Target Fqdn   :
    Target Uri    :
    Result        : Failure
    Latency       : 00:00:00
    Error Message : 10060, A connection attempt failed because the connected party did not properly respond after a period
                    of time, or established connection failed because connected host has failed to respond 194.90.8.20:5061
                    Inner Exception:A connection attempt failed because the connected party did not properly respond after
                    a period of time, or established connection failed because connected host has failed to respond
                    194.90.8.20:5061
    Diagnosis     :
    VERBOSE: Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow' started.
    Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow' completed in '5.62E-05' seconds.
    Target web service Url not provided. Will have to extract it from authentication challenge.
    An exception 'Unable to establish a connection.' occurred during Workflow
    Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow execution.
    Exception Call Stack:    at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
       at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)
       at Microsoft.Rtc.SyntheticTransactions.Activities.GetSTSUriActivity.InternalExecute(ActivityExecutionContext
    executionContext)
       at Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Execute(ActivityExecutionContext
    executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)
    'GetSTSUri' activity started.
    Starting STS Uri Discovery...
    ERROR getting STS Uri.
    'UnRegister' activity started.
    'UnRegister' activity completed in '3.12E-05' seconds.
    VERBOSE: Workflow Instance ID 'bca95636-af7b-4b0a-b43d-dba259294b2d' completed.
    VERBOSE: Workflow run-time (sec): 126.0548512.
    The Real Problem is that my Lync HP 4120 Phone can't make a sign in, not from USB cable loging, nor with PIN authentification
    When I try to make a login with the USB cable, I set the user and password and the phone says "Connecting to Lync".. "Downloading a certificate" ... "Installing certificate"... "Downloading Certificate"...
    "Installing Certificate".. forever 
    When I try to make a login with PIN Authentification, the phone first displays the following:
    Account used is not authorized, Please Contact your support team and then shows this:
    An Account matching this phone number cannot be found. Please contact your support team.
    The Pin authentification is enable
    In the Lync Server Enable Kerberos Authentification, Enable Integrated Windows Authentification and Enable Certificate Authentification are enable
    This is the configuration from DHCP 
    Starting Discovery ... 
    Sending Packet (Size: 284, Network Adapter: xx.xx.xx.xx, Attempt Type: Broadcast only)
    --Begin Packet--
    DHCP: INFORM                (xid=130EA7FA)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 319727610
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = Xx.xx.xx.xx
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 0.0.0.0
    DHCP: Client HW Address (chaddr)  = FC15B4###--End Packet--
    Received Packet
    Sender:xx.xx.xx.xx:67, Size:363
    --Begin Packet--
    DHCP: ACK                (xid=130EA7FA)
    DHCP: Op Code           (op)      = 1
    DHCP: Hardware Type     (htype)   = 6
    DHCP: Hops              (hops)    = 0
    DHCP: Transaction ID    (xid)     = 319727610
    DHCP: Seconds           (secs)    = 0
    DHCP: Flags             (flags)   = 0000
    DHCP: Client IP Address (ciaddr)  = xx.xx.xx.xx
    DHCP: Your IP Address   (yiaddr)  = 0.0.0.0
    DHCP: Server IP Address (siaddr)  = 0.0.0.0
    DHCP: Relay IP Address  (giaddr)  = 0.0.0.0
    DHCP: Client HW Address (chaddr)  = FC15B4100289
    DHCP: Server Host Name  (sname)   = 
    DHCP: Boot File Name    (file)    = 
    DHCP: Magic Cookie                = 99.130.83.99
    DHCP: Option Field
        DHCP: DHCP MESSAGE TYPE(  53) = (Length: 1) DHCP ACK
        DHCP: Server Identifier(  54) = (Length: 4) XX.XX.XX.XX
        DHCP: Client Identifier(  61) = (Length: 0)  ()
        DHCP: SIP Server( 120)        = (Length: 17) enc:0 lync.contoso.com (00046C796E6306756E69736F6E026D7800)
        DHCP: Host Name(  12)         = (Length: 0) 
        DHCP: Vendor Identifier(  60) = (Length: 0) 
        DHCP: Param Req List(  55)    = (Length: 0) 0 0
        DHCP: Vendor Info(  43)       = (Length: 86) MS-UC-Clienthttpslync.contoso.com443%/CertProv/CertProvisioningService.svcÜNAP (010C4D532D55432D436C69656E7402056874747073030E6C796E632E756E69736F6E2E6D78040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536572766963652E737663DC034E4150)
        DHCP: End of this option field
    --End Packet--
    Result: Success
    DHCP Server : xx.xx.x.xx.
    SIP Server FQDN : lync.contoso.com
    Certificate Provisioning Service URL : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
    thanks for all, hope somebody can help me with this problem.. i am going crazy...

    Hi, i connected the Lync Phone to another switch and i update the firmware to the newest firmware and i got the same problem..  
    The lync phone download the certificate but cant install it and the still the same error with the SIP login
    An Account matching this phone number cannot be found. Please contact your support team.

  • Lync Server 2013 Standard Deployment: Cannot Open Service Control Manager...

    Hi
    thanks for any advice.I've just install Lync 2013 Standard as the steps in Technet,When I publish the topology,meet the error as listed.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.XdsDatabase'****
     Initializing DbSetupBase
     Parsing parameters...
     Found Parameter: SqlServer Value lync2012ek.ek2012.net\rtc.
     Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
     Found Parameter: Publisheracct Value EK2012\RTCUniversalServerAdmins.
     Found Parameter: Replicatoracct Value EK2012\RTCUniversalConfigReplicator.
     Found Parameter: Consumeracct EK2012\RTCUniversalReadOnlyAdmins.
     Found Parameter: Role Value master.
     Trying to connect to Sql Server lync2012ek.ek2012.net\rtc. using windows authentication...
     Exception Stack:
     Type: System.InvalidOperationException, Message: Cannot open Service Control Manager on computer 'lync2012ek.ek2012.net'. This operation might require other privileges.
     Type: System.ComponentModel.Win32Exception, Message: Access is denied.
    best regards,
    George
    George Guo

    please verify your computer name while you creating FQDN pool FQDN of Server name
    example
    computer name
    is server1
    domain name is abc.ae
    so,
    your FQDN pool name will be server1.abc.ae
    problem solved :)

  • Clean up Active Directory after dirty deleted lync server 2013

    Hi All,
    i have trouble with my lync server, im gonna re-deploy my lync server 2013 after it has deleted without no purpose.
    based on my experience if we want to deploy with the same name and configuration like previously. setup with failed because it has already register in adsiedit ?
    please tell me how to clean up my AD.
    thanks for you assistance guys,
    Best Regards,
    ari

    Hi,
    On DC, please run adsiedit and connect to the Configuration naming context. 
    Browse down to Configuration > Services > RTC Service and then just delete the entire
    RTC Service container.  Also delete the Computer object(s) for any Lync Server you had previously installed. Then you can install the new Lync Server 2013 with no issue.
    Here is a similar case may help you:
    https://social.technet.microsoft.com/forums/lync/en-US/2fbbb75c-8e76-4284-9f32-a27e95e30c49/remove-lync-from-ad-for-fresh-deployment
    Best Regards,
    Eason Huang
    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]
    Eason Huang
    TechNet Community Support

Maybe you are looking for