App-V 5.0 SP1 and Outlook and Lync 2013

I am trying to sequence Outlook 2013 with App-V 5.0 SP1 but have run into an issue with using the virtualized package of Outlook 2013. When I try and open the application I get the following error:
Error: Cannot start Microsoft Outlook. Cannot initialize Microsoft shared utilities. Restart or reinstall Microsoft Outlook.
I am running the package locally and it has been published globally.
It seems as if the package is missing something. Any help would be appreciated.

I wasn't at first and that is possibly why I was getting that error. I have been trying to unsuccessfully today to use the Office 365 click to run.
I downloaded the click to run setup files. and now I'm trying to create the package.
Command Line to create the package: c:\setup.exe /packager C:\configuration.xml c:\package
I think the problem is with my config file:
<Configuration>





</Configuration>
when ever i try and run the Packager I get this error:
Windows cannot find 'C:\users....\Clientx86\integratedoffice.exe'. Make sure you typed the name correctly, and then try again.
I am pretty certain that my SourcePath is wrong. but what do i point it at?

Similar Messages

Office 2010 and Lync 2013 installed caused Powerpoint to become corrupted from internet sources

I'm finding that we're having problems with Office 2010 and Lync 2013.
Our environment is setup as follows:
Operating system: Windows 7 Enterprise
Office: Office 2010 (Word, Excel , Powerpoint, Access etc)
Office 2013 (Only Lync has been installed for 2013)
Problem: The issue is that when any Powerpoint documents come from internet sources (Such as Outlook or downloading directly from an internet browser), attachment manager deems the Powerpoint a security risk. When you open the Powerpoint it states that it's
corrupt and needs to be repaired, when you try repairing the powerpoint, it says it's not going to be possible.
The only workaround is right clicking the power point in explorer and clicking properties, there's then a security prompt at the bottom of the dialog box and an option to "Unblock".
The temporary fix: The fix is to remove Lync 2013 and the power point presentation open correctly from Internet sources.
Attempted:
I've attempted the following:
- Build a laptop with a plain version of Windows 7 enterprise
- Install Office 2010 Professional
- Test powerpoints from internet sources (Working)
- Install Lync 2013
- Test powerpoints from internet sources (Same error)
Any ideas?

Just to let you know that switching off protected view in Powerpoint for files originating from internet sources and Outlook attachments is a workaround for the issue.
I would be cautious about switching off Protected view though, here's a good article explaining the inner workings of Protected view:
http://blogs.technet.com/b/office2010/archive/2009/08/13/protected-view-in-office-2010.aspx
Concerning this problem, I also noticed that after removing Office 2013 and starting Powerpoint, a MSIEXEC instance is started.
Presumably some DLLs are missing or some registry keys are missing when installed with Lync/Office 2013.
I also went to the trouble of snap shotting the registry and using Procmon to see what gets loaded and added when Powerpoint repairs itself on first start after removing Office 2013.
Unfortunately there are a number of things which change and couldn't be changed on the Office 2010 and Lync 2013 setup to fix the problem.
My advice would be the following:
- Update to Office 2013 fully
- Downgrade to Office 2010 Lync
- Switch off protected view

Lync 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Cisco VCS/Codian MCU and Lync 2013 integration

Hi,
I would like to know if Lync 2013 is supported to work with:
- Cisco Tandberg VCS version x6.1
- Cisco Codian 4.1 (comp. 6.16)
Is it necessary to update both devices to be supported/homologated/qualified?
Thanks

