Lync 2013 client - Set people to "Blocked Contacts" relationship by default?

We are in the process of implementing Lync Server 2013 (on-premises). We have already implemented one front end pool and one edge pool and successfully tested the basic functionality.  Now we are moving on to configuring the various policies based
on our requirements. One requirement that has come late in the planning is to prevent people from receiving IMs unless they explicitly allow people to IM them and to have the ability to whitelist IMs from people on an individual basis.  This is a feature
that was submitted as a requirement by way of our IT HelpDesk manager.
From what I gather, this could be accomplished if someone had the ability to set the default to the "Blocked Contacts" relationship for everyone instead of "Colleagues".  In my research on how to set that as the default, I found
a setting "ShowManagePrivacyRelationship" in Set-CsClientPolicy.  I created a new per-user client policy called "TEST" and applied it to myself.  Then I set ShowManagePrivacyRelationShip to $true via PowerShell on the TEST policy. 
However, even hours after making the change and signing out and back into the Lync 2013 client, I still don't see any change in functionality or new options.
Now, if I instead sign in with the Lync 2010 client, I can indeed see a "Manage Privacy Relationships" option in a drop-down near the right side of the client which takes me to a view where I can see and move "People in my company" and
"People in domains connected to my company" pseudo-contacts from the "Colleagues" relationship to "Blocked Contacts" and this accomplishes exactly what we want to do.
Where can I find the "Manage Privacy Relationship" setting in Lync 2013 client?  If there is no setting called that, how can I accomplish what I am trying to do using Lync 2013?
I would rather not use the Lync 2010 client, as our HelpDesk technicians all use Windows 8.1 and Office 2013.

David:
Yes, I have all of those relationships categories in Lync 2013.  What I am missing is the ability to set the rest of the organization to
Blocked Contacts by default.  I can do this with the Lync 2010 client using the same user login and the same Lync Server 2013 environment.
The following image demonstrates the location of the Manage Privacy Relationships option I would like to leverage in Lync 2013.  The image is of the Lync 2010 client.
https://www.dropbox.com/s/i0g83i9su9e5zox/Manage_Privacy_Relationships.png
If I click that Manage Privacy Relationships option, I end up on the following screen.  Note that there is a
People in my company object under Colleagues.
https://www.dropbox.com/s/kkatgtoexea7evt/Default_Privacy_Relationships.png
I am able to move that People in my company object to another relationship option.  I moved it to
Blocked Contacts, as you can see below.
https://www.dropbox.com/s/956kw0ih15uksgr/People_In_Company_Blocked.png
As you can see in the following image, after making this change if I do not have a person on my Contacts list, they are unable to IM me.  As you can see in my Lync 2013 client relationships list, no one is in my
Blocked Contacts list yet the Lync Test Account is being blocked due to the fact that I put People in my company there and haven't added them to my Contacts list.
https://www.dropbox.com/s/cue09wjj8tidbau/Blocked.png
After adding the Lync Test Account to my Contacts list, the Lync Test Account is able to IM me.
https://www.dropbox.com/s/nalju5ia980lc30/Unblocked.png
I hope these images help make clear that there seems to be a capability present in the Lync 2010 client that I am unable to locate in the Lync 2013 client.  I can't find this
Manage Private Relationships option anywhere in the Lync 2013 client or any other option that lets me see those People in my company and People in domains connected with my company objects.
With regards to the EnablePrivacyMode option, I am already aware of it and that is not what we are looking for.

