Category Archives: Server 2008

How to push printers to Windows XP clients via Group Policy

If you are like me, you have been using the Print Management and Group Policy options in Server 2008 to push printer installs to all your Windows 7 clients. This is great and works well.

But, what happens if you still have Windows XP clients in your domain? Well, help is at hand with a Microsoft utility called PushPrinterConnections.exe which is found in the the C:\Windows\System32 directory on your server.

Here is how to push printer connections via Group Policy to your XP clients.

First, copy the PushPrinterConnections.exe file from the System32 directory on your server to your Desktop. Then follow these instructions:

  1. Open the GPMC.
  2. In the GPMC console tree, navigate to the domain or organizational unit (OU) that stores the computer or user accounts where you want to deploy the PushPrinterConections.exe utility.
  3. Right-click the GPO that contains the printer connections that you want to deploy using Group Policy, and then click Edit.
  4. Navigate to one of the following locations:
    • If the printer connections are deployed per-computer, go to Computer ConfigurationPoliciesWindows SettingsScripts (Startup/Shutdown).
    • If the printer connections are deployed per-user, go to User ConfigurationPoliciesWindows SettingsScripts (Logon/Logoff).
  5. Right-click Startup or Logon, and then click Properties.
  6. In the Startup Properties or Logon Properties dialog box, click Show Files. The Startup or Logon window appears.
  7. Copy the PushPrinterConnections.exe file from the %WINDIR%\System32 folder to the Startup or Logon window. This adds the utility to the GPO, where it will replicate to the other domain controllers with the Group Policy settings.
  8. In the Startup Properties or Logon Properties dialog box, click Add. The Add Script dialog box appears.
  9. In the Script Name box, type: PushPrinterConnections.exe
  10. To enable logging on client computers running Windows Server 2003, Windows XP, or Windows 2000, in the Script Parameters box, type: –logLog files are written to %WINDIR%\temp\ppcMachine.log (for per-computer connections) and to %temp%\ppcUser.log (for per-user connections) on the computer where the policy is applied.
  11. In the Add Script dialog box, click OK.
  12. In the Startup Properties or Logon Properties dialog box, click OK.
  13. Use GPMC to link the GPO to other OUs or domains to which you want to deploy the PushPrinterConnections.exe utility.

Provider cannot be found. It may not be properly installed.

I installed a new Windows Server 2008 R2 and I hosted my own web server. All was going well until I tried to connect a virtual directory to an Access database driven site and I received this error:

Error 500: Provider cannot be found. It may not be properly installed.

After a short search, I found that I needed to enable 32bit applications on this 64bit OS.

The easiest way to do this is to follow these steps:

  1. Open IIS manager on your server
  2. Click on the Application Pools link in the left column
  3. Click on the application pool for your website
  4. Choose Advanced Settings from the right column
  5. One of the first options should state “Enable 32-bit applications”. By default it is set to FALSE. Change this to TRUE.

And that’s it. Simple aye!?

1 Comment

Posted by on November 19, 2012 in IIS, Server 2008


Failed to join domain

I was setting up a new Hyper-V Core server with 3 network cards – 2 x LAN and 1 x WAN. I configured all cards with static IP Addresses. But when I attempted to join the domain, I received a very unhelpful error message:

Failed to join domain

And that’s it! No event log, nothing! Great. Now where do I go?

After searching all the corners of the internet, I found a solution. The problem was in the way the Hyper-V box ordered the network cards. It made the WAN card the first in the queue, so of course, when I attempted to connect it to the domain, it was going out into the Internet to find our domain. Doh!

To change the “order” of the network cards, you need to change the “Interface Metric”. In a normal Windows GUI, you can change each NIC interface metric by going into the properties of the NIC’s IP address, choosing advanced, and then manually changing the metric that way. NOTE: lower numbered metrics go first – but don’t choose ‘0’ as this signals an automatic metric which will put you back to where you are now. After you have changed the values, reboot for good measure.

But, if you have a server core machine without a GUI, then you need to perform some command line work.

Open a command prompt and do the following:

To display all of the adapters in the computer with their current IP addresses to determine the correct adapter name, type the following command:

netsh interface ip show config

To change to a static address, type the following command:

netsh interface ip set address “Local Area Connection” static ipaddr subnetmask gateway metric

For example, I need to change my Local Area Connection #7 to a metric of 5, I would do this:

netsh interface ip set address “Local Area Connection 7” static 5

And after a reboot, you will be able to join your server / PC to the domain without a problem.


How to remove a service under Windows Server 2008 / Windows 7

If you need to remove an unwanted service from your server / PC but there is no uninstall program, how do you do it?

Easy! Perform the following:

  1. Go to Administrative Tools and click on Services
  2. Find the Service you need to uninstall, right mouse click and choose Stop
  3. Close the Services box
  4. Open an admin command prompt
  5. Type in: sc delete <servicename> eg sc delete acmeservice

The idea is to run this command in the directory that the executable for the service resides else the program will not know where to find the service to remove.

Leave a comment

Posted by on June 29, 2012 in Server 2008, Windows 7


MMC could not create the snap-in for Server Management on Windows Server 2008

I had a weird problem after running Windows updates on a Windows Server 2008 machine. The Server Manager would not start and it displayed a weird MMC error. I couldn’t even add the MMC snap-in manually. But I found a solution.

1. Navigate to the following directory:


2. Copy the ‘machine.config’ file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That’s it, nothing else is needed. Try running Server Manager now and all will be good again in your world!

1 Comment

Posted by on December 1, 2011 in Server 2008