Hi, Kent ... From what I'm seeing so far the challenges of integrating Cisco/Tandberg equipment and Lync 2013 are the same as what you may have already encountered with Lync 2010. Since the Cisco endpoints and MCU cannot register directly to Lync 2010
or 2013, you will need to leverage the VCS systems as your SIP gateway between them and Lync clients. In Lync 2010 there were limitations as to the interoperability of the H.263/264 codec used by Cisco gear and the RTV codec that Lync was restricted
to, and we often experienced frozen video feeds from Lync clients or an inability to connect to individual Cisco endpoints or conferences hosted by the Codian MCU. Even though Lync 2013 will use H.264 as a codec for the video stream, I anticipate there
will still be challenges interconnecting through the VCS as well as providing content between Lync and Cisco endpoints. However, I expect an increase in the video quality since Lync 2013 supports higher resolutions and also uses a non-proprietary codec.
I expect content to still be unreliable for the Lync participant, even when using a Codian MCU.
You will still need to setup your VCS with a separate Neighbor zone for the Lync 2013 server just as you did for Lync 2010. I wouldn't hold my breath for Cisco to update the VCS software to accomodate the specific needs of Lync 2013, but at least the
VCS will get the correct video codec and connect your call. I don't know about you but I had to put my Cisco units and MCU into a separate SIP domain from the Lync pool, and then create a static route for the Cisco SIP domain on the Lync 2010 front-end
server. I expect to do the same in Lync 2013.
Ideally, Microsoft and Cisco would agree that SIP is SIP, and whether an endpoint registers with VCS, UCM or Lync shouldn't be relevant. Alas, it'll be a long, long time before that is true, certainly not as long as Microsoft and Polycom have
such a tight bond. I plan on implementing Lync 2013 in the next few months and will gladly post any progress here. At this point my plan is to simply mirror the static route and configuration I have with Lync 2010. My VCS and Codian units
are running software versions just a little ahead of yours and work fine.
Good luck!

Unknown Presence in Lync 2010 and Lync 2013 co-existence

I have lync 2010 and lync 2013 in my environment. Everything was working fine except when I moved the DNS of the Lync 2013 pool to the load balancer. When I did that, users on lync2013 could see the presence of users on Lync2010 pool but not vice versa.
I have point the Lyncdiscoverinternal.domain.com to the lync2013 pool DNS. I have opened migration ports on the load balancer but still not working. It works perfectly fine if I point the DNS of the pool to one server directly without going
through the Load balancer VIP.
Am I missing anything here?
Thanks!
Alert from TechNet Posting

Hi Kojo Obeng Antwi,
Please check out the following information.
Deploying DNS load balancing on Front End pools requires you to perform a couple of extra steps with FQDNs and DNS
records.
A pool that uses DNS load balancing must have two FQDNs: the regular pool FQDN that is used by DNS load balancing (such as pool01.contoso.com), and resolves to the physical
IPs of the servers in the pool, and another FQDN for the pool’s Web services (such as web01.contoso.com), which resolves to virtual IP address of the pool.
In Topology Builder, if you want to deploy DNS load balancing for a pool, to create this extra FQDN for the pool’s Web services
you must select the Override internal Web Services pool FQDN check box and type the FQDN, in the Specify the Web Services URLs for this Pool page.
To support the FQDN used by DNS load balancing, you must provision DNS to resolve the pool FQDN (such as pool01.contoso.com) to the IP addresses of all the servers in the pool
(for example, 192.168.1.1, 192.168.1.2, and so on). You should include only the IP addresses of servers that are currently deployed.
Best regards,
Eric

Co-Existence Lync 2010 and Lync 2013

Hi,
How do we check that CMS is moved from lync 2010 to Lync 2013 in Co-Existance environment lync standard edition.
I know that users are moved form Lync 2010 to Lync 2013 but i don't if CMS is moved? And in the existing co-existence we have two edge servers Lync 2010 and Lync 2013. How can i check if traffic is routing through Lync 2010 or lync 2013.
Because we want to Decommission the Lync 2010 STD Edition before doing this i want to make sure every thing go smooth.
Please help me on this.
Thanks
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

To find out if the CMS is moved:
Get-CsConfigurationStoreLocation, if it's a standard server it will tell you the pool name. If it's an Enterprise server, it will tell you the SQL server name associated with the pool.
http://technet.microsoft.com/en-us/library/gg412814.aspx
Otherwise it's at the top of the topology builder (the top top part that says Lync Server in the left pane, under the Central Management Server spot in the right pane.
For a full decommission article, here's a decent one with screenshots. As Ben said, if you can advise about the other places we could be more specific.
http://www.oiboran.com/?p=1073
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

App-V 5.0 SP2 and Office 2013 Publishing Problem

