MS Lync 2011

Hi Noah-

We've run into the same problem with Lync on Lion. Though fortunately Lion is in limited use here so it's not widespread (yet). I don't know of a way to remove the item because it's not a valid keychain item. If it were, you could easily do a look up by a fingerprint and then kill it. But without that info…

j
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

Just got this from our Microsoft guy...no more than 5 minutes ago. Once downloaded through the auto updater it can be pulled from ~/library/caches/TemporaryItems/

I'm testing with this now.
Lync for Mac update now available<http://blog.officeformac.com/lync_for_mac_update_now_available/>
by Office for Mac Team on October 21st, 2011 in Announcements<http://blog.officeformac.com/category/announcements/>, Lync for Mac<http://blog.officeformac.com/category/lync-for-mac/>
Hey everyone,
A quick update to the earlier post<http://blog.officeformac.com/lync_mac_osx1072/> about Lync running on Lion.
The Lync for Mac 14.0.1 update is now available from Microsoft AutoUpdate.
To use AutoUpdate, start Microsoft Lync or another Microsoft Office application, and then on the Help menu, click Check for Updates.
The Lync for Mac 14.0.1 update fixes problems associated with sign-in on Mac OS X 10.7.2 Lion, and also improves support for Office 365.
For more information about Lync, check out Lync Help<http://mac2.microsoft.com/help/office/14/en-us/lync/>.
http://blog.officeformac.com/lync_for_mac_update_now_available/

Sweet
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

I can't even get Lync to work.

Communicator 2011 auto-setups (once cert installed).

Any trickery needed to get the client working?

Regards,

Ben.

I had a few issues installing on an existing system. I used a fresh build and captured in Composer. After that every machine I pushed to worked flawlessly so I’m not 100% sure what my issue was.

Have you tried:
Installer –verbose –pkg <path to pkg> -target /

You might get a better idea?

Ahh. I installed the pkg on an existing mac with communicator.

Will try a new mac then tomorrow.

Hmm... If that works I'll have fun with the 130ish macs I manage that have communicator installed.

Regards,

Ben.

Got Lync logging in.

I needed to deploy the Lync cert whereas with Communicator our root cert was fine.

Also auto discovery of the Lync server fails, address book lookup fails & as such so does user images.

As the Lync site is down, any other good support resources?

Regards,

Ben.

Not that I found. Auto discovery worked great for me and I didn’t have any issues getting it to connect (at least once Microsoft delivered the hotfix). As always, google was my fried for those issues.

Hi Noah,

Do you have a proxy (non-authenticated or otherwise) in your environment?

Regards,

Ben.

We have an auto configuration pac file. It does require authentication.

thanks.. strangely according to the below it shouldn't work!

http://mac2.microsoft.com/help/office/14/en-us/lync/item/6009fb38-bf71-46aa-8aeb-2eccefe486d7?category=97986ed6-bbea-4837-a6be-57acfe1bb0ef

Lync does not support proxies that require authentications If your proxy server requires a password, you cannot sign in to Lync. Contact your administrator.

Just an update.. Our lync server was restarted as it had a new cert applied.. & had some updates applied.. once it was brought back up images & search worked :)

Auto discover still isn't.. but my lync admin advised it's a known issue for some environments & so we're awaiting the next version.

We have Lync running. We had an issue with Juniper VPN but a internal update from MS fixed that. I bundled our root and chain cert and all was well with kerberos authentication.

Has anyone got the MCX portions to work??? I can't get serveraddressinternal or serveraddressexternal from local machine to work and its starting to make me go insane!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Backward_Compatible_Version</key>
    <integer>1</integer>
    <key>Current_Version</key>
    <integer>1</integer>
    <key>hkey_local_machine</key>
    <string>&lt;&lt;MacRegNoValue&gt;&gt;</string>
    <key>hkey_local_machinesoftware</key>
    <string>&lt;&lt;MacRegNoValue&gt;&gt;</string>
    <key>hkey_local_machinesoftwarepolicies</key>
    <string>&lt;&lt;MacRegNoValue&gt;&gt;</string>
    <key>hkey_local_machinesoftwarepoliciesmicrosoft</key>
    <string>&lt;&lt;MacRegNoValue&gt;&gt;</string>
    <key>hkey_local_machinesoftwarepoliciesmicrosoftcommunicator</key>
    <string>&lt;&lt;MacRegNoValue&gt;&gt;</string>
    <key>hkey_local_machinesoftwarepoliciesmicrosoftcommunicatordisableservercheck</key>
    <integer>1</integer>
    <key>hkey_local_machinesoftwarepoliciesmicrosoftcommunicatorconfigurationmode</key>
    <integer>1</integer>
    <key>hkey_local_machinesoftwarepoliciesmicrosoftcommunicatorconfigurationmodeserveraddressinternal</key>
    <string>mycompany.com</string>
    <key>hkey_local_machinesoftwarepoliciesmicrosoftcommunicatorconfigurationmodeserveraddressexternal</key>
    <string>mycompany.com</string>
</dict>
</plist>

I was just working on this yesterday. I ended up including a customized MicrosoftLyncRegistrationDB file that is being pushed to each user's ~/Library/Preferences/ByHost folder.

I tried Microsoft's suggestion of a master DB file put into /Library/Preferences but the client application seemed to ignore it.

Thats not what I wanted to hear. I hate having to do byhost entries for something like this. I noticed that the configurationmode key actually works. If I change it from 0-1 etc. it will change the radio button from auto to manual it just won't follow the settings. I still find it odd that the keys are named communicator and not lync. Anyone else get the master DB local machine entry to work???

Just noticed that Microsoft released Communicator 13.1.3 a week ago. Interestingly, the release notes state, "This update also fixes an issue with the ServerAddressInternal managed preference setting".

Communicator is not Lync but this leads me to believe a Lync update may address the problem.

Lync also seems to wig out when you try and close it. Hopefully an update is coming soon. I find it unreasonable for large companies to Beta test through retail releases!

FYI Microsoft support was absolutely useless on this issue. I guess we'll just have to wait.

http://mac2.microsoft.com/help/office/14/en-us/lyncdeploy/item/81755f45-3c1b-4d09-bef1-2cf48b9fc29a

Worked with Microsoft and we were able to find the culprit. Instructions updated on the Lync page!