Microsoft Word and UAC


This morning one of my users started having problems opening Word Documents on the Network. When he double clicks on a document on the network he gets the following popup From User Access Control.

Do you want to allow the following program to make changes to this computer. If you say no Word exits if you say yes it opens but then you get a message that the directory is not valid. Once Word is open you can use file open to browse to the same folder and open the file with no problem. The same UAC message pops-up if you open Word from the Start-Menu.


Check if Word is set to run in administrator mode:

For Windows 7 (32 bit version)
C:\Program Files\Microsoft Office\OfficeXX\WINWORD.exe > right click on it > properties > compatibility >

For Windows 7 (64 bit version)
C:\Program Files (x86)\Microsoft Office\OfficeXX\WINWORD.exe > right click on it > properties > compatibility >

Uncheck the box “Run this program as an administrator” and also ensure that the box to “Run this program in compatibility mode” is unchecked verify the status.

Try opening Word and check if the UAC prompt doesn’t come up again.

OfficeXX -> Office12 = Office 2007; Office14 = Office 2010; Office15 = Office 2013

Installation is forbidden by system policy

On a Windows Server 2012 R2 RDS (Remote Desktop Services) server I suddenly had a problem installing an update of PDF XChange Pro. I got a message like “Installation is forbidden by system policy”.

I tried the “Set the RDS in install mode” by opening the CMD and type “change user /install“. But still no chance of installing the MSI for the software. Also some Office updates started to fail to install.

After some research on different forums, I found the solution:

  1. Go to START > RUN > Regedit
  2. Browse the registry to HKLM\Software\Policies\Microsoft\Windows\Installer
  3. Change the REG_WORD-value of DisableMSI to 0 (mine was set to 2)
  4. Close the registry editor and try to install the program/update again (it now installs)

I hope it helps someone to.

Migration DHCP server from Windows Server 2003 to Windows Server 2012R2

The DHCP database can be moved or migrated from a Windows Server 2003 server to a Windows Server 2012R2 server. I will explain how I did this for my network. It took me like 5 minutes to migrate.

To move a DHCP database and configuration from a server that is running Windows Server 2003 to another server that is running Windows Server 2012R2 (or 2008):

1. Log on to the source DHCP server by using an account that is a member of the local Administrators group. Domain Administrator worked for me.

2. Click Start, click Run, type cmd in the Open box, and then click OK.

3. Type “netsh dhcp server export C:\dhcp.txt all” , and then press ENTER.

Note: You must have local administrator permissions to export the data.

Configure the DHCP server service on the server that is running Windows Server 2012R2

1. Click Start, click Administrative Tools, click Server Manager. If needed acknowledge User Account Control.

2. In Roles Summary click Add Roles, click Next, check DHCP server, and then click Next.

Import the DHCP database

1. Log on as a user who is an explicit member of the local Administrators group. A user account in a group that is a member of the local Administrators group will not work. If a local Administrators account does not exist for the domain controller, restart the computer in Directory Services Restore Mode, and use the administrator account to import the database as described later in this section. (For me it worked with Domain Administrator account login in normal startup mode).

2. Copy the exported DHCP database file to the local hard disk of the Windows Server 2012R2.

3. Verify that the DHCP service is started on the Windows Server 2012R2.

4. Click Start, click Run, type cmd in the Open box, and then click OK.

5. At the command prompt, type “netsh dhcp server import c:\dhcp.txt all” , and then press ENTER, where c:\dhcp.txt is the full path and file name of the database file that you copied to the server.

6. Verify that all settings, scopes and clients are imported.

Authorize the DHCP server

1. Click Start, point to All Programs, point to Administrative Tools, and then click DHCP.

Note You must be logged on to the server by using an account that is a member of the Administrators group. In an Active Directory domain, you must be logged on to the server by using an account that is a member of the Enterprise Administrators group.

2. In the console tree of the DHCP snap-in, expand the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized.

3. Right-click the server object, and then click Authorize.

4. After several moments, right-click the server again, and then click Refresh. A green arrow indicates that the DHCP server is authorized.

5. On the old DHCP server (2003), unauthorize the DHCP server if everything went well.

Don’t forget to install another server with DHCP and create a DHCP Failover (Hot Standby or Load Balanced). This is one of the new nifty features since Windows Server 2012.

HP MSA 2040 and DL380 Gen8 – New storage and virtualization project

In our firm we needed a new solution for our ever growing storage demands. Also the current server and storage (Dell PowerEdge 2950 and MD1000) is out of support after 7 years :)
After deciding virtualization is THE solution to go for, I also choose to go for a proper central storage box. I invited some partners to show me their solutions and I made a shortlist of 3. Dell/Equallogic (PS 4100X), EMC (VNX 5100) and HP (MSA 2040). After intens talks and comparisons, I decided to choose for an HP MSA 2040 with dual 12Gb/s SAS controllers and 24x 900GB 10k Enterprise SAS disks together with 2 HP DL380 Gen8 dual 8-core and 128GB RAM to run VM Essential Plus on.
In my believe the EMC VNX 5100 8Gb/16Gb FC and the MSA 2040 6Gb/12Gb SAS are good competitors and they both gave me huge discounts, but in the end I choose for HP meanly because the VNX 5100 will probably be end of life (EOL) in 2014 and the HP is just launched 6 months ago.

