Error – “Cannot start Microsoft Outlook. Cannot open the Outlook Window”

Disabled Windows Search Indexing for any outlook items.

METHOD 1

1. To resolve this issue, add the following key to the Registry to prevent indexing of any Microsoft Outlook items

Root: HKEY_LOCAL_MACHINE

Data type: REG_DWORD

Key: SoftwareMicrosoftWindowswindows SearchPreferences

Value name: PreventIndexingOutlook

Value data in Hex: 0x00000001

outlook1

Restart the Outlook client and Windows Desktop Search Service.

METHOD 2

While Outlook is still running, open Control Panel, find Index Options and open it. Then click Modify button and uncheck Microsoft Outlook from the list and click OK.

OUTLOOK2

METHOD 3

Enable the below GPO to Prevent Indexing Microsoft Office Outlook.

Computer ConfigurationAdministrative TemplatesWindows ComponentsSearchPrevent Indexing Microsoft Office Outlook.​

outlook3

Related:

  • No Related Posts

Avamar: Unable to open ItemPoint on Exchange 2013 with Outlook 2007 32 bits — Error: The MAPI subsystem could not be initialized.

Article Number: 499291 Article Version: 3 Article Type: Break Fix



Avamar Client for Windows

Opening ItemPoint on a newly configured Avamar client, returns a windows error popup message:

User-added image

This is an Exchange 2013 with Outlook 2007 32 bits installed.

According to Kroll support, this issue is caused by an incompatibility between Exchange 2013 and the current Outlook version installed, in this case, Outlook 32 bits.

In order to resolve this issue:

1) Apply all available service packs to the current installed version of Outlook.

NOTE: ItemPoint 8.1 doesn´t support Outlook 2007.

or

2) Install another version of Outlook, higher than the current one.

In this particular environment, installing Outlook 2010 32 bits was the solution to taken to get ItemPoint working as expected.

Related:

Outlook crashing after its latest September update

I need a solution

We are using Office 365 (Monthly channel, 2016). After the recent September updates to Office, Outlook started crashing for some users when trying to sort emails by From, or other columns. If we uninstall Symantec Endpoint Protection, it stops crashing. On some PCs it even shows that Symantec’s add-in has beed disabled because it caused a crash, although Outlook still crashes in such case.

We are still using 14.0.1 – (14.0 RU1 MP2) – 14.0.3929.1200 and were only planning to start testing 14.2. I think 14.2 still came before September 5, when new updates for Office came out. But maybe it’s a known fixed issue? I have only filed a request with Microsoft so far. They are investigating.

Happens both on Windows 7 and Windows 10.

0

Related:

7023348: Workflows designed to trigger off of incoming exchange messages are not working after upgrade

This document (7023348) is provided subject to the disclaimer at the end of this document.

Environment


Aegis 3.4

Directory & Resource Administrator 9.2

Situation

Upgraded Aegis to 3.4 and DRA to 9.2. Workflows that were designed to trigger from incoming Exchange messages stopped working. Aegis isn’t creating events when receiving new messages.

Resolution

Uninstall Outlook and install the 64 bit version of Outlook.

Cause

Aegis 3.4supports only the 64 bit version of Outlook 2016 and Outlook 2010

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

Configuring KMS Licensing for Windows and Office

This article contains information for administrators about configuring Citrix Provisioning, formerly Provisioning Services (PVS) 5.6 Service Pack 1 (or later) target devices that are using the Microsoft Key Management Server (KMS) in their environment.

Background

User-added image

KMS can be configured on the virtual disk (vDisk) image to apply volume licenses for operating systems and Office including:

  • Windows 7s and Microsoft Server 2008 R2
  • Windows 8s and Microsoft Server 2012
  • Windows 8.1s and Microsoft Server 2012 R2
  • Windows 10s and Microsoft Server 2016
  • Office 2010
  • Office 2013
  • Office 2016

