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.

Similar Messages

Lync 2013 client deployment via SCCM with silent uninstall of Communicator / Live Meeting / Plugin

Hi
We are rolling out Lync 2013 across our org to many remote sites and are wondering the best approach for this.
We hope to leverage our SCCM, but so far we've only been installing Lync manually in our local test group.
I noticed that when installing Lync, it doesn't remove Communicator, Live Meeting, or the Live Meeting plugin for Outlook though.
Ideally, we would want to be able to push Lync 2013 client (standalone version, not Office 2013 Suite) via SCCM as well as uninstall Communicator 2007 R2, Live Meeting 2007 and Conferencing Add-in for Microsoft Office Outlook, all silently. Whether this
can be done while the user is logged in and using Outlook/Communicator, I am unsure (probably not), so doing this overnight with users logged off but machines on would probably work best.
Is there any documentation / guides from MS or other blog sites that have gone through this same process? From the searching I've done, it doesn't seem to be too common for a large deployment / jump from OCS 2007 to Lync 2013 on-premise.

Hi,
refer to this article it might help
http://social.technet.microsoft.com/Forums/lync/en-US/cf9ca58c-b9e8-465c-afb4-ed3992092f81/lync-2013-client-silent-installation
also did you try using Group Policy?
http://blogs.technet.com/b/mir/archive/2011/06/04/how-to-automate-lync-client-2010-deployment-in-multi-architect-environment-using-active-directory-group-policy.aspx
hope this help
If you find this helpful
please click "Vote as Helpful" if it answered your question please click "Mark as Answer"
Mostafa Eltohamy
Blog: http://Lyncdude.com Twitter:
LinkedIn:
XING:

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.

No audio device detected - Lync 2013 Client

I have a brand new Dell Latitude E6430 laptop running Windows 7 x64 SP1. I installed Office 2013, including the Lync 2013 client. We are running Lync 2013 server as well. I have connected three different audio devices.
Polycom CX600 phone.
Plantronics Bluetooth headset.
Logitech Video Camera (The video on this works with Lync but no audio)
I cannot get Lync to recognize either of them. I can see them as devices in Windows but within Lync I only get a screen that says "We didn't find an audio device, which you need for calling". Does anyone have any idea on how to resolve this issue?
It is driving me crazy. Especially since it worked perfectly on my old laptop that had the same OS and patches, etc...
Thanks for your help in advance.
Jamie

Had the same issue. For me it required uninstalling the Intel Widi device from device manager. I think it was titled "wiusb" or something similar. It was in its own group in device manager. After uninstalling that, Lync would then
recognize my mic/speakers again.
I had the exact same problem as everyone else. I purchased two Dell Latitude E6530 laptops with Windows 7 Pro 64-bit. Both laptops had the issue. I uninstalled the WIUSB devices, restarted Lync, and Lync suddenly is able to detect devices...
I refreshed device manager to see if the devices would auto-install again... but there weren't detected again.
William Christenson
This worked for me as well. Uninstalled the WIUSB and WIUSB Host Controller which was present under its own group, Exit Lync process and started again, it detected the Sound Devices again. Definitely a driver conflict but it was quick resolution to uninstall
and get it working. No other issues with user as far as another device stopped working due to uninstallation of the devices.
It does not look like any driver conflicts, all other software detects audio device perfectly (Skype, Recorder,softphone, Lync 2010 etc.), but only Lync 2013 client keeps saying ""we didn't find an audio device". it appears the faulty in Lync 2013 client

How to Silently Install Lync 2013

Dears,
I would like to install Lync 2013 silently without manual installation for clients computers, I have lyncentry.exe basic software and I don't need to create OCT I wants use create new package and mention EXE file not MSI, during deployment in clients
computer Lync 2013 basic installation not install silently, please any recommendation and advice to solve this problem thanks...
Thanks..

