July 7, 2014 By

Office 365/2013 Errors 30134-4 and 12007-4

We had a machine this morning that was being switched from a Office 2010 Home & Business PKC install to Office 2013 (via an Office 365 Midsize Business subscription). After uninstalling Office and rebooting the PC, the click to run installer for 2013 wouldn’t run – it was throwing error 12007-4. After some initial research, we ran the Microsoft Fix It tool for fully uninstalling Office, then ran Ccleaner to pick up any remaining pieces in the registry, and rebooted again.

After trying to run the installer this time, we got an error 30134-4, which we were unable to find any references to online. After some trial and error, this appears to be some related to some sort of DNS resolution issue – everything else was working fine network-wise, with the exception of this installer. Upon temporarily changing the DNS to Google (8.8.8.8 and 8.8.4.4), the Office installation went off without a hitch, and reverting back to the original DNS servers didn’t cause a problem afterwards.

Filed Under: Blog
June 17, 2014 By

Disabling Local Autodiscover During Office 365 Move

A common problem when migrating to Office 365 from an in-house Exchange server is configuring local clients to not point at that local Exchange server.

When you initially install Exchange, a couple of things happen from an autodiscover standpoint…

  • A directory named “AutoDiscover” is configured in IIS on the server.
  • An AD object called the service connection point (SCP) is created, which contains the authoritative sources for autodiscover information.

We need to clear out this SCP object in order to allow the clients to point out to Office 365 to obtain their configuration information. This can be done by using the Set-ClientAccessServer cmdlet. Execute the following command in the Exchange Server Management Shell (warning – don’t do this if you’re using the Microsoft Online Migrations Tool!):

Set-ClientAccessServer -Identity “SERVERNAME” -AutoDiscoverServiceInternalUri $NULL

If you’re running multiple Exchange servers, you may have to do this for each server in the directory.

Filed Under: Blog
May 19, 2014 By

Setting Up A Fujitsu S500/S510 On Your Mac

As those of us who have used them know, Fujitsu’s ScanSnap line of desktop scanners are great. They’re my go-to recommendation for all of our IT clients. Lawyers love them.

Unfortunately, if you’re trying to set up one of these older models on a Mac, Fujitsu’s recommended software doesn’t work. It results in the software not being able to sense the scanner.

Here’s how to fix it….

That’s it! After installing this newer version of the ScanSnap Manager software, your ScanSnap should be as good as new on your Mac.

Filed Under: Blog