Note: This is only a general guide for KMS with Provisioning Services. This does not imply that the previously mentioned operating systems and Offices are supported in all versions of Provisioning Services. Refer to the Provisioning Services requirements for the operating system and Office supported in the latest version of Provisioning Services.

In PVS, the option for KMS is configured while building vDisks using the Imaging Wizard. Alternatively, it can be configured at any time using the Console or MCLI/PowerShell command line interfaces. Refer to the PVS documentation for more information about managing Microsoft KMS volume licensing. Note: Information in this article applies only to specified Windows OS and Office versions.

KMS Configuration Scenarios

The following section outlines the steps to configure KMS in various scenarios to accommodate specific deployment environments. Read all the scenarios to verify which one best fits your deployment and follow the procedures accordingly.

Notes:

  • Citrix recommends that administrators complete all the steps in the proper order for a successful configuration.
  • The SOAP/Stream Service account must be a member of a local administrator group in PVS Servers.

The KMS configuration can be done in the following ways in accordance with various environments.You can configure KMS for:

  • both Windows and Office
  • only Windows
  • only Office

Office Folder – This will be referred to as %Office% in this document.

  • Office 2010 – Office14
  • Office 2013 – Office15
  • Office 2015 – Offcie16

Program Files folder – This will be referred to as %ProgramFiles% in this document.

  • 32-bit Office in 64-bit operating system, %ProgramFiles% is Program Files (x86).
  • Office and operating system are both 32-bit or 64-bit, %ProgramFiles% is Program Files.

Note – If the selected version of Provisioning Services supports versioning, the vDisk’s private mode and maintenance version can be used interchangeably. If a maintenance version is used, promote the maintenance version to production or test version; set vDisk access mode from Private to Standard.

Use the following scenarios to configure KMS accordingly:

Configuring KMS for the first time to a pre-existing vDisk
Maintaining or upgrading a vDisk image that is currently using KMS
Maintaining or Upgrading a vDisk Image enabled with vDisk Versioning that is currently using KMS
Installing Microsoft Office to an existing KMS configured (for Windows) vDisk
Upgrading Microsoft Office on an existing KMS configured (for Windows) vDisk

Scenario 1: Configuring KMS for the first time for a pre-existing vDisk

User-added image

Assumptions

A vDisk was pre-built using a tool like XenConvert or the Imaging wizard (with Microsoft Licensing Option set to None):

  • For both Windows and Office: A vDisk that has an operating system and Office installed on it is pre-built using XenConvert/Imaging Wizard but KMS has never been configured.
  • For only Windows or only Office: A vDisk that has the operating system installed on it (Optional: Office is included in the image); the image was pre-built using the XenConvert/Imaging wizard but KMS has never been configured.

Procedure

Note: It is important to perform this operation on a system started from the vDisk in Private Image mode so that the rearm count of the master target device hard disk is not reduced. Also, when the system is rearmed, it does not require rearming again.

  1. Connect to the PVS Server; in the Console, right-click the vDisk and select Properties.
  2. Click the Microsoft Volume Licensing tab and set the licensing option to None.
  3. Start the device from the vDisk in Private Image mode.
  4. Rearm the system for both Windows and Office, one after the other. If KMS is configured for only one of them, select your option to rearm accordingly:
  • For Windows: Run cscript.exe slmgr.vbs -rearm
  • For Office 2010, %ProgramFiles%Common Filesmicrosoft sharedOfficeSoftwareProtectionPlatformOSPPREARM.EXE
  • For Office 2013 and 2016: %ProgramFiles%Microsoft Office%Office%OSPPREARM.EXE
    • ​Note: When rearming both Windows and Office be sure to rearm Office first.
  1. A message appears requesting that you reboot the system. Do not reboot – instead, shut down the target device.
  2. Connect to the PVS Server; in the Console, right-click the vDisk and select Properties.
  3. Click the Microsoft Volume Licensing tab and set the licensing option to KMS.
  4. On the Mode tab, set the vDisk Access Mode to Standard Image mode.
  5. Stream the vDisk to one or more target devices.

