MS Office – Cannot Add Trusted Location

KB ID 0001171

Problem

I was doing a Domain/Exchange/RDS migration for a client this week. He had some Macros that he used for printing. Now Macros are something I know very little about. So I had made it clear, if he had problems with them, I would not be the best person to ask.

So when the call came in, that they were having problems with Macros I cringed! As it turned out, the problem wasn’t the Macros at all, it was the ‘Trust Center’ Settings in Word.

Error: Microsoft Office Trusted Location

The remote or network path you have entered is not allowed by your current security settings

 

Solution

I’m controlling all the office settings via group policy, this is easy to setup, and rather than reinvent the wheel read the following article if you don’t have GPO’s for office setup.

Stop the Office 2013 ‘Welcome To Your New Office Movie’

Now, that’s complete, you can solve this problem in one of two ways, (or both if you’re a belt and braces kind of a tech!)

Option 1

As you can see, (above), the location that the user was trying to add, was on a mapped drive (in this case S:), you can allow that from the following policy;

[box]

User configuration > Administrative Templates > Microsoft Word 2013 > Word Options > Security > Trust Center > Trusted Locations

[/box]

Pick one of the locations and configure as follows;

Option 2

Or simply allow the user to add network locations, to the trusted locations, from the following policy;

[box]

User configuration > Administrative Templates > Microsoft Word 2013 > Word Options > Security > Trust Center > Allow Trusted Locations on the network

[/box]

Enable the policy.

 

Related Articles, References, Credits, or External Links

NA

Microsoft Autoroute Install Errors (Windows 8)

KB ID 0000686 

Problem

I only use Autoroute once a month, (when I put my mileage in at work!). So this month I had a head slap when it was one of the bits of software I had forgotten to install on my freshly rebuilt laptop. So I fired up the setup for Autoroute 2007 and it failed.

So I moaned and was furnished with a shiny new copy of Autoroute 2011. But when I tried to install it, this happened.

Microsoft Autoroute 2011 Setup One of the prerequisite components failed to install. Setup will now exit.

Solution

It installed fine on my colleagues laptop so the problem had to be something to do with me. I did manage to get the product installed by running the data.msi file and installing the product that way, this got me further but then I got this error,

Microsoft Autoroute A licensing initialisation error has occurred. Please contact customer support for more assistance. Error 0x80070005

I got round that by installing in compatability mode, and running the install from command line admin mode. (Press Windows Key+X).

When I finally got the program installed, it would launch then crash. I installed it in a virtual machine and it worked faultlessly? I unistalled the product and compared my installed programs with the ones on my working virtual machine, I found that the C++ Distributable and the Microsoft Access database engine 2010 had different sizes? These were the prerequisites that Autoroute wanted to install at the very beginning.

So I unistalled everything ad tried to install the prerequisites manually, and then I located an issue,

You cannot install the 32 bit version of Microsoft Access Database Engine 2010 because you currently have 64-bit Office products installed.

So (begrudgingly) I removed x64 office and installed x86 Office.

Then the Access Database Engine Installed but the C++ wouldn’t! Because a newer version was installed.

A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine.

Microsoft could you please make this software MORE incompatible with MORE bits of your OWN software please, I’ve spent a large chunk of my morning trying to fix this now!

Fix the problem and get it installed.

1. Make sure you are running an x32 bit version of Office. (see above)

2. Press Windows Key+R > appwiz.cpl {enter}, Uninstall ALL the following if present,

Microsoft Office Access Database Engine. Microsoft Autoroute 2011. ALL Instanced off C++ Redistributable (all the x86 ones and All the x64 ones).

3. Reinstall Autoroute 2011.

4. Install the x64 bit C++ Redistributable from here.

5. It should now work fine.

 

Related Articles, References, Credits, or External Links

NA

Outlook – Disable Cached Mode with Group Policy

KB ID 0000507

Problem

I got asked how to do this today, a client has a number of roaming users (teachers) who don’t like waiting for Outlook to create a local copy of the mailbox each time they log on. To be honest as they have Exchange 2010 they would be better using the feature rich Outlook Web App (OWA) rather than the full client if they need to move around so much but hey, I was asked.

Solution

1. To do this you need to use a custom administrative template, thankfully Microsoft have them pre written go here to down load the administrative templates.

2. Download and extract the templates to your domain controller. Start > Administrative tools > Group Policy management console > either create a new policy and link it to your USERS or edit an existing policy.

