Windows 10 Features You Might Have Missed

Techy Geeks Home

Right now, when the whole world fits right in your pocket, there is nothing that one device is incapable of doing. But in IT industries or in any other profession there are certain devices assigned for one particular work. There are PCs designed for gaming, designing, business work, etc. Till now, there was no one … Read more

Microsoft Teams MSI Installers

Microsoft Teams Logo

In most business environments, you will find that Microsoft Teams is used a lot. Especially as Microsoft seem to be starting the push from Skype to Teams.

But, this means that if you are looking at a large deployment, you want to try and make the process as quick and easy as possible. For those IT professionals that has deployed software using platforms like SCCM, WDS or Group Policy, you will know that having the MSI installer makes life a lot easier!

So, you can now download both the x64 and the x86 versions of the Microsoft Teams explorer through us and we will also ensure that it is kept up to date.

Download Microsoft Teams MSI Installers

MSI Downloader Tool

Download MSI Downloader Tool

Direct Download

Download Microsoft Teams MSI Installers


SourceForge Download

Download MSI Installers
Download MSI Installers

RSS Update Feed

You can keep up to date with our latest MSI releases by using the RSS feed below:

https://sourceforge.net/projects/msi-installers/rss?path=/

Instructions

If you are pushing this out in your corporate environment, you will want to use the silent installer switches, so this is the command line that you should use for this:

msiexec.exe /i "teams-msi-x64.msi" /q /norestart

This means it will install quietly (using the /q switch) and will not reboot automatically (using the /norestart) switch.

You can also use the /qb+ switch to show a basic UI.

Feedback

We would love to hear your feedback on this article so come and join us on Facebook or Twitter or just leave us a message below.

Microsoft Office 2016 – Released to VLSC Customers

Microsoft Dumps Physical Office 2

With the recent release of Microsoft Office 2016 to the public, the VLSC version has now been released to volume licence customers.

So you can now download the various versions of Office 2016 by logging into your VLSC and searching for it or browsing for it.

Microsoft Office 2016 - Released to VLSC Customers 1

We will be testing it over the next few days and will add some screenshots and any guides that we feel may help our visitors.

COMMENTS

If you have any comments to add on your experiences of using Office 2016 then please feel free to leave a message below using our comments  system.

Microsoft Excel – Columns Displaying Numbers instead of Letters

excel

We have recently dealt with a problem that a customer had reported to us about their Excel spreadsheet columns suddenly appearing as numbers instead of the expected letters.

We doubted this very much as none of us had heard of it before, but no, there is was, columns as numbers just like this:

Microsoft Excel - Columns Displaying Numbers instead of Letters 2

This was a bit baffling to us, but is very easy to fix. This type of formatting for the columns is called R1C1 reference style. It is not a problem as such, just a different way of doing things, but as most people will want their Excel columns as letters, there is an easy way to revert this.

To show this easier, we have created a quick video guide on how to put this back to letter formatting:

VIDEO

COMMENTS

If you have any questions or comments about this guide, please feel free to use our comments system below.

Shared Mailboxes Sent Items in Outlook

outlook blue logo

If you are using shared mailboxes in Outlook, then you may find that when someone is sending an email from this mailbox, the sent email is going into the users own Sent Items folder rather than the Sent Items folder within the shared mailbox itself.

This is because there is a delegation registry key that needs to be set to allow the sent email to drop into the shared mailbox.

Considerations

Please note the part of the registry key that is in bold and red “14.0” – this is the version of Outlook that you are using and must be changed for your version.

The different versions of Outlook are:

  • Outlook 2007 – 12.0
  • Outlook 2010 – 14.0
  • Outlook 2013 – 15.0
  • Outlook 2016 – 16.0

Also note that this must be done logged in as the affected user that you want to amend.

Instructions

To do this, simply follow the instructions below:

  • Click Start
  • Click Run
  • Type regedit, and then click OK
  • Locate and then click the following registry subkey:
  • HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences
  • On the Edit menu, point to New, and then click DWORD Value
  • Type DelegateSentItemsStyle, and then press Enter
  • Right-click DelegateSentItemsStyle, and then click Modify
  • In the Value data box, type 1, and then click OK
  • Exit Registry Editor and reboot the machine