Note: Validate that the KMS configuration was successful by verifying that the CMID for each device is unique.

  • For Windows: Run cscript.exe slmgr.vbs –dlv
  • For Office: Change the directory to %ProgramFiles%Microsoft Office%Office% and then run cscript ospp.vbs /dcmid

Scenario 2-A: Maintaining or upgrading a vDisk image that is currently using KMS

User-added image

Assumptions

A vDisk is already configured for KMS and is deployed successfully.

  • For both Windows and Office: A vDisk is already configured for KMS, both Windows and Office, and is deployed successfully.
  • For Windows or Office: A vDisk is already configured for KMS “Windows” or “Office” and is deployed successfully.

Procedure

  1. In the PVS Console, right-click the vDisk and select Properties.
  2. On the General tab, set the vDisk Access Mode to Private Image mode.
  3. Start the target device.
  4. Apply the required operating system Application/Service Pack/Update.
  5. Shut down the target device.
  6. Connect to the PVS Server and in the Console, right-click the vDisk and select Properties.
  7. On the General tab, set the vDisk Access Mode to Standard Image mode.
  8. Stream the vDisk to one or more target devices.

Scenario 2-B: Maintaining or Upgrading a vDisk Image enabled with vDisk Versioning that is currently using KMS

User-added image

Assumptions

A vDisk is already configured for KMS and is deployed successfully. The vDisk is enabled to use vDisk versioning, and as a result, it might already have versions associated with it.

  • For both Windows and Office: A vDisk is already configured for KMS, both Windows and Office, and is deployed successfully.
  • For Windows or Office: A vDisk is already configured for KMS, “Windows” or “Office”, and is deployed successfully.

Procedure

  1. In the PVS Console, right-click the vDisk, and select Versions.
  2. Create a new disk version.
  3. Access target device properties and set Type to Maintenance.
  4. Start the Target device.
  5. Access the target device machine and select Maintenance from the Boot menu when prompted.
  6. Apply the required operating system Application/Service Pack/Update.
  7. Shut down the target device.
  8. Access the PVS Server Console, right-click the vDisk, and select Versions. Promote the vDisk from Maintenance to Production or Test.
  9. Access the PVS Server Console. Under target device properties, change the Type to Production or Test.
  10. Stream the vDisk with this version to one or more target devices.

Scenario 3: Installing Microsoft Office to an existing KMS configured for a Windows vDisk

User-added image

Assumption

A vDisk is already KMS configured for Windows and is deployed successfully.

Procedure

  1. In the PVS Console, right-click the vDisk and select Properties.
  2. Click the Microsoft Volume Licensing tab and change the licensing option from KMS to None.
  3. On the General tab, set the vDisk Access Mode to Private Image mode.
  4. PXE boot to the vDisk in Private Image mode to rearm.

    Note: An OS rearm is required along with the Office rearm.
  • For Windows: Run cscript.exe slmgr.vbs -rearm
  • For Office 2010, %ProgramFiles%Common FilesMicrosoft SharedOfficeSoftwareProtectionPlatformOSPPREARM.EXE
  • For Office 2013 and 2016: %ProgramFiles%Microsoft Office%Office%OSPPREARM.EXE
  1. A message is displayed to reboot the system. Do not reboot – instead, shut down the target device.
  2. In the Console, right-click the vDisk and select Properties.
  3. Click the Microsoft Volume Licensing tab and change the license option from None to KMS.
  4. On the General tab, set the vDisk Access Mode to Standard Image mode.
  5. Stream the vDisk to one or more target devices.

    Note: Validate that the KMS configuration was successful by verifying that the CMID for each device is unique.
  • For Windows: Run cscript.exe slmgr.vbs –dlv
  • For Office: Change the directory to %ProgramFiles%Microsoft Office%Office% and then run:
    • cscript ospp.vbs /dcmid
    • cscript ospp.vbs /dstatus (The OS and Office discovery of KMS is independent from each other and /dstatus shows if office has located KMS on network.)
    • cscript ospp.vbs /act (To expedite Activation)
  • ​Open Word and check the activation.
  • NOTE– Re-launch any Office App twice to kick off the activation service
  • Restart the service if you don’t get the CMID status.
  • Shutdown the target device; do not reboot.
  • Connect to the Provisioning Services Server. In the Console, right-click on the vDisk and select Properties.
  • On the General tab, set the vDisk Access Mode to Standard Image mode.
  • Stream the vDisk to one or more target devices

