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

Similar Messages

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.

Do we need License for Lync 2013 Edge server?

Hello Team,
We are currently running Lync 2013 Standard Edition Server. We are planning to enable users for External access and planning to deploly Lync 2013 edge server.
1. Do we need License for Lync 2013 Edge server?
2. Any other client licenses needed?
Please advise.

Hi,
No you don't required any additional License in order to install Lync Edge server. the only license required at OS level i mean windows server licence in terms of Lync concern you don't require any additional License
check this
https://products.office.com/en-us/lync/microsoft-lync-licensing-overview-lync-for-multiple-users
http://lyncuc.blogspot.in/2013/02/lync-2013-licensing-guide-how-to.html
And for client also you don't require any additional license with your existing client license will work for externally as well
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Uninstall Lync 2013 question

So I've tried building a new lync environment using sql mirroring and it looks like our DBAs didn't set up SQL correcty. Now I'm stuck at a point where my topology has been published and it won't connect to sql. I can't change the location either
because the SQL location is bound to the CMS. Since the Lync Front end service won't start, i'm having a hard time uninstalling the topology. I have 4 front end servers published in my topology but only tried installing on the 1st FE server.
Can I just wipe the OS and start over or what get thrown into AD that needs to get cleaned up?

Unfortunately we couldn't do much of anything. We tried to remove the enviornment via the topology builder, removing any other FE servers first, removing any confrencing (which also wouldn't go unless we used -force) and then tried to remove the environement
and publish. We got errors because I'm assuming it couldn't connect to sql in the first place and that the FE service wouldn't start.
We wound up wiping the server. We'll need to go in via ADSIEdit and clean up AD. The problem is that we have an OCS 2007R1 environment that is using the same objects.
Update:
We had a backup of AD before the schema was upgraded for Lync 2013. We mounted that backup and did a compare before/after install of lync. We then just deleted every object out of AD that was put in by Lync 2013. Hopefully that will be enough.
We'll find out when we try to reinstall again.

When replacing Labview 2013 with Labview 2014, do I firstly need to uninstall Labview 2013?

I have just recieved my latest version Labview 2014 CD.
When installing this new version, do I firstly need to uninstall previous Labview versions?
Solved!
Go to Solution.

Bob_Schor wrote:
The reverse, however, is not true. Once you install one version of LabVIEW, you cannot install an older version without uninstalling everything and "starting over". Be warned ...
Not exactly true. You can install just an older version of LabVIEW. I have had LabVIEW 2012, 2013, and 2014 installed on a computer and then installed 8.2.1. It is all of the support drivers and what not that do not install side-by-side. So the real lesson here is that if you install an older version of LabVIEW, pray that your current drivers support that version of LabVIEW. You will need to reinstall the drivers to install the support for the older version of LabVIEW though. Installing just the support takes hardly any time.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Lync 2013 Basic Client Silent Uninstall

When attempting a silent uninstall of Lync2013, I am getting the message "Are you sure you want to remove Microsoft Lync Basic 2013 from your computer?
We've noticed you have other Office products that will remain installed after you uninstall this product. We recommend you Repair these products from the Programs and features item in your Control Panel once you're done uninstalling."
If we select 'yes' to continue the uninstall, it completes successfully, but displays another prompt upon completion "Microsoft Lync Basic 2013 has been successfully uninstalled" and requires the user to click 'Close.'
The environment we wish to uninstall Lync 2013 from has other Office 2010 products installed, and the do not seem to be affected by allowing this uninstallation to run.
I am using a config.xml file <Display Level="none" CompletionNotice="no" SuppressModal="yes" NoCancel="yes" AcceptEula="yes" />
This config.xml works great for a silent installation, but how can I disable the 2 prompts during an uninstallation?

Hello
TCUSYSADM,
For silent removal of Lync Basic 2013 I'm using a batch file with the following commandline:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config c:\temp\config_uninstall_Lync_Basic.xml
Where c:\temp\config_uninstall_Lync_Basic.xml looks like this:
<Configuration Product="LYNCENTRY">
<Display Level="None" AcceptEULA="TRUE" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
</Configuration>
Start the batch file with the Run as Administartor option. Did not see any prompts.
Before this I tried to start the xml file from an UNC path, but that didn't work. So I copied the xml file to a local folder.