Hi
I have a big problem with app-v 5.0 and Office 2013, the thing is that I have published it globally to a RDS servers in my farm and I have 4 different configuration xml's to publsih the package. I'm also using app-locker to prevent the users that are not supposed
to have the package doesn't get it published. That is working fine.
The default configuration xml is to publish the package to the computer with Excel, Word, Outlook, Powerpoint, onenote and Publisher and create shortcuts to All Programs.
I have 1 user configuration xml to a group (group 1) that has the default configuration but including 3 shortcuts to the desktop, Excel, Word and Outlook. I have another user configuration xml to group 2 that has all the application and all the shortcuts in
Office 2013 Pro and 4 shortcuts to the desktop. I have 1 user configuration xml for Excel only and another one for Word only.
This has been working well for 2-3 days but now users are getting error "The application failed to launch. The application belongs to a packages or a connection group that is scheduled to be unpublished. Error code: 0xA7E0E502-00000516".
And the Office 2013 is pending to unpublish globally on all servers even though no one has done anything except log in or log out.
What am I doing wrong, there are no connection groups on the app-v server but there where 2 or 3 long time ago and have been deleted.
Kind Regards
Kristján R. Halldórsson
Best Regards Kristjan R. Halldorsson

I ran the get-appvclientconnectiongroup -all on my servers and there where none listed.
I have also enabled the Virtualization Subsystem debuglog on the client and I'm not finding any error that might relate to this problem.
The thing is I had a group policy enabled that said Enable Global Refresh on Logon = true but I changed that to false and published the package again globally and I'm just waiting now to see if the package goes to unpublish state as it did before.
Best Regards Kristjan R. Halldorsson

Outlook 2013 and Lync 2013 suddenly cannot run at the same time

We recently switched to Office 365 and up until this month's Tuesday Patch Day, everything was working great. As soon as I installed the patches from 3/12/2013. Ever since then I've had the following issue:
Launch Outlook 2013
Launch Lync 2013
Get the following dialog box: "Outlook Data File: The file <filename> is in use and cannot be accessed. Close any application that is using this file, and then try again. You might need to restart your computer."
Click Ok to dismiss the dialog box. Everything seems to function normally.
About three minutes later I get the following dialog box: "We're sorry, but Outlook has run into an error that is preventing it from working correctly. Outlook will need to be closed as a result. Would you like us to repair now?"
Click Close. Everything seems to function normally.
Steps taken to attempt to a fix:
I deleted the Outlook profile and recreated it from scratch. No improvement.
I rebooted the machine. No improvement.
I repaired the Outlook data file. No improvement.
Other notes:
If I start Outlook 2013 by itself, it works fine and no dialog boxes.
If I start Lync 2013 by itself, it works fine and no dialog boxes.

Hi all,
I had the same problem as the original poster, and I fixed it using the method I'm about to describe. First, let me state that I am using a volume-license version of Office 2013 Standard, installed the conventional way ... we are not using the desktop
apps available with Office 365 plans E3+E4 or "Midsize Business".
I had originally installed Lync 2013 using a 'streaming' installer that you find by logging into the Office 365 Portal site -> Office 365 Settings -> Software -> Lync -> Install.
That installer does not work with the version of Office 2013 I'm using. I uninstalled Lync, and reinstalled using the links below:
(32-bit):
http://www.microsoft.com/en-us/download/details.aspx?id=35451
(64-bit):
http://www.microsoft.com/en-us/download/details.aspx?id=35450
The version of Lync that you choose (32-bit or 64-bit) has to match the version of Office 2013 you already have installed. Upon installing the 64-bit version of Lync at the URL above, the error message "Outlook
Data File: The file <filename> is in use and cannot be accessed." disappeared and Outlook and Lync now happily cooperate.

Forefront 2010 dening outlook 2013 and lync 2013 access to ther server

we have currently, forefront TMG 2010, exchange server 2010 and lync 2010, running on our network and every working fine but recently i upgraded client MS Office 2010 to MS Office 2013 and suddenly forefront TMG 2010 started denying lync 2013 and outlook
2013 access to the server.
Please can somebody tell me how to resolve this problem.

Hi，
Thank you for your post here.
Do you mean that you have published exchange server 2010 and lync 2010 via TMG?
How dou you judge that TMG blocks your traffic?
Please check if there is any error information via TMG live logging.
You can try to delete publish rule and reconfigure it.
Best Regards
Quan Gu

Issues with Hosted Exchange, UM and Lync 2013.

