Lync 2013 client not processing history spooler folder (conversation history)

We have been using Lync 2013 fully patched up to latest & greatest, along with Exchange 2013 for about 6 months now & everything is working
great. (I did a AD migration from our old parent company in the UK as well as migrated exchange from 2010 to 2013, all that without a hitch for the most part.)
the issue that seems to be popping up intermittently is conversation history. I manged to work around some of them for the most part & getting
them to process; with the exception of 1 user.
If he logs into another PC his conversation history works fine.
However on his PC it does not seem to want to process the history spooler folder in "C:\Users\User\AppData\Local\Micros­oft\Office\15.0\Lync\[email protected]­m",
there are 737 files in there (all of his convo history)
Now what i did & it seems to sort of work is,Signed out of Lync, I deleted the users Sip folder after backing up the history spooler folder, logged
back into Lync which recreated the sip_user folder; logged back out of Lync , copied the History Spooler folder back to the SIP folder, & signed into Lync.
This took 10 files out of the history spooler folder, & then appeared in the convo history; both on Lync client & Outlook; but did not bring
all of them in. I did some testing and if you log out, then back in, it processes a few more. but not all.
EWS & MAPI settings & all other Lync configuration information settings match a users with no convo history issues.
So now the questions. 
1)What could possibly cause what ever mechanism that processes the History spooler folder to stop/only process a few items during sign in? Also what
is the mechanism? 
2)Is there any way through powershell to force the synchronization of the history spooler folder?
Thank you