3. Navigate to:

[box] User Configuration > Policies > Administrative Templates [/box]

Right click > Add/Remove Templates.

4. Add > Navigate to the folder where you extracted the templates > ADM folder > en-us folder (change depending on your locale) > Outlk14.adm > Open.

5. Now Navigate to:

[box] User Configuration > Policies > Administrative Templates > Classic Administrative Templates > Microsoft Outlook 2010 > Account Settings > Exchange > Cached Exchange Mode [/box]

Locate “Use Cached Exchange Mode for new and existing Outlook Profiles”

6. Set the policy to “Disabled” > Apply OK > Close the policy editor.

7. Then get the clients to log off and back on again, wait a couple of hours, or manually run “gpupdate /force” on them.

 

Related Articles, References, Credits, or External Links

NA

 

Office Install Error 1935

KB ID 0000399 

Problem

Seen while installing Office 2007 Enterprise On Server 2008 R2 (Don’t ask).

Error:
Microcyst Office enterprise 2007 encountered and error during setup.
Error 1935.An error occurred during the installation of an assembly component
{837Bf-1EB-D770-94EB-A01F-C8B389A1E18E}. HRESULT: 0x80070BC9

Solution

1. Essentially there is a .Net problem, On Server 2008 you will need to add in .Net as a feature. (Server Manager > Features > Add Feature > Locate and install .Net).

2. Follow the instructions, when finished run Windows Update to get the latest .Net service pack installed, then reboot.

3. Post reboot, it should install without error.

 

Related Articles, References, Credits, or External Links

NA

 

Office Find your Version and Licensing Information

KB ID 0000566 

Problem

Note: This is an OLD post, you might want to look at the following article instead;

Finding Out Your Microsoft Office Licence Version

I had some licencing issues a couple of weeks ago with Office 2010, and needed to check my version and licence details, thankfully Office 2010 comes with a VB script that makes this easy.

Solution

Getting your Office Version and Licence Details

1. Launch a command window (Right click and select run as administrator, or select the cmd icon and press CTRL+SHIFT+ENTER).

2. You need to change to the directory that the script is in, this directory will be different if you are running x32 bit Office on an x64 bit machine. execute one of the following commands;

For x32 bit Office on x32 Bit machines, OR 64 bit Office on x64 bit machines;

[box]cd “C:Program FilesMicrosoft OfficeOffice14″[/box]

For x32 bit Office on x64 bit machines;

[box]cd “C:Program Files (x86)Microsoft OfficeOffice14″[/box]

3. Then execute the following command;

[box]cscript ospp.vbs /dstatus[/box]

Example Output

(Above) This installation of Office 2010 (Pro Plus) is UNLICENSED, (it’s waiting for a licence key to be installed). It will run for another 30 days like this, then this will happen. You can fix this by manually installing an Office MAK key, or setting up a KMS server on your network.

(Above) This installation of Office 2010 (Pro Plus) is LICENSED and has been activated with a MAK key.

(Above) This machine has RETAIL versions of both Office 2010 (Pro Plus), and Visio (Premium). Both are LICENCED, and activated with a retail (or box product) Key.

Other uses for ospp.vbs

Install a MAK Key on a remote machine;

[box]cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx {remote-machine-name}[/box]

Activate a remote machine

[box]cscript ospp.vbs /act {remote-machine-name}[/box]

 

Related Articles, References, Credits, or External Links

NA

Word – Cannot Change the Default Language

KB ID 0000963

Problem

I know Microsoft is from America, that’s fair enough, and they have built into Windows the ability to change the ‘locale’ and language. But its really annoying when you install Office and it just assumes you want an American dictionary. Now something like 80% of my visitors are American and they will probably be surprised that us limeys spell things differently, after all we all speak English right – well yes we do, but written (British) English is different to written (American) English.

e.g. Centre, Colour, Theatre, Analyse, Catalogue, and Programme, etc.

Which is OK, you’ve had a few hundred years to do you own thing, and English is derived from Anglo-Saxon/German, Latin, French, Greek and a great deal of other languages anyway.

So when I go into Office Settings and SPECIFICALLY TELL IT I want my default language to be English (United Kingdom). Why would I want it to set the dictionary to English (US)?

Solution

I’m assuming you have already gore to File > Options > Language > And set the correct language settings.

1. Review > Language > Set Proofing Language.

2. Select your desired language > Set as Default.

Related Articles, References, Credits, or External Links

NA