It’s not greyed out, so if I change it to “Automatic configuration”, it accepts the change and stays there. However, it appears the setting is still in the MOC because when I click on ADVANCED, it’s still set for “manual configuration” with the old OCS FE server in the list. Now that we (finally) got the R2 client to work properly (working our way up to Lync 2010!!), I removed that GPO setting that forced “manual configuration” to our OCS FE server (ConfigurationMode = 1).
We used to have a GPO setup for the advanced settings in MOC. This seems like on oversight on Microsoft’s part, but maybe I’m just too dumb to find the appropriate configuration option to enable this feature… Other IM clients maintain what is essentially a continuous infinite history on a per-user basis, so that when I’m chatting with someone, I can scroll back to reference stuff that we talked about earlier in the day, yesterday, or any time in the past. The way Lync is working for me, at least, is that if I start a conversation with someone, then go off to a meeting and come back to my desk to resume the conversation, Lync has assumed that our conversation was finished, and therefore I have to go back into History to figure out where our conversation left off. This is probably a silly question, but do you know if there is any way to coerce Lync into maintaining a _single_ conversation for each user that you correspond with? This would be similar to how other IM clients work i.e., they tend to keep all conversation history lumped together under for each user that you chat with. Good idea, nothing a quick copy and paste into Excel can’t fix Of course, the best way to work with these is via PowerShell SuspendSoundWhenConversationWindowInForeground There are also the advanced connection settings under Lync User Client Registry keys are held under While some settings are provisioned in band for Lync, this is one you can edit in the Registry. This one just came up on Technet, How can I change the “Show Lync in foreground” Setting for all my users using GPO.
0 kommentar(er)
