Welcome to MSDN Blogs Sign in | Join | Help

As you might be already aware, proper functioning of Duet depends on a correctly configured Exchange account. Duet configuration settings are stored in a special hidden folder in your Exchange account. It is important that users and administrators do not accidentally delete messages from this folder.

If, for some reason, Duet configuration settings in this folder are deleted or corrupt, Duet will not function correctly. But, not all is lost!

We provide a repair tool to help you during such circumstances. You can find the executable Microsoft.OBA.ClientRepair.exe in the Duet installation folder. This is a very versatile tool and can do quite a few things. This blog post will cover two of those capabilities.

The first option is the /CleanupExchangeAccount option. It's important that you use this option only if you see the following message when Outlook starts: "Your Exchange account is corrupted...."

Running ClientRepairTool with /CleanupExchangeAccount option will do the following…

  • Delete the Duet special hidden folder
  • Reset the Duet registry key that points to your outlook profile
  • Mark Duet for re-deployment the next time (by resetting the appropriate registry key)

Run…

 Microsoft.OBA.ClientRepair.exe /CleanupExchangeAccount at the command prompt.

Once the client repair tool successfully runs, you should exit the Duet system tray utility and restart it from the Start menu. This will trigger the deployment (remember that the client repair tool had marked your computer for re-deployment). Deployment will restore the correct values for the stuff that were deleted above and re-create the hidden folder.

The second option I'm going to talk about is the /CheckExchangeAccountConfiguration. Yeah, it's a little verbose! But, that clearly explains what it is going to do, doesn't it? Alright, if you're a Duet 1.0 or Duet 1.5 preview user, you're not going to see this option yet. This is being introduced newly in the next version. Here's a sneak peak at what it is for.

More often than not, it will be desirable to figure out what went wrong before fixing the problem. Though the /CleanupExchangeAccount is a very useful option, you don't want to re-deploy Duet if the issue is something else. To be sure, it's your exchange account configuration with Duet that is corrupt, you can use this option. Here's a sample output from the tool (when Duet is configured properly with your Exchange Account).

    SUCCESS: The Exchange account configuration is correct for the user.
    SUCCESS: Successfully logged on to Exchange using profile: Duet.
    SUCCESS: Successfully logged on to Exchange using profile: Duet.
    SUCCESS: Duet settings configuration message is present in the Exchange user account mailbox.
    SUCCESS: Duet personalization message is present in the Exchange user account mailbox.
    SUCCESS: Duet SDS backup message is present in the Exchange user account mailbox.

The above checks are performed in sequence and printed to the screen. If the tool encounters an error doing any of the above checks it will print a corresponding error message (E.g.: "ERROR: {0} specific properties are missing or unreadable on the settings configuration message.") and exit.

We hope you find these options useful. As I said before, please exercise restraint when using the clean up option of this tool. Your feedback is important. Share it with us. We're listening!

-Sivashankar, Program Manager, Duet Supportability and Tools.

This blog is meant for Administrators of Duet

This blog provides a quick overview on how to configure Duet 1.0 to use X.509 certificates. Enterprises as part of their security infrastructure use X.509 certificates to authenticate and authorize user access to corporate resources. X.509 certificates are used during the web-services calls made from the Duet clients to SAP backend servers. All X.509 certificates have expiration dates. Enterprises control the validation period for these certificates.

Default configuration of Duet is to not use X.509 certificates. Not all enterprises issue X.509 certificates to the end users because of the complexity involved in managing the certificates. However in enterprises that do issue X.509 certificates to users, Duet can be configured to use these certificates.

Group policy settings:

These settings described below configure Duet to use X.509 certificates while making web service calls to SAP backend servers.

Parameters Common Name (CN), Organization (O), Country Name (C) are to be filled in. Click the link below for picture how the group policy will be for these parameters.

http://blogs.msdn.com/photos/teamduet/images/6787393/original.aspx

Duet will wait for the certificate to be deposited in the "users personal certificate store" prior to making the web service calls.

In the absence of the certificates, user will get periodic notifications informing the absence of the certificates. The user has to contact the administrator to obtain the certificates.

The checkbox "Do not show X.509 Certificate missing notifications" can be used to suppress the "notifications" regarding the absence of the certificates. This is useful when the administrator has acknowledged the problem and is working on it.

Disabling X.509 authentication

Uncheck the check box "Use X.509 Authentication" in the Group Policy settings dialog and X.509 certificate will not be used in those computers while making the web service calls to SAP backend server.

-Ramakrishnan Nagasamy Program Manager, Duet