Lync 2013 SP1 64 bit crashes on Windows 7 Enterprise 64bit SP1

Systems Involved:
Dell OptiPlex 9020 All in One (080) –Crashes Lync 2013 64bit SP1
Dell OptiPlex 9020 All in One (081) –Crashes with Lync 2013 64bit SP1 -Working okay with 2010 so far
Dell OptiPlex 9020 All in One (083) –Clean install Seems to be working okay
Details of the problems
I have a put in place 2 Dell OptiPlex 9020 All in One’s both with network card Intel I217-LM.
The first system (080) I put place crashed several times before, I put a different new 9020AIO (083) that I created a new with clean install from disk of Windows 7 and Office 2013 64 bit with Lync 2013 64 bit upgraded to SP1. After having this
system side by side with the system that was crashing all the time and network capturing software installed on the new system this issue appeared to disappear. The user has not reported an issue with Lync 2013 in three to 4 weeks.
After thinking this was an issue with Office 2013-upgraded SP1. I decided to create a new image Windows 7 and Office 2013 64 bit SP1 intergraded .iso from web store. (Not upgraded) thinking there was something wrong with the SP 1 upgrade the way I intended
it to work. I reimaged the other 9020’s I have including the one (080) that was having the crashing issues.
The second system (081) is a new image I created, the system got some office updates from the WSUS it should not have been updated with and Lync 2013 was also crashing. I decided to reimage (080) a clean format with the new image. I put this system in
place for the user knowing it was clean install and not have any issue but for the last 2 weeks Lync 2013 has crashed.
I did take their old system back to my desk and was able to get it to crash as well. I decided to see if this problem was with Lync so I installed Lync 2010 I have not seen issue with 2010 yet.
I have also rolled out 2 Dell OptiPlex 7010 towers with the same image as above with no issues so it seems like this issue is only related to the 9020AIO.
Issue:
The computer will operate fine for most of the time but Lync 2013 will crash with not responding, please sign into Lync on the phone (Plantronics D540m). I get windows circle thing spinning and Lync is not responding if you close the
program it will try to run solution finder but there is not anything that will help. The only way to fix this issue is to reboot at this time. At first I thought it was the network driver issue for Intel I217-LM but after installing the usb network
adapter I believe the issue is something related to Lync 2013 SP1
Things I have tried
1. System Event : Application Log pulled I will include below in this message
2. 9020 with Intel I217-LM
3. Update driver version = to current version
4. Change power management settings as outlined http://en.community.dell.com/support-forums/desktop/f/3514/p/19523337/20460673.aspx
5. Disable Wireless and Bluetooth
6. Reset users Lync account
7. USB Network Adapter.
Event Logs:
1.The program lync.exe version 15.0.4569.1503 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1be4
Start Time: 01cf5a40e5452e63
Termination Time: 60000
Application Path: C:\Program Files\Microsoft Office\Office15\lync.exe
Report Id: 11c8f99b-c65d-11e3-b675-c4d98743ad3b
2. Fault bucket, type 0
Event Name: AppTermFailureEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Temp\WER3076.tmpatk.kdmp
C:\Windows\Temp\WER3077.tmp.appcompat.txt
C:\Windows\Temp\WER30A7.tmp.xml
C:\Windows\Temp\WER3125.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER3126.tmp.hdmp
C:\Windows\Temp\WER4208.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0a244260
Analysis symbol:
Rechecking for solution: 0
Report Id: f6cda468-d60a-11e3-a941-c4d98743ad3b
3. Fault bucket 24029667, type 22
Event Name: AppHangB1
Response: Not available
Cab Id: 0
Problem signature:
P1: lync.exe
P2: 15.0.4569.1503
P3: 52b0bd5c
P4: ac33
P5: 1
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\netid\AppData\Local\Temp\WERFA2A.tmp.appcompat.txt
C:\Users\netid\AppData\Local\Temp\WERFE21.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\netid\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_lync.exe_fe2cd4e98d389da9ae67bda6ac81af366f458bb6_11cc0947
Analysis symbol:
Rechecking for solution: 0
Report Id: ec8f9268-d60a-11e3-a941-c4d98743ad3b
Then I get about 10 Office Software Protection Platform before the above error logs occur.

