A 2008 R2 Terminal Server with ACT 2012 installed, had been setup for Outlook Syncronisation. This gives it the user the opportunity to add Emails to Act Contacts. To set this up

Close Outlook.

Open up Act to the correct Database

Click on Tools then Preferences then Email and Outlook Sync. Then click on Email System Setup

Run through the Wizard for Outlook and add the correct PAD file. If you remove and readd the PAD file it refreshes the address list. You can leave all the other fields as defaul then Finish

Reopen up outlook and you should see the following, under Add In’s for Outlook 2010

After doing this , if the Quick Attach part dissapears randomly in Outlook sometimes you need to re add the ACT address book

To do this , Open Outlook 2010

Click File , Account Settings , Account Settings Again

Go to the far right address book tab. If you don’t see the ACT! Address Book

Go to New , Addiotinal Address Books, Choose ACT! Address Book. It will ask you for the PAD File, make sure this is correct then click Close and Next

Close down Outlook and Reopen

 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

***PLEASE CHECK THE BOTTOM OF POST FOR UPDATE!!***

Recently when setting up a domain which was already being filtered and hosted by Microsoft forefront into Office 365, Upon changing the nameservers, the MX records correctly updated from mail.global.frontbridge.com to 365’s one (domain.outlook.com) , however the email still flowed to the host setup up in Frontbridge instead of the 365 Mailbox

The local UK support number for Office 365 : 02034506455 did not pick up after 2 x 30minute sessions with holding music!

Next I tried Frontbridge International Support : 0018662917726 ( Which is free to call via Skype from anywhere ! ). Luckily a helpful techican ‘Mudassir Ansari’ helped me with the following :

You can fix this issue by performing the following ( pretty sure this will work to BPOS as well as 365) :

Make sure your domain is verified in Office 365 and the correct DNS is set or nameservers migrated

Download and install the Migration Tools 32bit here : http://www.microsoft.com/downloads/en/details.aspx?familyid=9ed5f4c1-7f0b-4506-a214-32093af6147a&displaylang=en

Go into your frontbridge control panel and disable the domain , then delete it!

Open a Power Shell Window

Enter this command : $LiveCred = Get-Credential

Enter your office 365 administrator Details

Enter this command : $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Then this command : Import-PSSession $Session

Then this command : Set-AcceptedDomain **ENTER YOUR DOMAIN HERE** -OutboundOnly $true

Wait 2-3 Minutes

Then this command : Set-AcceptedDomain **ENTER YOUR DOMAIN HERE** -OutboundOnly $false

Then wait for Microsofts Cloud SMTP Servers to Update , in my instance it took 15 minutes

**** UPDATE — 16/11/2012 *****

Upon trying this recent with a customer , the Domain removed off FrontBridge Online Protection Service ( FOPE ) however did not readd itself to 365 after running the above command

The issue was the domain was duplicated in FOPE for some reason

  • Login to Admin Panel of 365 as an account administrator
  • Choose – Exchange ( Outlook settings and protection. ) then Click Manage
  • Choose Mail Control on the left hand side , then Domain’s and Protection
  • Try Clicking on the “Configure IP safelisting, perimeter message tracing and email policies.” under Forefront Online Protection for Exchange ( on the right )
  • It will probably come up with an error
  • Click on the domain on the left hand side which should  be marked HOSTED
  • Change this to Share ( wait 30 seconds and change back to Hosted )
  • Log off then back in again and try to access the Configure IP safelisting, perimeter message tracing and email policies. which should work now and the domain should propigate



**** UPDATE — 23/03/2013 *****

As of the “new” office 365 (ie – the service based on Exchange 2013), there is a new process for swapping a domain from Frontbridge to Office 365. This replaces what we used to do for existing FOPE/Frontbridge customers.

The new process is actually very easy

  1. Change the MX record to the Office 365 MX record (domain-name.protection.outlook.com or similar)
  2. Disable the domain in Frontbridge/FOPE.
  3. Wait a couple of minutes and test mail flow. Email should start going to the O365 mailboxes.
  4. Remove the domain from Frontbridge.

Ref : Dan Furse @ Response IT!

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)

Further to my Easyspace post regarding TXT Updates , I tried to update TXT records for domain authentication for Office 365 on a new domain , however again, there was no where in plusnet’s manage DNS control panel to do this. A call on their support number, produced the fact they do not support TXT DNS Record updates.

Luckily in 365 there is another way to verify domain ownership which  is to use a low priority dummy MX record, which plusnet did allow. However … Microsoft utilise SRV records for Microsoft Lync to work. As Plusnet do not support these, or allow the changing of nameservers to Microsoft’s own ( Ns1.bdm.microsoftonline.com and Ns2.bdm.microsoftonline.com), I had to move the domain to 123-reg.co.uk a free transfer and allowed me to update the nameservers

All this would have been nice at : http://www.plus.net/support/hosting/domains/domain_admin_dns.shtml !

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: +2 (from 2 votes)

If you find Protrace files appearing on your desktop on your local machine or terminal server this is due to a database engine called Progress. If you open up the files which usually end in a .random number in notepad you should see a header such as :