Scenario 4: Upgrading Microsoft Office on an existing KMS configured (for Windows) vDisk.

Assumption

A vDisk is already KMS configured for Windows and Microsoft Office.

Procedure

  1. In the Provisioning Services Console, right-click on the vDisk and select Properties.
  2. On the General tab, set the vDisk Access Mode to Private Image mode.
  3. Start the target device.
  4. Run the new Microsoft Office setup and choose to perform an upgrade.
  5. Reboot the target as required by the installation.
  6. Shut down the target device.
  7. Connect to the Provisioning Services Server. In the Console, right-click on the vDisk and select Properties.
  8. On the General tab, set the vDisk Access Mode to Standard Image mode.
  9. Stream the vDisk to one or more target devices.

Important Information on Rearm

  • Microsoft restricts the number of rearms possible on installed operating systems and Office products.
  • With Windows and Office products utilizing KMS activation, the available rearm count will increment from 0 to 1 on a successful activation against a KMS host server.
  • If you run out of rearms, activating by using a KMS host lets you rearm once. This ensures that once administrators can activate a KMS client, they will be able to issue a rearm. For example, a KMS client with a rearm count of 1 issues a rearm using the remaining single rearm, and reboot. Upon reboot after the KMS client activates, the rearm count will return to a count of 1.
  • In all of the preceding scenarios, a successful KMS configuration for a Provisioning Services vDisk, does not require you to rearm the vDisk except the first time when it is configured.

Related:

How to Unleash the Power of Microsoft Teams

EMC logo


A little over a year ago, Microsoft introduced the world to a new product called Teams. Teams is designed to revitalize and revamp the way we communicate with each other in a more dynamic way. Teams not only allows us to communicate using previous methods of Email and Chat, it gives us a way to organize those communications with groups of people and topic streams, so that what we create together is more concise and focused.

Microsoft has recently added voice and video communications to Team’s list of rich features, along with the ability to share files and create team websites. All of this is only made possible provided we ensure the supporting infrastructure pillars Exchange Online, OneDrive, and SharePoint Online are in place within the Office 365 Tenants. If any of these supporting pillars are missing, the user experience will be degraded, hampering Teams from being the powerful tool it’s meant to be.

Microsoft Teams

The Pillars for Teams Functionality

Let’s briefly explore the three pillars Teams leverages before going to the main discussion of Teams and its abilities. I cannot stress this enough, ALL three pillars – Exchange Online, OneDrive, and SharePoint Online must be setup and configured within the Office 365 Tenant in order for Teams to access them and deliver new levels of communications and collaboration like never before.

  • Exchange Online provides email and contact information allowing users to communicate with both internal and external people. It can also provide a unified messaging component in the form of Voice Mail and Auto Attendants as well as very complex call routing and messaging capabilities. These features are typically grouped with Skype for Business Online to provide VoIP communications replacing aging PBX systems.
  • OneDrive is a fairly new product from Microsoft. It has only started to see usage within the Office 365 environment as security concerns for storing files on the internet have been a major concern. However, Microsoft has made substantial modifications to ensure the security of their customers’ data, making it very attractive for organizations to adopt it. The combination of increasingly mobile users and companies moving to Office 365, has raised interest in OneDrive. Storage of users’ files online is integrated and supported in all of the Microsoft Office Applications, making access to these files more readily available than ever before.
  • Microsoft TeamsSharePoint Online provides the ability to quickly setup websites for collaboration, including file shares and Wiki lookups. It helps provide structure for users to collaborate on topics and projects, as well as allows for internal and external users to access information in a very structured method. Security can be placed on any or all of the various parts to restrict or grant access, providing a platform of collaboration that can be archived and accessed as needed. SharePoint Online is also the engine for collaborating on Word, Excel, and PowerPoint documents, as it allows users to edit the same document simultaneously.

