Le Café Central de
Deva             


                    ... Deva blogs!!



  • Le Café Central de DeVa

    Fix: Windows Phone 7.5 & Facebook Password update “0x83cf1202”

    • 15 Comments
    Recently one of my customer changed his Facebook password via laptop. Later when he tried connecting via my Windows Phone/Facebook chat, it requested him to update the password. Unfortunately, he opted to delete the Facebook account, but it failed. After this, he can’t update his password. Doing so (Settings > Email+accounts > Facebook), it throws “Attention required – can’t delete Facebook” and error code “0x83cf1202”. 

    Tried the following steps, which helped him to fix the issue:

    1. Disconnect all devices/desktop apps and login with browser
    2. Delete Facebook account (connected with Hotmail account) using the browser
    3. Boot the phone
    4. In Phone, Sync the Hotmail account. At end of this, delete the Facebook account
    5. Now you can connect the Facebook account using Settings > Email+accounts > Facebook in the phone.

    Note: Prior to that I learnt that he is connected with messenger desktop app browser, Windows Phone to the Hotmail account. Also the Facebook updates, notifications, still seem to work, but only chat doesn't Smile

  • Le Café Central de DeVa

    Exchange PowerShell: How to get list of mailboxes, folders, subfolders, items in folder, foldersize programmatically?

    • 2 Comments

    One of my customer automated Exchange PowerShell with his .Net application. They had a requirement to enhance the functionality – to get the list of exchange mailboxes, folders and its sub folders, items in folder, foldersize. Finally it needs to be saved in .csv format. 
    To implement this, we used Get-Mailbox and Get-MailboxFolderStatistics Exchange cmdlets. For looping the objects, we used foreach-object and couple of pipes to achieve the goal.

    PowerShell (screenshot):

    Exchange PowerShell

    PowerShell (script) – adding for your reference:

    [PS] C:\Documents and Settings\Administrator>Get-Mailbox | Select-Object alias | foreach-object {Get-MailboxFolderStatistics -Identity $_.alias | select-object Identity, ItemsInFolder, FolderSize} | Export-csv c:\Stats.csv -NoTypeInformation

    Result:

    Output

    As you know you can automate your application using .Net programmatically by referring the following articles:http://msdn.microsoft.com/en-us/library/bb332449(v=exchg.80).aspx and http://msdn.microsoft.com/en-us/library/ff326159(v=exchg.140).aspx.

    Happy programming!!

  • Le Café Central de DeVa

    Zune Software: Installation failed with error code 0x80070643

    • 19 Comments

    Recently I tried to install Zune Software in my PC, encountered installation failed with the error code: 0x80070643 and message “Setup must stop because the required package ‘Zune"’ didn’t install.

    image

    Done research and found the following Microsoft support knowledge base article – states that “A required component cannot be installed when you try to install the Zune software”. This issue may occur when software updates that are required by the Zune software are not available when you try to install the Zune software. The following required updates are available from the Microsoft Update website: 

    • The .NET Framework 2.0
    • Microsoft Error Reporting
    • XMLLite
    • Windows Format SDK

    To obtain all required updates in one package, follow these steps:

    1. Verify that you have administrative rights to install software.
    2. Make sure that you have sufficient free space to install the Zune software. For more information about system requirements for Zune, visit the following website: http://www.zune.net/products/software/minsystemreqs.htm
    3. Click the Download button on the following page to install the update package:  http://go.microsoft.com/fwlink/?LinkID=104738
    4. In the dialog box that appears, click Run to start the installation process.
    5. The installation should start automatically. If you are prompted, type the name of the folder where the files will be extracted.
    6. When the files are copied to the folder, open the folder, and then double-click Startzune.exe to install the Zune software.

     

    This resolved the issue. Based on the above support KB, you may also receive one of these error messages when trying to install the following products:

    • The Microsoft .NET Framework 2.0
    • Microsoft Windows Media Format 11 runtime
    • Microsoft Error Reporting 2.0
    • XMLLite
    Additionally, the installation cannot continue.

    Happy troubleshooting!!

  • Le Café Central de DeVa

    Troubleshooting Outlook : Command line switches for Outlook 2010

    • 2 Comments

    Outlook 2010 provides the command line switches for our handy troubleshooting.

    image

    You can use some of these switches that are recommended for solving problems.

    If you do hit an unexpected issue and want to run one of these switches. During these times, these switches can also been used when you need to restore Outlook settings to the default settings. 

    Let we try to use the switches in Windows 7 and Outlook 2010:

    a) You can use either one of the 3 options:

    1) Open the Run command via Start-> Run

    2) Press the Windows Logo + R on your keyboard

    3) Open the Start Menu and use the Search field to type in for the next step. (see the pic)

    b) In the box you opened in option 1/2/3 and just type: outlook.exe

    c) Press the spacebar once, and then type a forward slash mark (/) followed by the switch you want to use (see the list given below).

    d) Let we take example using the command line CleanReminders switch. 
    The command you type in the Open box should look like this:

    outlook.exe /cleanreminders

    e) To run the command, click OK.


    List of command line switches for Outlook 2010:

    Switch Description

    /a

    Creates an item with the specified file as an attachment.

    Example: "C:\Program Files\Microsoft Office\Office11\Outlook.exe" /a "C:\My Documents\labels.doc"
    Note: If no item type is specified, IPM.Note is assumed. Cannot be used with message classes that aren't based on Outlook.

    /altvba otmfilename

    Opens the VBA program specified in otmfilename, rather than %appdata%\Microsoft\Outlook\VbaProject.OTM.

    /c messageclass

    Creates a new item of the specified message class (Outlook forms or any other valid MAPI form). Some of the related examples:

    • /c ipm.activity creates a Journal entry
    • /c ipm.appointment creates an appointment
    • /c ipm.contact creates a contact
    • /c ipm.note creates an e-mail message
    • /c ipm.stickynote creates a note
    • /c ipm.task creates a task

    /checkclient

    Prompts for the default manager of e-mail, news, and contacts.

    /cleanclientrules

    Starts Outlook and deletes client-based rules.

    /cleandmrecords

    Deletes the logging records saved when a manager or a delegate declines a meeting.

    /cleanfinders

    Removes Search Folders from the Microsoft Exchange server store.

    /cleanfreebusy

    Clears and regenerates free/busy information. This switch can only be used when you are able to connect to your Microsoft Exchange server.

    /cleanprofile

    Removes invalid profile keys and recreates default registry keys where applicable.

    /cleanpst

    Launches Outlook with a clean Personal Folders file (.pst).

    /cleanreminders

    Clears and regenerates reminders.

    /cleanrules

    Starts Outlook and deletes client- and server-based rules.

    /cleanschedplus

    Deletes all Schedule+ data (free/busy, permissions, and .cal file) from the server and enables the free/busy information from the Outlook Calendar to be used and viewed by all Schedule+ 1.0 users.

    /cleanserverrules

    Starts Outlook and deletes server-based rules.

    /cleansniff

    Deletes duplicate reminder messages.

    /cleansubscriptions

    Deletes the subscription messages and properties for subscription features.

    /cleanviews

    Restores default views. All custom views you created are lost.

    /designer

    Starts Outlook without figuring out if Outlook should be the default client in the first run.

    /embedding

    Opens the specified message file (.msg) as an OLE embedding. Also used without command-line parameters for standard OLE co-create.

    /f msgfilename

    Opens the specified message file (.msg) or Microsoft Office saved search (.oss).

    /firstrun

    Starts Outlook as if it were run for the first time.

    /hol holfilename

    Opens the specified .hol file.

    /ical icsfilename

    Opens the specified .ics file.

    /importprf prffilename

    Launches Outlook and opens/imports the defined MAPI profile (*.prf). If Outlook is already open, queues the profile to be imported on the next clean launch.

    /l olkfilename

    Opens the specified .olk file.

    /launchtraininghelp assetid

    Opens a Help window with the Help topic specified in assetid.

    /m emailname

    Provides a way for the user to add an e-mail name to the item. Only works in conjunction with the /c command-line parameter.

    Example: Outlook.exe /c ipm.note /m emailname

    /nocustomize

    Starts Outlook without loading outcmd.dat (customized toolbars) and *.fav file.

    /noextensions

    Starts Outlook with extensions turned off, but listed in the Add-In Manager.

    /nopollmail

    Starts Outlook without checking mail at startup.

    /nopreview

    Starts Outlook with the Reading Pane off.

    /p msgfilename

    Prints the specified message (.msg). Does not work with HTML.

    /profile profilename

    Loads the specified profile. If your profile name contains a space, enclose the profile name in quotation marks (").

    /profiles

    Opens the Choose Profile dialog box regardless of the Options setting on the Tools menu.

    /recycle

    Starts Outlook using an existing Outlook window, if one exists. Used in combination with /explorer or /folder.

    /resetfoldernames

    Resets default folder names (such as Inbox or Sent Items) to default names in the current Office user interface language.

    Note: If you first connect to your mailbox Outlook using a Russian user interface, the Russian default folder names cannot be renamed. To change the default folder names to another language such as Japanese or English, you can use this switch to reset the default folder names after changing the user interface language or installing a different language version of Outlook.

    /resetfolders

    Restores missing folders for the default delivery location.

    /resetnavpane

    Clears and regenerates the Navigation Pane for the current profile.

    /rpcdiag

    Opens Outlook and displays the remote procedure call (RPC) connection status dialog.

    /s filename

    Loads the specified shortcuts file (.fav).

    /safe

    Starts Outlook without extensions, Reading Pane, or toolbar customization.

    /safe:1

    Starts Outlook with the Reading Pane off.

    /safe:2

    Starts Outlook without checking mail at startup.

    /safe:3

    Starts Outlook with extensions turned off, but listed in the Add-In Manager.

    /safe:4

    Starts Outlook without loading Outcmd.dat (customized toolbars) and *.fav file.

    /select foldername

    Starts Outlook and opens the specified folder in a new window.
    For example, to open Outlook and display the default calendar use: "c:\Program Files\Microsoft Office\Office11\Outlook.exe" /select outlook:calendar

    /sniff

    Starts Outlook and forces a detection of new meeting requests in the Inbox, and then adds them to the calendar.

    /t oftfilename

    Opens the specified .oft file.

    /v vcffilename

    Opens the specified .vcf file.

    /vcal vcsfilename

    Opens the specified .vcs file.

    /x xnkfilename

    Opens the specified .xnk file.

    Happy troubleshooting with Outlook 2010!!
  • Le Café Central de DeVa

    PowerShell: Determine Version number, build number and Service Pack of Exchange Server

    • 2 Comments

    In my earlier article, we learnt how to get the Exchange Server version, version/build number of Exchange 2003 and it’s earlier. In this, we will see how to get these info & couple of additional info in Exchange Server 2007/2010 using Exchange Management Shell and Exchange Management Console.

    Using Exchange Management Console:

    To view the server properties in the Exchange Management console, try the following steps:

    1.Start the Microsoft Exchange Management console. In the navigation pane, expand the Server Configuration objects until you locate the server object, and then select the server object.
    2.On the right side, notice the Exchange version number.

    Using Exchange Management Shell:

    For this, I used Get-ExchangeServer cmdlet to view the server properties in Exchange Management Shell:

    clip_image001

    I want to save the above info in a .txt file (saved under c:\output.txt):

    clip_image002

    Now, I want to customize the above one by the following to get more clarity:

    clip_image003

    Still I want to add more info like Site, Server Role and Edition etc..

    clip_image004

    Hope this helps you to move ahead.

  • Le Café Central de DeVa

    Exchange Server 2007, 2010: How to query user mailboxes, its permissions using Exchange PowerShell?

    • 2 Comments

    In Exchange Server 2007/2010, you can use Exchange PowerShell cmdlets (especially using Get-Mailbox, Get-MailboxPermission, Get-ADPermission, Get-MailboxFolderPermission) to get a verity of info. I played with couple of the below in different scenarios and want to share the same with you – so that you can give a shot and make use of.

    Scenario # 1: How to query permissions on a mailbox (testuser1)?
    > Get-MailboxPermission test1

    image

    Scenario #2: How to query permissions of all the mailboxes on a particular server?
    > Get-Mailbox –Server “ServerName” | Get-MailboxPermission

    image

    Scenario #3: How to query permissions of all the mailboxes?
    > Get-Mailbox | Get-MailboxPermission
    Note: This will get the list of all permissions (including SELF permissions and inherited permissions)

    image

    Scenario # 4: How to query permissions of all the mailboxes (filter out SELF and inherited permissions)?
    > Get-Mailbox | Get-MailboxPermission | where {$_.user.tostring() -ne "NT AUTHORITY\SELF" -and $_.IsInherited -eq $false}

    Scenario #5: How to query mailbox permissions and Security permissions (only enumerate permissions that are not Inherited)?
    > Get-Mailbox | Get-MailboxPermission | where {$_.IsInherited -eq $False}
    Note: The above query will get you the “explicitly assigned permissions”

    Scenario #6: How to query the explicitly assigned permissions (filter out SELF permissions)?
    > Get-Mailbox | Get-MailboxPermission | where { ($_.IsInherited -eq $false) -and -not ($_.User -like “NT AUTHORITY\SELF”) }

    Scenario #7: How to query list of all mailboxes with Send-As permission assigned on them?
    > Get-Mailbox | Get-ADPermission | where {($_.ExtendedRights -like “*Send-As*”)} | FT –Wrap
    Note: This will get the list of mailboxes with Send-As permission assigned. Also you can notice that it shows Send-As permissions assigned to SELF on all mailboxes also.

    Scenario #8: How to query list of all mailboxes with Send-As permission assigned on them (filter out SELF and inherited permissions as similar to Scenario #4)?
    > Get-Mailbox | Get-ADPermission | where {($_.ExtendedRights -like “*Send-As*”) -and ($_.IsInherited -eq $false) -and -not ($_.User -like “NT AUTHORITY\SELF”)} | FT –Wrap

    Scenario #9: How to query the permissions of shared calendar in Exchange 2010?
    > Get-MailboxFolderPermission –identity “mailboxaccount*:\Calendar”
    Note: If you just try Get-MailboxFolderPermission with identity with mailboxaccount won’t get you the above.

    Scenario #10: How to query the users rights to a specific users mailbox?
    > Get-MailboxPermission –identity “username” | fl user, accessrights

    image

    Scenario #11: How to query the permissions for every users mailbox?
    > Get-MailboxPermission –identity * | fl user, identity, accessrights

    image

    Note:

    + Exporting the data:
    At anypoint of time, if you want to export the above results to a CSV file, then you can use “Export-csv”. Say, let we try with one of the above scenario – try with scenario # 2:
    > Get-Mailbox | Get-MailboxPermission | Export-csv C:\permissions.csv

    image

    + Automation using .Net Framework:
    If you want to like to add Exchange management capabilities to your Microsoft .NET Framework–based applications then you can try the above by referring the following: http://msdn.microsoft.com/en-us/library/bb332449(v=exchg.80).aspx and http://msdn.microsoft.com/en-us/library/ff326159(v=exchg.140).aspx.

    Happy PowerShelling and automation…!!

  • Le Café Central de DeVa

    Outlook 2010 : How to configure multiple exchange accounts to a profile?

    • 2 Comments

    If you use Outlook 2010 (Technical Preview), you can notice couple of new improvements got added. With Outlook 2010, you can configure multiple Exchange Accounts to a profile – a new special feature introduced along with this.

    Snapshot - Navigation Pane

    In order to implement this, you need to use the following procedure/steps to do so using OCT (Office Customization tool):

    1. From the root of the network installation point, run the following command line to start the Office Customization Tool: \\server\share\setup.exe /admin

    2. To edit an existing customization file (.msp), in the Select Product dialog box, click Open an existing Setup customization file. Or to create a new customization file, select the Office suite that you want to customize, and then click OK.

    3. In the Outlook area, click Outlook profile. Select how you want to customize profiles for your users. To change an existing profile or to add a new profile, choose Modify Profile or New Profile.

    4. To add and configure new and existing accounts, click Add accounts, and then click Customize additional Outlook profile and account information.

    5. To add an Exchange account, click the Add button.

    6. In the Add Accounts dialog box, select Exchange, and then click Next.

    7. In the Exchange Settings dialog box, enter an account name and the name of the Exchange Server computer. If you want to identify the user by using a specific value, enter a User Name. Otherwise, leave the default %username% value for the User Name. Each user’s account information in the Active Directory directory service will be automatically populated for the profile.

    8. If you want to change an existing Exchange account in a user’s profile, select the Overwrite existing Exchange accounts check box.

    9. Click More Settings for additional Exchange configuration options such as Cached Exchange Mode and Outlook Anywhere, and then click OK.

    10. When you are finished, click Finish.

    11. To add an additional Exchange account, repeat steps 5-10.

    12. If you are creating a new profile, add the Outlook Address Book account to the profile. This account allows you to use the Contacts folder in your Exchange mailbox as an address book when you create e-mail messages.

    13. After you have finished all your customizations, save the customization file (.msp) and exit the OCT. Put the .msp file in the Office installation source \Updates folder. Install the Microsoft Office 2010 from the original installation source.

    Please note:

    • More Info: If you want to hear more about this feature, you can read this article posted by Andrew Sullivan, Outlook Program Manager.
    • Modify/Remove exchange accounts: In order to You can easily modify or remove an Exchange account from a profile by using almost the same procedure as previously described in Add multiple Exchange accounts to a profile. In step 5, highlight the Exchange account that you want to modify or remove from the profile, and then click either Modify to modify or Remove to remove the account. Then, finish your customizations and save the customization file (.msp)

    Try this out and enjoy the new feature of Outlook 2010!!

  • Le Café Central de DeVa

    Outlook 2010 : Why CDO 1.2.1 not supported with Outlook 2010?

    • 4 Comments

    Collaboration Data Objects (CDO) 1.2.1 is a client library that provides a thin wrapper over Extended MAPI functionality. CDO does not install with Outlook 2010, and is available only as a download. For more information, see Collaboration Data Objects, version 1.2.1 in the Microsoft Download Center. CDO is not guaranteed to work correctly in an environment with multiple Exchange accounts. CDO 1.2.1 is a 32-bit client library and will not operate with 64-bit Outlook 2010. Therefore, CDO 1.2.1 is not supported for use with Outlook 2010. Most of the CDO 1.2.1 functionality has been incorporated into the Outlook 2010 object model.

    Then, what’s the alternative? As an alternative to CDO 1.2.1, update existing solutions that depend on CDO to use the Outlook object model or to use MAPI directly.

  • Le Café Central de DeVa

    Where i can find the Macros & Visual Basic Editor in new Microsoft Outlook 2010?

    • 6 Comments

    Couple of Outlook 2010 beta users reported that they can’t find the old VBA (Visual Basic for Applications) and Visual Basic Editor in new Outlook 2010? Whether the feature is removed? With respect to my last blog post, VBA is available with Outlook 2010. Let me explain in-detail. We know about how Outlook 2010 applications expose their object models; also we’re eager to calling object methods, setting object properties, and responding to object events. To do so, you must write your code in a place and in a way that Office can understand; typically, by using the Visual Basic Editor. Although installed by default, many users do not know that it is even available until it is enabled on the ribbon.

    Opening the Developer Tab

    All Office 2010 applications use the ribbon. One tab on the ribbon is the Developer tab, where you access the Visual Basic Editor and other developer tools. Because Office 2010 does not display the Developer tab by default, you must enable it by using the following procedure:

    To enable the Developer tab and view Visual Basic Editor, do the following steps:

    1. On the File tab, choose Options to open the Outlook Options dialog box.

    2. Click Customize Ribbon on the left side of the dialog box.

    3. Under Choose commands from on the left side of the dialog box, select Popular Commands.

    4. Under Customize the ribbon on the right side of the dialog box, select Main tabs, and then select the Developer check box.

    5. Click OK.

    Please note: In Office 2007, you displayed the Developer tab by clicking the Office button, clicking Options, and then selecting the Show Developer tab in Ribbon checkbox in the Popular category of the Options dialog box

    After you enable the Developer tab, Bingo, it is easy to find the Visual Basic and Macros buttons.

    Developer tab in Outlook 2010
    image 

    Continue your programming with VBA with Outlook 2010.

  • Le Café Central de DeVa

    Where does autocomplete gets stored in OWA?

    • 6 Comments

    There is always a related question regarding autocomplete feature on OWA. In outlook the auto complete gets stored in *.NK2. Where does it store for OWA ? The Auto Complete cache is stored as part of the user’s profile on the Exchange Server.

  • Le Café Central de DeVa

    How to get the EWS endpoint URL from Outlook 2007/2010?

    • 6 Comments
    You can try the following steps to get the EWS endpoint URL from Outlook 2007 or 2010:

    • CTRL+Right click the Outlook icon in the notification area in the lower right-hand area of the screen. You can notice the following window:

    image

    • Select Test E-mail Auto configuration.
    • Enter your email address and password.
    • Select the Use AutoDiscover box (you can uncheck the other boxes).
    • Select the Test button.

    image

    • In the results window, you can see the Availability Service URL  Smile
  • Le Café Central de DeVa

    Troubleshooting : EWS request throws “The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel” ?

    • 2 Comments

    One of my customer updated that whenever they try to make the remote Exchange Web Service (EWS) call from his C#.Net 2008 application (VS.Net 2008 - .Net Framework 3.x), he gets the following error:

    The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel

    I had a detailed look at their application code.

    // Create the Exchange Service Binding        
    ExchangeServiceBinding esb = new ExchangeServiceBinding();        
     
    // Add its relevant Credentials like user name, password, domain and URL        
    esb.Credentials = new NetworkCredential(userName, Password, domain);        
    esb.Url = @"https://myexchangeserver/EWS/Exchange.asmx";

    We checked the credentials passed; it seems everything was fine. But still it was failing whenever we make the request to the server with the above same message. When we checked their environment, we found customer uses the self-signed certificate on the server. This is because, by default, .NET checks whether SSL certificates are signed by a certificate from the Trusted Root Certificate store.

    To over-ride this behavior, we need to use the following line in the code, which validate the x509 certificate:

    ServicePointManager.ServerCertificateValidationCallback = (sender, certificate, chain, sslPolicyErrors) => true;

    This will accept all certificates, regardless of why they are invalid, which resolved the customer’s issue.

    By validating the X509 certificate provided by the computer running Microsoft Exchange Server 2007 for SSL over HTTP, you help to provide a layer of security for the client application. You must validate certificates before you can start programming with Exchange Web Services proxy classes. If the callback is not set up, the first call will fail with a certificate error.

    Happy troubleshooting!!

  • Le Café Central de DeVa

    Outlook: How to compact my PST/OST file in Outlook 2010?

    • 3 Comments

    I listed some of the regular questions that we see from our customers from PST/OST are,

    1) How to reclaim the space from PST?
    2) How to compact my PST file?
    3) How to compact PST/OST files to eliminate deleted item space in Outlook?
    4) My PST is filling my hard disk?

    To conserve space on your hard disk, you can delete unwanted items from the various .pst/.ost files, and then compact the files to make them smaller. If you use Outlook 2002, 2003, 2007 and 2010 then try the following steps specified in the support KB.

    Try this out and reclaim more room in your PC!!

  • Le Café Central de DeVa

    Custom forms deployment : Where we can publish Outlook Custom forms?

    • 1 Comments

    In Outlook, custom forms are typically published to a forms library so that only one copy of a form is stored on your computer. Individual items contain a Message Class field that indicates which form to use to display the data that is contained in the item. When you publish custom forms to a forms library, Microsoft Exchange Server-based computers and Outlook use considerably less resources and bandwidth because the form itself does not need to be stored within each individual item.

    Considerations When You Are Deciding Where to Publish a Form:

    There are many questions to take into account when you are deciding where to publish a form:

    • Is the form based on a folder solution, or is it an e-mail message form that is designed to be sent to recipients?
    • Are you using an Exchange Server-based computer? If you are using an Exchange Server-based computer, is it possible to publish the form to the Organizational Forms Library, or has your organization placed restrictions on what types of forms can be stored there?
    • How many people need access to the form?
    • Will the form be updated often, making it important to have only one copy of the form deployed centrally?
    • Does the form need to be available offline?
    • If this is an e-mail message form, will it be used only inside the organization, or will it be sent to other recipients outside of the organization?
    • How will the new form be opened?

    Where we can publish?

    Now we can see where we can publish these custom forms.

    Outlook forms solutions can vary greatly, especially because Outlook has a number of different types of standard forms. It is often difficult to determine the best place to publish a form, and there are many factors to take into account when you make the decision. Forms can be published to three locations:
    (1) A folder (or Folder Forms Library)
    (2) Organizational Forms Library
    (3) Personal Forms Library

    We’ll discuss them in detail and how these three makes differences:

    (1) A folder (or Folder Forms Library):

    • For most folder-based forms solutions, publish the form to the folder so that it is available whenever someone is using the folder.
    • If you publish the form in a public folder, the form is available to everyone who can access the folder.
    • If you publish the form to one of your personal folders, it is available only to you when you are using that folder.
    • Contact, Post, Task, and Journal forms are examples of the types of forms that are typically associated with a folder.
    • One advantage to publishing a form to a folder is that the form is available on the Actions menu when you are in the folder.

    (2) Organizational Forms Library:

    • Publish the form to this library if you want to make the form available to everyone in your organization, such as a form to report vacation time.
    • This library is often used for e-mail message forms because they are typically not based on a specific folder.
    • You can publish a form to the Organizational Forms Library when you want to use the same custom form in more than one folder.
    • When you do this, you can maintain only a single published form.
    • Forms that are published to this library are accessible to everyone in the organization as long as they are given permissions to the library by the administrator.
    • The library is stored on the Microsoft Exchange Server-based computer.
    • The administrator must give you permissions to publish to the Organizational Forms Library.
    • This permission is typically given to only a few individuals or a department that manages the Exchange Server-based computer.

    (3) Personal Forms Library:

    • Forms that are saved in this library are only accessible to you.
    • When you publish a form to the Personal Forms Library, the form is stored as a hidden item in the root folder of your mailbox or Personal Folders (.pst) file, whichever is your default mail delivery location.
    • Like forms that are stored in the Organizational Forms Library, these forms can be opened by using the Choose Form command.
    • Save a form to this library when you create a form for your own personal use, such as a standard e-mail message form that is pre-addressed to recipients.

    Please note: It is also possible to store an Outlook form as a file in the file system or as an item in an Outlook folder. Microsoft recommends that you to avoid these approaches, because the form will be a one-off form.

    image

    Deciding Where to Publish Folder-based Forms:
    • When you create a folder-based solution where the primary focus of the form is to display the items in a single folder, typically publish the form to the folder itself.
    • When you publish the form to the folder, the folder is a self-contained entity and the form is available on the Actions menu.
    • However, there are scenarios where you may not want to publish a typical folder-based form to a folder.
    • If you use a form in more than one folder, and each folder always uses the same version of the form, consider publishing the form into either the Organizational Forms Library or the Personal Forms Library. When you do this, there is only one copy of the published form and it is easier to update if you need to make changes.
    • If you are the only person who needs access to this form, publish the form in Personal Forms Library.
    • If other people need to access to the form, and the form is typical in a public folder on an Exchange Server-based computer, investigate whether or not you may be able to publish the form to the Organizational Forms Library.
    • Note: One potential disadvantage to this approach is that the form will not be available under the Actions menu unless it is published to the folder. However, if it is the default form for the folder, as is typically the case, this will not make too much of a difference because you or the users can use a toolbar button to open new items.
    Deciding Where to Publish Message-based Forms
    • If the form is based on an e-mail message and it is used by you and only a couple of other users, publish the form to the Personal Forms Library for all of the users. However, if you are going to create new items based on this form, you may want to publish it to your Inbox so that you can access it on the Actions menu.
    • If the form is going to be used by many people within an organization, publish it in the Organizational Forms Library so that there is only one copy of the form to maintain and all of the users have access to it. This approach, however, can make the form more difficult to open.
  • Le Café Central de DeVa

    How to: Determine which Microsoft .Net Framework version and service pack installed?

    • 2 Comments

    This is one of our frequent question: How to determine which version(s) and service pack level(s) of the Microsoft .NET Framework are installed? You can use the registry information below to determine which version(s) and service pack level(s) of the Microsoft .NET Framework are installed.

    .NET Framework

    Service Pack Level

    Registry Key Name

    Value

    4 - Client

    Original Release

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client

    Name: Version, Type: REG_SZ, Data: 4.0.30319.0

    4 - Full

    Original Release

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

    Name: Version, Type: REG_SZ, Data: 4.0.30319.0

    3.5

    Original Release

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

    Name: SP, Type: REG_DWORD, Data: 0

    3.5

    Service Pack 1

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5

    Name: SP, Type: REG_DWORD, Data: 1

    3.0

    Original Release

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: SP, Type: REG_DWORD, Data: 0

    3.0

    Service Pack 1

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: SP, Type: REG_DWORD, Data: 1

    3.0

    Service Pack 2

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0

    Name: SP, Type: REG_DWORD, Data: 2

    2.0

    Original Release

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: SP, Type: REG_DWORD, Data: 0

    2.0

    Service Pack 1

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: SP, Type: REG_DWORD, Data: 1

    2.0

    Service Pack 2

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727

    Name: SP, Type: REG_DWORD, Data: 2

    1.1

    Original Release

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322

    Name: SP, Type: REG_DWORD, Data: 0

    1.1

    Service Pack 1

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322

    Name: Install, Type: REG_DWORD, Data: 1

     

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322

    Name: SP, Type: REG_DWORD, Data: 1

    1.0 (on supported platforms except for Windows XP Media Center and Tablet PC)

    Original Release



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{78705f0d-e8db-4b2d-8193-982bdda15ecd}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.0

    1.0 (on supported platforms except for Windows XP Media Center and Tablet PC)

    Service Pack 1



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{78705f0d-e8db-4b2d-8193-982bdda15ecd}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.1

    1.0 (on supported platforms except for Windows XP Media Center and Tablet PC)

    Service Pack 2



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{78705f0d-e8db-4b2d-8193-982bdda15ecd}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.2

    1.0 (on supported platforms except for Windows XP Media Center and Tablet PC)

    Service Pack 3



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{78705f0d-e8db-4b2d-8193-982bdda15ecd}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.3

    1.0 (shipped with Windows XP Media Center 2002/2004 and Tablet PC 2004)

    Service Pack 2



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.2

    1.0 (shipped with Windows XP Media Center 2005 and Tablet PC 2005)

    Service Pack 3



    HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24}

    Name: Version, Type: REG_SZ, Data: 1.0.3705.3


    Hope this helps.
  • Le Café Central de DeVa

    Free eBook: Programming Windows 8 Apps with HTML, CSS and JavaScript

    • 17 Comments

    Programming Windows 8 Apps with HTML, CSS and JavaScriptThis wonderful eBook is written by Kraig. He provides comprehensive coverage of the platform for Windows Store apps, and devoted chapters on live tiles, notifications, background tasks, background transfers, networking, devices, printing, WinRT components, accessibility, localization, and the Windows Store itself. The final eBook contains 17 chapters. And of course all of the earlier chapters have also been reviewed and refined—over 800 pages in total, along with new and updated companion content!

    So you can download the eBook in PDF format here: http://go.microsoft.com/FWLink/?Linkid=270056 (17.9 MB)

    EPUB format is here: http://go.microsoft.com/FWLink/?Linkid=272592 (37.3 MB)

    MOBI format is here: http://go.microsoft.com/FWLink/?Linkid=272591 (69.5 MB)

    The eBook's companion content is here: http://go.microsoft.com/FWLink/?Linkid=270057 (59.9 MB)

    Just make use of it and develop new Windows 8 apps. Happy programming!!

  • Le Café Central de DeVa

    Download : Office 2010 Primary Interop Assemblies (PIA) Redistributable

    • 1 Comments

    The Microsoft Office 2010 Primary Interop Assemblies (PIA) Redistributable is a Microsoft Windows Installer package that contains the Primary Interop Assemblies for Microsoft Office 2010 products.

    The redistributable contains the PIAs for the following products:
    • Microsoft Access 2010
    • Microsoft Excel 2010
    • Microsoft InfoPath 2010
    • Microsoft Outlook 2010
    • Microsoft PowerPoint 2010
    • Microsoft Project 2010
    • Microsoft Publisher 2010
    • Microsoft SharePoint Designer 2010
    • Microsoft Visio 2010
    • Microsoft Word 2010

    You can download it from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=938fe8ad-583b-4bd7-a345-23250dc15855
  • Le Café Central de DeVa

    Part # 1 : Exchange Web Services (EWS) & VB.Net – Creating Calendar (non-Recurrence type)

    • 2 Comments

    Hi Peers,

    I have include the part 1 of Exchange Web Services & VB.Net. Earlier my couple of VB developer customers were looking for relevant VB.Net related articles and found very few. Keeping in that mind, i have created this EWS_VB.net_Calendar thread to start with.

    In this session we will going to see how we can create the Calendar using Exchange Web Services (EWS). I tried to provide things as simpler as i can…

    I would appreciate to know if you have any suggestions/clarifications regarding this…

     

    Step 1: Create Exchange Service Binding

    'Create Exchange Service Binding
    Dim esb As New ExchangeServiceBinding()
    'Provide the NetworkCredential
    esb.Credentials = New NetworkCredential("username", "password", "domain")
    'Provide the URL
    esb.Url = https://Fully qualified domain/ews/exchange.asmx


    Step 2: Create Calendar

    ' Create the appointment.
    Dim appointment As New CalendarItemType()


    Step 3: Set the properties of the appointment

    ' Set the properties of the appointment.
    appointment.Start = "2/24/2009 12:30:00PM"
    appointment.StartSpecified = True
    appointment.[End] = "2/24/2009 1:30:00PM"
    appointment.EndSpecified = True
    appointment.Subject = "Planning meeting by Deva"
    appointment.Location = "Building 3, Room 311"
    appointment.Body = New BodyType()
    appointment.Body.BodyType1 = BodyTypeType.Text
    appointment.Body.Value = "Plan the department party."

    Step 4: Add the required attendees

    ' Add required attendees.
    appointment.RequiredAttendees = New AttendeeType(1) {}
    appointment.RequiredAttendees(0) = New AttendeeType()
    appointment.RequiredAttendees(0).Mailbox = New EmailAddressType()
    appointment.RequiredAttendees(0).Mailbox.EmailAddress = "chris@contoso.com"

    Step 5: Create the array of items that will contain the appointment

    ' Create the array of items that will contain the appointment.
    Dim arrayOfItems As New NonEmptyArrayOfAllItemsType()
    arrayOfItems.Items = New ItemType(1) {}
     
    ' Add the appointment to the array of items.
    arrayOfItems.Items(0) = appointment
     
    ' Create the CreateItem request.
    Dim createRequest As New CreateItemType()
     
    'The SendMeetingInvitations attribute is required for calendar items.
    createRequest.SendMeetingInvitations = CalendarItemCreateOrDeleteOperationType.SendToAllAndSaveCopy
    createRequest.SendMeetingInvitationsSpecified = True
     
    'Add the destination folder(calendar) to the CreateItem request.
    createRequest.SavedItemFolderId = New TargetFolderIdType()
    Dim dfCalendarFolder As DistinguishedFolderIdType = New DistinguishedFolderIdType()
    dfCalendarFolder.Id = DistinguishedFolderIdNameType.calendar
    createRequest.SavedItemFolderId.Item = dfCalendarFolder


    Step 6: Add the items to CreateItem request

    ' Add the items to the CreateItem request.
    createRequest.Items = arrayOfItems
     

    Step 7: Create the appointment by calling the CreateItem method & Check the result

    ' Create the appointment by calling the CreateItem method, which has the side effect of sending invitations to attendees.
    Dim createResponse As CreateItemResponseType = esb.CreateItem(createRequest)
     
    ' Check the result.
    If createResponse.ResponseMessages.Items(0).ResponseClass <> ResponseClassType.Success Then
         Throw New Exception("SendAppointment failed.")
    Else
                Console.WriteLine("Calendar Item Created")
    End If


    Step 8: Result

    image

  • Le Café Central de DeVa

    Development : Is Visual Basic 6.0 Runtime still supported?

    • 1 Comments

    We get many request/references regarding support of Visual Basic 6.0 runtime support for various Microsoft Operating systems including MS Windows 7.

    There is a wonderful article regarding this MSDN article titled “Support Statement for Visual Basic 6.0 on Windows Vista, Windows”. It states that the “…Visual Basic team is committed to “It Just Works” compatibility for Visual Basic 6.0 applications on Windows Vista, Windows Server 2008 including R2, and Windows 7. The Visual Basic team’s goal is that Visual Basic 6.0 applications that run on Windows XP will also run on Windows Vista, Windows Server 2008 and Windows 7. The Visual Basic team is also committed to the Visual Basic 6.0 development environment running on Windows Vista, Windows Server 2008 and Windows 7…”  

    In short, as detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of Windows Vista, Windows Server 2008 and Windows 7, which is five years of mainstream support followed by five years of extended support (http://support.microsoft.com/gp/lifepolicy).

    We need to understand certain things here. I want to provide certain excerpts out of this Support statement. In general, Visual Basic 6.0 is made up of these key deliverables:

    · Visual Basic 6.0 IDE [Integrated Development Environment]
    · Visual Basic 6.0 Runtime -- the base libraries and execution engine used to run VB 6.0 applications
    · Visual Basic 6.0 Runtime Extended Files – select ActiveX control OCX files, libraries, and tools shipping with the IDE media and as an online release

    The Visual Basic 6.0 IDE

    The Visual Basic 6.0 IDE will be supported on Windows Vista and Windows Server 2008 as part of the Visual Basic 6.0 Extended Support policy until April 8, 2008.  Both the Windows and Visual Basic teams tested the Visual Basic 6.0 IDE on Windows Vista and Windows Server 2008.  This announcement does not change the support policy for the IDE.

    The Visual Basic 6.0 Runtime

    The Visual Basic 6.0 runtime is defined as the compiled binary files originally included in the redistribution list for Visual Basic 6.0.  These files were marked as distributable in the original Visual Basic 6.0 license.  Examples of these files include the Visual Basic 6.0 runtime library (msvbvm60.dll), controls (i.e. msflxgrd.ocx) along with runtime support files for other major functional areas (i.e. MDAC).     

    The runtime is divided into the three groups:

    · Supported Runtime Files – Shipping in the OS: Key Visual Basic 6.0 runtime files, used in the majority of application scenarios, are shipping in and supported for the lifetime of Windows Vista, or Windows Server 2008, or Windows 7. This lifetime is five years of mainstream support and five years of extended support from the time that a given version of Windows ships.  These files have been tested for compatibility as part of our testing of Visual Basic 6.0 applications running on Windows Vista.  Note: the list of files shipping in Windows Vista, Windows Server 2008, Windows 7, and Windows XP are nearly identical and redist requirements for applications should be nearly identical.  One key difference is TriEdit.dll was removed from Windows Vista and later versions.  

    · Supported Runtime Files – Extended Files to Distribute with your application: extended list of key controls, libraries, and tools that are installed from the IDE media or from Microsoft.com to the developer machine.  Typically the VB6 IDE installed these controls to the developer machine by default.  The developer still needs to redistribute these files with the application.  The supported version of the files is available online on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=142927).

    · Unsupported Runtime Files: Some files have either fallen out of mainstream support or they were never included as a part of the runtime redist (e.g. they were included in \Tools folder on the IDE media to support legacy VB4/VB5 applications or they were 3rd party controls).  These files are not supported on Windows Vista or Windows Server 2008; instead they are subject to whatever support agreement applies to the media they were shipped with.  These files have been tested to work on Vista as part of our application compatibility and testing process, but this implies no warranties around support and servicing.  In some instances, later versions of these libraries are supported.  Details on backward compatibility or migration to supported versions are provided below.

    The Visual Basic 6.0 runtime has been tested for compatibility between Windows XP and Windows Vista / Windows Server 2008/Windows 7 with a goal that applications work similarly on these operating systems.  As with any release of the operating system, there may be differences in functionality that will require modifications to your applications.  These differences will be addressed on a case-by-case basis via normal support channels.  Any issues that are found will be documented on the Visual Basic Support site (http://msdn2.microsoft.com/en-us/vbasic/ms789193.aspx).  

    For specific details on the files included in each support group see the “Runtime Definition” section below.

    Visual Basic 6.0 Support Lifetime

    Supporting and/or shipping Visual Basic 6.0 runtime binaries on Windows Vista/Windows Server 2008/Windows 7 does not change the support policy for the Visual Basic 6.0 IDE or Visual Studio 6.0 IDE as a whole.  Those products will move out of extended support in April 8, 2008.

    Further details on the support policy for the Visual Basic 6.0 and Visual Studio 6.0 products can be found at http://msdn2.microsoft.com/en-us/vstudio/aa718686.aspx.     Details on the support lifecycle of Microsoft products can be found at http://support.microsoft.com/gp/lifepolicy.   As a part of this support lifecycle, Microsoft will continue to support the Visual Basic 6.0 runtime on Windows NT 4.0, Windows 2000, Windows XP and Windows Server 2003 for the support lifetime of those operating systems.  This means, for example, that the Visual Basic 6.0 runtime will be supported on Windows Server 2003 until June, 2008 for Mainstream Support and June, 2013 for Extended Support.

    For more details on the support lifecycle or to find out about additional support options, please visit our support page at http://www.microsoft.com/support

    64-Bit Windows

    Visual Basic 6.0 runtime files are 32-bit.  These files ship in 64-bit Windows Operating Systems referenced in the table below.  32-bit VB6 applications and components are supported in the WOW emulation environment only.  32-bit components must also be hosted in 32-bit application processes.

    The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor has the 32-bit IDE been supported on 64-bit Windows.  VB6 development on 64-bit Windows is not and will not be supported.

    Windows 7

    Since the initial release of this support statement, the Windows 7 operating system has been announced.  This document has been updated to clarify Microsoft’s support for VB6 on Windows 7.

    VB6 runtime will ship and will be supported in Windows 7 for the lifetime of the OS.  Developers can think of the support story for Vista being the same as it is for Windows 7.  However there are no plans to include VB6 runtime in future versions of Windows beyond Windows 7.

    Supported Windows Operating System Versions

    This section provides additional information regarding the operating systems that offer some level of support for VB6. 

    Windows Operating System

     

    Has support?

     

    VB6 Supported Runtime - Files Shipping in Windows

     

    VB6 Supported Runtime – Extended Files to Distribute with Your Application

     

    VB6 IDE

     

    Windows 7, all 32bit editions

     

    Yes *

     

    Yes *

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows 7, all 64bit editions

     

    Yes*
    32bit apps running in WOW only

     

    Yes*
    32bit apps running in WOW only

     

    No

     

    Windows Vista, all  32bit editions

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows Vista, all x64 editions

     

    Yes*

     

    32bit apps running in WOW only

     

    Yes*

     

    32bit apps running in WOW only

     

    No

     

    Windows Server 2008, all 32bit editions including R2

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows Server 2008, all x64 editions including R2

     

    Yes*

     

    32bit apps running in WOW only

     

    Yes*

     

    32bit apps running in WOW only

     

    No

     

    Windows XP, all 32bit editions

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows XP, all x64 editions

     

    Yes*

     

    32bit apps running in WOW only

     

    Yes*

     

    32bit apps running in WOW only

     

    No

     

    Windows 2003 server, all 32bit editions including R2

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows 2003 server. all x64 editions including R2

     

    Yes*

     

    32bit apps running in WOW only

     

    Yes*

     

    32bit apps running in WOW only

     

    No

     

    Windows 2000 Professional, all editions

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    Windows 2000 Server, all editions

     

    Yes*

     

    Yes*

     

    Yes*, Extended support until April 2008, Custom Support after April 2008

     

    * VB6 runtime support is limited by the OS support lifecycle.  E.g. if the target OS is in Extended support, VB6 cannot have a higher level of support than Extended support.  

    Visual Basic 6.0 Runtime Usage Inside VBA and Office

    Visual Basic for Applications, or VBA, is a distinct technology commonly used for application automation and macros inside of other applications, most commonly inside Microsoft Office applications.  VBA ships as a part of Office and therefore the support for VBA is governed by the support policy of Office.  However, there are situations where VBA is used to call or host Visual Basic 6.0 runtime binaries and controls.  In these situations, Visual Basic 6.0 supported runtime files in the OS and the extended file list are also supported when used inside of a supported VBA environment.

    For VB6 runtime scenarios to be supported inside VBA, all of the following must be true:

    · The host OS version for VB runtime is still supported

    · The host version of Office for VBA is still supported

    · The runtime files in question are still supported

    Visual Basic Script (VBScript)

    VBScript is unrelated to Visual Basic 6.0 and this support statement.  However, VBScript is currently shipping as a part Windows Vista, Windows Server 2008 and Windows 7 and is governed by the OS support lifecycle.   

    Third Party Components

    Microsoft is unable to provide support for third party components, such as OCX/ActiveX controls.  Customers are encouraged to contact the original control vendor for details on support for those components.

    Reporting Issues with VB 6.0 Application Running on Windows Vista, and Windows 7

    Developers planning to use Visual Basic 6.0 with Windows Vista should install Windows Vista and begin application compatibility testing using original application acceptance testing.

    If you find an issue with your Visual Basic 6.0 application running on Windows Vista or Windows 7 (where the same code worked as expected on Windows XP), please follow your normal support channels to report the issue.

    Supported and Shipping in Windows Vista, Windows Server 2008, and Windows 7

    atl.dll
    asycfilt.dll
    comcat.dll
    compobj.dll
    dbnmpntw.dll
    dcomcnfg.exe
    dllhost.exe
    ds16gt.dll
    ds32gt.dll
    expsrv.dll
    hh.exe
    hhctrl.ocx
    imagehlp.dll
    iprop.dll
    itircl.dll
    itss.dll
    mfc40.dll
    mfc42.dll
    mfc42enu.dll
    msadce.dll
    msadcer.dll
    msadcf.dll
    msadcfr.dll
    msadco.dll

    msadcor.dll
    msadcs.dll
    msadds.dll
    msaddsr.dll
    msader15.dll
    msado15.dll
    msador15.dll
    msadrh15.dll
    mscpxl32.dll
    msdadc.dll
    msdaenum.dll
    msdaer.dll
    msdaora.dll
    msdaosp.dll
    msdaprst.dll
    msdaps.dll
    msdasc.dll
    msdasql.dll
    msdasqlr.dll
    msdatsrc.tlb
    msdatt.dll
    msdfmap.dll
    msdfmap.ini
    msjtes40.dll

    msorcl32.dll
    msvbvm60.dll
    msvcirt.dll
    msvcrt.dll
    msvcrt40.dll
    mtxdm.dll
    mtxoci.dll
    odbc16gt.dll
    odbc32.dll
    odbc32gt.dll
    odbcad32.exe
    odbccp32.cpl
    odbccp32.dll
    odbccr32.dll
    odbccu32.dll
    odbcint.dll
    odbcji32.dll
    odbcjt32.dll
    odbctrac.dll
    oddbse32.dll
    odexl32.dll
    odfox32.dll
    odpdx32.dll
    odtext32.dll

    ole2.dll
    ole32.dll
    oleaut32.dll
    oleaut32.dll
    oledb32.dll
    oledb32r.dll
    oledlg.dll
    olepro32.dll
    olethk32.dll
    regsvr32.exe
    rpcns4.dll
    rpcrt4.dll
    scrrun.dll
    secur32.dll
    simpdata.tlb
    sqloledb.dll
    sqlsrv32.dll
    stdole2.tlb
    stdole32.tlb
    storage.dll
    vbajet32.dll
    vfpodbc.dll

    Supported Runtime Files to Distribute with Your Application

    comct232.ocx
    comct332.ocx
    comctl32.ocx
    comdlg32.ocx
    dbadapt.dll
    dbgrid32.ocx
    dblist32.ocx
    mci32.ocx
    msadodc.ocx

    msbind.dll
    mscdrun.dll
    mschrt20.ocx
    mscomct2.ocx
    mscomctl.ocx
    mscomm32.ocx
    msdatgrd.ocx
    msdatlst.ocx
    msdatrep.ocx

    msdbrptr.dll
    msflxgrd.ocx
    mshflxgd.ocx
    mshtmpgr.dll
    msinet.ocx
    msmapi32.ocx
    msmask32.ocx
    msrdc20.ocx
    msrdo20.dll

    msstdfmt.dll
    msstkprp.dll
    mswcrun.dll
    mswinsck.ocx
    picclp32.ocx
    richtx32.ocx
    sysinfo.ocx
    tabctl32.ocx

    Unsupported, But Supported and Compatible Updates or Upgrades are Available

    dao350.dll
    mdac_typ.exe
    mschart.ocx
    msdaerr.dll
    msdatl2.dll

    msexch35.dll
    msexcl35.dll
    msjet35.dll
    msjint35.dll
    msjt4jlt.dll

    msjter35.dll
    msjtor35.dll
    msltus35.dll
    mspdox35.dll
    msrd2x35.dll

    msrepl35.dll
    mstext35.dll
    msxbse35.dll
    odbctl32.dll
    oledb32x.dll

    Unsupported Runtime Files

    anibtn32.ocx
    graph32.ocx
    keysta32.ocx
    autmgr32.exe
    autprx32.dll
    racmgr32.exe
    racreg32.dll
    grid32.ocx
    msoutl32.ocx

    spin32.ocx
    gauge32.ocx
    gswdll32.dll
    ciscnfg.exe
    olecnv32.dll
    rpcltc1.dll
    rpcltc5.dll
    rpcltccm.dll
    rpclts5.dll

    rpcltscm.dll
    rpcmqcl.dll
    rpcmqsvr.dll
    rpcss.exe
    dbmsshrn.dll
    dbmssocn.dll
    windbver.exe
    msderun.dll
    odkob32.dll

    rdocurs.dll
    vbar332.dll
    visdata.exe
    vsdbflex.srg
    threed32.ocx
    MSWLess.ocx
    tlbinf32.dll
    triedit.dll

    Localization Support Binaries

    The following binaries are necessary for supporting Visual Basic 6.0 applications running on localized versions of the Vista and Windows 7 operating system.  They are supported but are not shipped in Vista.  These files are required to be shipped with your application setup.

    Supported Runtime Files to Distribute with Your Application

    JPN

    KOR

    CHT

    CHS

    mfc42jpn.dll
    scrrnjp.dll
    vb6jp.dll
    cmct2jp.dll
    cmct3jp.dll
    mscc2jp.dll
    cmctljp.dll
    cmdlgjp.dll
    mscmcjp.dll
    dbgrdjp.dll
    dblstjp.dll
    mcijp.dll
    msadnjp.dll
    adodcjp.dll
    mschtjp.dll
    msch2jp.dll
    mscomjp.dll
    datgdjp.dll
    datlsjp.dll
    datrpjp.dll
    dbrprjp.dll
    flxgdjp.dll
    mshfgjpn.dll
    htmprjp.dll
    inetjp.dll
    msmpijp.dll
    msmskjp.dll
    rdc20jp.dll
    rdo20jp.dll
    stdftjp.dll
    mswcrjp.dll
    winskjp.dll
    pcclpjp.dll
    rchtxjp.dll
    sysinjp.dll
    tabctjp.dll

    mfc42kor.dll
    scrrnko.dll
    vb6ko.dll
    cmct2ko.dll
    cmct3ko.dll
    mscc2ko.dll
    cmctlko.dll
    cmdlgko.dll
    mscmcko.dll
    dbgrdko.dll
    dblstko.dll
    mciko.dll
    msadnko.dll
    adodcko.dll
    mschtko.dll
    msch2ko.dll
    mscomko.dll
    datgdko.dll
    datlsko.dll
    datrpko.dll
    dbrprko.dll
    flxgdko.dll
    mshfgkor.dll
    htmprko.dll
    inetko.dll
    msmpiko.dll
    msmskko.dll
    rdc20ko.dll
    rdo20ko.dll
    stdftko.dll
    mswcrko.dll
    winskko.dll
    pcclpko.dll
    rchtxko.dll
    sysinko.dll
    tabctko.dll

    mfc42cht.dll
    scrrncht.dll
    vb6cht.dll
    cmct2cht.dll
    cmct3cht.dll
    mscc2cht.dll
    cmctlcht.dll
    mscmccht.dll
    cmdlgcht.dll
    dbgrdcht.dll
    dblstcht.dll
    mcicht.dll
    msadncht.dll
    adodccht.dll
    mschtcht.dll
    msch2cht.dll
    mscomcht.dll
    datgdcht.dll
    datlscht.dll
    datrpcht.dll
    dbrprcht.dll
    flxgdcht.dll
    mshfgcht.dll
    htmprcht.dll
    inetcht.dll
    msmpicht.dll
    msmskcht.dll
    rdc20cht.dll
    rdo20cht.dll
    stdftcht.dll
    mswcrcht.dll
    winskcht.dll
    pcclpcht.dll
    rchtxcht.dll
    sysincht.dll
    tabctcht.dll

    mfc42chs.dll
    scrrnchs.dll
    vb6chs.dll
    cmct2chs.dll
    mscc2chs.dll
    cmct3chs.dll
    cmctlchs.dll
    mscmcchs.dll
    cmdlgchs.dll
    dbgrdchs.dll
    dblstchs.dll
    mcichs.dll
    msadnchs.dll
    adodcchs.dll
    mschtchs.dll
    msch2chs.dll
    mscomchs.dll
    datgdchs.dll
    datlschs.dll
    datrpchs.dll
    dbrprchs.dll
    flxgdchs.dll
    mshfgchs.dll
    htmprchs.dll
    inetchs.dll
    msmpichs.dll
    msmskchs.dll
    rdc20chs.dll
    rdo20chs.dll
    stdftchs.dll
    mswcrchs.dll
    winskchs.dll
    pcclpchs.dll
    rchtxchs.dll
    sysinchs.dll
    tabctchs.dll


    ITA

    FRA

    ESP

    DEU

    mfc42ita.dll
    scrrnit.dll
    vb6it.dll
    cmct2it.dll
    mscc2it.dll
    cmct3it.dll
    cmctlit.dll
    mscmcit.dll
    cmdlgit.dll
    dbgrdit.dll
    dblstit.dll
    mciit.dll
    msadnit.dll
    adodcit.dll
    mschtit.dll
    msch2it.dll
    mscomit.dll
    datgdit.dll
    datlsit.dll
    datrpit.dll
    dbrprit.dll
    flxgdit.dll
    mshfgit.dll
    htmprit.dll
    inetit.dll
    msmpiit.dll
    msmskit.dll
    rdc20it.dll
    rdo20it.dll
    stdftit.dll
    mswcrit.dll
    winskit.dll
    pcclpit.dll
    rchtxit.dll
    sysinit.dll
    tabctit.dll

    mfc42fra.dll
    scrrnfr.dll
    vb6fr.dll
    cmct2fr.dll
    mscc2fr.dll
    cmct3fr.dll
    cmctlfr.dll
    mscmcfr.dll
    cmdlgfr.dll
    dbgrdfr.dll
    dblstfr.dll
    mcifr.dll
    msadnfr.dll
    adodcfr.dll
    mschtfr.dll
    msch2fr.dll
    mscomfr.dll
    datgdfr.dll
    datlsfr.dll
    datrpfr.dll
    dbrprfr.dll
    flxgdfr.dll
    mshfgfr.dll
    htmprfr.dll
    inetfr.dll
    msmpifr.dll
    msmskfr.dll
    rdc20fr.dll
    rdo20fr.dll
    stdftfr.dll
    mswcrfr.dll
    winskfr.dll
    pcclpfr.dll
    rchtxfr.dll
    sysinfr.dll
    tabctfr.dll

    mfc42esp.dll
    scrrnes.dll
    vb6es.dll
    cmct2es.dll
    mscc2es.dll
    cmct3es.dll
    cmctles.dll
    mscmces.dll
    cmdlges.dll
    dbgrdes.dll
    dblstes.dll
    mcies.dll
    msadnes.dll
    adodces.dll
    mschtes.dll
    msch2es.dll
    mscomes.dll
    datgdes.dll
    datlses.dll
    datrpes.dll
    dbrpres.dll
    flxgdes.dll
    mshfges.dll
    htmpres.dll
    inetes.dll
    msmpies.dll
    msmskes.dll
    rdc20es.dll
    rdo20es.dll
    stdftes.dll
    mswcres.dll
    winskes.dll
    pcclpes.dll
    rchtxes.dll
    sysines.dll
    tabctes.dll

    mfc42deu.dll
    scrrnde.dll
    vb6de.dll
    cmct2de.dll
    mscc2de.dll
    cmct3de.dll
    cmctlde.dll
    mscmcde.dll
    cmdlgde.dll
    dbgrdde.dll
    dblstde.dll
    mcide.dll
    msadnde.dll
    adodcde.dll
    mschtde.dll
    msch2de.dll
    mscomde.dll
    datgdde.dll
    datlsde.dll
    datrpde.dll
    dbrprde.dll
    flxgdde.dll
    mshfgde.dll
    htmprde.dll
    inetde.dll
    msmpide.dll
    msmskde.dll
    rdc20de.dll
    rdo20de.dll
    stdftde.dll
    mswcrde.dll
    winskde.dll
    pcclpde.dll
    rchtxde.dll
    sysinde.dll
    tabctde.dll

    Hope this helps.

  • Le Café Central de DeVa

    Rules series # 2 : One or more rules could not be uploaded to Exchange server and have been deactivated. This could be because some of the parameters are not supported or there is insufficient space to store all your rules.

    • 1 Comments

    Couple of customers reported that after upgrading to Microsoft Office Outlook 2007 or  Microsoft Office Outlook 2003, they found that some of the rules are disabled and cannot be enabled. Remaining other rules work correctly. Also if you try to enable the disabled rules they receive the following error message:

    One or more rules could not be uploaded to Exchange server and have been deactivated. This could be because some of the parameters are not supported or there is insufficient space to store all your rules.

    Why it occurs: This behavior occurs if the rules that are in your mailbox exceed a size of 32 kilobytes (KB). The rules size limit for mailboxes on Microsoft Exchange Server is 32 KB. In Outlook 2003/Outlook 2007, the size of rules has increased mostly to provide support for the Unicode format.

    Note The rules size limit for mailboxes in Microsoft Exchange Server 2007 has been increased to a default size of 64 KB per mailbox. The rule limit is now a customizable limit up to 256 KB per mailbox.

    Please find the following KB, which helps us how to mitigate this situation and has couple of workarounds for this issue.

  • Le Café Central de DeVa

    Outlook 2010, Windows Mobile & SMS Sync: Send and receive text messages from your e-mail account

    • 0 Comments

    You can send and receive text messages from your e-mail account if you're using a Windows Mobile 6.5 phone or you've downloaded and installed the Outlook Mobile Update on your Windows Mobile 6.1 phone. This functionality is known as SMS Sync.

    Enable Text Message Synchronization

    To enable text message synchronization on a Windows Mobile 6.1 phone or a later version that's synchronized with a Microsoft Exchange account, use the following steps.

    1. On the mobile phone, select the Text Message application.
    2. To display the configuration page, select Menu > Tools > Manage SMS Sync.
    3. On the Manage SMS Sync options page, turn on SMS Sync by selecting either Inbox or Text Message. These are the two folders that can hold your text messages.
    4. To complete the setup, select OK.

     

    image

    Note: An update is required for Windows Mobile 6.1 phones. This update can be downloaded and installed on your phone after it's synchronized successfully with an Exchange server that supports SMS Sync.

    Sending Text Messages from Your Account

    After you've set up your mobile phone to synchronize text messages with your e-mail account, you'll receive an e-mail message titled Send and receive mobile text messages on your computer. Text messages from your mobile phone will be synchronized to your mailbox and will appear in either the Inbox or the Text Message folder.
    image

    To start sending text messages from your e-mail account, close and reopen Outlook 2010 or Outlook Web App. To send a new text message, click Text Message in the New drop-down menu. When you click Send, the message will be synchronized from your mailbox to your phone and then sent through your phone.
    image

    Note: Normal text message fees apply and will appear on your phone bill.


    Depending on your synchronization settings, there might be a short delay before your text message is sent from your phone. To avoid delays, set ActiveSync on your phone to synchronize items as they arrive instead of on a schedule.

    To set ActiveSync on your phone to synchronize items as they arrive, use the following steps.

    1. On your mobile phone, select the ActiveSync application.
    2. Select Menu > Schedule to open the scheduling options page.
    3. Select As items arrive.
    4. Select OK.


    Note: We don't recommend that you choose a synchronization schedule of as items arrive unless you have an unlimited mobile phone data plan.

  • Le Café Central de DeVa

    How to: Configure Outlook Social Connector for Facebook?

    • 0 Comments

    If you had followed my previous blog post, downloaded and installed Outlook Social Connector (OSC) for Facebook, you can have a look at this video:

    Get Microsoft Silverlight

    If you want to configure just follow the steps to configure it:

    • Once you install the download, restart Outlook, and you will be prompted by the Outlook Social Connector configuration wizard to connect to Facebook.
      1. Under Social Network Accounts, select Facebook.
      2. For User Name: enter your Facebook email account.
      3. For Password: enter your Facebook password.
      4. Click Connect
      5. Once the connection is successfully completed, click Finish
    • If you were not prompted by the Outlook Social Connector configuration wizard, you can still connect to Facebook.

      For Outlook 2010:
      1. On the View tab, in the People Pane group, click People Pane, and then click Account Settings.
      2. Under Social Network Accounts, select Facebook.
      3. For User Name: enter your Facebook email account.
      4. For Password: enter your Facebook password.
      5. Click Connect.
      6. Once the connection is successfully completed, click Finish.

      For Outlook 2007 and Outlook 2003:
      1. Click Tools, and then click Social Network Account Settings.
      2. Under Social Network Accounts, select Facebook.
      3. For User Name: enter your Facebook email account.
      4. For Password: enter your Facebook password.
      5. Click Connect.
      6. Once the connection is successfully completed, click Finish.

    Hope this helps.

  • Le Café Central de DeVa

    Outlook error : Your mailbox has been temporarily moved on Microsoft Exchange Server

    • 0 Comments

    Recently one of my customer tried opening Outlook and it thrown the following error:

    Outlook Connectivity Error

    During troubleshooting we noticed that the OWA works fine but problem while accessing Outlook. This happens because he still using the same profile and the mailbox was recreated some time earlier.

    In this scenario, i recommended him to delete the existing profile and create a new one like (Control panel-> Mail-> Show profiles...-> remove existing profile ->Create new profile). This resolved the issue and helped him to move ahead.

  • Le Café Central de DeVa

    Outlook 2010: Migrating CDO based application to Outlook Object Model(OOM) library

    • 3 Comments

    Recently one of my developer customer migrated from Outlook 2003 to 2010. He tried running the custom application (uses CDO & Outlook 2003) in Outlook 2010. It throws the error “ActiveX component can’t create object”. 

    Using the following test sample, I can reproduce the exact issue at my end:

    image

    As you know, Microsoft Outlook 2010 includes many architectural changes to the client-side MAPI subsystem. Of particular concern are scenarios in which Outlook is configured to use multiple Exchange accounts. Also, CDO 1.2.1 is a 32-bit client library and will not operate with 64-bit Outlook 2010. Given all these factors, CDO 1.2.1 is not supported for use with Outlook 2010 and we don’t recommend its usage with Outlook 2010. As updated earlier, in Outlook 2010 you need to re-write/migrate the code base referencing CDO to Outlook Object Model or MAPI, messaging libraries which ever suits you.  So the programs/custom applications that use CDO should be re-designed to use other Application Programming Interfaces (APIs) instead of CDO.

    Starting with Outlook 2007, the Outlook object model was greatly expanded to provide functionality that was previously available only by using CDO 1.2.1. The Outlook 2010 object model includes some new features to expand on this more. For example, the Outlook 2010 object model has new functionality to operate correctly with multiple Exchange accounts. The Outlook object model also works for both 32-bit and 64-bit versions of Outlook. Developers should use the Outlook 2010 object model instead of CDO 1.2.1. Also, developers can still use Extended MAPI (which requires unmanaged C++) in some scenarios where CDO was required. However, if it is possible, we generally recommend that the Outlook object model be used instead of Extended MAPI.

    In this post, we will take the above code sample and will show how you can migrate/re-write the CDO based application to Outlook Object Model library.

    CDO sample – created in Outlook 2003:
       1: Dim MapiSession As Object
       2: Dim MapiMessage As Object
       3: 
       4: 
       5:   
       6: Set MapiSession = CreateObject("Mapi.Session") ' Create the MAPI Session.
       7:  
       8: MapiSession.Logon , , , False                  ' Log on to the session.
       9:  
      10: Set MapiMessage = MapiSession.Outbox.Messages.Add
      11:  
      12: With MapiMessage
      13:     .To = "testuser@contoso.com"
      14:     .Subject = "Test"
      15:     .Text = "Test"
      16:     .send showdialog:=True
      17: End With
      18:  
      19: MapiSession.Logoff
      20:  
      21: Set MapiSession = Nothing  ' Clear the object variable.
    • In order to start with, we will do it from the declaration section – you can see the CDO/OOM migrated sample and notice the changes.
    • In CDO code, it’s specified as Set MapiSession = CreateObject(“Mapi.Session”). When it comes to Outlook Object Model, then it should be converted as, Set MapiSession = CreateObject("Outlook.Application")
    • Now, we will try the next line, which is doing logon() call. In CDO, it’s MapiSession.Logon , , ,False. In OOM, it’s you need to add GetNamespace, so MapiSession.GetNamespace("MAPI").Logon , , , False
    • Next line in CDO points that a new mail item will be created in Outbox folder. In OOM, it need to be simplified: MapiSession.CreateItem(olMailItem).
      • Please note I haven’t used outbox folder like, MapiSession.GetNamespace("MAPI").GetDefaultFolder(olFolderOutbox)
    • I don’t see much changes when you specify the values for MapiMessage, except for .Send (CDO) – just needs to be trimmed as .Send(in OOM)

    Once you done with migration, the OOM code (created in Outlook 2010) will look like the below:

       1: Dim MapiSession As Outlook.Application
       2: Dim MapiMessage As Outlook.MailItem
       3:           
       4: Set MapiSession = CreateObject("Outlook.Application") ' Create the MAPI Session.
       5: MapiSession.GetNamespace("MAPI").Logon , , , False
       6:                            
       7: Set MapiMessage = MapiSession.CreateItem(olMailItem)
       8: With MapiMessage
       9:     .To = "testuser@contoso.com"
      10:     .Subject = "Test"
      11:     .Body = "Test"
      12:     .Send
      13: End With
      14:  
      15: Set MapiSession = Nothing

    Please note: Microsoft product support can help developer customers migrate custom programs from using CDO 1.2.1 to using other APIs. However, Microsoft will not provide support for any scenarios in which CDO 1.2.1 is used with Outlook 2010.

    Happy programming!!

  • Le Café Central de DeVa

    Outlook 2007 & RSS Feeds : RSS Feeds synchronization failed ?

    • 0 Comments

    rss_feed One of my customer and several others, have subscribed to RSS Feeds with Outlook 2007. It was working fine and all of a sudden it showing the error mark in the status bar.

    For example, whenever we make a Send/Receive, we get error mark in the status bar saying that “Task ‘RSS Feeds’ reported error (0x8C5C0008) : Synchronization to RSS Feed: […] has failed. Outlook cannot download the RSS content from […] because of a problem connecting to the server.”

    Here there might be lot of parameters may play here.

    • RSS synchronization interval with outlook
    • By default, RSS Feeds roam with users from one computer to another. So we need to make sure due to this we’re not getting these issue
    • If you have the latest service pack / latest version / patches can also create this issue.
    • It might be with their older feed entries in some kind of local store.
    • Sync utility might have issue with the new feed entries
    • As you know these RSS feeds are published by their own editors in an XML format. It contains only the latest headlines. The exact number of these headlines is chose by the editor, and, each time a new entry is added in the feed, the oldest one is removed (it's a FIFO behavior).
    • Some RSS clients (like Outlook and the Windows RSS Platform) keep the older feed entries in some kind of local store, so you can always see these entries, but these are no longer publish by their original editors.

    You can try these below for workarounds.

    1) Workaround # 1:

    • The frequency of RSS updates can be set by the user, but precedence is given to limits set by a provider on how frequently a subscriber can request updates from their site.
    • This helps avoid overloading the provider's server with excessive update requests

    2) Workaround # 2:

    • You can use the default RSS folder home page provided with Office Outlook 2007 , or you can create one tailored to your organization. Whether you use the default home page or provide a custom one, users must be connected to the network to view the home page. With both default and custom RSS home pages, you can take steps to ensure that the offline experience is not confusing to your users. When users are offline and switch to the RSS folder, an error message appears, stating that the page is not found.

    For users to have a good offline experience, Outlook displays a message explaining the problem instead of simply returning the standard "Page not found" error when it determines that a folder home page is being loaded.

    When users are offline, there are two requirements for Outlook to display the explanatory message instead of a standard error:

    · A string must be included at the end of the title on the page used for the folder home page.

    · The folder must be created with a new Outlook folder type.

    To meet the first requirement, you add the following string to the end of the title of the custom RSS home page you create: (Outlook Homepage). The string and anything after that string is not displayed in the title of the page. When a user is offline, the explanatory message is displayed. When a user is online, the folder home page is displayed with the string removed so users do not see the string in the title.

    The second requirement—a new Outlook folder type—ensures that the explanatory message for the RSS folder home page is not displayed for other folder home pages when users are offline. The standard Outlook folder type is IPM.Folder. The new folder type for RSS folders is IPM.Folder.OutlookHomepage

    Note: For more information, you can find more information from http://technet.microsoft.com/en-us/library/cc179173(TechNet.10).aspx

Page 1 of 26 (649 items) 12345»