Welcome to Port Seven!

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.

Creating An After Hours Workflow In ConnectWise

How do you handle your after hours workflow? Can customers contact you via various channels (e-mail, phone, etc), or do you want to route all after hours contact through a specific channel to ensure you hit your SLAs? We try to route everyone to phones for after hours support, which gets in touch with whoever our on-call tech is for that time. However, some folks will still try to contact through your other support channels (primarily e-mail from our experience), so you want to make sure they know how to contact you in the case of an emergency.

Here’s how to set up an after hours e-mail workflow in ConnectWise…

Go to Setup Tables > Workflow Rules

Screen Shot 2014-06-20 at 10.03.03 AM

Create a new workflow rule called “Inform clients of after hours request”. Make sure the Table Reference is set to Service Tickets (since that’s what we’re firing off of), and set the location/department/service board to your standard support board. Check the Activate box, and we recommend running every 10 minutes during 24 hours to balance processing time with load on the CW server.

Screen Shot 2014-06-20 at 10.04.14 AM

 

Create a new event with the below properties (Ticket in “new” status and created outside of business hours).

Screen Shot 2014-06-20 at 10.09.26 AM

Save and exit the event, then select Edit Actions and create a new action. Create an e-mail with the settings in the below screenshot, and format the e-mail however you prefer.

Screen Shot 2014-06-20 at 10.10.50 AM

That’s it! Your workflow will now fire off whenever a client sends in a ticket after hours (as defined by the business hours in your Location record).

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 […]

Continue reading...

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 […]

Continue reading...