Microsoft has provided these three very powerful tools within the Office 365 ecosystem to enable all forms of communications and collaboration from anywhere, at any time. Up until the introduction of Teams, there wasn’t a single app that could tie these three powerful tools together, enabling information to be shared and tracked as needed within various groups or teams. Teams brings one-to-one and one-to-many communication and collaboration to a whole new level.

The Power of Teams Unleashed

Teams leverages the functionality of the three pillars within Office 365 and adds a single interface in the form of the Teams App. It takes the contacts and email communications from Exchange Online to provide a connection or Groups. It uses the file storage of OneDrive along with the structure and security of SharePoint Online to add in file storage organization and Wiki/Web site access. Teams brings instant messaging with persistent chat for conversation history and presence, as well as voice and video support to take conversations to new heights.

In the coming months, Microsoft plans to add Dial-in Conferencing, Phone System (previously Cloud PBX) with Direct Inward Dialing (DID) and voicemail, completing the planned roll up of the Skype for Business Online features into Teams.

Groups

In Teams, conversations are created and tracked by the groups of people that are talking about a particular subject. In order to create these groups or teams of people, Teams needs Exchange Online to provide the contact list, which is also used to send notifications for joining the conversation. Exchange Online is where the calendar of scheduled meetings will continue to reside. Without Exchange Online all of these features would be missing.

Instant Messaging (IM), Chat and Presence

Instant Messaging (IM), chat conversations, and presence are basic features that are provided by the Teams application, all migrated from Skype for Business Online. Your group conversations in IM and chat will be recorded and stored to allow review of past conversations as well as allowing others in the group to see what’s been discussed. Presence tells you when a user is online and available. All these functions are inherent to Teams.

Adding Tabs or Apps

Tabs in the conversations and Apps (a full list of the currently available Web Apps that can be added in the Teams Conversations can be found here) is provided by the SharePoint Online capability in the background of Teams. With this feature you can add Microsoft Office Documents, websites, and links to other locations that are of interest to group the conversation or you can use tabs to help manage the work that is being done. All of these discussion points show up in the main conversation tab, but they’re also sorted or filtered in the other tabs of the conversation within the Teams tab.

Microsoft Teams Tabs

File Sharing

File sharing is controlled and aided by SharePoint Online and OneDrive. OneDrive allows users to select their stored files and add them to conversations. SharePoint Online provides the structured file storage and security for the files once they have been added to the conversations.

Voice and Video

The ability to start voice and video conversations between team members is a powerful feature now available in Teams inherent to the application. It allows you to engage in voice, video and one to one or group meetings with people in your contact list. Microsoft is planning to add the ability to record these meetings in the next update release due out in the 4th quarter of 2018. These recordings will be stored in the conversation tabs in the cloud, unlike in Skype for Business Online where the recordings are stored on the local hard drive of the recording initiator. This makes for easy access by everyone engaged in the conversation. Translation of Voice to Text for these meetings is also in the planned release.

Inbound and outbound Public Switched Telephone Network (PSTN) calling has been included with the added Phone System service in Office 365 . This allows you to have a fully functioning phone system within Teams, just like what’s currently available with Skype for Business Online, including voicemail. Connection to on-premises PBX systems is targeted to be released by Microsoft some time later, as 3rd party vendors are working to get this capability verified and tested with their hardware. These functions are inherent to Teams.