This blog is meant for Administrators and End Users of the Duet

This blog provides a back ground to the synchronization design of Duet. This blog will help end users and Duet administrators understand some of their experiences with Duet. Let us take an example of a new Duet Contact created in SAP backend. While some Duet users are able to view this Duet contact in Outlook others are not able to see this contact. This is a common scenario. Similarly, changes made to a Duet Item on a laptop never reached SAP backend. This is a common occurrence as well. This blog will attempt to demystify some of these experiences by high lighting the Duet design.

Duet Vision

Duet is a productivity application that integrates complex set of technologies through a multi-tier architecture. Duet landscape consists of Duet clients that end users interact with. These Duet client computers interact with of a variety of servers in the corpnet. Duet design and architecture ensures that end user productivity is not compromised when one or many or all of these services are not available at a given time. For users who are mobile, intermittent connectivity or total lack of connectivity to the corpnet services is the norm. Even business critical services are subject to planned shut-down. Duet design accommodates these conditions and ensures that end user stays productive at all times.

Let's take the scenario for a mobile user. Access to corpnet at all times is nearly impossible for this user. Offline access to business critical thus becomes very important. Similarly, the ability for this mobile user to change data on the road is equally important a feature. Duet ensures that these changes ultimately get submitted to SAP when this users computer joins the corpnet.

Duet Design

Duet cache on the client

Duet uses a client cache to store Duet Items that pertain to the user. This cache enables the user to interact with the Duet Items in Offline mode (where the computer is not connected to corpnet). All the changes made by the user are stored in this cache as well. When the computer is connected to the corpnet, these changes get submitted to the SAP. This is a huge productivity enhancer. The end user continues to interact with business critical data when is Offline and Duet ensures that the changes made by the user eventually get submitted to the SAP without any explicit user involvement.

Leveraging Exchange for SAP initiated workflow

While the user is roaming (mobile), SAP servers in the enterprise are processing workflows and thus create new Duet items or change existing Duet items that are of interest to the mobile user. However the user is mobile and not connected to the corpnet. This information (new Duet items or changed Duet items) need to reach the end user computer for it to be useful. To enable the flow of information, Duet leverages the power of Exchange. SAP servers queue these messages in the form of Control Messages which are instructions to Duet clients and route them to via Exchange. Exchange stores these Control Messages in special folders for the user, while the user is roaming. Once the Outlook on the user computer connects to Exchange, these Control Messages are delivered to the client where they are processed. New items or changes to existing items appear to the end user and are stored in the Duet cache as well for Offline use.

Here you can see the power of Duet design. SAP servers are processing workflow at their own pace. These servers are not dependent on the availability of the Duet clients being reachable. When SAP servers decide to communicate the required changes to the end user computer, they communicate with Exchange which is available for the servers at all times. Similarly, the Duet client users are not restricted on their mobility. When they connect to Exchange, all the relevant data is downloaded to their computer.

By leveraging Exchange in the design, Duet enables the productivity of the organization stay high by ensuring mobility restrictions are not placed on the end users for accessing business critical data.

Scalability

Duet is designed to scale. As described in the preceding 2 paragraphs, Duet design has 2 different routes communicate the changes to Duet items. User initiated changes are stored in the Duet cache and are submitted directly to SAP servers when the client is able to connect to SAP servers. SAP initiated changes are queued in Exchange and are delivered to the end user when the computer is able to connect to Exchange. This design allows IT administrators to effectively plan for Duet roll out without placing heavy burden on any one aspect of the system.

Possible causes for synchronization problems outlined in the first paragraph could be because of the connectivity of the client computer to either Exchange or SAP backend. When one or both of these servers could not be reached by the client some part of the data could not be synchronized. While this state will eventually heal itself and is the design goal of Duet, it could cause some confusion in the short term and hopefully this blog could go a little way into demystifying the experience.

-Srikanth Ranganathan, Lead Program Manager, Duet

This blog is meant for IT Planners and Administrators and end users of the Duet

In this blog we talk about 5 most commonly asked questions with respect to Duet 1.0.

1. Duet users must be domain users in the enterprise

Typically in enterprises, access to enterprise resources is controlled by domain level access control. Non domain users like local computer user or a workgroup user may not be able to access these resources. Duet leverages this pattern of access control and can used only domain joined users. End user credentials acquired at the time of domain login is used in all subsequent access to data from SAP. There is no plan to support non domain users in the future.

2. User (On the primary machine) should log-off from their desktop or laptop only after all the pending items are submitted to SAP.

Duet utilizes the concept of Primary, Secondary Duet machines. While the user can use the any Duet machine, changes made by the user are submitted to SAP from only the Primary machine for the user. In these primary machines, the user should stay logged in until all the Duet items have been submitted to SAP. Duet items not submitted to SAP will remain on the computer and will be submitted when the user logs on to the machine next time around.

For more information on Primary and Secondary Duet Clients, refer blog: http://blogs.msdn.com/teamDuet/archive/2007/08/31/primary-secondary-machines-in-Duet.aspx

3. Outlook and Duet utility should be running on the primary machine all the time

There are many users who use multiple machines to work on Duet items. This section deals with some constraints they have to work with. As mentioned in the earlier paragraph, there is one Primary machine for each user. This machine is used to submit all the changes to the Duet items to SAP. Outlook and Duet Utility should be running all the time in this primary machine.

Duet uses Exchange to route all the changes to the Duet Items made on the Secondary machines, and these changes are aggregated in the primary machine for that user and then submitted to SAP.  Duet Utility is the agent that is responsible for submitting these changes to SAP.

Outlook will receive all the changes and process them for submitting to SAP. If Outlook is shut down on the primary machine, then changes to Duet Item from the secondary machines (other Duet machines for this user) will never reach the primary machine. Hence these changes will not be submitted to SAP.

If Duet Utility is shut down on the primary machine, the changes to Duet Items will not be submitted to SAP.

4. The user should have configured at least one Outlook Exchange profile for that user on that client computer.

For Duet to be usable on the computer, Outlook Exchange profile must be configured. Duet cannot be configured for usage in the absence of an Outlook Exchange profile. In this situation,
Duet functionality will not be available for the user in Outlook. The Event logs identify the absence of Outlook Exchange profile for that user.

To enable Duet functionality in this situation, the user has to create an Outlook Exchange profile, and log off and log on.  Duet Utility will start to configure Duet after successful log on. Once Duet is successfully configured, Duet functionality will be available for that user. 

5. Platform Matrix for Duet 1.0

Duet utilizes premium features in available in Enterprise editions of Office. IT planners and Administrators should ensure that Duet is installed in Office 2003 Enterprise editions. The supported Operating systems for Duet 1.0 are Windows XP and Windows 2000.

 

-Ramakrishnan Nagasamy, Program Manager, Duet

This blog is intended for Administrators of Duet Landscape and for users who are running Vista. It will briefly outline installation and uninstallation procedures on Vista.

For customers who have installed a version of Microsoft Windows earlier than Microsoft Windows Vista on their computers, the majority of user accounts are configured as a member of the local administrator's group, because administrator privileges are required to install, update, and run many software applications without conflicts and to perform typical system-level tasks. Even the simplest operation, such as clicking the taskbar clock to view a calendar, requires administrator privileges.

Granting end-users administrative privileges makes individual computers and networks vulnerable to malware and increases total cost of ownership because users can make unapproved system changes. Malware can exploit the system-level privileges provided to the local administrator—damaging files, changing system configurations, and even transmitting confidential data outside the network. Unfortunately, deploying computers in a locked-down state by requiring users to operate in standard user mode severely limits user productivity. Without local administrative rights, many applications will not function properly, because they are designed to write to system locations during normal operation.

Windows Vista & User Account Control: Delivering a More Secure Desktop
The main goal of User Account Control is to reduce the exposure and attack surface of the operating system by requiring that all users run in standard user mode. This limitation minimizes the ability for users to make changes that could destabilize their computers or inadvertently expose the network to viruses through undetected malware that has infected their computer. With User Account Control, IT administrators can run most applications, components and processes with a limited privilege, but have "elevation potential" for specific administrative tasks and application functions.

Conversely, when users encounters a system task that requires administrator privileges, such as attempting to install an application, Windows Vista will notify the user and require administrator authorization. This type of prompting helps ensure that users do not accidentally make modifications to their desktops. It also helps eliminate the ability for malware to invoke administrator privileges without a user's knowledge.

If a user wishes to run a program that requires administrator permissions, they must give consent through a User Account Control prompt. This helps limit malware's ability to make system-wide changes without the administrator's knowledge. However, Administrator Approval Mode does not provide the same level of security or control as a true standard user account. More information on UAC can be found here. http://technet.microsoft.com/en-us/windowsvista/aa905113.aspx

1.      Installation of Duet on Vista

Installing Duet 1.5 on Vista will require Administrative Privileges. Its not enough to be logged on a administrator. Its also required be run with elevated privileges. The admin has to launch the setup.exe in a command window with admin privileges from the language folder for the language in which he wishes to install. For example to install German duet, on the DVD the Administrator should change folder to

