Showing posts with label Microsoft office. Show all posts
Showing posts with label Microsoft office. Show all posts

June 25, 2016

Microsoft Outlook: 5 Common Errors and How To Fix Them

             5 Common Outlook Errors and How to Fix Them


Email is one of, if not still the most important communications tools for individuals and businesses today in the 21st century. Whenever it stops working, people start to get nervous. While there are many things that a user can do to mess up their email, many of these problems can be resolved with a restart of the software or the computer. 

However when the old standby of restarting doesn’t work, it is time to start looking into the issue a bit more deeply. Here are some of the most common errors and how to fix them found in Outlook 2007 and 2010:

1. Error message that reads: “Cannot open your default e-mail folders. The information store could not be opened.”
This issue can be fixed by first locating Outlook.exe that can be found here: C:\Program Files (x86)\Microsoft Office\Office14. Next, right click Outlook.exe and then click on Properties. On the Compatibility tab, clear the check box that reads ‘Run this program in compatibility mode’. Then click Ok and restart Outlook.

2. Error message that reads: “Your Microsoft Exchange Server is unavailable.”
This error is a bit trickier to resolve only because there can be many different causes. No data connection – test your SMTP connection using telnet. If you are unsure how to do this, Microsoft has published a handy-dandy guide on their TechNet site that walks you through this process: http://technet.microsoft.com/en-us/library/bb123686.aspx.

A. Office Outlook files are locked – there are times when .ost and .pst files are accidentally, or purposefully, set to read only. Check the permissions of these two files by navigating to: C:Users<username>AppDataLocalMicrosoftOutlook for .pst files and C:Program FilesMicrosoft OfficeOffice12 for .ost files. Make sure that neither is set to read only.

B. Third party applications are interfering with Outlook – many programs, including anti-malware solutions, can interfere with Outlook connecting to the Exchange Server. To check to see if this is the cause, start Outlook in safe mode. Outlook files are corrupted – this can happen after an upgrade is applied to Outlook. If any of the .dat files listed below are present they should be deleted or renamed.
  • Extend.dat – C:Documents and Settings<username>Local SettingsApplication DataMicrosoftOutlook
  • Frmcache.dat – C:Documents and Settings<username>Application DataMicrosoftForms
  • Views.dat – C:Documents and Settings<username>Application DataMicrosoftOutlook
  • Outcmd.dat – C:Documents and Settings<username>Application DataMicrosoftOutlook
All the files, with the exception of Outcmd.dat will be re-created. The Outcmd.dat file saves customized toolbar settings so if it is removed these settings will have to be re-applied.

3. Office Outlook will not open personal folders or personal folders do not show up in Outlook.
Personal folders are often the main cause of many problems related to Outlook. Microsoft has published the Inbox Repair tool, Scanpst.exe, that can be used to scan .pst and .ost files for errors in the file structure. If this is not intact, it will reset the file structure and rebuild the headers. This tool will only work on the files that reside on your computer’s hard drive, not the files on the Microsoft Exchange Server. This will also help to resolve the error message: “Cannot open your default e-mail folder.

4. Error messages that read either: “The action cannot be completed. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway” or “Your Microsoft Exchange Server is unavailable”.

This error occurs when Outlook is unsure of the default gateway address. The former is the error message that shows when the Outlook profile is configured automatically and the latter appears when the profile is manually configured. Both have the same fix.
  • To repair this you will need to edit the registry so clicking on Start and then Run is necessary.
  • Then, enter regedit in the Open box and click OK. Next, navigate to the registry key:
    HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0OutlookRPC
  • On the Edit menu, point to New, and then click DWORD Value.
  • Type DefConnectOpts, and then press ENTER.
  • Now, right-click DefConnectOpts, and then click Modify.
  • In the Value data box, type 0, and then click OK.
5. None of the authentication methods supported by this client are supported by your server.
This happens to people when they use their computer in multiple locations. For example, a laptop is taken home and connected to the home network or perhaps a computer is taken on the road. Basically, it comes from authentication rules for the SMTP server. When this error occurs go to the Account Settings tab and click on Change then More Settings. Now select the Outgoing Server tab. The option that reads: “My outgoing server requires authentication” and the one that reads: “Log on to incoming mail server before sending mail” should both be looked at. If there is a check in the option box remove it.