so in some more testing i had check the history spooler folder, & there were about 700+ files.
as a note* (Upon deleting the users sip folder & logging back in thus re-creating the folder new convo's where saving. So i did "fix" the issue with no new convo's during my initial work prior to opening this thread.)
I then removed a good chunk of the *.hist files & only left convo's from this month. signed out then back in, 10 files processed. then did it again, another 10. did it again, & it did 4 then stopped. I noticed there were some files over 1 mb. &
remember coming across this post (Lync
not processing files over 1mb) so i removed the 1mb files & then logged out then back in. processed 10 more. 
i then added all the files to the history spooler file with the exception of the files over 1 mb, & logged in & out about 70 times to process the whole folder. Now all of the convos are in Lync & outlook as well as new convo's being saved. However
i have a folder now with 130 files that are over 1mb that will not process at all..
so now i am trying to find some validity on the statement in the link above 
"We did open a case with Microsoft and they confirmed it is a bug in the Exchange EWS HTTP stack. It
is supposedly under review by the Dev team, but my guess is that it won't be fix soon. The magic size is exactly 1MB or 1048576 bytes."
If that is actually true it sucks & is some B.S as it is nearly 2 months later & this is obviously
a major problem & not even a CU or PU has been released to address the issue.

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

  • Lync 2013 client not finding audio device

    I've got a problem with the Lync 2013 client on Windows 7 x64 Ent that's  giving me a real headache, please help!
    It's the 32-bit version (15.0.4535.1002) downloaded with Office 365 Pro Plus and it's refusing to pick up my USB headset/microphone - a Plantronics Blackwire C320-M. The message I get in Lync Tools|Audio Device is "We didn't find an audio device,
    which you need for calling"
    First and foremost, the device is working with the Lync 2010 64-bit client without issue
    (I've not yet de-installed it) and is showing as working correctly in my Device Manager.
    I'm aware of a few similar threads here and elsewhere where this has been seen, so I've tried the following advice:
    1. Tried a different Headset (Plantronics C310-M)
    2. Installed all MS Office 2013 updates
    3. Reset all Generic USB and USB Root Hubs listed in Device Manager USB Controllers
    4. Disabled "Allow the computer to turn of this device to save power" for each of the above USB Controllers
    5. Uninstalled and reinstalled USB controllers above
    6. Removed old/stale USB drivers using 3rd party tool (USBDView)
    7. Multiple restarts of my HP Compaq Pro 6300 Micro Tower PC!
    None of the above has made any difference. Any helpful suggestions very gratefully received!
    Thanks
    Paul

    Update:
    Whilst browsing through the Windows App Event Log, I found these two entries:
    Log Name: Application
    Event ID: 1
    Source: Lync
    The description for Event ID 1 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    Log Name: Application
    Event ID: 12
    Source: Lync
    The description for Event ID 12 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Lync
    I tried both a "Repair" and "Online Repair" in Control Panel | Programs and Features | Office 365 Pro Plus. The events still appear when starting Lync 2013.

  • Lync 2013 Client - Not saving persistent chat options between logins

    We run Lync Server 2013. The Persistent Chat options for When a new Message arrives, Show the message in a new window, Show me an alert and Play this sound do not stay checked. They will spontaneously uncheck themselves. We have confirmed it's not an Antivirus
    issue. We are using folder redirection on the desktop and my documents folder. Where are these settings stored? It's very annoying that they do not stick. I can replicate with over 100 users. 

    We are having similar issues at our company as well, and would like some kind of answers or feedback please. Our issue is that when we select the "Persistant Chat" options, they dont seem to do anything at all meaning the alerts dont work, etc. If we log
    out and back in they still dont function, but they are still checked. When we reboot the entire PC then they revert back to being "unchecked".
    We previously had 2010 lync and 2010 group chat installed, we removed 2010 normal lync but group chat was still installed. We got the settings in lync 2013 working correctly for a short time by uninstalling everything lync, and reinstalling only 2013 version,
    but after 2-3 days and 1-2 reboots later, the issue returns.
    I hope someone can assist us, otherwise we will have to find a different solution for our business.

  • Lync 2013 client ews has not fully initialized

    Hello
    I have Lync 2010 server and Lync 2013 client. whenever Lync 2013 client logs in from outside(external) I get a exchange authentication pop up. and when I checked the status of lync - it says ews is not fully initialized. lync 2013 client works fine
    from inside.  If I use lync 2010 client from outside than it works fine, no pop up and ews status is ok. so I know that my TMG rules are accurate but something wrong with lync 2013 client itself.  I have upgraded the client to the latest update. 
    Also I have tried various combinateion of this below registry fix without any success.
    also Microsoft remote connectivity analyzer test is clean.  no errors.
    http://uclobby.com/2014/01/03/lync-client-2013-ews-has-not-fully-initialized/
    any thoughts?
    thanks

    Hi 
    Can you try clearing the user local cache SIP folder  who logs in externally and see the results
    User\App Data\Microsoft\Office 15\lync\SIP
    Is your SIP domain different from your domain name
    If it is so you can try by adding the SMTP Domain as trusted using the following cmdlet:
    reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v TrustModelData /t REG_EXPAND_SZ /d <SMTP Domain> /f
    If it is for multiple users you can also try the below  article
    http://technet.microsoft.com/en-us/library/gg398920.aspx
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • 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.

  • Outlook 2010 contacts not showing phone number in Lync 2013 client

    Hi,
    We have Lync 2013 with Exchange 2010. Recently we started upgrading Lync clients from 2010 to 2013.
    A few users started reporting that their local Outlook contacts does not show phone numbers in Lync 2013 (working with 2010)
    I have installed the august patch which should solve this issue
    981751 - Lync 2013 does not display telephone number of an Outlook 2010 contact in the contact card
    Any idea where to look next?

    Hi Tobias Borgen Nielsen,
    Lync expects all the phone numbers to be in the E.164 format, meaning they should be +1-111-11111111 etc. If they’re not like this, you will have to normalize them if you want Lync
    to publish them.
    The related article for your reference.
    Lync not populating contact cards phone numbers from Active Directory (Or: How to normalize AD phone numbers for Lync Server 2010 and 2013)
    http://y0av.me/2012/02/23/normalize_ad_numbers/
    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.
    Hope it can be helpful.
    Best regards,
    Eric

  • Dial-In Conferencing page does not open from Lync 2013 client

    Hello Everyone,
    I am facing this strange issue with my Lync Clients. All the users started experiencing the same behavior. So, I think this has something to do at the Server side.
    Earlier, when trying to open the Dial-in conferencing settings from the Lync Client (Tools --> Dial-in conferencing settings), it would automatically open the Dial-In conferencing settings in a new web page. But, recently this is not happening. The strange
    thing is I will be able to open the dial-in conferencing settings manually from a web browser by typing in the URL.
    Has anyone experienced similar issues in the past? I would appreciate any ideas regarding this from your part so that I can try to resolve this. Thanks in advance.

    Hi,
    Try to rerun Step 2-Setup or Remove Lync Server Components and then test again.
    Check if Lync Address Book update to the latest status.
    Make sure all Lync 2013 client update to the version.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 client is showing EWS not deployed.

    Hi,
    I am facing issue with lync 2013 client in the configuration information. it is showing EWS not deployed .
    UCS Connectivity State;      Exchange connection Down;           --;
    MAPI Information;              Status OK;MAPI Status OK;
    EWS Information;;             EWS not deployed;
    I am facing this issue both internally and externally.
    I am using Lync 2010 server and exchange 2010.
    Lync  2010 client is showing all EWS information correct. No issue with lync 2010 client.
    Thanks 

    Had the same issue.  Couple of things you can try:
    1.  Verify EWS virtual directory is configured properly on your Exchange CAS or Front-End servers (Get-WebServicesVirtualDirectory)
    But the thing that fixed it for me was:
    2.  Create SRV records for (_autodiscover, _TCP, 443) pointing to your CAS or Front-End server/array.  This has to be done for the forward zone of your public domain name (i.e. contoso.com, not contoso.local).  I did them both just
    to be on the safe side, but was the public domain that did it.

  • 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

  • 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).

  • 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.

Maybe you are looking for