Top IT Providers

Outlook 2010 Zoom Glitch

I recently ran into an issue where a client asked to have the default zoom size increased when reading emails in Outlook 2010. Although Outlook 2010 has both a zoom slider and a zoom button when reading emails, this feature does not hold as a default. I have checked around and my conclusion is that this is a glitch as there is no way to fix this natively in Outlook. Interestingly enough it works fine in Outlook 2007 and 2010 Beta.

 

So here is a little VBA script that addresses this zoom issue. You are more than welcome to use it if the situation arises. Hopefully MS will fix this glitch. I have included both the script and the directions to add it.

 

Script:

Option Explicit

Dim WithEvents objInspectors As Outlook.Inspectors

Dim WithEvents objOpenInspector As Outlook.Inspector

Dim WithEvents objMailItem As Outlook.MailItem

 

Private Sub Application_Startup()

Set objInspectors = Application.Inspectors

End Sub

 

Private Sub Application_Quit()

Set objOpenInspector = Nothing

Set objInspectors = Nothing

Set objMailItem = Nothing

End Sub

 

Private Sub objInspectors_NewInspector(ByVal Inspector As Inspector)

If Inspector.CurrentItem.Class = olMail Then

Set objMailItem = Inspector.CurrentItem

Set objOpenInspector = Inspector

End If

End Sub

 

Private Sub objOpenInspector_Close()

Set objMailItem = Nothing

End Sub

 

Private Sub objOpenInspector_Activate()

Dim wdDoc As Word.Document

Set wdDoc = objOpenInspector.WordEditor

wdDoc.Windows(1).Panes(1).View.Zoom.Percentage = 140

End Sub

 

Instructions:

1. While in Outlook 2010 press Alt-F11 to invoke the VBA Editor
2. On the left side locate ThisOutlookSession (you may have to open up Project1)
3. Double click on ThisOutlookSession
4. On the right window of the screen copy and paste the code above
5. Then click Tools -> References
6. In the scroll box scroll down and select Microsoft Word 14.0 Object Library
7. Click OK and make sure this is now added
8. Click on Save
9. Quit VBA Editor Alt-Q
10. Now you should be back in Outlook
11. Select File -> Options -> Trust Center
12. Click the Trust Center Setting button
13. Select Marco Settings
14. Select Enable All Marcos (Not recommended…)
15. Click OK twice
16. Close and exit Outlook
17. Restart and open an email

 

You will notice the last line of code “wdDoc.Windows(1).Panes(1).View.Zoom.Percentage = 140” The number is the zoom percentage. You can change this if you would like and test it out. See which one works best for you.

Also if your organization has a class 2 or class 3 digital certificate you can digitally sign the macro. With a digitally signed macro select “notification for digitally signed macros…” in step 14 above.

 

Debugging Windows 7 Blue Screen of Death (BSOD) Part 1

  

Part One:

Through the years the Microsoft Windows Operating System (OS) has grown from 16-bit to 32-bit and now to 64-bit. Even though Microsoft has added features and security settings that have caused the OS to swell in ize, it is actually much more stable and harder to crash than previous versions. The newest OS, Microsoft Windows 7, uses the User Mode and the Kernel Mode protection systems to allow multiple applications to run at the same time while greatly reducing the chance for a system crash. But crashes do happen, especially the Blue Screen error affectionately known as the “Blue Screen of Death” or BSOD. Whether or not you have a helpdesk to call for your network support needs, figuring out the cause and troubleshooting BSOD can be exhausting. We have found that the most common causes of BSOD in Windows operating systems are faulty device drivers, but it can also be caused by software or hardware errors, Windows installation errors, startup errors, or intermittent errors.

So knowing what causes Windows 7 to crash is the first step. The next step is finding the best way to stop these crashes from happening. Keeping your system updated is a good start. This means Microsoft updates for Windows and other software, such as Microsoft Office, third party drivers – especially video drivers, hardware drivers and firmware, and BIOS. Check your system by running a virus and spyware scan. Check the computer for hardware or memory errors – memory faults can easily cause Blue Screen errors. Another way to stop these crashes is by undoing recent changes with System Restore or booting into safe mode to troubleshoot the startup or driver issues. You can also try and load the default BIOS settings as resource conflicts and timing issues can be caused by incorrect BIOS settings. But in reality the most common cause of blue screen errors is a faulty device driver. Outdated, incorrect or corrupt drivers can cause the system to encounter a Stop error, resulting in a BSOD. The easiest way to fix a BSOD is to reinstall and update the systems device drivers.

