Exchange 2013 ECP redirects to old Exchange 2010 OWA

I recently setup an Exchange 2013 Server in an Exchange 2010 Environment.

All worked fine, but logging in to https://servername/ecp redirected me to the old Exchange 2010 Interface.

If you have this problem, you can add the Exchange Version to the URL using “?ExchClientVer=15″.

So https://servername/ecp?ExchClientVer=15 will redirect you to the correct Management Interface.


No bootable drives have been found or no OS

Provisioned a XenApp 6.5 Server as a golden image wiyh Citrix Provisioning Services 6.1, was getting the following error. when trying to PXE boot off the vDisk after the initial image creation.

“No bootable drives have been found or no OS”

Found that because the golden 2008 R2 Image had the 100mb System Reserved Partition which contains the boot files The Vdisk image wouldn’t bring across the 100mb partition.  and therefore couldn’t boot. So I removed the partition and recreated the Vdisk to fix the problem. below is how you delete the partition.

Here is how to delete the partition:

1) Open a command prompt with administrator privileges (right click => run as administrator)


bcdboot c:windows /s c:

You should get a message similar to:

Boot files successfully created.

2) Open the Disk Management GUI (you could use diskpart for scripts), locate the C: partition right-click and select “Mark Partition as Active”, select yes to the “do you want to continue message”

3) Reboot to confirm that everything is ok.

4) In Disk Management you can now delete the 100Mb System Reserved partition by right clicking on it and selecting “Delete volume”

Netgear DG834 Bridged Mode (PPPOE)

If you own a Netgear DG834 ADSL router, and for some reason you’d like to terminate the PPPoE connection on another device, you’ll probably be disappointed as we first were to see that there is no “bridge mode” option in the web interface, even after a firmware upgrade followed by a factory reset.

This doen’t mean however that you can’t. It’s just undocumented… Here is how I finally got it up & running, after trying several procedures found here and there. you need to get to the mode page which is hidden from the menu’s by going directly to the url. ; on that page you can set the device to operate in “modem-only” mode.


2008 R2 SP1 kills Remote Desktop Services

Ran into this problem this morning when installing 2008 R2 SP1. Service Pack installs successfully, but cannot login via remote desktop services. Checked the eventlog remotely. found the following in the application log. Event ID 7034 reports which doesn’t help a lot.  Also Event ID: 1000 reports an application error.

Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66
Exception code: 0xc0000005
Fault offset: 0x000000000000a793
Faulting process id: 0xf80
Faulting application start time: 0x01cd1e4172e7da89
Faulting application path: C:WindowsSystem32svchost.exe
Faulting module path: C:Windowssystem32rdpcorekmts.dll
Report Id: eec16b12-8a34-11e1-8e8c-0050568ac72d

after a quick google I found the following thread

And the following fix.

You need to run this with a user that is an admin on the target system.
Copy psexec and rdpcorekmts.dll (the new version) to a folder.
Create a file named servernames.txt and add the name of the server(s) you want to fi
Create a start.cmd file edit it and add the following:

@echo off
Echo ****************************************************
echo * This process will update and change the file rdpcorekmts. *
echo * If you don’t want to do that, ‘X’ out now                 *
echo ***************************************************

:stop remote desktop services for /f %%i in (servernames.txt) do psexec \%%i net stop “Remote Desktop Services” /y

:Take Ownership for /f %%i in (servernames.txt) do psexec \%%i takeown /F c:windowssystem32rdpcorekmts.dll

:Change permissions to full for /f %%i in (servernames.txt) do psexec \%%i icacls c:windowssystem32rdpcorekmts.dll /grant administrators:F

:Copy in newer version for /f %%i in (servernames.txt) do copy rdpcorekmts.dll \%%ic$windowssystem32

:Change permissions back to read-only for /f %%i in (servernames.txt) do psexec \%%i icacls c:windowssystem32rdpcorekmts.dll /grant administrators:R

:start the service back up for /f %%i in (servernames.txt) do psexec \%%i net start “Remote Desktop Services” /y

echo * Remove the names of the affected servers in the file Servernames *

Echo *Should be all done now. *
echo **************************

pause exit

Doubleclick start.cmd

You should now be able to login to your server.

Sysprep 2008 / 2008 R2

I was looking to sysprep a 2008 server today and I went to the installation DVD and couldn’t find sysprep. A quick google later and a bit of poking around revealed that sysprep is now installed by default on Windwos Server 2008. You can find it at:


The experience is also streamlined considerably. Simply run sysprep.exe above and you are presented with:

Check the “Generalize” checkbox (regenerates system SID), change the Shutdown Options to “Shutdown”, and click OK. The system will go through the sysprep process and shut itself down.

Moving MYOB EXO to a new Server

Make a copy of the existing payroll directory and past it onto the new server and required install location.

Please download the application for the following location – only install payroll from the selection menu. Install it over the top of the folder copied from the old server.

Ensure a share with full read, write privileges is placed over the payroll folder

  1. From the existing workstations re-map the existing setup to the new server payroll directory
  2. From within the mapped drive run the network.exe – this will ensure the linkage and all components are correct
  3. Test the application by launching from the desktop icon created.

Confirm all workstations point to the correct share. You shouldn’t need to reinstall the workstation clients.


Moving or Reinstalling National Online (NAB Online)

To move the National Online software, you will require the following:

  1. National Online installation CD.  If installing to Windows 2003 Server ensure you have Version 8.11+. for 2008 you will need Version 9.2+
  2. Some form of backup medium such as USB Memory Stick, zip disk, blank or network access.

Files to save:

  • C:Program FilesNational Online BankingNATIONAL-ONLINE.GDB – This is the most IMPORTANT file (as it contains your data).
  • C:Program FilesNational Online BankingUPGRADE – back up this folder and all of its contents.
  • C:Program FilesNational Online BankingARCHIVE – back up this folder and all of its contents.
  • C:Program FilesNational Online BankingBackup – back up this folder and all of its contents.

Summary of Steps required to move National Online Software

  1. Save the above files from the existing directory on your computer.
  2. Install National Online on your new computer, using your installation CD.
  3. Once setup is complete click Finish to launch National Online you will then be prompted for your registration ID and password. DO NOTenter reg ID or password.  Press Cancel
  4. Copy all the saved files and folders from earlier to the following location:
    C:Program FilesNational Online Banking (When prompted that the files already exist, select ‘Yes to all’ to replace existing files.).
  5. Launch National Online from the shortcut now on your desktop.
    On launching National Online NAB online should upgrade to the latest version that was installed.

Should you have any problems during the installation, or on completion you do not get to your ‘Login and Password’, call theNational Online Helpdesk on 1300 652 565. they are very helpful.

Installing HP Universal Driver on Terminal Services and Citrix.

The HP Universal driver when installed using the GUI can be very clunky, the notifications are a pain, and you probably just want to install the driver and not a printer.

Install the driver from the command line to avoid the notifications

start /wait install.exe /q /h /dm /npf

and to delete the printer with powershell use:

gwmi win32_printer | where {$ -like “HP Universal*”} | % {$_.delete()}