Close Menu
    Facebook X (Twitter) Instagram
    Monday, May 19
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»CM2012»How to Deploy Microsoft Yammer Client using SCCM Configmgr

    How to Deploy Microsoft Yammer Client using SCCM Configmgr

    Eswar KonetiBy Eswar KonetiJanuary 25, 12:21 pm2 Mins Read CM2012 7,145 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Yammer  is enterprise social networking service used for private communication within organizations. Access to a Yammer network is determined by a user's Internet domain so that only individuals with approved email addresses may join their respective networks.

    Yammer can be used to discuss ideas, share updates, and crowd source answers from co-workers around the globe. Yammer gives you a faster, smarter way to connect and collaborate across your company.

    If your organisation moved to O365 ,you will hit requirement to deploy O365 applications like Microsoft Teams,Onedrive,Yammer ,AIP etc. All of these applications (except AIP) are user specific and they will be installed in user profile (%AppData%) instead of %programfiles%

    Deploying applications to computers would be straight forward but for applications that are user specific and installation does in %appdata% ,there will be little challenges for application detection method .

    Application detection is one of the main criteria to identify if the application is installed correctly or not ,also it helps to reinstall the app if the app is removed on user machine (this happens with application deployment evaluation cycle ).

    As i mentioned in my previous blog deploying Microsoft Onedrive using Configmgr , we will be similar method with detection rule for Yammer also.

    Before we start of with this ,Download Yammer client (MSI) file from https://support.office.com/en-us/article/yammer-for-windows-and-mac-50920c05-cbfc-4f11-8503-e20fb2e623a5 .

    Once the MSI file downloaded ,extract the file using 7zip or WinRAR to get the actual installer used to deploy to users. You will see something like below.

    image

    Copy the file to your SCCM source files ,start creating Application as you do for other EXE applications.

    For Deployment Type ,choose script Installer

    Installation Program:"yammerdesktop.exe" /s

    Uninstallation Program:"%LocalAppData%\yammerdesktop\Update.exe" --uninstall -s

    image

    Detection Rule:

    Key: Software\Microsoft\Windows\CurrentVersion\Uninstall\yammerdesktop

    Value:DisplayVersion

    change the version value (1.3.1) name as per the application you are installing.

    image

    User Experience:

    image

    Requirements: Windows 7,windows 10 (based on where you need this to be installed).

    Deploy the application to user collection .So when the user receive policy (user policy evaluation cycle) ,application will get install and shortcut icon will be created on users desktop.

    image

    Following is the registry location that application get installed.

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\yammerdesktop

    SNAGHTML3a0f1df

    Hope it helps!

     

     

    Application creation configmgr Deploy Yammer detection method O365 application SCCM yammerdesktop
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    Investigating Co-Management Issues with Windows Endpoints in SCCM/Intune

    October 26, 10:45 pm

    11 Comments

    1. appleoddity on June 22, 2018 10:13 PM

      The Yammer 1.3.2 MSI files available at the link you provided are broken. All references on the internet point back to that URL. I'm not sure what else to do. They are useless. Both 32-bit and 64-bit versions have a 32-bit platform type configured in the MSI and are picked up as 32-bit packages. Then when it installs, both versions extract themselves to "Program Files (x86)" and both versions make an entry in the 32-bit HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run referring to the executable in %Program Files%\Yammer Installer\yammerdesktop.exe which fails because the executable is NOT in Program Files, it is in Program Files (x86). This problem didn't exist with the 1.3.1 version of installers. Any ideas how to escalate this with Microsoft?

      Reply
      • Eswar Koneti on July 8, 2018 9:13 PM

        Hi Ken,
        It works for me .Visit https://support.office.com/en-us/article/yammer-for-windows-and-mac-50920c05-cbfc-4f11-8503-e20fb2e623a5 and look for Get the app ,you have both 32bit and 64bit for windows7+ .
        What is not working for you .

        Regards,
        Eswar

        Reply
    2. Jay on April 11, 2018 4:02 AM

      It is worth mentioning that Yammer v1.3.1 DID NOT leave an entry in the registry regarding it being installed. Fortunately, Yammer 1.3.2 is out, and my testing shows the entry being there again.

      Reply
      • Eswar Koneti on July 8, 2018 9:15 PM

        Hi Jay,
        that is really strange .Could be that, the version might have changed how it leave the entries in registry but we have stopped deploying Yammer client as web browser provide more features and also much faster to use.

        Regards,
        Eswar

        Reply
    3. Leo Leon on March 19, 2018 1:58 AM

      Have any suggestions for App Detection Method? I have followed instructions and software will install but Software Center reports it as failure. I've tried different ways for detection method such as changing RegKey but no luck. Thanks!

      Reply
      • Eswar Koneti on April 1, 2018 10:10 AM

        After the Install of Yammer on client PC,did you check if there are any entries in HKCU as per the guide ? If there are not entries then for sure detection method will fail. If there are registry entries about Yammer ,then you need to cross verify the detection rule with HKCU.
        you can also look at folder location %localappdata% .

        Regards,
        Eswar

        Reply
        • JAy on July 10, 2018 10:33 PM

          I've noticed that with 1.3.2, they have replaced the entry in the registry.

          In the interim, I did develop a detection script that will work independent of the registry key. This works if you have one primary user per machine:

          $loggedInUserName = get-wmiobject win32_computersystem | select username
          $loggedInUserName = [string]$loggedInUserName
          $loggedinUsername = $loggedInUserName.Split("=")
          $loggedInUserName = $loggedInUserName[1]
          $loggedInUserName = $loggedInUserName.Split("}")
          $loggedInUserName = $loggedInUserName[0]
          $loggedInUserName = $loggedInUserName.Split("\")
          $loggedInUserName = $loggedInUserName[1]
          Return $loggedInUserName
          }
          $user = CurrentUser

          $bRes = if(Get-ChildItem "C:\Users\$user\AppData\Local\" | Where Name -eq "yammerdesktop") { $true } else { $false}

          if($bRes) { $true } else { $null }

          Reply
    4. Pingback: System Center Şubat 2018 Bülten – Sertac Topal

    5. MartijnS on February 9, 2018 10:11 PM

      Works great. Thanks for the document!

      Reply
    6. ramg1967 on January 25, 2018 9:09 PM

      Thanks for sharing. Will test out the deployment this weekend.

      Ram

      Reply
      • MartijnS on February 9, 2018 10:09 PM

        Works great. Thanks for the document!

        Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.