So you’ve done all of the above but are still experiencing crashes and blue screens? Troubleshooting the BSOD error can be difficult, but Microsoft has given us some tools to uncover and address the source of the operating system crash. The first thing to do is to setup the Startup and Recovery settings as shown in Fig 1. 

 

By unchecking the ‘Automatically restart’ option the computer will no longer automatically reboot after a BSOD and we can take a look at the crash screen and get the error message and stop error code (Fig 2). This also allows us to get a physical dump or ‘Minidump’ of the processes that were running and/or loaded in memory. Note: Although we will get both a Kernel dump file and a Minidump file for each crash the system will only save the last Kernel dump file. You will have a Minidump file for every crash event.

 

There are a myriad or stop error codes and messages. I will list the common ones below and what they reference.

Stop Code : STOP 0x0000000A IRQL_NOT_LESS_OR_EQUAL	This error is caused by a buggy device driver or an actual hardware conflict. If you’ve recently added new hardware to your system, try removing it and see if the error goes away.
Stop Code: STOP 0×00000019 BAD_POOL_HEADER	This is, perhaps, the most obscure error message. In most cases, if you receive this error, it’s related to the most recent change you’ve made on your system. Try undoing the change to get rid of the error
Stop Code: STOP 0×00000024 NTFS_FILE_SYSTEM	This error indicates a file system or hard disk corruption. If your system is bootable, run CHKDSK /F on all of your partitions immediately. If your system isn’t bootable, you may have to try repairing the OS or reinstalling.
Stop Code: STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE	Just as the name implies, this error indicates that Windows is having trouble reading from the hard disk. This error can be caused by a faulty device driver, defective cable, or bad hard drive. It could be an incorrect ARC path or Boot.ini reference. If you’ve checked for these problems, but are still receiving the error, check to make sure that a virus hasn’t destroyed your boot sector.
Stop Code: STOP 0×00000080 NMI_HARDWARE_FAILURE	This is a generic error message in which the hardware abstraction layer can’t report on the true cause of the error. In such a situation, Microsoft recommends calling the hardware vendor. This error can sometimes be caused by defective or mismatched RAM.

 

A complete list of stop codes and descriptions can be found on the MSDN Library site located here: http://msdn.microsoft.com/en-us/library/hh406232(v=VS.85).aspx

Although these error codes are helpful, we can also check the Windows event logs for more information related to the crash (Fig 3).  You should check all system and application events that preceded the system crash.

 

We can also look at the error report generated by Windows before sending it to Microsoft (Fig. 4) to see if it sheds any more light on the error and for the location of the Minidump file.

 

An important point that is not well known is that most crashes are repeat crashes. This is because most administrators are not able to resolve system crashes immediately. As a result those crashes unfortunately tend to occur again.

Hopefully these steps will assist you in resolving the BSOD error.

In the next installment of this blog we will use the WinDbg utility to analyze the MEMORY.DMP and Minidump files to further track down the cause of the system crash.

IT Checklist: Moving to a New Office

When you’re moving to a new office, you consider a number of things: How much space do we need? Do we need new furniture? Will we have room to grow?

These considerations are important, but even more vital to your relocation is the moving and setup of your technology. Without technology, most businesses cannot operate. Can you work without the internet? Without the phone? Without access to your network?

Review this checklist at least eight weeks before your move to ensure you’ll be fully operational at your new office.

1.    Do a Walk-Through. Identify where your PCs, printers and other systems will sit in the new office. Determine if you need new outlets installed to accommodate your equipment. Keep in mind your servers should not share outlets with other equipment. You’ll likely need a dedicated 30 Amp circuit for servers in a room that you can temperature-control.

2.    Assess the Telephone System. As your company grows, your telephone system must grow with it. Some providers limit the flexibility of phone systems to force you to purchase a whole new system as your company expands. If you’re going to purchase a new telephone system for your new office, make sure it’s flexible. Also, purchase you’re a system that can make calls through the Internet. Cheap internet calls are the way of the future, so even though you may not use this service much at first, you don’t want to pay to upgrade later.

3.    Choose Phone Features. Identify features you can’t live without and those that aren’t essential. Find out what features carry more fees. Here are some features for you to consider:

• Call transfer, conference and forwarding
• Hunt groups or Pick-up groups
• Voicemail
• Auto attendant (press 1 for billing, 2 for sales, etc)
• Hold music
• Reporting & analytics
• Call recording
• Remote connection for mobile devices

4.    Choose Extensions. Do all employees need their own extensions? Each additional line will carry an extra cost. If you don’t do most of your work over the phone, you may only need a few phone lines.