Scheduling and hosting meetings allows for people to work together on issues or documents without having to physically go to a meeting room or come together at a single location. Work can now be done simultaneously on documents as part of the meetings between some or all of the people participating. You no longer have to share an application screen and have just one person do the editing.

Harness the Power of Teams

As you can see, Teams has the ability to provide users with a whole new way to manage communications and dynamically collaborate, including how we track the way we work and communicate in groups. However as the name implies, Teams requires the three supporting pillars – Exchange Online, OneDrive, and SharePoint Online – to be setup and running together to enable these powerful communications and collaboration features.

Microsoft Teams Features

Remove or fail to enable any one of the three pillars and you might just end up providing a tool that causes more work to use, versus the tangible benefits that can be realized with Teams.

This is what makes our jobs as experts so important, because we must fully educate our customers on the capabilities that are available with Teams, providing the right time and effort is put in place to leverage the powerful features it offers.

Are You Planning to Adopt Teams for Your Workforce?

Dell EMC can help. We’re a gold-certified Microsoft partner and our consulting services team is responsible for all things Office 365. If you have any questions or happen to need assistance with any of these services, contact your Dell EMC representative or comment below and I’d be happy to respond.

The post How to Unleash the Power of Microsoft Teams appeared first on InFocus Blog | Dell EMC Services.


Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

ShareFile Office Online Editing

Limitations and Known Issues ShareFile Requirements Microsoft Requirements File Requirements Browser Requirements
Enable within the account Preview File Edit File Co-editing

User-added image


Limitations and Known Issues

ShareFile User Requirements

This feature is available to both Employee and Client users so long as the following requirements are met:

Previewing Files Editing Files
Download Permission on the folder where the file is stored. A Microsoft Office 365 Commercial license (a Work or School account)
Upload and Download Permissions on the folder where the file is stored
File Versioning (You will not be able to edit a file if File Versioning is disabled on the folder containing the file.)
To Edit Exclusively (No Co-Editing) – In addition to the above requirements, you must check out a file if you wish to prevent other users from joining your editing session.

Supported Office 365 Plans*

  • Office 365 Enterprise K1
  • Office 365 Enterprise E1
  • Office 365 Enterprise E3
  • Office 365 Enterprise E4
  • Office 365 Enterprise E5
  • Office 365 ProPlus
  • Office 365 Business Essentials
  • Office 365 Business Premium
  • Office 365 Business
  • Office 365 Education License

Click here for information on supported features and plans across Office 365 plan types.

*These requirements are determined by Microsoft

File Type Requirements*

Previewing Files Editing Files
Word .doc .docm .docx .dot .dotm .dotx .odt .docm .docx .odt
Excel .ods .xls .xlsb .xlsx .ods .xlsb .xlsm .xlsx
PowerPoint .odp .pot .potm .potx .pps .ppsm .ppsx .ppt .pptm .pptx .odp .ppsx .pptx
PDF .pdf Not supported
*These requirements are determined by Microsoft



Browser Requirements

Click here to view Microsoft Office Online web browser and system requirements.

Enable Office Online Editing – Citrix-Managed Storage (Cloud Zones)

For customers utilizing Citrix-managed storage (customers not utilizing on-prem storage) – This feature must be enabled by an Administrator user on the account. Disclaimer: By enabling this feature, you are confirming that you have reviewed and agreed to the Microsoft Terms of Use and Privacy Policy linked. Editing cannot be enabled without the Preview option.

  • Admin Settings > Advanced Preference > File Settings.

User-added image

Note: The above setting does not apply to Private Zones. For editing files on Private Zones, the setting on the StorageZones Controller will override the above setting.

Enable Office Online Editing – Customer-Managed Storage