Once you have rebooted the machine you should then test sending an email from the shared mailbox and you should now see that the email has gone into the correct folder within the shared mailbox itself.

Feedback

If you have any questions or comments on this, please feel free to use our comments system below.

Fix Office 2010 and Office 2013 Products Compatibility & Mimecast Default Exchange Account Error

mimecast

If you are trying to use Office 2010 and Office 2013 products like Visio or Project and you have Mimecast for Outlook Client, you may find that you get an error like:

“Default account is not an exchange account”

The process below should fix this for you.

Under the following registry key you’ll find a 9.4 key referring to Office 2010 and a 9.5 key referring to Office (inc. Project and Visio) 2013. Please note that this is based on a x64 machine, same applies for x86 but using x86 variables.

HKEY_CLASSES_ROOTWow6432NodeTypeLib{00062FFF-0000-0000-C000-000000000046}

  1.  Close all Office products
  2.  Find the registry key as above
  3.  Delete the entire 9.5 key found at this registry location
  4.  Restart machine

This should fix the Mimecast error of “Default account is not an exchange account”.

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012

Microsoft Dumps Physical Office 2

If you have a requirement to add any Office 2010 language packs to your SCCM 2012 Software Catalog then you may find that it is not the simplest of tasks.

I’ve spent some time working on different methods of doing this and although creating the packs as an application and pushing them out is fairly simple, to offer them through the catalog was more difficult.

After lot’s of testing, I have found a way that not only works, but also seems to be the more simple and as always, I thought I’d document this information to help others facing the same task.

So, below is a guide to help you create your own language packs through the software catalog.

The below guide assumes you have access to language packs and that you know how to create packages already in the catalog. For the purposes of this guide, I am using the Norwegian Office 2010 Language Pack.

To begin, you need the language pack itself, so you can download individual packs from your Microsoft Volume Licence website.

Once you have downloaded the files (or if you have downloaded the ISO, extract the files using an extract tool like 7-Zip), you should copy them to your network location storage ready for you to point your package to.

Then go into the folder with the files in it, you should see a folder called “OMUI.nb-no” (NOTE: the nb-no in this guide states the language is Norwegian, this part of the folder name changes dependent on the language you are using..).

Go into this folder and you should then see a file called “config.xml”, right click on this file and click edit.

Where the line says (yours may be slightly different):

<!– <Display Level=”full” CompletionNotice=”yes” SuppressModal=”no” AcceptEula=”no” /> –>

You should replace this with:

<Display Level=”none” CompletionNotice=”no” SuppressModal=”yes” AcceptEula=”yes” />

Then save the file and exit. You then move on to packaging the folder in SCCM.
Go into the SCCM Console and click on “Software Library” then Applications.

Then right click and select “Create Application”

On the wizard page, select “Manually specify the application information” and click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 3

On the second wizard page, fill out all the fields as you wish and click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 4

On the next page, you can set the custom user settings and click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 5

On the next page, click the Add button

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 6

Then on the new dialog box, click “Manually specify the deployment type information” then click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 7

Enter the custom package details and then click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 8

You should then enter the content location (where you copied the files to earlier in this guide..)

You then need to enter the installation program, it will be the same apart from the changes in the language pack folder details for different languages:

setup.exe /config OMUI.nb-noconfig.xml

This is the config.xml file that we edited earlier in this process.

You also need to enter the uninstall information as:

setup.exe /uninstall

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 9

On the next page, click “Add Clause”

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 10

In the Setting Type, from the drop down menu select “Windows Installer” then under Product Code, click Browse. Then browse to the OMUI.nb-no folder at the network location and select the OMUI.msi file.

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 11

Then click OK

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 12

and then next.

You can then setup your User Experience settings and click next

Office 2010 Language Pack Deployment in the Software Catalog for SCCM 2012 13

You then have the option to set your requirements and software dependencies.

You can go on and complete the wizard.

Once completed, you can then distribute the package and deploy where you need to.

If you have any issues with this guide, please leave a comment and I’ll try and help.