February 2008 - posts - Bart Wessels' blog

Bart Wessels' blog

Weblogs

Links

February 2008 - posts

Tips and Tricks to Get the Most Out of Microsoft Office Outlook 2007

Mijn collega Mor geeft een sessie over productiviteit in Outlook:

Mor Hezi - Tips and Tricks to Get the Most Out of Microsoft Office Outlook 2007

This presentation will provide tips and tricks for Microsoft Office Outlook 2007 and will focus on ways that outlook and its integration with other Office applications can help make you more productive.


Video: Mor Hezi - Tips and Tricks to Get the Most Out of Microsoft Office Outlook 2007

Bart

Posted: Feb 28 2008, 01:29 PM door Bart Wessels | met no comments
Opgeslagen onder:
Office Business Application for Customer Support Management

Er is een voorbeeld applicatie gepubliceerd waarmee je kan leren hoe je zelf een oplossing kan maken, gebruik makend van het Office System:

Summary: Learn to build custom applications that use Microsoft Office SharePoint Server 2007, Microsoft Office InfoPath 2007, SQL Server Analysis Services, SQL Server Integration Services, and the Business Data Catalog. (28 printed pages)

Applies to: 2007 Microsoft Office System, Microsoft Office SharePoint Server 2007, Microsoft Office InfoPath 2007, Microsoft Visual Studio 2008, Microsoft Visual Studio 2005, and Microsoft SQL Server 2005.

Customer Service Request Solution

Providing timely, accurate responses to customer service requests is a key factor in the success of any customer support organization. The degree to which an organization's Customer Service Request system facilitates the process of monitoring and responding to service requests has a direct relationship to customer satisfaction.

Some common challenges organizations face when implementing a Customer Service Request solution are:

  • Context switching. Many customer service request solutions require support personnel to switch between applications to track and work with customer requests. This context switching creates the possibility of missed service requests and reduces employee productivity.

  • Deployment and maintenance costs. The cost to the IT department of deploying and maintaining a customer service request system on the desktop of support personnel can be extremely high.

  • Ease of access to customer service request line-of-business (LOB) data. Managers must often switch between applications to monitor service request activity.

This article presents an example of an Office Business Application built on the Microsoft Office system that addresses typical collaboration and business insight requirements of a Customer Service Request application. The solution allows end users to live in familiar Microsoft Office applications and use their natural workflows while being connected to line-of-business systems. The Office Business Application makes use of the following key Microsoft products and technologies:

  • Microsoft Office InfoPath 2007

  • Microsoft Office Outlook 2007

  • Microsoft Office SharePoint Server 2007 including

    • Business Data Catalog

    • Microsoft Office Excel Services and Excel Web Access

    • InfoPath Forms Services

  • Microsoft Visual Studio 2008

  • Microsoft Visual Studio 2005 Extensions for Windows SharePoint Services 3.0

  • Microsoft SQL Server 2005 database, Analysis Services, and Integration Services

Using these products and technologies deliver the following benefits:

  • Rapid application development with familiar tools and reusable components. You can use the familiar Visual Studio development environment to develop the different solution components. The solution uses a single InfoPath form to allow customers to submit requests and support personnel to manage responses.

  • Simplified application deployment and maintenance. The solution uses server-based services and removes the need to deploy anything to the desktop.

  • No context switching. Using Microsoft Office Outlook 2007 as the user interface for working with service requests allows support personnel to stay in the familiar applications they use.

  • Easy access to LOB data. LOB data from the customer service request system appears in Office Outlook as dashboards. This integration removes the need for support personnel to switch to a different system to monitor active service requests.

The combination of rapid application development, ease of deployment, and natural workflow creates an attractive solution to developers, IT staff, and end users.

Klik hier voor het hele document.

Bart

GPOAccelerator

Brief Description:

    The GPOAccelerator is a script that creates GPOs to deploy security settings for the 2007 Microsoft Office release, Windows Vista, and Windows XP in Active Directory environments.