It this moment of writing, I’m waiting for the new boxes to be delivered. Maybe within 1 or 2 weeks I will receive everything and then I will do some I/O testing on this setup.

Here’s my setup:
-2 X HP Proliant DL380p Gen8 Servers (2 X 8 Core processors each, 128GB RAM each)
-HP MSA 2040 Dual Controller – 12Gb/s SAS
-HP MSA 2040 is equipped with 24 X 900GB 10k SAS Dual Port Enterprise Drives
-Each host is directly attached via 2 X 12Gb/s SAS miniHD cables (Each server has 1 SAS cable going to controller A, and Each server has 1 SAS cable going to controller B)
-On the servers, VMWare Essentials Plus will be installed as the hypervisor and for the vm’s I will be installing Windows Server 2012 R2 Datacenter.

Update on the setup and testing soon.

How to pin My Computer to Windows 7 taskbar?

Do you hate it also that you can’t open My Computer directly from the Windows 7 Taskbar.

If we drag N drop My computer to taskbar, it gets pinned to windows explorer rather than creating a new place for itself. Windows explorer opens libraries which irritates me and quite a lot of users. So, I’ve found a simple trick to pin My Computer to Windows 7 taskbar. Below procedure also works with Windows 8 Developer Preview.

Follow the simple steps below to Pin My Computer to Taskbar:

1) Right click on Desktop, and select New > Shortcut.
New Shortcut

2) In location of the item enter the following string exactly as given below:

%SystemRoot%\explorer.exe /E,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}
Name Shortcut

3) Give a name to shortcut. For example, My Computer

4) Now you’ll see a new shortcut of ‘My Computer’ placed on desktop. It has the same icon like that of Windows explorer. You can change its icon if you wish.

5) To pin the shortcut to Windows 7 Taskbar, just right click on it and select “Pin to Taskbar”.
Pin to Taskbar

6) Enjoy! Your direct shortcut to My computer is pinned on taskbar now.

Office 2007 update KB2412171 (11 januari 2011) nog steeds problemen

De volgende problemen kunnen zich voordoen na de installatie van KB2412171 van 14 december 2010.
– Problemen met archiveren
– Performance problemen
– Verzend problemen met error 0x800CCC80
– Problemen met ontvangen e-mails die Secure Password Authentication gebruiken (SPA)

Deze update is 2 dagen later verwijderd uit de automatische Microsoft Update. Op 11 januari 2011 is er een nieuwe versie van deze update uitgebracht en sindsdien er wederom problemen ontstaan (althans in mijn situatie). Probleem wat zich nu voordat bij onze (80) medewerkers is dat als je Outlook 2007 opstart er elke keer wordt gevraagd om in te loggen.
Oplossing voor ons is om deze update (KB2412171) weer te verwijderen via het configuratiescherm en daarna via Microsoft Update deze update te verbergen, zodat deze niet meer geïnstalleerd wordt. Anders wordt deze bij iedere update weer opnieuw geïnstalleerd.
Hopelijk komt Microsoft snel met een definitief goede patch, of ze laten deze maar vervallen.

Om dit probleem te verhelpen moet update KB2412171 verwijderd worden. Dit kan op de volgende manier uitgevoerd worden:

Windows Vista en 7:
1. U kunt Geïnstalleerde updates als volgt openen: klik op de knop Start, klik op Configuratiescherm, klik op Programma’s en klik vervolgens onder Programma’s en onderdelen op Geïnstalleerde updates weergeven.
2. Selecteer KB2412171 en klik vervolgens op Installatie ongedaan maken. Typ het wachtwoord of een bevestiging als u wordt gevraagd om het Administrator-wachtwoord of een bevestiging.
3. Herstart het systeem als hierom gevraagd wordt.

Windows XP:
1. Ga naar Start en druk op uitvoeren
2. Typ appwiz.cpl in het zoekvak en druk op Enter
3. Vink bovenin het scherm de optie aan om updates weer te geven
4. Zoek in de lijst naar KB2412171 en verwijder deze
5. Herstart het systeem als hierom gevraagd wordt.

Nadat je deze update gedeïnstalleerd hebt dien je dus wederom Windows Update of Microsoft Update uit te voeren en dan deselecteer je de update KB2412171 en zet je een vinkje bij verbergen update.
Voor meer informatie zie:

Update Pixelpost v1.7 voor Lightroom 3.2

Eindelijk heb ik een update gevonden voor Pixelpost v1.7 voor Adobe Lightroom v3.2. Tot nu toe werkte deze alleen nog maar voor Lightroom 2, en ik moest daardoor alle foto’s handmatig uploaden naar de website van mijn dochter Vanaf heden werkt het weer automatisch d.m.v. de exportfunctie in Lightroom 3.

De originele post in het Pixelpostforum:
Een link naar het bestand: Pixelpost Lightroom v3 export