For customers utilizing on-prem storage servers – Additional configuration on the StorageZones Controller is required. Click here for instructions.

  • When using an Office Online Server, it must be able to communicate with *.sf-api.com.

Preview a File

To preview a Microsoft Office file, click the file to open the preview in the Content Viewer. The preview will be rendered in the pane on the left.

User-added image

Edit a File

To edit a Microsoft Office article, right-click the file and select Edit Document.

User-added image

You will be prompted to verify your Microsoft Office credentials before accessing your file.

User-added image

Once you have verified your credentials you may edit the file as needed.

User-added image

Changes to the file will automatically be saved. You can view the Save status of your file at the bottom of the editor. Please ensure that it says “Saved to ShareFile” before exiting the editor.

User-added image

Co-Editing

Multiple users can edit a file simultaneously, all from within the ShareFile web application. To co-edit a document or join an active editing session, right-click the file and choose the Edit Document option. After verifying your Microsoft credentials, you may use the web-based editor to modify the file. Other users in the editing session are denoted by colored cursors within the document. You can also view editing users in the upper right corner of the editor menu.

User-added image


How do I know a file is currently being edited?

A file that is currently being edited is denoted by the orange icon shown below. Hovering your cursor over the orange icon will display the status of the file.

User-added image

Related:

7021399: Managing Updates to Shared VBA Macro Code for Multiple Users

Note: The steps in this technical note apply to both IBM and VT terminals, however the example code refers to an IBM terminal. The event names are slightly different for VT terminals.

Reflection VBA macro code is stored in Reflection settings files (.rd3x, .rd5x, .rdox), along with other necessary configuration details for each host session. If you provide a group of users with a settings file that includes custom macro code, then it later becomes necessary to update this macro code, you could simply provide updated settings files to everyone, however, any personal settings that have been saved by individual users would be lost.

To avoid the problem of losing personal settings, and to simplify administration of Reflection VBA macro code among groups of users, Microsoft Visual Basic for Applications Extensibility can be used to enable everyone to receive updates automatically on a regular basis; for example, each time a session is opened. Code can be added to the IbmTerminal.BeforeConnect event in VBA that will update the local VBA project with new code from a central location each time a settings file is opened.

How It Works

  1. Create and test the VBA macro code that will be distributed to end users. Place all code that needs to be centrally managed in a single VBA module. Name the module something other than Module1. The example in this technical note uses SharedMacroCode.
2621_0.gif
  1. When custom code for this module is complete, export it to a separate text file by clicking File > Export in the VBA Editor. Accept the default file name SharedMacroCode.bas.
  1. Copy SharedMacroCode.bas to a central location accessible to all users who will need it, for example, Z:remotelocationSharedMacroCode.bas.
  2. Create a new settings file (.rd3x, .rd5x, .rdox) for distribution to end users that will include the VBA Extensibility code necessary to dynamically import this remotely located macro code. Open the Visual Basic Editor, click Tools > References, and select the Microsoft Visual Basic for Applications Extensibility check box:
  1. In the Project pane of the Visual Basic Editor, under Reflection Objects, double-click ThisIbmTerminal (or ThisTerminal for VT sessions) to open the associated module for the Terminal object.
  2. Select the IbmTerminal object from the drop-down object list above the Editor pane, then select its BeforeConnect event from the drop-down event list. Visual Basic will automatically add the stub of an event-handler subroutine, as shown:
  1. Add code to the event-handler subroutine created in step 6 to import code from SharedMacroCode.bas into the local VBA project. Follow this example:
---------------------------------------------

Private Sub IbmTerminal_BeforeConnect(ByVal sender As Variant)



'handle errors in-line...

On Error Resume Next



'include reference to "Microsoft Visual Basic for Applications Extensibility"

Dim vbproj As VBProject

Dim vbc As VBComponent

Set vbproj = ThisIbmTerminal.VBProject



'Error will occur if component with this name is not in the project

Set vbc = vbproj.VBComponents.Item("SharedMacroCode")