Does the issue disappear when you uninstall the update?
If so, it seems that the Lync update is incompatible with your computer.
Please try to uninstall Lync 2013 SP1.
Lisa Zheng
TechNet Community Support

How do I enable users to attend on Lync 2013 meeting on Windows 2008 R2 Terminal Services/XenApp 6?

Hi,
We are not using Lync internally. But some of my users need to attend Lync 2013 meetings. We run a Windows 2008 R2 Terminal Services/XenApp environment. Users are not allowed to install applications.
In the past, I was able to install administratively a Lync 2010 attendee client.
How do I enable my users to attend a Lync 2013 meeting?
Thanks.

This is not viable. I don't know which user is going to be attending Lync meetings from suppliers or customers ahead of time and have no contacts to request a test meeting. This is a loop. How does Microsoft expect sysadmins to support their products if
the client software is not easily available.
At this point if I have a user who needs this, I will only know about it after the meeting has failed. At that point the user is not very receptive to the idea of involving his contact in troubleshooting and setting up test meetings. It's even worse if it's
an executive.
Is there any way of pre-installing the pre-requisites for attending Lync 2013 meetings?
My only choice is to inform my user community that we have no way of supporting Lync and request that they use GotoMeeting or WebEx with their contacts who try to do a Lync meeting.
I am very disappointed in Microsoft's approach with Lync 2013.
Thanks for your time.

I uninstalled Lync 2010 and it still launches. How do I uninstall it?

This is a weird one I know but I need to uninstall Lync 2010 on several laptops.
My process has been to uninstall it from add/remove programs. It seems to uninstall properly. Note that I think it is a click to run version of Lync.
However, on a reboot the program is still there and will launch. It no longer has a reference in Add/remove programs.
How can I uninstall it properly?

Hi,
Please check if Lync 2010 folder is still exist, if exist please delete manually.
Please also delete information about Lync 2010 (Communicator) in Registry Editor HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE.
Please also check if Lync 2010 software set to Startup, if set please disable it.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Activate Microsoft Lync 2013 basic to full version.

Hi,
In our customer environment around 5000 machines have been installed with LYNC 2013 Basic, however We have the licensed LYNC 2013 full version need to replace LYNC 2013 basic version What is the best way to achieve this.
Thanks in Advance.
Regards,
Madhan

Hi Tanders,
This is what you need to do:
1. Take that download and run lyncentry.exe /extract (when prompted, drop the files into a new folder)
2. Inside of the lyncentry.ww it creates, edit a file called "config.xml"
3. Change the "Display Level" Line to: <Display Level="None" CompletionNotice="No" SuppressModal="no" AcceptEula="Yes" />
4. Make sure to remove the  at the begiinning and end of the line.
5. Then, you are going to publish the setup.exe in the top level folder. You must upload the entire folder and its sub folders to Intune (there is a checkbox to upload all the subfolders as well)
6. When prompted to provide command line options, use: /config lyncentry.ww\config.xml
That should be it. It will completely unattended and silently.
Hope that helps.
Thanks,
Jon L. - MSFT - This posting is provided "AS IS" with no warranties and confers no rights.

Can't uninstall Exchange 2013 - (Distribution groups)

I need help uninstalling Exchange 2013. The uninstaller fails with these 2 errors:
This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue.
This computer is responsible for expanding the membership of 1 dynamic distribution groups. These groups must be reassigned to another server before Setup can continue.
I've gone so far as to disabling all distribution groups which removes its email properties and the uninstaller still fails.
This is what happens in the eventlog:
System.Management.Automation.ParseException: At line:1 char:67
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+ ~~~~~~~~~~~~~
Unexpected token 's-Hertogenbosch/ou=Exchange' in expression or statement.
At line:1 char:175
+ ... s/cn=CADEXCDB13'}
+ ~~
The string is missing the terminator: '.
At line:1 char:38
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+ ~
Missing closing '}' in statement block.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
] [ParentValue:"<NULL>"] [Thread:11] [Duration:00:00:00.0156248]
I'm sure what happens here is the powershell commands looking at the distribution groups fail, because of our city name ('s-Hertogenbosch). Because of the apostrophe, the parameter is not passed successfully of this legacyExchangeDN. As this check fails,
I believe the readiness check fails on these steps.
This legacy administrative group name is still left from a 2003 -> 2010 -> 2013 migration.
I've opened a Microsoft support request for this last week, but I thought someone might have dealt with this? I want to do a clean uninstall if possible.

After I removed the distribution groups, I did restart the server.
The problem is the the powershell script to check for existing distribution groups use a single quote to pass the server name to it. The server name contains a single quote itself so the parameter is not passed successfully. If the powershell script
used a double quote it would pass the parameter correctly.
This works:
Get-DistributionGroup | where ExpansionServer -eq "/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13"
This does not work:
Get-DistributionGroup | where ExpansionServer -eq '/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13'
Do you see the difference? (Parameter is passed in a single or double quotation)

How to remove OCS and install lync 2013 on MS Office 2007 and 2010

Hi,
We need to install lync 2013 on our systems having office 2007 and 2010 via SCCM 2012.
Please suggest.
Regards, Syed Fahad Ali

Lync 2013 no longer has its own installer, but instead uses the Office installer. You can create a customized installation and deploy it just like you do with Office:
http://technet.microsoft.com/en-us/library/jj204827.aspx
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Lync 2013 Test Server Deployment

Hi All,
I have been asked to look at using Lync 2013 in our organisation.
As this is a test deployment to start with, I have the following restrictions:
Access to only 1 public IP Address
Mobility is a requirment
No budget for Reverse Proxy
I have been looking at various ways to test this, but have been unable to successfully get this working. I have started again, with a blank canvis. I am now at the stage where I need to install Lync 2013 on our test domain and am not sure where to go.
I have read about external DNS (A Record for sip.domain.co.uk to point to public IP & SVR Record for _sipfederationtls._tcp.domain.co.uk points to sip.domain.co.uk on port 5061).
Could anyone give me any pointers?
Thanks in advance

Hi Daymondeo,
As thamaraw said, the Reverse Proxy is required for functioning mobility.
With one public IP, you have to deploy TMG . Using TMG as a reverse proxy, then you can have all the Lync features.
Have a look at this article,
http://social.technet.microsoft.com/wiki/contents/articles/9807.how-to-configure-forefront-tmg-2010-as-reverse-proxy-for-lync-server-2010.aspx
Best regards,
Eric

Lync 2013 & Skype Integration 3rd Party Cert. Requirement

hi to all
I am a liitle bit confused about the Trusted Certificate (public certificate) need for the Lync 2013 server and Skype integration.
Our problem is trying to Integrate Skype with our Lync 2013. We configured Lync Edge and Lync Backendserver with internal Certification Authority Certifcates ,we finished provisioning Lync 2013 with Skype according to the "http://www.microsoft.ctom/en-us/download/details.aspx?id=39071"
document and we received answer from Microsoft that we ıntegration is finished.
But we could not make any call or add contacts either from Skype no Lync client.
Some forums say that we had to integrate Trusted Certificates to our Lync Edge server (http://social.technet.microsoft.com/Forums/lync/en-US/ec3142cb-179a-427d-909c-135052621043/how-to-deploy-the-federation-with-skype?forum=ocsmobility)
But I could not see in official documents.Can someone lead me the correct way to do this ?
Thanks

You will need to change the external Edge certificate to a public issued UC/SAN certificate. Without a public cert the remote party (in this case the MSN/Skype servers) won't be able to establish trust and will fail.
You can do this by re-running the Lync Deployment Tool & Request/Assign Certificates
Here is a walk through:
http://www.digicert.com/csr-creation-lync-2013.htm
http://www.digicert.com/ssl-certificate-installation-lync-2013.htm
Because you are replacing, you will need to restart your Edge services afterwards for it to take effect (You can use Lync Management Shell and run Stop-CsWindowsService & Start-CsWindowsService)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

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

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

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

Need to uninstall Lync 2013

Similar Messages

Maybe you are looking for