April 13, 2016

Office 365 Channels & Current Updates Explained

Office 365 Updates As Of April 12, 2016
  • Current Branch is now called Current Channel
  • Current Branch for Business is now called Deferred Channel
  • First Release for Current Branch is now called First Release for Current Channel
  • First Release for Current Branch for Business is now called First Release for Deferred Channel
Only the names are changing. The servicing model for each of these channels remains the same. We are in the process of updating our content, so you will continue to see the previous naming during this transition.
Last month, we started a community project to help IT pros with Office client deployments using PowerShell to streamline the process. For more details, see Office Deployment Scripts for IT Pros. A month later, it’s time to check in on some of the new developments with this project. As a reminder, all of the scripts are available on our GitHub repository and released under the MIT license.

Reorganized scripts

For starters, we’ve added a folder structure to help IT pros to find useful scripts quickly and easily. We’ve divided all scripts into different categories including:
  • Preparation
  • Information
  • Deployment
  • Management
  • Updates
By grouping similar scripts together, it’s easier than ever for you to find the one you need.

More documentation

We’ve also added a wiki to the repository that contains useful information designed to provide context for using these scripts in real-world situations. The wiki is your go-to source for all information related to Office IT pro deployment scripts. It holds information explaining completed scripts, upcoming scripts and general information around contributing to the project. So if you are interested in learning about the scripts that are available or learning how to run different scripts, you will now find all of that information in the wiki.
But it’s not all housekeeping; here are some of the new additions to the project.

Office 365 ProPlus Configuration XML Editor

The Notepad is either your tool of choice or a last resort for editing XML files, but without the red squiggly lines we have come to love in Office. If you have ever accidentally typed </congifuration> then the web editor for the Office ProPlus Click-to-Run Configuration.xml file is for you. This web page provides a graphical method to generate and edit the Office Click-to-Run Configuration.xml file.
The Click-to-Run for Office 365 Configuration.xml file is used to specify Click-to-Run installation and update options. TheOffice Deployment Tool includes a sample Configuration.xml file that can be downloaded. Administrators can modify the Configuration.xml file to configure installation options for Click-to-Run for Office 365 products.
The Click-to-Run Configuration.xml file is a necessary component of the Office Deployment Tool. Click-to-Run customizations are performed primarily by starting the Office Deployment Tool and providing a custom Configuration.xml file. The Office Deployment Tool performs the tasks that are specified by using the optional properties in the configuration file. For the Office 2016 release of the product, administrators can download the Office Deployment Tool from the Microsoft Download Center. We also took advantage of the awesome new Office UI Fabric project to hide our IT professional design sensibilities.
Deployment scripts for Office 2016 1

Reverse engineer your configuration

The Generate-ODTConfigurationXML PowerShell script queries the existing configuration of the target computer and generates the Configuration.xml file for Click-to-Run for Office 365 products. This XML is used with the Office Deployment Tool (ODT) to deploy Office Click-to-Run products. This script dynamically generates a Configuration.xml file to either install new or modify existing Office Click-to-Run deployments. This script is particularly useful when trying to deploy Office 365 ProPlus in environments where different languages are required. It allows you to dynamically configure Office based on the languages that are currently in use on the computer. More information can be found in the README.
Deployment scripts for Office 2016 2

Putting it all together

The Deploy-OfficeClicktoRun solution uses several scripts from the GitHub repository to create a complete solution to deploying Office Click-to-Run. The solution uses the Generate-ODTConfigurationXML function to generate the Configuration XML based on the current configuration of the user’s computer. It then uses the Edit-OfficeConfigurationFile functions to modify the Configuration XML to the desired state. Finally, it will utilize the Install-OfficeClicktoRun to install or modify Office Click-to-Run.
There are several examples in the folder that show different approaches:
  • Example Script 1: ExampleDeployGeneric.ps1—Provides an example on how to use the deployment scripts in one script to provide a solution for deploying Office Click-to-Run.
  • Example Script 2: ExampleDeployWithOfficeFilter.ps1—Provides an example on how to use the deployment scripts in one script to provide a solution for deploying Office Click-to-Run, which includes an example on providing custom configuration based on the location of the workstation in Active Directory.