\Microsoft\Duet Client\German and launch the setup.exe

2.      Using Duet Tools on Vista

Some features on the duet setting manager tool will require administration privileges, like changing the parameters like MDS URL, MD refresh check interval, and cache size. These feature are intended for administrators only, hence they require elevation. 

3.      Duet Client Pre-requisites - If Duet Administrator will be installing the pre-requisites himself/herself (The other option is to allow the setup to install )

a.      SQL Express SP2

b.      .NET 2.0

Duet Client was built on .NET 2.0 and hence .NET 2.0 is a requirement for Duet. Even though Windows Vista comes pre-installed with .NET 3.0, Duet installation wizard will fail if NET 2.0 is missing,

4.      Uninstalling Duet 1.5 from Windows Vista

When an Administrator wishes to uninstall Duet from a Windows Vista, he/she should open a command line with elevated privileges and run the setup.exe and select the remove option Or the user can click on setup.exe, setup.exe will ask privileges or administrator can remove from Add/Remove Program.

Ramakrishnan Nagasamy. Duet PM.

My name is Chris Keyser.  I’m the Group Program Manager for Duet.  We’ve kicked off our blog, and it’s just the start of establishing a richer dialog with our customers.  We want to hear from you about what you think about Duet, what you think about Office Business Applications, and what you’d like to see coming in the future.  And if something is preventing you from becoming a Duet customer, we’d like to hear about that too.  You can reach me at ckeyser@microsoft.com.

 

I moved into my current role in Microsoft about six months ago.  I took the opportunity because I believe that Office Business Applications will transform the way that many users interact with line of business systems and think about the value of Office.  I am enthusiastic about partnering with the leader in enterprise line of business application, SAP, to develop the richest set of enterprise class Office Business Applications on the planet.  We want to make you and your company more effective in the way you execute your job today, and open up new ways for you to innovate and collaborate on driving your business moving forward – to not just talk about, but actually enable bridging the way that people interact and collaborate every day more effectively and broadly with valuable data and processes in back end business systems.

 

We’ll be giving you more and more technical content moving forward via this blog.  Delivering a joint product between two big companies presents challenges, but SAP and Microsoft are committed to working together making  our Duet product a success.  Part of that is figuring out how we jointly support our product.  Along those lines, I thought the first tidbit from one our technical specialists will actually be about a tool for validating a SAP backend prerequisites for Duet:

 

The Check Tool is delivered when you install the ECC-SE 500 add-on (for ECC 5.0) or ECC-SE 600 add-on (for ECC 6.0) into your ABAP system with Support Package 03.  Add-on’s are installed using transaction SAINT.  Support Packages are installed using transaction SPAM.

   

To launch the tool, go to transaction SE38 and execute program /OSP/CHECKTOOL.  From the list above, you can see there are many fixes to the tool that have to be implemented using transaction SNOTE.  Fixes are downloaded from the SAP Service Marketplace Notes section using the SAP Download Manager and applied via SNOTE in SAPGUI.

 

 

    Duet has a 3 tier architecture. Duet client can now be installed on a single user or multi user computer systems, with a few limitations. Citrix is a Multi user system running on Windows 2003 OS Platform.

     

    Many enterprises who use both SAP ERP and Microsoft Office software solutions have invested on Citrix as the IT Platform for their Information Workers. Number of such customers are in the order of 10s of thousands and the number of individual users in millions. Duet 1.5 planned to be released next year (2008) will support Citrix Presentation Server.

     

    Duet 1.5 and Citrix support

    Duet 1.0 client was designed only for Windows XP and Windows 2000. Customers have been giving us lots of feedback and it was clear that support for Citrix would enhance the value proposition of Duet enabling enterprises to leverage their investments. Duet 1.5 now supports Citrix Presentation Server. Citrix CPS runs on top of Windows 2003 Server R2 edition.

     

    High level changes to Duet architecture to support Citrix

     

  1. Duet Utility
  2. The duet utility runs Duet services which manage Client-Server Synchronization, Application download, and  User notifications. In Duet 1.0 only one instance of this service can run on the client. Running multiple instances results in unpredictable behavior. However, in Duet 1.5 multiple of these services, one for each user that is logged into the client is run. This ability ensures that all the user specific client-server synchronization, Application download, User notifications happen within the context of the logged user.

     

  3. Database storage changes
  4. Duet uses a local database to store information. This database (SQL Express) gets installed along with the Duet platform. For a single user system this database was sufficient. However with multiple users that roam across the collection of instances served by Citrix Presentation Server, there was a need to externalize the storage and provide isolation of data. Duet 1.5 allows the administrator to setup and use a centralized DB server (SQL Server) for all the users in the system.  

     

    -Ramakrishnan Nagasamy, Program Manager, Duet