Hello everyone!
I am trying to deploy UM with Office 365 Hosted Exchange. We are using one Lync 2013 Standard Edition FE and have deployed one edge server. We have set up our firewall to host the Reverse Proxy.
We do not use wildcard certs. External DNS resolves the _sipfederation and sip._tls SRV records to the external face of the edge server. The edge server functions as it should for remote users and mobility.
I have tried to follow these instructions to the letter three times over to no avail.
http://y0av.me/2014/01/07/lyncum365/
Neither Snooper or Event Viewer show any particular issue, though when I try to dial out to voice mail I will get one to two rings and then 5 seconds of silence a fast busy, and finally "Call Unsuccessful".
When checking the firewall logs I notice a seemingly random 10.x.x.x address being sent to the firewall by the external leg of the edge server. Wireshark captures it as STUN packets on port 3478 being sent to port 3478. These are being dropped by our firewall.
I believe them to be RTP packets but I do not know if this is normal behavior. Has anyone any ideas?

My mistake. Here is the snooper result.
TL_INFO(TF_PROTOCOL) [edge\edge]0C4C.05E4::06/18/2014-15:43:34.153.0000000C (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [3770767507]
Trace-Correlation-Id: 3770767507
Instance-Id: 2E5A
Direction: incoming;source="external edge";destination="internal edge"
Peer: exap.um.outlook.com:5061
Message-Type: response
Start-Line: SIP/2.0 488 Compression algorithm refused
From: sip:sip.domain.net;tag=08FB9ED133BA396696FE6546EA6F3031
To: sip:exap.um.outlook.com;tag=B8FFE4E9267ED6ECB78ADCC60126B53F
Call-ID: 66602CE1F9980BFA94AD
CSeq: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.11.11.23:50752;branch=z9hG4bK2132316E.5B3AF52DE2753A36;branched=FALSE;received=207.46.5.9;ms-received-port=50752;ms-received-cid=60172700
Content-Length: 0
Server: RTC/5.0
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000D (SIPStack,NegotiateLogic::SetCompressionType:NegotiateLogic.cpp(2701)) [559249495]( 00000079B1274FB8 ) Compression type is now CompOff
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000E (SIPStack,NegotiateLogic::ProcessCompressionResponse:NegotiateLogic.cpp(2217)) [559249495]( 00000079B1274FB8 ) Peer refused [488] our request for compression
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000F (SIPStack,NegotiateLogic::AdvanceOutboundNegotiation:NegotiateLogic.cpp(910)) [559249495]( 00000079B1274FB8 ) Outbound negotiation sequence is complete
$$end_record
And finally..
TL_INFO(TF_PROTOCOL) [edge\edge0C4C.05E4::06/18/2014-15:43:49.379.0000002E (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [962697980]
Trace-Correlation-Id: 962697980
Instance-Id: 2E61
Direction: incoming;source="internal edge";destination="external edge"
Peer: fe1.domain.net:61254
Message-Type: request
Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;transport=Tls;ms-fe=CO1PR02MB111.namprd02.prod.outlook.com SIP/2.0
From: <sip:[email protected]>;tag=b736386270;epid=9bcee72318
To: <sip:[email protected];opaque=app:voicemail>;tag=eced411395;epid=07C3F2A933
Call-ID: 4266a095bdef8280d67c7e7df58446fc
CSeq: 2 BYE
Via: SIP/2.0/TLS 10.10.10.25:61254;branch=z9hG4bKC848F11A.A88BCA6858661A50;branched=FALSE
Via: SIP/2.0/TLS 10.10.10.125:49156;ms-received-port=49156;ms-received-cid=401200
Route: <sip:edge.domain.net:5061;transport=tls;opaque=state:Si;lr>
Route: <sip:exap.um.outlook.com:5061;transport=tls;epid=07C3F2A933;lr;ms-key-info=AAEAARc45bIQE6UJAYvPAR8eV4QTvCH3EE2Kxtie7I2PMCSj-2aArKHP8dStYlJe-9jphIkz_mDEkCD_v8hY-mghQEHD6-F12E7E14YG-TJ2gEcQE0Bx2r_rDB3LrzRZzgQ0WVvxreLPWGI80elWF-xfbc_X3JE8mOR2OB9KQM8-e9WOjfq2kj6CnDGeL0yzgz4OB8zm-ao03Yo4gMZ-BpwaxC3BNuvvVDJo9wqrYftq_Z3MIVewWrqcDt5Td4vxCsMiXdwEqtEIRKVvQoqboleBJAyQl-C3qGgfEoSkUnApFuTSnQYRa4kbZ1iPaACpdKT-VTQGjc9HXfps48YJCsIXW0Ab_NSM2uvhUyw900men1ukXSmoZoWZbwqe5siuWVUcFoQl1h1Jcy4lCyZUfDZoqPzDioLqTk9iUmS8fa-PAJjsq72yGjVB_y1aJSxtHVsw7MiDqOGOPqT3dmF-sINkeyuokCy8UCf_cQHmEHwVzZLUJqaVccr3QNCLsBzhcWSypnC60ZZphOKuwl6RvUXWICPf0ubLTL2ppC3tWEgFdUUWOPVd84uGlMcqRLKGb1qrmpj8Nu6Lte7t5n2pMEBCfgAe79t4GO0C5KScdKT_XBM1iIBRXdNkPKHfSgC-wPQgRikdw7vRD-hOWlN5Lay7-zkQ4Ag6rauszFTAwbft99OieAOxKIsgYcxXxcG6;ms-route-sig=fiEMuzbN4_PyEz_I5gG3g8FtqNAonwgZCoRnOq-ByfYEtywTZp-Hk_eAAA>
Max-Forwards: 69
Content-Length: 0
ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";CallerMediaDebug="audio:ICEWarn=0x40003a0,LocalSite=10.10.10.125:6735,LocalMR=10.11.11.23:51430,RemoteSite=10.27.46.15:5286,RemoteMR=207.46.5.80:54106,PortRange=1025:65000,LocalMRTCPPort=51430,RemoteMRTCPPort=54106,LocalLocation=2,RemoteLocation=2,FederationType=0"
$$end_record

Lync 2011 for MAC and Lync 2013 Server Std

Hello,
We are using a Lync 2013 Std (single-server) as a POC. It works fine for Windows-clients but I cannot connect using Lync 2011 for MAC from any MAC machine.
Using automatic configuration, I cannot connect to the Lync server.
Using manual configuration (I tried putting in just the server name and adding port 5061 to it, both to no avail) I keep getting 'Sign in to Lync failed. Please verify your credentials and try again.'.
Lync server is on the latest CU version with all components, MAC clients are on update 140321.
I noticed that Lync tries to create the OC_keycontainer_username@domain, but it seems not te be created. It flashes by and disappears again when the client fails to login. I have imported the Lync server certificate, issued by our windows 2012
root CA, on the Mac clients and have stored it in the 'Login' container.
Does anybody know if Lync2011 for Mac is supported for use with Lync server 2013 Std?
Cheers

Hi,
To clear cached data and corrupted certificates in Lync, you can do the following steps:
First, delete the following folders:
Users/Home Folder/Library/Caches/com.microsoft.Lync
Users/Home Folder/Documents/Microsoft User Data/Microsoft Lync History
Then, delete any corrupted or cached certificates. To do this, follow these steps:
1. Open the Keychain Access certificate management utility. To do this, in Finder, click Applications, click Utilities, and then click Keychain Access. Or, search for Keychain Access by using Spotlight.
2. In the left pane, click login, and then click Certificates.
3. In the right pane, find a certificate that's named Unknown or Communications Server, select it, and then delete it.
Note: You may have to unlock your keychain by using your password.
4. Close Keychain Access.
5. Restart Lync for Mac.
You can refer to Lync Mac for Lync Server online, but similar for Lync on-premises:
http://support.microsoft.com/kb/2629861
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Cisco Call Manager 8.5 and Lync 2013

Dear all,
Our customer wants to integrate their Lync 2013 to the Cisco Call Manager 8.5.
Out of some not so recent information i thought that if u want to use the enterprise voice of lync you'll have to make a sip trunk between Cisco Call Manager & Lync 2013.
I think that this still counts, i've also heard that there have been a moderate amount of changes between cucm 8.5 and cucm 8.6 on matters of sip.
I'm unable to find them though, also what does CUCI - Lync do?
Kr,
Yannick Vranckx

Hi Yannick,
There can be three types of integrations between Lync and Cisco Systems
1) Direct SIP Trunk between Lync Server and Call Manager - In this, we can setup shared line between Cisco extensions and Lync extensions, and Sip trunk between the servers. Any Cisco phone / Lync client can call each other vice-versa. Initial setup needs planning, but later it does not need much configurations in client side. The following document explains the configurations needed.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0B36AC1_00_cisco-uc-integration-for-microsoft.pdf
2) CUCILYNC, which is like Cisco Jabber client but connects with Lync and Call Manager: Lync Client <----> CUCILYNC <-----> CUCM
In this option, a plug-in is installed in each client side. Although initial configurations is easier, each user needs to install the client and operate it. The below document explains the configuration and setup.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0545A41_00_cisco-uc-integration-for-microsoft.html
3) RCC (Remote Call Plugin) which just provides basic call control feature but for that you need Cisco Unified Presence Server: Lync Client <----> CUPS <-----> CUCM
HTH
Manish