More information can be found in the README.
Deployment scripts for Office 2016 3

Fallback to the CDN for updating mobile PCs

The Update-Office365Anywhere function is designed to provide a way for Office Click-to-Run clients to have the ability to update themselves from a managed network source or from the Internet, depending on availability of the primary update source. Setting the Office Click-to-Run update source to a local network source reduces the Internet traffic. However, mobile workers, who may not be in the office, may not get their PC updated. This script detects if the configured update source is available, and if it isn’t, it will update from the Internet. The script also has the ability to monitor the progress of the update and block the script from exiting until the update has completed. More information can be found in the README.
Deployment scripts for Office 2016 4

Get involved!

We strongly recommend that you check back often, as the existing scripts continue to evolve and new scripts are added on a regular basis. We would also like to hear from you on some of the current challenges you face with deployment and how we might be able to help by automating steps. Feel free to post your feedback and ideas on the Office 365 Network.
As a reminder, anyone is welcome to contribute to the Office IT Pro deployment scripts GitHub project, but we ask that you clone the Development branch to create a feature branch where you can make changes to existing scripts or create new ones. Information on contributing to the project can be found in this README.
Thanks for taking the time to catch up on the latest with this project. We hope that you will take advantage of these scripts and help us continue to improve on what is out there.
—Alistair Speirs, senior operations program manager for the Office Deployment team

April 4, 2016

Outlook Premium: Pricing, Details, and Features Released (Unofficial At The Moment)


Microsoft’s additional features in Outlook will be priced at $3.99 per month, according to an updated page on Microsoft’s website, uncovered today. 
Earlier this year, news leaked of a new, paid version of Microsoft’s Outlook.com email service, called “Outlook Premium,” which would allow users to set up custom domain accounts to serve as more professional email addresses (rather than @outlook.com, @live.com or @hotmail.com). However, while Microsoft confirmed the pilot program at the time, it didn’t offer further details on launch, pricing, or full feature set.
According to Outlook Premium’s landing page, users who choose to sign up for Outlook Premium will get five personalized email addresses, an ad-free inbox, and more, for $3.99 per month. However, the site notes that the entire first year will be free, with the subscription only kicking in afterward.
There is still no formal launch date for the service, which as of today requires that interested users request an invite to try out Outlook Premium, as opposed to being able to immediately sign up from the website. That link is here: https://auth.microsoftonline.com/PremiumOutlook.aspx?InviteId=6d441136-51fd-4dfb-b27p-064717567b6a#InviteUsedView
While Microsoft has not yet made a formal announcement about its plans with Outlook Premium, it did earlier confirm that the program was considered an “experiment” in the pilot phases. The company said then it was not “an existing offering.”
What’s also interesting about Outlook Premium is that it will, to some extent, compete with Microsoft’s “Ad-Free Outlook,” priced at $19.95 per year – a bit less than Outlook Premium. Of course Premium offers more features. (See below screenshot taken today, 4/4/2016).
outlook-premium-features
According to a FAQ linked to from Outlook Premium’s website, Microsoft has partnered with domain provider GoDaddy to help Premium customers acquire the domain they want to use with their personalized email address. This domain will also be free for the first year, but then customers will need to renew the name every year with GoDaddy or another provider, if they choose to later transfer it.
After signing up thousands of users as a Microsoft MVP, this process is dead simple, especially with Outlook 2016/365. During sign-up, Outlook Premium walks users through an interface where they can check for available domain names, and it will propose others. After completing this registration process, customers can then set their new personalized email as the default and choose which email they want to send from when composing a new message. Users are also able to share calendars, contacts and documents with the other people who have emails on the same domain.
In addition, Microsoft says that Outlook Premium will work with those customers who bought Office 365 Home with a personalized email address. By adding on the Premium service, users can invite up to four other individuals to create personalized emails on this account.
Summary
The amazing and Microsoft's innovation shines brightly, because this means that Premium works as both a standalone product and an add-on to Office 365 Home. This also means that Premium could work for both businesses and families who either want or need multiple email addresses that can be managed from the Outlook.com Premium Domain Dashboard.