Hi Dana.Kadi,
This may be helpful to you.
Lync 2013 Client - Silent Installation
http://social.technet.microsoft.com/Forums/lync/en-US/cf9ca58c-b9e8-465c-afb4-ed3992092f81/lync-2013-client-silent-installation
Hope it can be helpful.
Best regards,
Eric

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.

Need to uninstall Lync 2013

We download ProPlus 2013 through Office365 and we need to uninstall Lync 2013. It interferes with our phone system soft clients. Is this possible?

Hi mkirchner13,
You can remove Lync. You need to create a configuration.xml file and use the ExcludeApp element to list the programs to remove.
Here are the basic steps to exclude programs from an Office 365 ProPlus installation:
Download the Office Deployment Tool from the
Microsoft Download Center.
Use the Office Deployment Tool to
download Office 365 ProPlus to your local network.
Create a
configuration.xml file that lists which Office programs to exclude.
Use the Office Deployment Tool and your configuration.xml file to
deploy Office 365 ProPlus to your users’ computers.
For more details, please check out the following article,
https://technet.microsoft.com/en-in/library/dn745895.aspx?f=255&MSPPError=-2147217396
Best regards,
Eric

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

Lync 2013 client - part of Office 2013 Pro Plus - unable to edit or remove picture, option is grayed out.

Hi Team,
Lync 2013 client - part of Office 2013 Pro Plus - unable to edit or remove picture, option is grayed out.
Using Exchange 2010 Server and Lync 2010 Server at the back. To the best of my knowledge, this option is only available when using Exchange 2013 rather than Ex 2010.
Can somebody confirm this as I am not 100% sure about it.
Appreciate your help. Thanks
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

Hi,
The photo precedence in Lync 2013 is high-resolution photo from Exchange 2013 -> Photo from web address -> Active Directory photo. The "Edit or Remove Picture" button is available if you integrate Lync Server 2013 with Exchange 2013.
Since you are Lync server 2010 and Exchange 2010, you can choose the following two options:
The thumbnailPhoto attribute on the user's object in Active Directory Domain Services
A URL configured by the user
More details:
http://blogs.technet.com/b/nexthop/archive/2010/11/22/microsoft-lync-2010-photo-experience.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 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 Clients prompting repeatedly for credentials for calendar data from outlook

Our Exchange server had crashed recently (nothing major) and a reboot of the CAS server resolved the issues. However since then all our domain computers with Lync 2013 clients are prompting for credentials for calendar data from outlook. We would but in
our domain credentials but it still asks. It would sometime ask once a day or sometimes repeatedly throughout the day.
I have look on the forums and tried fixes that included: editing IIS Autodiscover and ESW to use NTLM first , rebuilt lyncs cache in app data etc and none seems to resolve the issue. Any help would be appreciated.
Note: Our Lync 2013 environment is internal only. Only users on domain computers can access the service. We do use a proxy server here for internet but I do not believe Lync is going through the proxy since its internal to our network only. This is NOT happing
to our users with the Lync 2010 client.

Please update your Lync client with the latest version.
You can check the following KB:
http://support.microsoft.com/kb/2825630/en-us
November 7, 2013 update for Lync 2013 fix the issue Proxy authentication dialog box appears when you sign in to Lync 2013.
Lisa Zheng
TechNet Community Support

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.

"Collect Logs Button" available in Lync 2013 client?

In the Lync 2010 client I was able to enable a "Collect Logs" button for gathering logs pertaining to voice quality.
http://blogs.technet.com/b/nexthop/archive/2010/12/10/collectlogs.aspx
I've looked everywhere and can't find any references for this option in the Lync 2013 client. Can anyone confirm if this has been removed from the 2013 client? Or are there different settings to turn it on for 2013 clients?

It is not listed in the Lync Server 2013 Client Policies, so I am afraid this feature is not there.
Lisa Zheng
TechNet Community Support

Silent Uninstall lync 2013 client

Similar Messages

Maybe you are looking for