Monthly Archive for May, 2012

Update rollup 2 for Exchange 2010 Service Pack 2 (KB2661854) ended prematurely

When you are trying to install Update rollup 2 for Exchange 2010 Service Pack 2. The setup will stop and display the above image.

This is due to UAC and you will need to run the update as administrator. You normally do this by right click the exe and select “run as administrator”

But this can be as this update is not a exe but a msp file.

To fix:

I have download the update rollup to c:\installs

1)Run a command prompt as a administrator (Find the command prompt in the start menu and right click it and select “Run as administrator”)

2) Change to the installs directory and execute “Exchange2010KB2661854-x64-en.msp”

The update rollup should install successfully. It make take a long to complete as is has to generate a lot of .net code and images

10,897 total views, 1 views today

HP Insight Deployment (RDP) and Sysprep not using the Correct servername when deploying Windows 2008 R2

If you are using HP Insight control 6.3/7 to deploy server via the Deployment console (Symantec Altiris) and deploying a windows 2008 R2 sysprep image with a image you have already capture. Once the job has completed it has not deployed any of the information from the sysprep xml file.The main thing you will notice is that the server has keep the server name of the original server which was imaged and the computer object in  Deployment console will change from the name you have chose to name of the original imaged server.Also you will get prompted to set the password for the Administrator.

There seem to be a bug in Version 6.9 SP5 MR1. The standard sysprep image job does not copy the sysprep.xml to the correct locations. The Job renames the sysprep.xml to a unattend.xml file and places it in %WINDIR%\System32\Sysprep directory. The problem is that when the sysprep job get to stage where it looks for the answer file for the windows setup, it looks for the unattend.xml file in the %WINDIR%\Panther directory.

When you run a capture image job to be use with a sysprep job. The system which is to be imaged is put in a sysprep mode so that it is ready to be imaged and then can deployed using sysprep. Before it is imaged the job inject a system built  unattend.xml in %WINDIR%\Panther director. So once the system has been imaged and has been rebooted it can turn the machine back to it pre sysprep state. The one thing it can’t do it guess the password and that why you are required to change the password for the administrator account.

To Fix this you first need to add a task and to the job after the system has deployed imaged so that it copy the file to the right location.

1)Using a Image explorer tool to browse the system iamge file to delete the unattend.xml file in the follow location:



2)Create a batch file in C:\Program Files\HP\RDP\Deployment Server called copyunattend.bat. Enter the following information assuming you c:\ drive is you system drive.

copy C:\windows\system32\sysprep\unattend.xml C:\windows\panther

3)Edit the sysprep job and add a new “run script” task

4)Select “Run the script from a file” and select the copyunattend.bat and make sure “windows” selected in the bottom box and click next

5)Select “Automation pre-book environment” and chose “WinPE Managed (64 Bit)” and click next.

6) Click next and click finish on the last windows.

7)The Task will be placed at the bottom of list you will need to move the task so it run after the “Distribute Disk Image”

This is also you should have to do.

There is seem to be no fix from HP or Symantec yet.

I found out about this issue form here:






106,620 total views, 3 views today

Cisco 7940 Freepbx

I have been trying to get a Cisco 7940 a friend has given to me to using with Freepbx. I am using PBX in a Flash.I have managed to get the softphones working with freepbx but had no luck with the 7940.

This is my first blog post to show i got it working!

Most cisco phone which have been working with cisco call manager or call manager express. Will be setup to use skinny protocol  and not SIP. A quick google search will show you can achieve this viaa TFTP server.

Once you have done this you will need the following to get the 7940 to auto regster with the freepbx.

  • DHCP Server
  • TFTP Server
  • Cisco Phone Firmware Files
  • Phone Config Files
1) Start of by creating the Extenison in the freepbx and assigning a strong password. With upper and lower case, a number and special characters like !
My settings are
ext 299:
Display name:office
SIP Password:Extpass203!
2)Setup a TFTP server, I have one running on my windows box which also run DHCP. I am running tftpd32 as you can view the log files to view which files the 7940 is requesting.
3)Setup a DHCP to give your phone a IP address automatically add “Option 66” Boot Server Host Name as give it the IP Address of the TFTP server. This tell the phone where to pick in config and firmware files up form.
4)You will need to cisco firmware files and example phone config files. You will need a smart net contract to find these.
5)You will need to place all the files in the TFTP server the following are the most import one:
  • The four firmware files (P0S3-8-12-00.loads,P0S3-8-12-00.sb2,P003-8-12-00.bin,P003-8-12-00.bin)
  • OS79XX.TXT ( This is the first file phone access to see if there is any firmware updates)(This should contain the firmware file name in my case:P0S3-8-12-00)
  • SIPdefault.cnf
  • SIP00B0D086BBF7.cnf  (This is the config file what the Phone Picks up to automatic auto register with freepbx, You will need to change the file name to mac adress of the phone)
6)Edit the SIP00B0D086BBF7.cnf  file so that it reflects the following settings:
proxy1_address: “
proxy2_address: “”
proxy3_address: “”
proxy4_address: “”

line1_name: “203
line1_shortname: “OFFICE
line1_displayname: “203
line1_authname: “203
line1_password: “Extpass203!

line2_name: “”
line2_shortname: “”
line2_displayname: “”
line2_authname: “UNPROVISIONED”
line2_password: “UNPROVISIONED”

proxy_emergency: “”
proxy_emergency_port: “5060”
proxy_backup: “”
proxy_backup_port: “5060”
outbound_proxy: “”
outbound_proxy_port: “5060”

nat_enable: “0”
nat_address: “”
voip_control_port: “5060”
start_media_port: “16348”
end_media_port: “20134”
nat_received_processing: “0”

phone_label: “FreePBX!
time_zone: GMT

7)The above setting point to the my Freepbx which in my example points to Freepbx ip adress of

8)If you power up the phone it should go and register with Freepbx!!


40,646 total views, 3 views today