Overview:

    GPOAccelerator

    The GPOAccelerator automatically deploys the security recommendations in the 2007 Microsoft Office Security Guide, the Windows Vista Security Guide and the Windows XP Security Guide. These guides recommend Group Policy configurations and, in the case of Windows Vista and Windows XP, security template configurations that are enforced via Active Directory in your environment. Each of these guides contains prescriptive recommendations for two security baselines, Enterprise Client (EC) and Specialized Security – Limited Functionality (SSLF). These baselines have been thoroughly tested and validated. The recommended EC and SSLF Group Policy objects (GPOs) for the 2007 Office release, Windows Vista, and Windows XP are included in this download for quick, error-free deployment.

    How To Use the GPOAccelerator

    This download also includes a How To guide that provides step-by-step guidance for setting up a test environment, configuring the GPOs, linking the GPOs to a test or production OU structure, and deploying them. The following list describes each chapter:

    • Chapter 1: GPOAccelerator Commands and Switches. This chapter describes how to use the tool to create and deploy GPOs in your organization and also describes the tool's functional capabilities.

    • Chapter 2: Using the GPOAccelerator with Windows XP. This chapter provides step-by-step guidance about how to use the tool to create and deploy GPOs for Windows XP. It describes how to use the /LAB option, test a customized Windows XP GPO design in a lab environment, and deploy a customized Windows XP GPO design in a production environment.

    • Chapter 3: Using the GPOAccelerator with Windows Vista. This chapter provides step-by-step guidance about how to use the tool to create and deploy GPOs for Windows Vista. It describes how to use the /LAB option, test a customized Windows Vista GPO design in a lab environment, and deploy a customized Windows Vista GPO design in a production environment.

    • Chapter 4: Using the GPOAccelerator with the 2007 Microsoft Office Release. This chapter provides step-by-step guidance about how to use the tool to create and deploy GPOs for the following six applications in the 2007 Office release:
        • Microsoft Office Access 2007

        • Microsoft Office Excel 2007

        • Microsoft Office InfoPath 2007

        • Microsoft Office Outlook 2007

        • Microsoft Office PowerPoint 2007

        • Microsoft Office Word 2007

          • This chapter also describes how to test a customized 2007 Office GPO design in a lab environment and deploy a customized 2007 Office GPO design in a production environment.

        Klik hier voor de download.

        Bart

        SharePoint Designer Training

        Hier kan je training vinden voor SharePoint Designer:

        Office SharePoint Designer 2007 Training Standalone Edition

        The Microsoft Office SharePoint Designer 2007 Training (Standalone Edition) leads the learner step-by-step through SharePoint Designer features using easy to understand videos.

        Office SharePoint Designer 2007 Training Portal Edition

        The Microsoft Office SharePoint Designer 2007 Training (Portal Edition) leads the learner step-by-step through SharePoint Designer features using easy to understand videos.

        Bart

        UPDATE: Links aangepast...

        Introduction to the OBA Composition Reference Toolkit

        Introduction to the OBA Composition Reference Toolkit

        Platform Architecture Director Javed Sikander discusses the new OBA Composition Reference Toolkit which was just announced at ODC 2008. OBA has come a very long way since we last chatted with Javed. The OBA Composer, which ships as part of the toolkit, is really impressive WYSIYG designer tool for Sharepoint applications.

        lees hier verder.

        Bart

        deja vu

        David heeft dit keer een comic die ik graag hier ook even plaats:

        She sure has moxie

        Hier kan je zijn dagelijkse comic vinden.

        Bart

        Posted: Feb 26 2008, 09:04 PM door Bart Wessels | met no comments
        Opgeslagen onder:
        Bob Sutton - Introduction to SharePoint

        Voor een ieder die nog niet echt bekend is met wat SharePoint is en kan geeft Bob Sutton hier een overzicht:


        Video: Bob Sutton - Introduction to SharePoint

        Bart

        Posted: Feb 26 2008, 01:29 PM door Bart Wessels | met no comments
        Opgeslagen onder: ,
        Microsoft SharePoint Server 2007 and System Center

        Gisteren is deze datasheet gepubliceerd:

        Brief Description

        Managing, deploying, and protecting SharePoint Server 2007 with System Center
        Read this datasheet and find out how System Center solutions can help deploy, monitor, and protect Microsoft Office SharePoint Server 2007.

        Overview

        Microsoft Office SharePoint Server 2007 is the driving force behind companies building integrated workflow and collaboration systems. With SharePoint, businesses leverage in-house expertise; build teams to accomplish project tasks; and manage content and workflow, regardless of the physical locations of the participants. Read this datasheet and find out how System Center solutions can help deploy, monitor, and protect Microsoft Office SharePoint Server 2007.

        Klik hier voor de download.

        Bart

        VSTO Power Tools

        Microsoft Visual Studio Tools for the Office System Power Tools v1.0.0.0

        Brief Description

        A set of developer tools designed to complement Visual Studio Tools for Office.

        Overview

        A set of developer tools that provide additional functionality useful in Office-based development. These tools include Visual Studio add-ins as well as standalone Windows Forms and console applications. The VSTO Power Tools also include a set of re-usable class libraries to simplify Office development.

        Klik hier om de tools te downloaden.

        Bart

        Posted: Feb 22 2008, 09:47 AM door Bart Wessels | met no comments
        Opgeslagen onder: , ,
        SkyDrive beschikbaar in nederland

        Vanaf vandaag is SkyDrive ook beschikbaar in Nederland:

        image

        http://skydrive.live.com

        Handig bestanden online bewaren (5 gig ruimte!)

        Bart

        Wat zijn de gevolgen voor Office?

        Zoals in mijn vorige post te lezen is, gaat er veel veranderen.

        Gray schrijft Over de implicaties hiervan voor Office op zijn blog:

         

        For Office 2007, we will design and make available interfaces that can enable different file formats to be set as a default format in Word, Excel and PowerPoint. This addresses a key concern of organizations like BECTA who desire to have ODF or UOF or other formats enabled as a "default" for Microsoft Office applications. Should other file formats emerge in the future that are suited to word processing, spreadsheets or presentations, these new interfaces will enable their use with Office as well. In the past few years, we've seen a lot of momentum around document format support, and today's announcement will only improve the ability for others to integrate with our products.

        It's important to note that the interoperability principles are unrelated to the current ISO standardization process for Open XML, and that process will proceed without regard to what is being announced today. But the objectives of Open XML now have an increased focus and sharpness. The purpose of the Ecma standard (and proposed ISO standard) is to represent content that exists in billions of binary documents, as well as delivering the type of business process integration enabled by the use of custom-defined schema. Open XML is unique in this regard.

        We've said this before, but the goals of Open XML are distinctly different than ODF, PDF or UOF, and hopefully we can begin to separate the conversation about product functionality from the necessity for the Open XML standard. In our view, these have always been different conversations. The addition of these interfaces removes a potential obstacle to the adoption of other standards within our products.

        The change should also underscore the idea that support for Open XML is not the same as opposition to other standards, despite many claims to this effect. Different formats are a means to achieving specific types of work, and interested communities exist to offer support for them. Today's commitment creates new opportunities to use many document formats in Office, and will allow people a greater ability to choose the formats that best suit their specific needs. This is good for our customers, but it's good for our business, too; adding these interfaces makes a lot of sense.

        Lees hier zijn hele post

        Bart

        Microsoft Makes Strategic Changes in Technology and Business Practices to Expand Interoperability

        Via de pers site:

        New interoperability principles and actions will increase openness of key products.

        REDMOND, Wash. — Feb. 21, 2008 — Microsoft Corp. today announced a set of broad-reaching changes to its technology and business practices to increase the openness of its products and drive greater interoperability, opportunity and choice for developers, partners, customers and competitors.

        Specifically, Microsoft is implementing four new interoperability principles and corresponding actions across its high-volume business products: (1) ensuring open connections; (2) promoting data portability; (3) enhancing support for industry standards; and (4) fostering more open engagement with customers and the industry, including open source communities.

        “These steps represent an important step and significant change in how we share information about our products and technologies,” said Microsoft chief executive officer Steve Ballmer. “For the past 33 years, we have shared a lot of information with hundreds of thousands of partners around the world and helped build the industry, but today’s announcement represents a significant expansion toward even greater transparency. Our goal is to promote greater interoperability, opportunity and choice for customers and developers throughout the industry by making our products more open and by sharing even more information about our technologies.”

        According to Ray Ozzie, Microsoft chief software architect, the company’s announcement reflects the significance that individuals and businesses place upon the ease of information-sharing. As heterogeneity is the norm within enterprise architectures, interoperability across applications and services has become a key requirement.

        “Customers need all their vendors, including and especially Microsoft, to deliver software and services that are flexible enough such that any developer can use their open interfaces and data to effectively integrate applications or to compose entirely new solutions,” said Ozzie. “By increasing the openness of our products, we will provide developers additional opportunity to innovate and deliver value for customers.”

        “The principles and actions announced today by Microsoft are a very significant expansion of its efforts to promote interoperability,” said Manfred Wangler, vice president, Corporate Research and Technology, Software and Engineering, Siemens. “While Microsoft has made considerable progress on interoperability over the past several years, including working with us on the Interoperability Executive Customer Council, today’s news take Microsoft’s interoperability commitment to a whole new level.”

        “The interoperability principles and actions announced today by Microsoft will benefit the broader IT community,” said Thomas Vogel, head, Information Management, Novartis Pharma. “Ensuring open connections to Microsoft’s high-volume products presents significant opportunities for the vast majority of software developers, which will help foster greater interoperability, opportunity and choice in the marketplace. We look forward to a constructive, structured, and multilateral dialogue to ensure stakeholder-driven evolution of these principles and actions.”

        The interoperability principles and actions announced today apply to the following high-volume Microsoft products: Windows Vista (including the .NET Framework), Windows Server 2008, SQL Server 2008, Office 2007, Exchange Server 2007, and Office SharePoint Server 2007, and future versions of all these products. Highlights of the specific actions Microsoft is taking to implement its new interoperability principles are described below.

        Ensuring open connections to Microsoft’s high-volume products. To enhance connections with third-party products, Microsoft will publish on its Web site documentation for all application programming interfaces (APIs) and communications protocols in its high-volume products that are used by other Microsoft products. Developers do not need to take a license or pay a royalty or other fee to access this information. Open access to this documentation will ensure that third-party developers can connect to Microsoft’s high-volume products just as Microsoft’s other products do.

        As an immediate next step, starting today Microsoft will openly publish on MSDN over 30,000 pages of documentation for Windows client and server protocols that were previously available only under a trade secret license through the Microsoft Work Group Server Protocol Program (WSPP) and the Microsoft Communication Protocol Program (MCPP). Protocol documentation for additional products, such as Office 2007 and all of the other high-volume products covered by these principles, will be published in the upcoming months.

        Microsoft will indicate on its Web site which protocols are covered by Microsoft patents and will license all of these patents on reasonable and non-discriminatory terms, at low royalty rates. To assist those interested in considering a patent license, Microsoft will make available a list of specific Microsoft patents and patent applications that cover each protocol.

        Microsoft is providing a covenant not to sue open source developers for development or non-commercial distribution of implementations of these protocols. These developers will be able to use the documentation for free to develop products. Companies that engage in commercial distribution of these protocol implementations will be able to obtain a patent license from Microsoft, as will enterprises that obtain these implementations from a distributor that does not have such a patent license.

        Documenting how Microsoft supports industry standards and extensions. To increase transparency and promote interoperability, when Microsoft supports a standard in a high-volume product, it will work with other major implementers of the standard toward achieving robust, consistent and interoperable implementations across a broad range of widely deployed products.

        Microsoft will document for the development community how it supports such standards, including those Microsoft extensions that affect interoperability with other implementations of these standards. This documentation will be published on Microsoft’s Web site and it will be accessible without a license, royalty or other fee. These actions will allow third-party developers implementing standards to understand how a standard is used in a Microsoft product and foster improved interoperability for customers. Microsoft will make available a list of any of its patents that cover any of these extensions, and will make available patent licenses on reasonable and non-discriminatory terms.

        Enhancing Office 2007 to provide greater flexibility of document formats. To promote user choice among document formats, Microsoft will design new APIs for the Word, Excel and PowerPoint applications in Office 2007 to enable developers to plug in additional document formats and to enable users to set these formats as their default for saving documents.

        Launching the Open Source Interoperability Initiative. To promote and enable more interoperability between commercial and community-based open source technologies and Microsoft products, this initiative will provide resources, facilities and events, including labs, plug fests, technical content and opportunities for ongoing cooperative development.

        Expanding industry outreach and dialogue. An ongoing dialogue with customers, developers and open source communities will be created through an online Interoperability Forum. In addition, a Document Interoperability Initiative will be launched to address data exchange between widely deployed formats.

        The Interoperability Executive Customer (IEC) Council, an advisory organization established in 2006 and consisting mainly of chief information and technology officers from more than 40 companies and government bodies around the world, will help guide Microsoft in its work under these principles and actions. The full text of Microsoft’s new Interoperability Principles, and a full list of the actions Microsoft is taking, can be found on Microsoft’s Interoperability site.

        The interoperability principles and actions announced today reflect the changed legal landscape for Microsoft and the IT industry. They are an important step forward for the company in its ongoing efforts to fulfill the responsibilities and obligations outlined in the September 2007 judgment of the European Court of First Instance (CFI).

        “As we said immediately after the CFI decision last September, Microsoft is committed to taking all necessary steps to ensure we are in full compliance with European law,” said Brad Smith, Microsoft general counsel. “Through the initiatives we are announcing, we are taking responsibility for implementing the principles in the interoperability portion of the CFI decision across all of Microsoft’s high-volume products. We will take additional steps in the coming weeks to address the remaining portion of the CFI decision, and we are committed to providing full information to the European Commission so it can evaluate all of these steps.”

        Hier staat het orginele bericht: http://www.microsoft.com/presspass/press/2008/feb08/02-21ExpandInteroperabilityPR.mspx?rss_fdn=Press%20Releases

        Bart

        Videos over de Open XML to Daisy Convertor

        Afgelopen maandag heb ik in een blogpost verteld over de Open XML to Daisy Convertor. Er staan ook een tweetal filmpjes op het web die hier meer over vertellen:

         En deel 2 met een demo:

        Bart

        Posted: Feb 20 2008, 07:51 PM door Bart Wessels | met no comments
        Opgeslagen onder: ,
        toegankelijkheid van software

        Na mijn post over Accessibility door de Open XML to Daisy Convertor ben ik me verder gaan verdiepen in toegankelijkheid van Software. Dat er in Office al veel mogelijk was dat wist ik al, maar sinds de 2007 versie is er nog meer aan gewerkt.

        Overigens wordt aan toegankelijkheid van software niet alleen in het Office team aandacht besteed. Ook in Windows Vista is hier aan gewerkt.

        Op deze website kan je informatie over dit onderwerp vinden: http://www.microsoft.com/enable/

        • Toegankelijkheid in Office kan je in verschillende groepen indelen:
        • Toegankelijkheid in het menu
        • Toegankelijkheid via sneltoetsen
        • Zoom functies
        • Galerieën voor sneller professioneler resultaat
        • SmartArt
        • Spraakherkenning (dankzij Windows Vista)

        En meer…kijk hiervoor op eerdergenoemde site.

        Laten we op de sneltoetsen eens klein stukje inzoomen:

        Toegankelijkheid via Sneltoetsen

        Interessante informatie is onder andere een presentatie over hoe je via het toetsenbord optimaal gebruik kan maken van Office 2007:

        Training presentation (PowerPoint Template): Microsoft Office Keyboard shortcuts in the 2007 system

        Enkele punten waar ik zelf iets van opgestoken heb vandaag zijn F6 en TAB:

        Via F6 kan je door delen van de applicatie heen “fietsen” in Office 2007. In dit soort gevallen grijp ik altijd naar mijn muis, maar dat is dus niet altijd nodig:

        Afbeelding die de volgorde van verspringen via de F6 toets in een Office applicatie laat zien

        Als je door de ALT toets de focus op de ribbon het gebracht, en worden alle functies met een letter weergegeven in het menu, je kan vervolgens met ALT-letter of met de pijltjes door de menuopties “lopen”:

        Afbeelding die de ALT functies in een Office applicatie weergeeft

        Met de TAB toets kan je eventueel ook door alle opties in het menu lopen:

        Afbeelding die de TAB opties in een Office applicatie weergeeft

        Wanneer je bijvoorbeeld document sjablonen maakt, dan kan het handig zijn dat je rekening houdt met de opties in Office. Een handige lijst met tips kan je hier vinden:

        Er zit dus in Office 2007 erg veel op het gebied van toegankelijkheid, en ik heb vanuit de productteams al meegekregen dat we hier nog niet klaar zijn. In Office 14 zal je dus nog meer in deze hoek kunnen verwachtten.

        Bart

        ps. Tijdens het schrijven van dit stuk had ik een instelling niet goed staan in Word, waardoor links als volgt weergeven werden:

        clip_image002

        Toggle Show fieldcodes in de opties in Word lossen dit op. Waarvoor dank aan Andre, Hans en Ingeborg...

        Posted: Feb 19 2008, 09:41 PM door Bart Wessels | met no comments
        Opgeslagen onder:
        Centric doet Open XML en ODF

        Terwijl ik mijn vorige post aan het plaatsen ben, komt er een nieuwsbrief binnen van IT Executive, met daarin een artikel met de volgende titel:

        Centric switcht naar open standaarden

        Dat Centric iets ging doen met Open Standaarden had ik eerder deze week al gelezen in de Automatiserings Gids, maar hierin werd vrijwel alleen ODF genoemd, terwijl het persbericht van Centric toch veel duidelijker de ondersteuning voor zowel ODF als Open XML aangaf.
        In de nieuwsbrief van IT Executive zie ik nu inderdaad terug dat het niet alleen ODF betreft, maar ook Open XML. Daarmee genereert Centric dus ook keuze mogelijkheden voor haar gebruikers op basis van open standaarden.

        In het laatste deel van het uitermate interessante artikel raak ik de weg even kwijt:

        Centric verwacht zijn applicaties voor gemeenten pas na de zomer volledig aangepast te hebben aan deze nieuwe formaten.
        De aankondiging van Centric werd door Aad Koppenhol van Sun, de grote sponsor achter het OpenOffice.org project, met enige scepsis ontvangen. "Dat Centric gemeenten garandeert dat ze binnenkort ook met odf kunnen gaan werken neem ik met een korreltje zout. Een voorwaarde daarvoor is namelijk dat Centric een onderhoudscontract met Sun afsluit voor OpenOffice.org en voor Sun's odf-plugin voor Office 2003. Zo'n contract is er helemaal nog niet, dus ze kunnen die garantie niet waarmaken."
        Koppenhol noemt het een grote misvatting dat, omdat deze software gratis beschikbaar is, er geen geld meer hoeft te worden gestoken in de verdere ontwikkeling ervan. "Kijk naar de Apache webserver of naar MySQL. Grote afnemers sluiten daarvoor onderhoudscontracten af. Dat stelt de verdere ontwikkeling voor een belangrijk deel zeker. Je moet daar niet alleen de vrijwillige community mee belasten."
        Ben van Lier van Centric: "Wij gaan ODF ondersteunen, niet OpenOffice. Dat is een wezenlijk verschil. Concreet houdt dat in dat onze documentgenerator DOC4all, die nu het rtf-formaat als output heeft, nog dit jaar ook odf, ooxml en pdf als mogelijke output krijgt. Voor die aanpassing hebben we Sun niet nodig. Dat kunnen we zelf."

        Is hier sprake van een misverstand?

        Van een verkeerd citaat?

        Wat bedoelde Aad Koppenhol van Sun hier met zijn opmerking dat een voorwaarde voor het ondersteunen van ODF door Centric een contract met Sun zou moeten zijn?

        ODF versie 1.0 is in ieder geval een ISO standaard (ISO 26300), de andere ODF versies in de praktijk zijn ofwel “grijze” proprietary versies of OASIS standaarden. Maar dan nog, de ODF specificatie is toch zeker vrij voor iedereen te implementeren?

        In het andere geval zou Sun hier bedoelen dat om Open Office.org te mogen gebruiken er een onderhoudscontract met Sun vereist is? Of voor het gebruik van de Sun ODF plug-in?

        Ik ga maar uit van een misverstand tussen Sun en de journalist.

        Dat overkomt ons ook nog wel eens Smile

        Bart

        Posted: Feb 19 2008, 04:38 PM door Bart Wessels | met no comments
        Opgeslagen onder:
        Meer posts Volgende pagina »