PROGRESS stack trace as of Wed Nov 30 16:06:55 2011

From progress site  :

A protrace files (also called stack trace) is a report generated to aid in debugging by showing where exactly an error occurs. The last few stack frames often indicate the origin of the problem or the bug.  A protrace file is generated from a core file. A core file is generated by an error in a Progress executable.  A protrace file is a stack trace from a Progress session that had a serious error. The protrace file is created from a core file being ‘unwound’ by an operating system utility.

They are usually created when a user crashes out of a session or a session ends abnormally, so you can delete these of your own accord or forward them onto your database/program developer!

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently a client using an open source ASP CMS system to edit a website was having with the CMS’ page timing out due to script errors. It seemed it was timing out on the MCE editor part of the page. Checking the local firewall on the machine , disabling the anti virus did not resolve the issue. I then tried to VPN to another site , which used a different default gateway ( Router ) and it worked straight away.

Upon diagnoses of the local router a ‘BT 2Wire’, it seemed the advanced filewall settings where causing the issue. As soon as we turned off Stealth Mode it fixed the issue

http://btbusiness.custhelp.com/app/answers/detail/a_id/10866/~/editing-advanced-firewall-settings

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently a client had bought a Philips LFH2310/00 Dictation Foot Pedal to go with a Philips LFH9375/00 Dicatation Device

The dictaphone came with SpeechExec Dictate software, however after playing around with the settings, it seems the foot pedal was only recognised in ‘SpeechExec Dictate Pro‘. To purchase this Pro license it was going to an extra cost around £135

One issue I had with this software anyway was that you could not assoicate .DSS or DS2 files with the Philips Speed Exec Player.  This means you would have to save the file on your computer and open through the Philips Speed Exec Player each time instead of just doubling click on the DSS File.

After some searching around, I found some free Software which works with the foot pedal and file assoication for anyone else with this issue here’s the link : http://www.nch.com.au/scribe/index.html

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Most software that comes with nework printers ( HP, Brother or Lemark ) addprinters through a WDS Printer Port Interface. This is good when it works, because printers advertise themselves on networks so windows can find them as well as their device driver. Sometimes I find the WDS Service stops on local machines causing issues. Trying to diganose whether the problem is communication related between the computer and the printer or an actual printer issue is hard through WDS. If I go get issues I like to find the IP address of the device to ping it, as well as remapping the device through a Local TCP/IP address instead of WDS. To find the IP address of a printer using WDS in Windows 7 or Visata. If you right click on the print in Device and Printers, and click properties. You should be able to see the Web Services Tab. Click on this and at the bottom should be the IP Address. If the device responds a ping reply, then try changing the port to TCP.

VN:F [1.9.22_1171]
Rating: 8.6/10 (12 votes cast)
VN:F [1.9.22_1171]
Rating: +4 (from 6 votes)

When trying to open my RDP Client MSTSC.exe , it gave me the follow error: “Remote desktop connection has stopped working” , after looking at the crash it seemed the fault had occured with mstscax.dll

I found the file from a working Windows 7 SP1 32bit machine here : http://pariswells.com/upload/mstscax.zip and copied and replaced the dll in C:\Windows\System32\mstscax.dll , which fixed the issue

To get round the trusted installer , you will need to give yourself ownership of the file , then change the security settings so you have full write access to it

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently after trying to set file associations for a .accdb file ( Access 2007 / 2010 file type ) , when trying to open an .accdb file it would display the .accdb “is not a valid Win32 Application”.

When trying to right click on the file and choose “open with” and find the MSACCESS.exe executable in C:\Program Files\Microsoft Office\Office 14 ( 2010) Office12 ( 2007\ it would still display the same error message. If you opened Access up and went to file open , and find the file manually it would open the file correctly. The issue is the file associations are set in Explorer , so you have to reset the file associations, then restart explorer for them to work.

Go to Regedit and deleted the following key : HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.accdb

Then download this , and run it :

http://www.pariswells.com/upload/fixaccdbfileassoc.zip

Now go to CTRL ALT Delete , Task Manager , Find Explorer.exe under processes, End the process. Then go to File and Run and type in Explorer.exe and press enter. You should now be able to open your .accdb files. A restart would of also performed this acction

VN:F [1.9.22_1171]
Rating: 8.9/10 (7 votes cast)
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)

I was installing Blackberry Enterprise Server 5.03 on a Small Business Server 2008 Box. Following through the receommend guide here http://www.edutech.me.uk/bes-express/installing-bes-express-on-sbs2008-server/

However after the reboot of the server it brought up the Database Management prompt and would not allow me to select a Local Server even though I had asked the Blackberry setup to create a New Database. Looking through the SQL Server 2005 Configuration it didn’t look like the BLACKBERRY Database had been setup. After a brief look online it looks like the blackberry account ( besadmin ) setup needs to modify through Active Directory via the following:

Account tab > Account options: Select option: Use Kerberos DES encryption types for this account.

I made the change, uninstalled the software and went through re installation again , and after the reboot , the database had been created this time and setup was able to complete

VN:F [1.9.22_1171]
Rating: 8.5/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)