Duet has a client – server architecture. Duet clients are of two types. Primary and Secondary. If as a user you have only one machine in which Duet is installed, then you do not have to worry about primary and secondary machines. Only users with multiple machines and Administrators need to understand these concepts.

Background

In many enterprises Information Workers (IW) use more than one computer on their job. IWs work with Duet items on all their computers.  To ensure integrity of the changes from all these computers be reflected in your SAP system, there is a need to sequence the changes.  In Duet, one user machine is identified as the sequencer and it is called the Primary machine. Primary machine identification is made at deployment time. The end user functionality is identical between a Primary machine and secondary machines. The only requirement is that the Primary machine needs to be running for synchronizing the data between Duet client and your SAP system.

 

In normal usage, when Duet is functioning correctly, there is no need for the user to know which machines are Primary and Secondary Duet machines.

     

  • How does the user know a computer is a primary machine?
  • The first computer on which the initial configuration is done for a user for the first time is designated as the primary machine.

    Clicking on Duet utility in the system tray, displays a status dialog. This will indicate if the machine is primary or secondary. Status dialog will display the synchronization details only if the machine is a primary machine.

     

  • The primary machine should always be up and outlook and duet utility should be running all the time.
  • Synchronization with SAP system happens only the primary machine. If the primary machine is not running for a user, changes to Duet items are never propagated to backend SAP system.

     

  • Assigning a new machine to be a primary machine
  • First shutdown current primary machine, then run the Promote Machine tool on the machine which you want to convert it to a Primary Duet machine. Restart the old Primary machine and it will automatically become a Secondary machine.

     

  • When the primary machine loses connection to the corpnet, but its still active and running.
  • Users can still create Duet items on Primary or Secondary machines using the offline functionality of Duet. But these items will not get synchronized with the SAP system. When the Primary machine gets connected to the corpnet and the exchange account, the items will be synchronized with the SAP backend.

     

  • Duet Utility not running on the primary machine.
  • If the Duet utility is not running on the Primary machine, changes to Duet data will not get synchronized to the SAP system. One indication that the Duet utility is not running, is the absence of the Duet Icon on the System Tray Applet region of the task bar. Users can start the Duet utility by launching it from Start menu->Programs->Duet->Duet utility.

     

    -Ramakrishnan Nagasamy, Program Manager, Duet

Duet is all about improving Information Worker (IW) productivity. Productivity gains are realized when structured process and communication styles complement intutive unstructured, adhoc commuication styles. IW's managing their own vacation schedules from within Outlook is a powerful example of such productivity gains, realized when Outlook and SAP modules work with each other seamlessly. As you can see from this screenshot http://blogs.msdn.com/photos/teamduet/picture4540888.aspx  IW's can schedule vacation requests from within Outlook and all SAP business rules will be applied. The window on the right side shows relevant contextual information from the backend SAP system.

- Srikanth Ranganathan, Lead PM, Duet

 

Greetings!!  My name is Srikanth Ranganathan, and I am a Lead Program Manager for Duet. Starting today, I am joining several other members of the Microsoft Duet team in sharing information about Duet. Initially, I will be writing about what's coming in Duet 1.5, planned to be released later this year. The Duet product development team is very excited about the product we are building, and I am looking forward to being able to talk about all the great work the team has been doing publicly. As things unfold, I look forward to your feedback on what you would like to read about. 

With that said, let's finish this initial post with some discussion of a feature that has made customers ask for more. Offline access...

Improving Information Worker productivity is the nucleus, DNA, mantra of Duet. If there is one feature that is so fundamental to IW productivity it's the Offline access to LOB data. IW's are aware of the productivity gains due to Offline access features of Outlook. Duet extends these productivity gains to accessing LOB data as well. Customers who experience Offline access to LOB data in Duet become so excited that they want to see more of it.

While Offline access is very useful, it needs careful design to ensure integrity, confidentiality and security are not compromised. Offline access is achieved via a concept of synchronization between Outlook and the backend LOB system. We have significantly improved synchronization in Duet 1.5.

Duet 1.5 will see improved performance, improved error handling and improved diagnostics. We will expand on this capability in our subsequent releases as well. We will discuss this is in more detail in subsequent articles in this blog.This is an exciting feature for us for it applies to a broad range of scenarios resulting in increased productivity to the IWs.

 

 
Page view tracker