Mac Lync 2011 and Lync 2013 - Autodiscovery not working

We're currently setting up a Lync 2013 topology including Front End Pool and Edge Server. I've been told that the Lync 2011 client should work with lyncdiscover and lyncdiscoverinternal as it does for IOS and Windows.
However looking at the logs being generated by the Lync 2011 client this doesn't seem to be the case. I'm seeing
sipinternal, sip, sipexternal when Lync 2011 is set to AutoConfigure. I do not have any of these configured.
If I manually specify lyncdiscover and lyncdiscoverinternal the logs show it's starting to find the Front End Servers, but still errors.
What am I doing wrong?

Hi,
Please add the following SRV records in internal DNS Server:
_sipinternaltls._tcp.sipdomain.com
_sipinternal._tcp.sipdomain.com
_sip._tls.sipdmain.com
Then flush the DNS cache on the local Mac computer, then test the issue again.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Replication issue between lync 2010 FE and lync 2013 FE

Hello
I face any issue in my lync server's .
I was in the last steps in the migration process from lync 2010 to 2013 enterprise edition .
where CMS was moved already to 2013 , and later on many time I checked the replication and it was fine , then I deleted the CMS DB FROM 2010 FE and I checked the replication and it was fine .
later on I proceed to delete the archiving server and monitoring server and it was fine .
later on I proceed to
Reset call admission control
Prevent sessions for services
Stop Lync Server 2010 services
Remove a Front End Server from a pool
I just I face this replication issue after I start the process to delete the lync 2010 pool which im stuck on it now .
one more thing while I was trying to delete the 2010 front end pool , I got the error .
Error: An error occurred: "System.InvalidOperationException" "Cannot publish topology changes. Conference directories still exist on a pool that would be deleted. Remove the conference directories before continuing."
so I moved the conference directories from 2010 pool to the 2013 pool successfully.
but later on when I check the replication I notice the replication issue ?
Get-CsManagementStoreReplicationStatus
UpToDate           : False         """""""""""""""""""it is already shutdown
ReplicaFqdn        : HQ-EDGE01.mydom
LastStatusReport   :
LastUpdateCreation : 3/23/2015 11:22:17 AM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydom
LastStatusReport   : 3/19/2015 5:21:27 PM
LastUpdateCreation : 3/19/2015 5:21:25 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydom
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 11:52:17 AM
ProductVersion     : 4.0.7577.0
then I run the
I run Invoke-CsManagementStoreReplication
Get-CsManagementStoreReplicationStatus
UpToDate           : False     """""""""""""""""""it is already shutdown """"""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 4.0.7577.0
====================
Get-CsManagementStoreReplicationStatus
UpToDate           : False """"""""""""""" it is already down """""""""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     : 4.0.7577.0
why LastUpdateCreation : 3/23/2015 10:53:23 PM from the lync 2010 pool ????
I'm not doing any change on 2010 pool now (I just try to delete it ) , all the change it is on 2013 pool .
for edge server 2013 I shut down the server since there is another configuration issue there (so replication to edge server not the issue now since it is down).
my question is this will affect my lync 2013 since it is the production now ? is this un completed steps for removing the 2010 pool affect my production.
is the replication issue affects my 2013 pool ?
Kind Regards
MK

Hi,
From your description above, did you mean before deleting the Lync Server 2010 Pool from topology, you found the replication of Lync 2010 FE Server not update to date?
If it is the case, based on my knowledge, there is no affect for Lync Server 2013 Pool. Please double check if Lync Server 2013 Pool work normally, and Lync users in Lync 2013 Pool can use all Lync function without issues. Then you can delete Lync 2010 Pool
from Topology and publish it. After finish it, please re-run step 2 on Lync Server 2013 FE Servers.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

App-V 5.0 SP1 and Outlook and Lync 2013

Similar Messages

Maybe you are looking for