5.    Order Call Redirection. If you don’t get to keep your old phone number, divert the calls automatically through call redirection. Your telephone provider can set this up. Don’t forget to change your address and phone number on your website, business cards and stationery.

6.    Check the Cabling. If your network runs in Gigabit speeds, your cabling must be a minimum of CAT5e or CAT6.

7.   Choose the Type of Data Connection. Talk to a managed service provider to determine which connection type will best suit your needs. For example, if you have a high level of data and voice throughput, choose a T1 line, which carries 24 phone lines. This option can get pretty expensive. Broadband service can come from your cable TV company, phone provider, and more. It can come in digital T1 or T3 lines, DSL, or fiber optic connections.

8.    Plan Your Timing. It can take at least two weeks for your new service provider to install and get your systems running properly. Time your move properly so you’re not moved in and unable to run your business.

9.    Update MX Records. When the broadband connection to your new office changes, the MX records will need to be updated. Although this usually happens quickly, it can take up to 48 hours to take effect. Consider requesting the update on Friday before you close for the day. This way, come Monday morning, you should be all set. If you need help, contact an experienced IT company for help.

10.    Back Up & Pack Up. Back up your systems before you unplug. Label everything so that reassembly is a cinch. Take proper care in packing and moving your technology safely.
The key to any office move is organization. Plan ahead with your technical service providers to ensure your move goes smoothly.

The key to any office relocation is organization. Plan ahead with your IT services provider to ensure your move goes smoothly

Windows Server 2008 Domain Controller Boots to Black Screen with Mouse Cursor

In the last two days, we’ve had two Windows Server 2008 servers reboot to a black screen with a mouse cursor, but nothing else. The problem is that the System Reserved partition is assigned the C: drive letter, and the boot partition (the one with the Windows folder), is assigned the next available drive letter.

To resolve the issue, boot into Windows RE (stands for Recovery Environment). When you reboot the server, you’ll get two options. One to “Start Windows Normally”, the other says “Launch Startup Repair (recommended)”. Choose Startup Repair. After entering the local Admin password (which on Domain Controllers is the AD restore PW), you’ll see a Window with a few options. Click Command Prompt to open a DOS prompt Window.

At the DOS prompt, DIR C:. You will probably see volume information that says System Reserved and no files. If you do see a Windows directory on the C: drive, then you probably do not have the problem described in this article.

At the DOS prompt, enter REGEDIT. This will open the Registry Editor. Browse to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. Look for the values named \DosDevices\drive letter:. We need to find the boot partition’s drive letter. It will usually be assigned the first available drive letter after C: From the command prompt, perform a directory listing of each drive letter after C: until you find the drive with the \Windows and \Users directories. This is the real C: drive. Note its drive letter.

In Registry Editor, rename the value \DosDevices\C: to \DosDevices\J: (or any other available letter). Next rename the value representing the real C: drive to \DosDevices\C:.

Reboot your computer and you’re all set. We still attempting to determine what’s causing this, but following these steps will get a Windows server having this issue up and running promptly.

Bill Gross, Technical Services Director
MCSE: Security, RHCE, VCP4
IT Solutions Consulting, Inc.
http://www.itsolutions-inc.com

8/9/2011 Update:

We still have no idea what’s causing this issue, but it’s happened on a few more of the domain controllers we manage. Fortunately, using this method we’ve been able to get them up and running pretty quickly. That being said, I discussed this with a colleague, Mike Brehm, who pointed out that when I run regedit from the Recovery Environment, I’m actually editing the Recovery Environment’s registry, and not the Windows installation’s registry. (The Windows installation’s registry can be opened by running a reg add command). The server Mike was working on was not fixed by the Regedit trick, instead he booted into AD Restore Mode and reinistalled VMware tools. That resolved the issue in his instance. Other servers experiencing this problem have been fixed, at least temporarily, using the Regedit method, though sometimes the engineers implementing the solution had to try it a couple of times. I used the fix on two servers, it worked the first time on both, but the issue did recur on one.

So, we now have an intermittent problem of unknown cause, that can apparently be resolved by a trick that, based on our understanding of Windows, shouldn’t work.

All servers experiencing this problem have been Domain Controllers running Windows Server 2008 on ESX and ESXi 4.1. So, maybe it is does have something to do with a VMware driver, and reinstalling VMware tools is a true fix, and whatever happens with my registry fix is pure luck.

Excel 2003 Slowness on Windows Servers Since June 15, 2011