If Err.Number <> 0 Then

Err.Clear

'so add it...

vbproj.VBComponents.Import "Z:remotelocationSharedMacroCode.bas"

If Err.Number <> 0 Then

MsgBox "Could not import new VBA code: Z:remotelocationSharedMacroCode.bas", , _

"IbmTerminal_BeforeConnect event"

End If

Else

'no error - vbc should be valid object

'remove existing version first before adding new version

vbproj.VBComponents.Remove vbc

vbproj.VBComponents.Import "Z:remotelocationSharedMacroCode.bas"

If Err.Number <> 0 Then

MsgBox "Could not update VBA code from Z:remotelocationSharedMacroCode.bas", , _

"IbmTerminal_BeforeConnect"

End If

End If

End Sub

------------------------------------------------

  1. The settings file containing this code can now be distributed to end users, and each time it is opened, this BeforeConnect event will automatically update the local VBA project’s SharedMacroCode module with a new version retrieved from Z:remotelocationSharedMacroCode.bas.

Note the following:

  • All users who need to access dynamically updated VBA code in this manner will need to have the same drive mapped to the same folder, as in the example, Z:remotelocation....
  • Exported modules from VBA (.bas files) are plain text. You can make edits to the file without re-importing it into Visual Basic.
  • Event names are slightly different for VT terminals than the IBM terminal example in this technical note. For VT sessions, the “Terminal_Connected” event is recommended.
  • The example shows how to dynamically import a single standard module into a VBA project, however, it is also possible to import user forms and VBA classes as well. For more information about working with the VBA Extensibility library, search the Microsoft Visual Basic Reference Help index for "VBProject object."

Related:

7022686: Programming Resources for Reflection and Extra!

This document (7022686) is provided subject to the disclaimer at the end of this document.

Environment

Extra! X-treme

Reflection Desktop products

Reflection 2014 products

Reflection 2011 products

Reflection version 14.x products

Reflection FTP Client

Reflection for the Web

Situation

This technical note provides information on programming guides, API and language reference materials, software development kits (SDKs), code samples (macros, scripts, etc.), and other resources useful to developers.

Resolution

Reflection Desktop/2014/2011

  • VBA Guide for creating macros: 16.1 SP1 / 16.1 / 16.0 / 2014 R1
  • .NET API Guide: 16.1 SP1 / 16.1 / 16.0 / 2014 R1
  • COM (OLE Automation) API support: KB 7021508
  • Terminal User Control (TUC) – video
  • SmartUx Controls: KB 7021450
  • Many legacy Reflection 14.x and Extra! programming interfaces are supported:
    • Extra! Basic macro (.ebm) support: KB 7021465 (if running multiple session macros with modal dialog boxes, see also KB 7021513)
    • Reflection version 14.x VBA macros: User Guide (PDF)
    • Modal dialog box issue when running legacy Extra! or Reflection macros: KB 7021513
    • Legacy OLE Automation (COM) interfaces as described below (both Extra! and Reflection 14.x)
    • Reflection Basic (.rbs) and Reflection Command Language (.rcl) scripts: KB 7021623
    • HLLAPI with Extra! or Reflection compatibility
    • Extra! EHLLAPI, WD_API, and WinHLLAPI: KB 7021278

Tips and Best Practices for VBA Macros and .NET

  • Efficient Programming Practices: KB 7021427
  • Shared VBA Macro Code: KB 7021399
  • VBA events to auto-invoke actions when host text is displayed: KB 7021510
  • VBA macro compile error “User-defined type not defined:” KB 7021497

Reflection FTP Client

Extra! X-treme

Legacy Reflection version 14.x and earlier

Sending Reflection Commands from the Host

Reflection for the Web

Additional Information

For Databridge, InfoConnect, and Verastream products, programming information is available in the product documentation.

Legacy KB ID

This article was originally published as Attachmate Technical Note 2183.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: