Registry Hack For Mac Location Of Microsoft Office Programs

  1. Registry Hack For Mac Location Of Microsoft Office Programs Download

Close Outlook, then open up a program called Registry Editor by pressing the windows icon and typing in simply regedit. Navigate using the arrows on the left-hand side to the following location: HKEYCURRENTUSERSoftwareMicrosoftOffice16.0OutlookAutoDiscover. If you need to uninstall Office first, see Uninstall Office from a PC or Uninstall Office for Mac. Note: The steps to install the 2016 or 2013 versions of Office Professional Plus, Office Standard, or a stand-alone app such as Word or Project might be different if you got Office. Thanks Microsoft for getting rid of the options to customize our desktop! What used to be so easy is now a registry hack! In order to change the desktop icon spacing (horizontal and vertical), you have to edit two values in the registry. Check out our previous post below. Change Desktop Icon Spacing in Windows 10. Click to Last Active Window. Get started with Office 365 for free. Students and educators at eligible institutions can sign up for Office 365 Education for free, including Word, Excel, PowerPoint, OneNote, and now Microsoft Teams, plus additional classroom tools. Use your valid school email address to get started today.

Learning has never been so easy!

Sometimes after uninstalling older versions of Microsoft Office some registry keys are left behind. This causes Spiceworks to think that those older versions of Office are still installed, even though the actual program files are all removed. You can follow the steps here to clean up those old registry keys so Spiceworks can get a proper inventory of the software on the machine.

NOTE: Please make a backup of Registry before making any changes to it. You can severely damage a machine if an incorrect edit is made.

4 Steps total

Step 1: Open up RegEdit

Open up RegEdit by going to Start>Run and typing 'regedit' and pressing Enter or OK. You can also enter the 'regedit' command into a Command Prompt to open up the editor.

Step 2: Locate the Office Registry Key

Microsoft stores all of the installation information for Office Products in HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice. Underneath this key you will see various version numbers, each corresponding to different versions of Office. They are as follows:

-9.0 is Office 2000
-10.0 is Office XP
-11.0 is Office 2003
-12.0 is Office 2007
-14.0 is Office 2010

Step 3: Locate the Corresponding Registration Key

Underneath each of the version number keys you should see a 'Registration' key. Depending on how many Office products you have installed (Visio, Project, etc. all will be stored underneath one of those version keys) on the machine there will be multiple hashed keys present underneath the Registration key. Each of these hashed keys should have a value underneath it called 'ProductName'. You can use this value to correctly determine which hashed key is related to the product you want to remove.

Step 4: Delete the Hashed Key

Once you have located the correct hashed registry key, delete it. As mentioned above, though, make sure you have a good backup before doing this!

Once you have performed the steps above run a scan on the device by either running a full network scan or a rescan underneath the Tools section of the device. Once the scan is complete you should see that the long deleted Office products are now gone from your Spiceworks Inventory. If the scan is still showing that the software is present, you might need to disable Incremental Scanning in Settings>Network Scan.

I hope this helps!

Published: Nov 15, 2011 · Last Updated: Jul 11, 2012

22 Comments

  • Cayenne
    Marciab Nov 15, 2011 at 04:50pm

    Great How to.... Thanks for sharing

  • Ghost Chili
    Kellanved Nov 15, 2011 at 04:55pm

    Thank you so much! Finally someone narrowed down which keys to delete! I could only recommend a general registry cleaner to others having this issue.

  • Ghost Chili
    JustRob Nov 15, 2011 at 06:02pm

    Nice. Good to know exactly what to look for, when even the M$ 'fix it' doesn't get it all.

  • Datil
    Brian Steingraber Nov 15, 2011 at 11:45pm

    Office 2010 is really bad about removing these keys so this is a all too common task for me!

  • Habanero
    John6020 Nov 16, 2011 at 06:14am

    Brilliant - thanks for the information.

  • Serrano
    tech_freak Dec 15, 2011 at 02:03pm

    Good One.

  • Serrano
    pnadon Jan 24, 2012 at 05:06pm

    Thank you!!

  • Mace
    hsc5775 Apr 20, 2012 at 04:03am

    great work
    thx for share

  • Serrano
    Craig Manske Apr 24, 2012 at 07:54am

    On a 64bit machine it is under HKLMSOFTWAREWow6432NodeMicrosoftOffice.

  • Datil
    Paolo0111 May 17, 2012 at 05:26am

    Thank you very much, James B!

  • Datil
    spike7 Aug 27, 2012 at 10:49pm

    Nice.. thank you!

  • Mace
    Gabrielle.L Sep 20, 2012 at 01:31pm

    Thank you for this! I've started doing Office upgrades on our workstation, and it was driving me crazy that my Spiceworks inventory showed multiple versions installed on a machine when there clearly was not.

  • Jalapeno
    Dvir IT Nov 4, 2012 at 03:56pm

    It didn't do it for me a first. Until now...
    Solved!

    1. Disable Incremental Scanning in Settings>Network Scan. – Super Important!!!
    2. Use Microsoft fixit http://go.microsoft.com/?linkid=9669698
    3. Scan Device.
    Thanx a lot!
    Dvir

  • Pure Capsaicin
    Justin.Davison Nov 14, 2012 at 05:04pm

    Nice one, just saw this and it is a good guide for a common issue people have.

  • Datil
    Angus S-F Feb 28, 2013 at 04:38pm

    Nirsoft has a free tool to retrieve the Office keys from your domain: Produkey. It has a command-line option to '...enumerate all computers in the specified domain, and load the product key information from them.'

    Get it here:
    ProduKey - Recover lost product key (CD-Key) of Windows/MS-Office/SQL Server
    http://www.nirsoft.net/utils/product_cd_key_viewer.html

  • prev
  • 1
  • 2
  • next
Registry Hack For Mac Location Of Microsoft Office Programs -->

Topic Last Modified: 2013-01-10

To define custom presence states in Lync 2013, create an XML custom presence configuration file, and then specify its location by using the Lync Server Management Shell cmdlets New-CSClientPolicy or Set-CSClientPolicy with the parameter CustomStateURL.

Configuration files have the following properties:

  • Custom presence states can be configured with the Available, Busy, and Do Not Disturb presence indicators.

  • The availability attribute determines which presence indicator is associated with the status text of the custom state. In the example later in this topic, the status text Working from Home is displayed to the right of the green (Available) presence indicator.

  • The maximum length of the status text is 64 characters.

  • A maximum of four custom presence states can be added.

  • The CustomStateURL parameter specifies the location of the configuration file. In Lync 2013, SIP high security mode is enabled by default, so you will need to store the custom presence configuration file on a web server that has HTTPS enabled. Otherwise, Lync 2013 clients will be unable to connect to it. For example, a valid address would be https://lspool.corp.contoso.com/ClientConfigFolder/CustomPresence.xml.

Note

Although it is not recommended in a production environment, you can test a configuration file that is located on a non-HTTPS file share by using the EnableSIPHighSecurityMode registry setting to disable SIP high security mode on the client. Then you can use the CustomStateURL registry setting to specify a non-HTTPS location for the configuration file. Note that Lync 2013 honors Lync 2010 registry settings, but the registry hive has been updated. You would create the registry settings as follows:

  • HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice15.0LyncEnableSIPHighSecurityMode

    Type: DWORD

    Value data: 0

  • HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice15.0LyncCustomStateURL

    Type: String (REG_SZ)

    Value data (examples): file://lspool.corp.contoso.comLSFileShareClientConfigFolderPresence.xml or file:///c:/LSFileShare/ClientConfigFolder/Group_1_Pres.xml

Localize your custom presence state by specifying one or more locale ID (LCID) schema in the XML configuration file. The example later in this topic shows localization into English - United States (1033), Norwegian - Bokmål (1044), French - France (1036), and Turkish (1055). For a list of LCIDs, see Locale IDs Assigned by Microsoft at https://go.microsoft.com/fwlink/p/?linkid=157331.

To add custom presence states to Lync 2013

  1. Create an XML configuration file that uses the format of the following example:

  2. Save the XML configuration file to a web server with HTTPS enabled. In this example, the file is named Presence.xml and saved to the location https://lspool.corp.contoso.com/ClientConfigFolder/CustomPresence.xml.

  3. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.

  4. In the Lync Server Management Shell, define the location of your XML configuration file by using a command similar to the following:

  5. Use the Grant-CSClientPolicy cmdlet to assign this new policy to users.

For details, see New-CsClientPolicy and Grant-CsClientPolicy in the Lync Server Management Shell documentation.

Note

Registry Hack For Mac Location Of Microsoft Office Programs Download

  • By default, Lync Server 2013 updates client policies and settings every three hours.

  • If you want to continue using Group Policy settings from previous releases, such as CustomStateURL, Lync 2013 will recognize the settings if they are located in the new policy registry hive (HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice15.0Lync). However, server-based client policies take precedence.