Thanks to Microsoft, we may have to deal with some Excel 2003 issues in the future.  The issue began when Microsoft released a patch for Office 2003 (Excel) on June 15, 2011. When running Excel 2003  on PC (XP or Win 7) and opening Excel files on a Windows Server 2003 environment, there is a huge delay when the file is 500KB and greater.  It can take up to 3 minutes or longer to complete (or just freeze up completely).  As a network services engineer, it is not uncommon to run into issues like this. Below is one solution I have found to get rid of the delay.

Solution:

-          Log on to the client PC, launch Add/Remove Programs and remove the following Microsoft Office 2003 Updates (Post SP3 Updates).

• Remove the Office 2003 KB2541025 Update first, then close out of Add/Remove Programs
• Launch Add/Remove Programs and you will see the Office 2003 KB250278 Update appear, remove this update.

Once the 2 updates are removed in the order above, you can launch Excel 2003 and the delay will be gone. It is a good idea to block these patches going forward.

Must-Have tool for troubleshooting wireless networks

If you don’t already have a tool in your bag of tricks like this one, I encourage you to download and install inSSIDer 2.0 from the folks at Metageeks.net. (http://www.metageek.net/products/inssider/)

The tool gives you some very valuable information about ALL the wireless networks visible (and sometimes invisible) to your wireless NIC.

MAC addresses, broadcast channels, privacy type, even WAP Vendor all on display.  The Channel Display makes it easy to see how different networks broadcast on conflicting/interfering channels, as well as comparative strength of WLAN signal strength.

 Plus, it’s free!

FileMaker Feud Hosted By MightyData at DevCon

Most of you know MightyData as a FileMaker Consulting and Development Company. But did you ever thing of them as game show hosts? Well you can now. At this year’s DevCon, they are hosting the FileMaker Feud. Similar to the Family Feud, contestants will partake in “FileMaker” topics and “feud” it out.

Some of the prizes include iPads, iTunes gift cards, iPods and even some FileMaker Training. So if you’re going to DevCon and want to play or watch, check out all the details on FileMaker Feud.

How To Buy EMR Equipment

As the use of electronic medical records becomes widespread, so does the importance of EMR software and equipment. Medical equipment often comes with steep price tags, so to make sure you are spending your budget efficiently, here are some ideas on how to buy EMR equipment:

Financing. Companies specialize in financing for medical equipment. These companies understand the intricacies of the medical industry and specialize in working with doctors and medical facilities. Research and select a medical equipment financing company. Look into their customer reviews and choose a company with which you are comfortable.

Loans. Before you apply for a medical equipment loan, check if you can pre-qualify.  Identify what equipment you need to purchase and how much money you will require. Determine your FICO score, whether you will take the loan personally or through the company, and identify any assets you could pledge for the loan. Take the proper steps to ensure you are not applying for a loan you cannot afford.

Leasing. Should you opt not to finance your purchase, look into leasing EMR equipment. Leasing allows startup practices to build profits instead of spending them. Leasing also comes with tax breaks, such as dollar-for-dollar tax write offs on your payments. Further, leasing allows you to upgrade your equipment as it becomes obsolete.

Whatever you financial situation is, you cannot ignore the importance of EMR equipment. Analyze your financials and identify what purchasing option works for you so you can outfit your medical practice with the best EMR equipment available.

Microsoft Lync Event – New York

If you’re in the New York area and have an interest in Microsoft Lync and Unified Communications, then you might want mark off May 12th on your calendar. Chips Technology Group, a computer consulting firm in Syossett, NY is hosting an event all about Microsoft Lync.

Along with a night of learning, there will also be games, refreshments and fun. The even is sponsored by Jabra and Polycom and if interested you can register here.  The doors will open at 6pm and won’t close until 10, so check it out if you can.

New Email Encryption Offering!

IT Solutions has recently begun to offer email encryption services. With today’s online and mobile society, confidential data is always on the move and always at risk. Our email encryption product is a cloud-based email security solution which protects valuable and confidential messages from being seen. This security solution can encrypt outgoing emails based on keywords in the message – for example, the user types “encryption” in the email body and the email is automatically encrypted. It can also detect credit card numbers and automatically encrypt the message based on that or any number of criteria. The recipient gets an email saying that an encrypted message is waiting for them on a web portal and they click the link to retrieve it.

Easy to implement, manage and use, email encryption is a scalable, reliable and secure service which protects your most valuable and confidential data. Add the ultimate message protection for you and your clients and vendors. Contact your VCIO today or call 1.866.PICK.ITS to learn more.