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

WDS – “The Network Path was not found” when adding an Unattend file

KB ID 0000487

Problem

Saw this last week, while trying to use an unattended file for the roll out of some machines with WDS.

Every time you try and enter a value you get “The network path was not found” error, no combination of file path or UNC path seems to cure the problem.

Solution

This is a “work around” not a fix, essentially it will not accept any value you put into the path without throwing and error. If you close and reopen this page the value you enter has not been accepted.

So we are going to populate the entry by editing the registry, if you go back and view the entry afterwards it will STILL ERROR but the value will say put and the unattended file will work (providing the path you specify is correct of course!)

1. On the WDS server >Start > regedit {enter}.

2. Navigate to:

[box]HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWDSServerProvidersWdsImgSrvUnattend[/box]

3. Locate the “Enabled” value and change it from 0 to 1.

4. Below this key you will see there is a key for each “image processor type”. I’m adding a 32 bit (x86) Unattended file so expand that, and set the “FilePath” value to your unattended xml file (Note: the path is from the WDS root directory, keep it simple and put your unattended file in the WDSClientUnattend folder. In this example mines called WDSClientUnattend.xml).

5. Finally restart the “Windows Deployment Services Server” service.

 

Related Articles, References, Credits, or External Links

NA

GNS3 – Network Cards Are Missing

KB ID 0000964 

Problem

Like most techies, I am always fiddling with things. One of my mottoes is “If you never break anything, you never learn how to fix things”. So after messing around with the networks in VMware Workstation (What I typically use for connecting GNS3 to either real machines, or the outside world). I lost the network connections in GNS3 and could not get them back. Seems like any new NICs that you add are not listed either.

Solution

Note: It might be worth resetting your VMware Workstation Network settings before continuing. (Edit > Virtual Network Editor > Restore default).

1. To make things simple, I’ve renamed the Network Cards installed by VMware workstation to something a little more descriptive, (if you unsure which is which, just run ‘ipconfig’).

2. Let’s double check, drop to command line and run the following command;

[box]
netsh interface ipv4 show interfaces
[/box]

3. And let’s affirm what GNS3 is telling us by running the following script from the GNS3 directory;

[box]
“C:Program FilesGNS3network-device-list.cmd”[/box]

LEAVE THIS WINDOW OPEN

4. As you can see (above) there is a discrepancy. To get GNS3 to ‘sync’ with windows we need to restart the NetGroup Packet Filter Driver service. Open an elevated command prompt and issue the following commands;

[box]

net stop npf
net start n/f

[/box]

5. Now execute the script again and it should show the correct network adapters.

6. Now from within GNS3 you can add the correct network cards to your ‘Clouds’.

Related Articles, References, Credits, or External Links

NA

ARCserve – Addling Licences

KB ID 0000444 

Problem

Normally you can just add licenses from Help > About CA ARCserve Backup > Add/View Licences.

However you may find that you cannot enter a “Backup Suite” Licence code/Activation key.

Solution

1. To do this you need to locate the “CALicnse.exe” file and run it.

2. This tool will let you enter the correct licenses.

Note: Depending on ARCserve version the folder location may vary.

 

Related Articles, References, Credits, or External Links

NA