Similar Messages

  • Lync 2013 Client Not Display Numbers in Contact Card

    Hi
    I have a problem where Lync 2013 client connecting to Lync 2010 backend appears not download the contact list completely. Lync 2010 clients are all operating normally.  On Lync 2010 client, you can view all contact details including Enterprise Voice
    numbers and cell numbers for all users. However on Lync 2013 clients, Lync contact details for some users do not populate completely. In most cases, Enterprise numbers/Work Numbers/Mobile Numbers are missing.  If the contact is pinned then the details
    are retrieved.
    In cases where Work/Voice/Cell numbers are not displayed, affected users is limited to making lync to lync  calls only. The user can still dial the number  and get through without any issues.
    I have deleted and contacts cache on Lync 2013 but this has not helped.
    Regards

    Hi,
    How about check the contact of “Outlook Test” user from the Lync 2010 client?
    According to the second screenshot, since it’s an external account, the information will be limited.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Outlook contact not added Email do not show all information i Lync 2013 Client

    I have seen if no Email address is added into contact personen I only get emty Card of user i Lync 2013.
    When I add Email adr. into contact person and wait a littel then user get all information right i Lync 2013 user Card.
    IS this right or should it also showing user and all information from Outlook contact Card into lync 2013 client Card?

    Lync aggregates contact data from Microsoft Exchange GAL, Outlook and Microsoft Lync Server.
    So you can see information from outlook in Lync user card.
    Lisa Zheng
    TechNet Community Support

  • User search from "Find Someone" in Lync 2013 client does not show contact availability

    Running Lync 2013 Client / Server, when a user searches in the "find someone" field, contact names are returned, but the contact's presence status shows "Updating..." and never populates with the users presence.  If you then select
    a name from the search and open an IM session with them, the presence data is there and is accurate.  I think this feature used to work fine.  

    Hi,
    Did the issue happen only for you or for multiple users?
    Please enter the sip address instead of the name of the user in the “find someone” field to test the issue.
    Please also run Update-CsUserDatabase on FE server then remove Lync client profile to test the issue.
    User profile path: <user profile>\AppData\Local\Microsoft\Office\15.0\Lync\
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Unable to search GAL on Lync 2013 Front End Pool through Lync 2013 client

    I'm in the beginning of a 2010 to 2013 migration and I'm currently testing co-existence functionality between pools.  I've noticed that users cannot search the GAL from their Lync client after being moved to the 2013 pool. 
    When trying to access the internal URL https://fepool13.domain.com/abs/handler the user is prompted to login and after three failed attempts, receives "401 - Unauthorized: Access is denied due to invalid credentials.  You do not have permission
    to view this directory or page using the credentials that you supplied".
    Searching withing a Lync 2010 or Lync 2013 client returns no results, but there are no errors as well as nothing in the event logs or tracing folder regarding not being able to search.
    The 2010 pool has been in production for a few years now and when accessing its internal ABS URL https://fepool10.domain.com/abs/handler the user is granted access after a successful login. 
    In the IIS logs there are slightly more detailed 401 error codes, but I’m not sure what to make of them.
    The rtcab database appears to have user information and all three front end servers appear to be syncing with active directory.  I say the rtcab database appears to have user info because the AbUserEntry table is filled with User ID'd, GUID's and a
    bunch of other stuff.
    The authentication on 2013 front end servers “internal lync website/abs/handler” is set to 1. Negotiate, 2. Ntlm - which is the same as the 2010 front end servers.
    Any ideas?

    Hi,
    Which step did you do among migration from Lync Server 2010 to Lync Server 2013?
    Did you already move CMS from Lync Server 2010 to Lync Server 2013?
    Please create a new Lync account on Lync Server 2013 pool and test the issue again.
    Please check if User Replication has completed with the help of the link below:
    http://technet.microsoft.com/en-us/library/jj204680.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • App V 5.0 Sequence - Lync 2013 Client

    Hello,
    Could you please help me find sequencing steps to virtualize Lync 2013 Client (Basic/Enterprise) using App-V 5.0 SP2?
    Regards,
    Srinivasa Prasad

    Follow that link for advice on how to download Office click-to-run and convert it to an App-V package...
    When I did this, I set the Product ID in the CustomConfig.xml file as ProPlusVolume and used ExcludeApp tags to exclude all apps except for Lync:
    Access
    Excel
    Groove
    InfoPath
    OneNote
    Outlook
    PowerPoint
    Project
    Publisher
    SharePointDesigner
    Visio
    Word
    Here is the info on how to configure this file:
    http://technet.microsoft.com/library/jj219426(v=office.15).aspx
    I believe it is also possible to set the Product ID to Lync, but not sure of the exact value to set and I have not tried this myself. Bonus tip - when you deploy Lync 2013 virtually, the plugins automatically integrate with the locally installed copy of
    Outlook!
    Dan Gough
    UK App-V MVP
    packageology.com
    @packageologist
    LinkedIn

  • Lync 2013 client is deployed but user accounts are not migrated from OCS to Lync 2013 Server - how to open Lync meetings automatically in the Lync Web Plug-in

    We have in our enterprise the following scenario:
    1 - Lync 2013 client is installed
    2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
    3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
    4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
    5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
    on the browser, using Lync Web Plug-in?

    Thanks for the response,
    First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
    Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
    Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
    Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
    Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
    We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue.

  • Silent Uninstall lync 2013 client

    Hi,
    i try to uninstall Lync 2013 Client silently but no matter what i try Lync won't uninstall.
    maybe someone can explain me what i'm doing wrong
    I tried the recommended command
    copy "%~DP0uninstall_lync.xml" "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup
    Controller\uninstall_lync.xml"
    "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
    Config File
    <Configuration Product="LYNCENTRY">
    <Display Level="None" AcceptEULA="TRUE" />
    <Setting Id="SETUP_REBOOT" Value="NEVER" />
    <Logging Type="standard" Path="c:\windows\log\" Template="Microsoft Office Lync Uninstall(*).log" />
    </Configuration>
    Log:
    2014/11/24 14:49:11:039::[4844] PERF: TickCount=11665520 Name=OBootStrapper::Run Description=Begin function
    2014/11/24 14:49:11:040::[4844] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
    2014/11/24 14:49:11:040::[4844] Running 32-bit setup on a 64-bit operating system.
    2014/11/24 14:49:11:040::[4844] Command line: "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
    2014/11/24 14:49:11:040::[4844] Parsing command line.
    2014/11/24 14:49:11:040::[4844] Config XML file specified: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:040::[4844] Uninstall requested for product: LYNCENTRY
    2014/11/24 14:49:11:040::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:060::[4844] Preferred product specified in config.xml to be: LYNCENTRY
    2014/11/24 14:49:11:060::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
    2014/11/24 14:49:11:060::[4844] Logging type standard specified in config.xml.
    2014/11/24 14:49:11:060::[4844] Log directory: c:\windows\log\ specified in config.xml
    2014/11/24 14:49:11:060::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
    2014/11/24 14:49:11:060::[4844] Display level none specified in config.xml.
    2014/11/24 14:49:11:075::[4844] Using setup controller dll at location [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
    2014/11/24 14:49:11:075::[4844] Verify file signature in "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe"
    2014/11/24 14:49:11:129::[4844] C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe is trusted.
    2014/11/24 14:49:11:129::[4844] Verify file signature in "C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL"
    2014/11/24 14:49:11:198::[4844] C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL is trusted.
    2014/11/24 14:49:11:296::[4844] Using setup controller dll at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
    2014/11/24 14:49:11:296::[4844] PERF: TickCount=11665785 Name=OBootStrapper::Run Description=Calling RunSetup
    2014/11/24 14:49:11:302::[4844] PERF: TickCount=11665785 Name=RunSetup Description=Begin function
    2014/11/24 14:49:11:303::[4844] WER element [P2] is set to value [OSETUP.DLL]
    2014/11/24 14:49:11:303::[4844] WER element [P3] is set to value [15.0.4569.1503]
    2014/11/24 14:49:11:304::[4844] Catalyst execution began: 11/24/2014 14:49:11.
    2014/11/24 14:49:11:305::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:307::[4844] Preferred product specified in config.xml to be: LYNCENTRY
    2014/11/24 14:49:11:307::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
    2014/11/24 14:49:11:307::[4844] Logging type standard specified in config.xml.
    2014/11/24 14:49:11:307::[4844] Log directory: c:\windows\log\ specified in config.xml
    2014/11/24 14:49:11:307::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
    2014/11/24 14:49:11:307::[4844] Display level none specified in config.xml.
    2014/11/24 14:49:11:308::[4844] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [enabled] for the [UninstallExecutionMode]
    2014/11/24 14:49:11:308::[4844] Ensuring the install-state of setup controller files for product [LYNCENTRY].
    2014/11/24 14:49:11:308::[4844] Warning: Product registation information for 'LYNCENTRY' not detected. ErrorCode: 1011(0x3f3). Failed attempt to force-repair setupexe boot files.
    2014/11/24 14:49:11:308::[4844] Searching for default versions of resource files under the folder [C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller].
    2014/11/24 14:49:11:328::[4844] Found [1] resource files under the default folder.
    2014/11/24 14:49:11:328::[4844] Running in [UninstallExecutionMode]. Run from TEMP folder at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214].
    2014/11/24 14:49:11:345::[4844] Loaded resource file [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUPUI.DLL] (CultureTag=de-DE).
    2014/11/24 14:49:11:345::[4844] WER element [SuppressModal] is set to value [false]
    2014/11/24 14:49:11:346::[4844] WER element [P1] is set to value [15.0.4569.1503]
    2014/11/24 14:49:11:346::[4844] Loaded Dll : C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL.
    2014/11/24 14:49:11:346::[4844] Catalyst version is : 15.0.4569.1503
    2014/11/24 14:49:11:346::[4844] JobExecutionMode is UninstallExecutionMode.
    2014/11/24 14:49:11:547::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:11:547::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:11:548::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
    2014/11/24 14:49:11:548::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
    2014/11/24 14:49:11:548::[4844] Ensuring the install-state of setup controller files for all Products.
    2014/11/24 14:49:11:548::[4844] Opening registry key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
    2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller files for product [LYNC].
    2014/11/24 14:49:11:549::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
    2014/11/24 14:49:11:549::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
    2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0407-1000-0000000FF1CE}].
    2014/11/24 14:49:11:549::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0407-1000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:11:549::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:13:038::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0000-1000-0000000FF1CE}].
    2014/11/24 14:49:13:038::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0000-1000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:13:038::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:15:639::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-006E-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:15:639::[4844] Product INSTALLSTATE for ProductCode '{90150000-006E-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:15:639::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:18:424::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0410-0000-0000000FF1CE}].
    2014/11/24 14:49:18:424::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0410-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:18:424::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:20:222::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:20:222::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:20:222::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:21:766::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-040C-0000-0000000FF1CE}].
    2014/11/24 14:49:21:767::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-040C-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:21:767::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:23:339::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0409-0000-0000000FF1CE}].
    2014/11/24 14:49:23:339::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0409-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:23:340::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:25:046::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002C-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:25:047::[4844] Product INSTALLSTATE for ProductCode '{90150000-002C-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:25:048::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:26:619::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012B-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:26:620::[4844] Product INSTALLSTATE for ProductCode '{90150000-012B-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:26:620::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:28:951::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012C-0000-0000-0000000FF1CE}].
    2014/11/24 14:49:28:951::[4844] Product INSTALLSTATE for ProductCode '{90150000-012C-0000-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:28:952::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:36:136::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:36:136::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:36:136::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
    2014/11/24 14:49:36:136::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
    2014/11/24 14:49:36:136::[4844] Not showing message because suppress modal has been set. Title: 'Setupfehler', Message: 'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
    2014/11/24 14:49:36:136::[4844] Message returned: 1
    2014/11/24 14:49:36:141::[4844] Error: Catalyst boot time check failed Type: 66::PreReqCheckFailure.
    2014/11/24 14:49:36:141::[4844] Catalyst execution finished: 11/24/2014 14:49:36. Return code: 30066. Exception caught: PreReqCheckFailure.
    2014/11/24 14:49:36:141::[4844] PERF: TickCount=11690621 Name=RunSetup Description=End function
    My next attempt was to look for MSI Files in Windows\Installer and the Uninstall RegKey
    MsiExec.exe /X{90150000-012C-0000-0000-0000000FF1CE} /qn /norestart /L*v
    "c:\windows\log\Microsoft_Lync_2013_Update_KB2817626_x86_0185_Install.LOG"
    MSI (s) (10:4C) [15:10:52:612]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (10:4C) [15:10:52:628]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (10:4C) [15:10:52:631]: End dialog not enabled
    MSI (s) (10:4C) [15:10:52:631]: Original package ==> C:\Windows\Installer\bfb379.msi
    MSI (s) (10:4C) [15:10:52:631]: Package we're running from ==> C:\Windows\Installer\bfb379.msi
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall Flags override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90150000-012C-0000-0000-0000000FF1CE}'.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (10:4C) [15:10:52:649]: Opening existing patch 'C:\Windows\Installer\bfb3d2.msp'.
    MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb37a.msp'.
    MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb386.msp'.
    MSI (s) (10:4C) [15:10:52:651]: SequencePatches starts. Product code: {90150000-012C-0000-0000-0000000FF1CE}, Product version: 15.0.4569.1506, Upgrade code: {00150000-012C-0000-0000-0000000FF1CE}, Product language 0
    MSI (s) (10:4C) [15:10:52:652]: Note: 1: 2205 2: 3: MsiPatchMetadata
    MSI (s) (10:4C) [15:10:52:652]: SequencePatches returns success.
    MSI (s) (10:4C) [15:10:52:652]: Final Patch Application Order:
    MSI (s) (10:4C) [15:10:52:652]: {27D7A8D0-8E28-4A2A-A1D4-473E31DF6438} -
    MSI (s) (10:4C) [15:10:52:652]: {73E81413-5A7E-40A3-9BD5-821ADDF30B10} -
    MSI (s) (10:4C) [15:10:52:652]: {D448DFE1-B83E-4394-9484-25563EFBF58D} -
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisablePatch' is 0
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (10:4C) [15:10:52:653]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4569.1506
    DEBUG: Error 2746: Transform 90006E0401000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:653]: Skipping validation for patch transform #90006E0401000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4420.1017
    1: 2746 2: 90006E0401000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0401000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0401000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4481.1005
    1: 2746 2: 90006E0401000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0402000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4569.1506
    1: 2746 2: 90006E0402000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4505.1008
    1: 2746 2: 90006E0402000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4454.1509
    1: 2746 2: 90006E0402000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4454.1509 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4454.1509. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0405000015.0.4481.1005
    1: 2746 2: 90006E0402000015.0.4454.1509 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4569.1506
    1: 2746 2: 90006E0405000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4505.1008
    1: 2746 2: 90006E0405000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4454.1004
    1: 2746 2: 90006E0405000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0405000015.0.4454.1004. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4481.1005
    1: 2746 2: 90006E0405000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4569.1506
    1: 2746 2: 90006E0406000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4433.1507
    1: 2746 2: 90006E0406000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4433.1507 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4433.1507. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0406000015.0.4505.1008
    1: 2746 2: 90006E0406000015.0.4433.1507 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4569.1506
    1: 2746 2: 90006E0406000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0407000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0407000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4420.1017
    1: 2746 2: 90006E0407000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0407000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0407000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4481.1005
    1: 2746 2: 90006E0407000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0408000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4569.1506
    1: 2746 2: 90006E0408000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4505.1008
    1: 2746 2: 90006E0408000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4454.1004
    1: 2746 2: 90006E0408000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4454.1004. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0409000015.0.4569.1506
    1: 2746 2: 90006E0408000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0409000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0409000015.0.4420.1017
    1: 2746 2: 90006E0409000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0409000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0C0A000015.0.4569.1506
    1: 2746 2: 90006E0409000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0C0A000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0C0A-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:076]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:076]: Produkt: Microsoft Lync 2013 -- Das Entfernen ist fehlgeschlagen.
    MSI (s) (10:20) [15:16:59:077]: Das Produkt wurde durch Windows Installer entfernt. Produktname: Microsoft Lync 2013. Produktversion: 15.0.4569.1506. Produktsprache: 0. Hersteller: Microsoft Corporation. Erfolg- bzw. Fehlerstatus der Deinstallation: 1603.
    MSI (s) (10:20) [15:16:59:079]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
    MSI (s) (10:20) [15:16:59:085]: Deferring clean up of packages/files, if any exist
    MSI (s) (10:20) [15:16:59:085]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
    MSI (s) (10:20) [15:16:59:085]: Unable to delete the file outside of the engine. LastError = 2
    MSI (s) (10:20) [15:16:59:085]: MainEngineThread is returning 1603
    MSI (s) (10:4C) [15:16:59:089]: RESTART MANAGER: Session closed.
    MSI (s) (10:4C) [15:16:59:089]: No System Restore sequence number for this installation.
    === Protokollierung beendet: 24.11.2014 15:16:59 ===
    MSI (s) (10:4C) [15:16:59:090]: User policy value 'DisableRollback' is 0
    MSI (s) (10:4C) [15:16:59:090]: Machine policy value 'DisableRollback' is 0
    MSI (s) (10:4C) [15:16:59:090]: Incrementing counter to disable shutdown. Counter after increment: 0

    2014/11/24
    14:49:36:136::[4844]
    Error: Product
    is not installed, therefore transition to
    MMode is unsafe
    for product: LYNCENTRY
    Type: 27::InstalledProductStateCorrupt.
    2014/11/24
    14:49:36:136::[4844]
    Not showing message because suppress modal has been
    set.  Title:
    'Setupfehler', Message:
    'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
    From the snippet of the log, it appears that the product installation has been corrupted. Probably, try to repair it from Control Panel first and then test the command again?
    Also, is it Microsoft Lync Basic 2013?
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Lync 2013 client doesn't read proxy.pac file Lync exclusions

    Hi all,
    I have a very annoying issue where by the Lync 2013 client ignores the proxy.pac file exclusions set below:
    (host == "lync.test.domain") || (host == "lyncdiscoverinternal.test.domain") ||
    (host == "lyncwacdca.test.domain") ||
    (host == "lyncwacdcb.test.domain") ||
    (host == "lyncwebintdca.test.domain") ||
    (host == "lyncwebintdcb.test.domain")
    IE is set to use automatic configuration script of
    http://proxy.test.domain:8083/proxy.pac This file can be reached through and IE browser, downloaded and it's syntax read.
    If I set my proxy server and exclusions manually within IE9 then they are adhered to. That is Lync 2013 is able to read.
    My thinking: that some application may be iterferring with Lync 2013 getting to
    http://proxy.test.domain:8083/proxy.pac or reading in the exclusions set within the file.
    If I enter https://lync.test.domain into the browser URL search field I can see that it is being sent straight out to the proxy as opposed to bypassing it.
    Does anyone have an example of their proxy.pac exclusion set for Lync 2013 just in case my syntax is not looking the best.
    Cheers

    Update to this issue - solution was to move the proxy exclusions to the top of the proxy.pac
    Outcome resulted in Windows WinHTTP processing the the Lync proxy exclusions prior to the Lync.exe firing during logon. I don't believe you would see this in a typical infrastructure. Since initially looking into this issue I  have been
    able to show through packet traces, large periods of latency in delivery of desktop profile items due to backend profile storage issues.
    In eddition this moving the exclusions to the top of the pac file I made use of substrings. I don't believe the use of substrings is any better or worst, but just easier for others to understand what the exclusion allows specifically.
    Example of pac exclusion now:
    if (url.substring(0,39) == "http://lyncdiscoverinternal.testdomain.") { return "DIRECT"; } //matches 31 characters including last . or period
    I entered similar entries for all required exclusions. The result was Lync signing in within 6 seconds as opposed to the 40 second (through the user of legacy SRV records).

  • Schedule a meeting via Lync 2013 client

    Hi All,
    quick run down of my set up,
    Exchange 2013 SP1 (no UM) and new installation of Lync 2013 FE with Feb 2015 cumulative updates (no Ent voice )
    haven't integrated Exchange with Lync.
    my problem is when i try to schedule a meeting with a colleague via Lync 2013 client it says "no free/busy information could be retrieved and if i let it stay open for 5 min it will come up or unless I unselect and reselect the user the information
    comes up.
    any idea what's causing thus and how to fix it?
    Thanks in advance

    Not sure of a fix, but Michael LaMontange posted a workaround for it:
    http://realtimeuc.com/2013/04/no-free-busy-when-scheduling-meeting-from-lync/
    Some other thoughts here:
    http://www.doitfixit.com/index.php?option=com_content&view=article&id=82:no-freebusy-information&catid=34:exchange-2010&Itemid=53
    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.

  • Can't open email items from search after installing Lync 2013 client

    Hello,
    We're deploying Lync 2013 in our environment.
    At the moment we're using Office 2010 on the clients.
    For testing the deployment I've installed the Lync 2013 client.
    After installing, when I perform a search on my pc and outlook items are found, they suddenly appear with an Outlook 2013 icon.
    When doubleclicking, nothing happens, neither when I rightclick.
    I've checked the "associate a file type or protocol with a prgram", and "set your default programs" in the control panel.
    In neither of them I can find the Outlook 2013 icon, and for email, every file type is configured to open with Outlook 2010.
    Does anyone know what might be the problem. We have this problem with every user for which we install the Lync 2013 client.

    You can do the following to restore functionality:
    If you have office 2010 use the keys below, the Lync install will change them to Office15:
    [HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}]
    @="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-110"
    [HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\DefaultIcon]
    @="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-504"
    [HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\InprocServer32]
    @="C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL"
    "ThreadingModel"="Apartment"
    [HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\ShellFolder]
    "Attributes"=dword:20140000

  • Auto logout or disconnect of Lync 2013 client after inactivity

    Is there any way to configure the Registry or perhaps a GPO so that Lync 2013 clients running on Windows 7 will auto logout or disconnect from the server if they have been inactive after a certain amount of time? Searched around and could not find anything.
    I found the link below but it uses Preferences which have undesirable side affects.
    http://unifiedme.co.uk/2014/01/lync-2013-group-policy-enforce-ringtones-centrally/

    Hi,
    There is no method naturally to auto logout of Lync 2013 after inactivity. You may need to configure auto-logoff Windows after idle time to log off the Lync can check 
    the thread below to configure auto-logoff Windows:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/2d618fdb-faf7-41a1-9207-ff07b8d29091/how-to-automatically-log-off-idle-users?forum=winserversecurity#c7c21990-73b4-41ac-a9b5-4d571372ec10
    Or you may need to custom your own Lync client, you can post the question on MSDN Lync SDK forum. Thank you for your understanding.
    Here is the link to MSDN forum:
    http://social.msdn.microsoft.com/Forums/en-US/communicatorsdk/threads
    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

  • Lync 2013 Clients in Child Domain Log "The server returned HTTP status code '403 (0x193)' with text 'Forbidden'."

    Hey All, I am really stumped on this one. 
    Environment - Is using split DNS
    Forest Root Domain - Contains new Lync 2013 Server Standard, ADDS, DNS, Enterprise CA, Workstations
    Clients in this domain connect and work beautifully. No errors. 
    Child Domain - ADDS, DNS, Workstation, Lync 2013 client
    Client autodiscovers, and then asks for a password. Enter the password and this comes up...
    Can't sign in to Lync, You didnt get signed in, It might be your sign-in address or logon credentials..  blah blah blah" 
    Client log shows 
    Error:
    There was an error communicating with the endpoint at 'https://domainlync13srv.Domain.net/WebTicket/WebTicketService.svc'.
    The server returned HTTP status code '403 (0x193)' with text 'Forbidden'.
    The server understood the request, but cannot fulfill it.
    As far as i can tell certificates are correctly configured with all the SAN's possible in my forest. The user is correctly set up in Lync control panel. Autodiscovery seems to be working as it should. EWS is working correctly. 
    Repaired client, removed cached creds, has all lync 2013 updates no dice
    Thank you all! 

    I am an IDIOT. 
    I did not prepare the child domain with the LYNC setup tool. Logged on to a file server in the child domain with domain admin rights and sure enough the setup said the domain was "partial". Ran the setup and bam it all started working. 

  • Question about adding Distribution Groups to Lync 2013 clients

    Hello Everybody,
       Hopefully somebody can assist me with this issue. I created a Universal Distribution Group within our domain which consists of about 75 people. I logged onto the lync server and ran Update-CsAddressBook waited for it to complete and then
    followed Terence Luk guide to force the lync 2013 client update http://terenceluk.blogspot.com/2013/02/forcing-lync-2013-client-to-download.html However
    even after the update has completed I am unable to locate this group in the lync client any suggestions would be greatly appreciated. 

    Hi,
    Please type the complete sip address to search it.
    If the issue persists, please remove lync profile and sign in again.
    Kent Huang
    TechNet Community Support

  • Lync 2013 client still show titles that is turned off on Lync 2010 server

    Hi All
    I have another unique issue it seems.
    Environment - Lync Server 2010 on CU5. Lync 2010 and Lync 2013 client.
    The client has used absconfig and removed the titles as the don't want that to be displayed.
    The lync 2010 clients does not show the titles - so that is working.
    Lync 2013 from external access the titles does not show - so that is working.
    Internally on the LAN the Job Titles shows on the Lync 2013 client - so not working.
    What I've tried so far :
    Disabled exchange contact sync on a client policy
    Used webdownload only for address book.
    Using registry to force download of address book.
    Deleted the Lync folder on the client computer to make sure when it downloads the .idx and .db file that it is the latest version.
    None of the above remediations seems to have any impact on the lync 2013 client.
    I have tried to replicate this in my lab (without an exchange server) and the the lycn 2010 and 2013 clients behave as they should be not displaying the job titles.
    Having anyone come across this before?
    I will be patching the lync 2010 server to the latest CU update, but I think the issue is somewhere else.
    Any suggestions will be appreciated.
    Regards
    Danie

    Hi Danie,
    I suggest you could install the latest CU update first, because the CU update would fix many problems.
    In addition, shall we test Lync 2013 on a fresh computer without Outlook?(You could test this using Lync 2013 Basic).
    Best regards,
    Eric

Maybe you are looking for

  • Cannot Get Mail Connection to Server Failed

    Ok, I am not a very good with setting things up but I have the itouch 16GB, I have managed to set up my email and am receiving new ones but I can not connect when I am away from my home, everytime I try to connect I get the following message, *Cannot

  • Problem with Bapi_po_Getdetail return values

    We have developed a web service in asp.net to get the details of a particular purchase order number calling Bapi_po_Getdetail. The input parameters that we pass are: string  ITEMS = “X” string PURCHASEORDER= “<purchase order number>” But when we debu

  • HT2500 delete address book entries

    How do you delete address book entries?

  • Why can't apple put a simple audible low battery indicator on the iphone?

    I get so tired of having my iphone shut down on me mid-conversation. My screen is black and up to my ear; my phone is in my purse while I'm talking on my blue tooth and also has a black screen; or my phone is on my hip with a black screen while I tal

  • Not able to download with Firefox 9.01 on OSX 10.7.2

    Hi I was not able to download the LR 4 Beta 1 with Firefox 9.01 on OSX 10.7.2, The Browser just got into a loop. https://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_lightroom4 no problem with Safari Version 5.1.2 (7534.52.7) br Mike