The Windows 10 VDA exhibits slow logon at Welcom screen

DelayedDesktopSwitchTimeout registry helped to fix the issue.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

  1. Open the registry editor
  2. Locate the following registry subkey:
  3. HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
  4. Double-click the DelayedDesktopSwitchTimeout registry entry.
  5. In the Value data box, type 5, and then click OK.
  6. On the File menu, click Exit.

Related:

  • No Related Posts

VIP self service portal MacOS Mojave

I need a solution

Hi, i‘am trying to Add the symantec-auth-client-plugin-1_16-installer.dmg to my Macbook Air (Mojave 10.14.2). After running the Installer the Double-click to install.app opens. After clicking the Installationsprogramm started. At the end i get the Information that the Installation is finished. Nevertheless at the end the Programm isn‘t in the MAC Finder. Can somebody help?

0

Related:

  • No Related Posts

7023276: Sentinel core report is missing

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

Environment

Sentinel Reporting

Situation

One of my Sentinel core reports is missing from the view.

Resolution

Use the following steps to restore a report previously installed from the “sentinel core solution pack”. For this example let’s say the user accidentally deleted the “Sentinel core event count trend” report. To restore this report use the following steps.
1. go to sentinel control centerconfigurationsolution packs
2. double click solution packs to open solution pack manager.
3. Highlight “sentinel core solution pack” and click the icon at the top right “open with solution manager”.
Note: it might take a few minutes to open
4. Now drill down to Sentinel core solution packevent management controlsevent trends
5. highlight “event trends” and click the uninstall button.
6. After it is uninstalled hightlight “event trends” again and click the install button.
7. the report should reappear.
Note: This same procedure can be used to restore other items from this solution pack, however the location within the solution pack might be different so steps 4 thru 6 would need to be changed.

Cause

A user accidentally deleted one of their Sentinel core reports. These are the reports added when the “sentinel core solution pack” is installed.

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

7021617: Enabling the Script Menu in Reflection

Enabling the Script Menu in Reflection for HP, UNIX and OpenVMS, and ReGIS Graphics

To enable the Script menu in Reflection for HP, UNIX and OpenVMS, and ReGIS Graphics, follow these steps:

  1. Start Reflection.
  2. On the Setup menu, click Menu to open the Menu Setup dialog box.
  3. In the Defined Menu box, click Macro.

Note: The Macro menu will only appear in the Defined Menu box if Visual Basic for Applications is installed as a component of Reflection.

  1. In the Available Options box, double-click Additional Items.
  2. Double-click Items from Version 6.x, and then click Script.
  3. Click the Add After button to add the Script menu to the Defined Menu list.

Note: You can choose to add the Script menu before or after any existing menu.

  1. Click OK. The Script menu should now appear on Reflection’s main menu.
  2. Click Save on the File menu to save the changes to your settings file. If necessary, create a new settings file.

Enabling the Script Menu in Reflection for IBM

To enable the Script Menu in Reflection for, follow these steps:

  1. Start Reflection.
  2. On the Setup menu, click Menu to open the Menu Setup dialog box.
  3. In the Defined Menu box, click Macro.

Note: The Macro menu will only appear in the Defined Menu box if Visual Basic for Applications is installed as a component of Reflection.

  1. In the Available Options box, double-click Additional Items.
  2. Click Script.
  3. Click the Add After button to add the Script menu to the Defined Menu list.

Note: You can choose to add the Script menu before or after any existing menu.

  1. Click OK. The Script menu should now appear after the Macro menu on Reflection’s main menu.
  2. Click Save on the File menu to save the changes to your settings file. If necessary, create a new settings file.

Related:

XA 7.x: Getting “HTTPError500.0-InternalServerError” after reinstalling .NET on server.

1. Open Internet Information Services

2. Click on the computer name on the left list.

3. Double-click on ISAPI Filters

4. Change the \ to so the path reads:User-added image

C:WindowsMicrosoft.NETFrameworkv4.0.30319aspnet_filter.dll

5. Close IIS Manager and restart IIS from the command prompt (Start -> Run -> iisreset)

Related:

7001461: How to trace LDAP operations to the screen or log file


c. Then go back to the information tab (on the LDAP Server object) and click the Refresh button (you may have to scroll down to see it)

2. On the server start dstrace to see the information.

On NetWare, use these commands. (make sure you delete the dstrace.log file first)

dstrace <enter>, dstrace -all <enter>, dstrace + time +tags +ldap <enter>, dstrace screen on file on <enter>

Then run your LDAP process you want to trace.

unload dstrace <enter> will turn off tracing and close the file.

You can then get the trace file at sys:systemdstrace.log

On NT/2000, use these commands. Load the DSTrace utility by double-clicking DSTrace from the NDS Services window on the Control Panel. Choose Edit | Options. Click “Clear All”, then click the “LDAP” checkbox. Information is logged to a file using the drop-down FILE menu.


On Linux, use these commands (make sure you delete the ndstrace.log file first) (it helps to oversize your terminal window to see all the ndstrace options prior to starting ndstrace)

ndstrace <enter>, set ndstrace=nodebug <enter>, ndstrace +time +tags +ldap<enter>, ndstrace file on screen on

Then run your LDAP process you want to trace.

exit <enter> will turn off tracing and close the file.

You can then get the trace file at (OES1) /var/nds/ndstrace.log (OES2) /var/opt/novell/eDirectory/log/ndstrace.log

3. iMonitor provides a method of capturing the LDAP activity that works with every supported platform. If sending a trace into technical support, DO NOT USE iMonitor to capture the trace unless instructed explicitly to do so.

1. Login to iMonitor and click on the Trace Configuration button.

2. Click on ‘Clear All’ and the LDAP radio button under the DS Trace Options section.

3. Click on ‘Trace On’ to start logging the LDAP activity.

4. A new Trace button will be available at the top of the screen. Click on it.

5. The most recent trace information will be shown. Click on Trace History to access archived trace files.

Additional Note: To include information about the eDirectory indexes being used by LDAP communications in the trace, you can add the +recm flag for linux, or check the Storage Manager flag for Windows / iMonitor. It will display what indexes, if any, are being used during LDAP queries in the trace log.

Related:

7021512: Creating a Hotspot that Opens a Web Page

Using Hotspots

A hotspots file enables you to interact with your terminal session by using the mouse instead of the keyboard. Each new terminal session includes a pointer to a default, built-in hotspots file. You can choose a different hotspots file for each session, and you can create custom hotspots files with the settings you prefer.

Typically, clicking a hotspot transmits a terminal key or command to the host, but you can also configure hotspots to open a web page, launch a macro, or perform a variety of other actions.

Creating a Hotspot to Open a Web Page

You can create a hotspot that opens a particular URL with an exact match or a variable match. An exact match configuration assigns one specific URL to the designated hotspot text. A variable match configuration enables a generic hotspot to open more than one URL, depending on the text that follows the hotspot text. (Examples follow.)

Enable Hotspots

Before setting an exact or variable matching configuration, first enable the hotspot feature and decide how you want to activate the hotspot.

  1. In Reflection, open a terminal session and log on.
  2. On the Appearance tab, click Hotspots (in the ribbon).
  3. On the Set Up Hotspot Display Settings screen:
    1. Click the check box to Enable all defined hotspots, and select a hotspot style (Button, Outline rectangle, or Not visible).
    2. Select how you want the hotspot to be activated. For example, clear the Double-click check box to open the hotspot with a single left-click.
    3. Near the bottom of the left navigation bar, click Manage Hotspots.
  4. On the Manage Hotspots screen, note the Currently selected file. Click Create a new hotspots file from an existing hotspots file.
  5. On the Create a New Hotspots File screen:
    1. Click the Custom option.
    2. Select a file. You can choose one of the defaults.
    3. Check the box to Use the new file in the current session document. (This setting makes the new hotspots file available in the current terminal session.)
    4. Click OK to open the Modify Hotspots screen.

Continue with the steps to Configure an Exact-Match Hotspot or to Configure a Variable-Match Hotspot.

Configure an Exact-Match Hotspot

An exact match configuration assigns one specific URL to the designated hotspot text. Using this feature, you can configure a hotspot to open your company’s intranet Help Desk web page or another helpful web site.

Follow the steps below to create a hotspot that maps the word Main to the Micro Focus Support web site.

  1. On the Modify Hotspots screen, in the Hotspot text field, enter main.
  2. In the Select Action drop-down menu, select Open URL.
  3. In the URL field, enter http://support.microfocus.com
  4. Select how you want the web page to open, such as in a default browser. Click OK.
  5. In the Hotspot Mapper list, select the Hotspot text, main. Click Modify.
  6. On the Hotspot Options screen:
    1. Verify that the hotspot text is entered correctly. Keep the default check boxes selected. Click OK.
    2. Click OK again to exit the Modify Hotspots screen.
  7. When prompted, enter a File name and save the hotspot file.
    1. On the Manage Hotspots screen, note the Currently selected file.
If it is not the file you just saved, click Select another hotspots file. On the Select a Hotspots File screen, click Custom, and then select the file you saved.
    1. Click OK; click OK again to exit the Manage Hotspots screen.
  1. Save the session document to preserve the hotspots file configuration.
  2. In the Reflection workspace, test the hotspot you just created.
    1. Find or type the word Main.
    2. Depending on how you configured the hotspot, click or double-click the highlighted text, Main.
    3. The web site, support.microfocus.com, should open in a new web page.

Note: In IBM terminal 3270 and 5250 sessions, hotspots are matched only in protected fields that the user cannot edit. To test the hotspot, you could send a message that includes the hotspot text (main) in the message. The hotspot text is highlighted in the displayed message. Click the text to open the web page for Micro Focus Support.

Configure a Variable-Match Hotspot

A variable-match hotspot recognizes common text in a string or phrase as an exact match. The remaining (variable) text in the string or phrase defines the exact action that will be performed, such as opening a specific URL.

For example, to create one hotspot that is capable of opening different web pages, configure a hotspot that recognizes http:// as the opening syntax of a URL. The remaining (variable) text of the URL defines which web page will open. After you type in a full URL, and click the http:// hotspot, the specific web page for that URL opens. Type a different URL, click the hotspot, and a different web page opens.

Follow this example to configure a variable-match hotspot:

  1. On the Modify Hotspots screen, in the Hotspot text field, enter http://
  2. In the Select Action drop-down menu, select Open URL.
  3. Select the check box to Use matched hotspot text for the URL. (Note: the URL field becomes unavailable.)
  4. Select how you want the web page to open, such as in a default browser. Click OK.
  5. In the Hotspot Mapper list, select the Hotspot text, http://. Click Modify.
  6. In the Hotspot Options screen, select the check box to Match until a delimiter.
  7. Verify that the Space delimiter is checked. Click OK to exit the Hotspot Options screen and click OK again to exit the Modify Hotspots screen.
  8. When prompted, enter a File name and save the file.
    1. On the Manage Hotspots screen, note the Currently selected file.
If the file is not the one you just saved, click Select another hotspots file. Click Custom, select the file you saved, and click OK.
    1. Click OK to exit the Manage Hotspots screen.
  1. Save the session document to preserve the hotspots file configuration.
  2. Test the hotspot.

In a VT terminal session document, type http:// and look for the highlighted box. Type a full URL, such as http://support.microfocus.com, and press the spacebar or Enter. (In this example, the hotspot will not activate until a space is detected.) Click the hotspot to open the web page.

In IBM 3270 and 5250 terminal session documents, hotspots are matched only in protected fields that the user cannot edit.

3270: As you type in a 3270 session document, the hotspot text will become active. After you type a full URL (followed by a space), click the hotspot to open the web page.

5250: In a 5250 session document, test the hotspot by sending a message that includes a URL. Follow these steps as you progress through the screens.

    1. From the Main Menu, enter 6 for Communications.
    2. Enter 2 for Messages.
    3. Enter 1 to Send a message.
    4. Enter message text such as, “See http://support.microfocus.com for more information.” Note: You must enter a space immediately after the URL; if a period or other character is present, the web page will not open correctly.
Enter a user name or profile to receive the message. Press Enter.
    1. On the Messages screen, enter 3 to Display messages.
    2. On the Display Messages screen, check that the user name or user profile is selected (underlined). Press Enter.
    3. The hotspot should be highlighted on the Work with Message screen. Click the hotspot to open the web page.

Troubleshooting

If the hotspot is not behaving as expected, follow these steps:

  1. Open the Manage Hotspots screen. (Another path: From the Quick Access toolbar, click the Document Settings button. Under Terminal Appearance, click Manage Hotspots.)
  2. Verify that the Currently Selected File is the one in which you saved the hotspot file. If not, click Select another hotspots file, and select the correct one.
  3. Click Modify the currently selected hotspots file.
  4. Select the Hotspot text, for example Main, in the Hotspot Mapper list. Click Modify and check the options you want to save. Click OK until you return to the Reflection workspace.
  5. Save the session document.
  6. Test the hotspot again to see if the web page opens.

Related:

How to Export and Install an SSL Certificate for StoreFront to Use HTTPS

Overview diagram of exporting and installing SSL certificate for StoreFront to use HTTPS

User-added image
Export your certificate

If you already have your SSL certificate in a .pfx file, skip to Import your certificate.

1. On the server containing the certificate you wish to export, click the Windows icon (User-added image) and type mmc.

Note:
The screenshots used in this article were taken on a Windows Server 2012 R2. Images may differ.

2. Click mmc. This opens the Microsoft Management Console.

User-added image
3. Click File | Add/Remove Snap-in.

User-added image
4. Select Certificates, then click Add >.

User-added image
5. Select Computer account, and click Next >.

User-added image
6. Click Finish.

User-added image
7. The Certificates snap-in has been loaded. Click OK.

User-added image
8. Expand Certificates then Personal. Click on Certificates.

User-added image
9. Right-click on the certificate to export, and select All Tasks, then Export…

User-added image
10. Click Next.

User-added image
11. Select Yes, export the private key, then click Next.

User-added image
12. Click Next.

User-added image
13. Select the Password: checkbox, then enter and confirm a password to protect the private key. Click Next.

User-added image
14. Select a location for the certificate. Click Next.

User-added image
15. Click Finish.

User-added image
16. Click OK. This creates a .pfx (Personal Information Exchange) file containing the password-protected private key of the certificate.

User-added image

Import your certificate

1. Copy the .pfx to the StoreFront server, or map a drive to the file’s location.

2. Start the Microsoft Management Console (MMC), and add the Certificates snap-in (see steps 1 to 7 above).

3. Expand Certificates, right-click Personal, select All Tasks, and then click Import…

User-added image
4. Click Next.

User-added image
5. Click Browse… to locate the certificate.

User-added image
6. Change the dropdown to look for *.pfx files.

User-added image
7. Highlight the file and click Open.

User-added image
8. Click Next.

User-added image
9. Enter the password used when the certificate was exported. If you want to be able to export the certificate from this server for use on another server, make sure to select Mark this key as exportable. Click Next.

User-added image
10. Click Next.

User-added image
11. Click Finish.

User-added image
12. Click OK.

User-added image
13. Click Certificates.

User-added image
14. Right-click on the certificate and select Properties (or double-click the certificate).

User-added image
15. Confirm that you have the private key for the certificate. That line must be present for the certificate to function correctly.

User-added image

Bind the SSL certificate to IIS

1. Start InetMgr.

2. Expand IIS Manager, right click on Default Web Site, and click Edit Bindings…

User-added image

3. Click Add…

User-added image
Note: Do not remove the http binding.

4. Select the Type: dropdown.

User-added image

5. Select https, then select the certificate you just imported. Click OK.

User-added image

6. Click Close.

User-added image

Configure StoreFront to use the SSL Certificate

1. To modify StoreFront to use the SSL certificate, we must change the Base URL. Start StoreFront.

2. StoreFront is not currently using the SSL certificate. Click Server Group in the left pane.

User-added image

3. Click Change Base URL.

User-added image

4. Change http: to https: and click OK.

User-added image
User-added image

5. StoreFront is now using the SSL certificate. Repeat on any remaining StoreFront servers in the server group.

Related:

  • No Related Posts

7021487: Reflection Windows-Based Emulation Products and JAWS Compatibility

Reflection Support for JAWS

Attachmate has performed basic interoperability testing of JAWS with Reflection terminal emulation products for Windows. Testing was performed using the current version of JAWS at time of Reflection product releases.

Configuring Reflection 2014 or 2011

When using JAWS with Reflection 2014, Reflection for UNIX and OpenVMS 2014 or 2011, and Reflection for IBM 2014 or 2011, for best results, we recommend that you configure the Reflection Workspace user interface to use the Classic mode menu and toolbar (instead of the default Office 2010-style Ribbon).

  1. Click File (upper left).
2241_3.gif
  1. In the drop-down menu, click Reflection Workspace Settings.
2241_4.gif
  1. In Reflection 2014 or 2011, click Configure Workspace Settings.
  2. In the Configure Workspace Settings page, scroll down to User Interface (or, on the left, under Jump To, click User Interface).
  3. Under UI Preferences, select Classic for the User interface mode.
  4. Click OK.
  5. Close the Reflection Workspace.
  6. Restart the Reflection Workspace. The Workspace is now using the Classic mode menu.

Note the following:

  • If you change this setting after configuring sessions, the appearance of those sessions may be unpredictable.
  • When using the Classic user interface, only one document can be open in a workspace. Classic mode does not support features such as custom ribbon configurations and multiple tabbed documents.
  • The online help procedures are written for the Ribbon user interface.
  • In some instances, when the Reflection terminal display is refreshed, JAWS is not prompted to read the text. To manually prompt JAWS to read the screen, press Press Insert + Down Arrow (Say All).
  • If you need to later switch back to Ribbon UI, do one of the following. The available menu options vary depending on the type of connection, the template, and the product.

Click Options > Global Preferences > Configure Workspace Setings

or

Click Setup > View Settings > Reflection Workspace Settings (on bottom left) > Configure Workspace Settings

or

Click Tools > Document Settings > Configure Workspace Settings.

  • If JAWS is configured to read your keystrokes aloud, your password will be vocalized when you enter it, since JAWS vocalizes all keystrokes. To bypass this issue, you may wish to record a login macro. Follow the steps in the next section.

Record a Login Macro and Set it to Run Automatically on Connection

Use a login macro to prevent your password from being vocalized by JAWS. The login macro will prompt you to enter your password into a Windows login pop-up, which records each keystroke as an asterisk (*).

Follow the steps below to record a login macro, with the Reflection UI in Classic mode, and then configure the login macro to run automatically on connection. Different steps are provided for 3270/5250 and VT connections.

3270 or 5250 Connections

Record the login macro:

  1. In Reflection, connect to your host, and then click Session > Disconnect.
  2. Click Macro > Record Macro.
  3. Click OK to accept the default wait times.
  4. Click Session > Connect.
  5. Enter your login name and password, and then click Macro > Record Macro (to stop recording).

Note: Unless you change the value of Save Passwords settings (Setup > View Settings), Reflection will not include your password in the recorded macro.

  1. Enter a Macro name, and then click OK.
  2. Click Session > Disconnect.

Configure the macro to run automatically on connection.

  1. Click Options > Settings.
  2. Under Host Connection, click Configure Advanced Connection Settings.
  3. Scroll down to the Connection Action section (or click Connection Action on the Jump To menu).
  4. Select the check box to “Run a macro or other action after the initial connection.”
  5. Select “Select macro,” and then click OK.
  6. Select the check box to “Run when reconnecting,” and then click OK.

VT Connections

Record the login macro:

  1. In Reflection, connect to your host, and then click Connection > Disconnect.
  2. Click Macro > Record Macro.
  3. Click Connection > Connect To Best Network.
  4. Enter your login name and password, and then click Macro > Record Macro (to stop recording).

Note: Unless you change the value of Save Passwords settings (Setup > View Settings), Reflection will not include your password in the recorded macro.

  1. Enter a Macro name, and then click OK.
  2. Click Connection > Disconnect.

Configure the macro to run automatically on connection.

  1. Click Connection > Session Setup.
  2. Under Host Connection, click Configure Connection Settings.
  3. Scroll down to the Connection Action section (or click Connection Action on the Jump To menu).
  4. Select the check box to “Run a macro or other action after the initial connection.”
  5. Click Select Action.
  6. Select “Select macro,” select the macro you recorded, and then click OK.
  7. Select the check box to “Run when reconnecting,” and then click OK.

Test the Macro

For 3270/5250, click Session > Connect.

For VT, click Connection > Connect to Best Network.

The macro automatically enters the user ID. After a pause, you will be prompted to enter your password in a Windows Password Entry dialog box. Each password character is read aloud by JAWS as “star.”

Save the Session and Macro to a Desktop Icon

  1. Click File > Save, and save your Reflection session.
  2. Click File > Save As, right-click your saved file, and drag the file to the desktop. When you release the mouse, select Create Shortcuts Here.

When you double-click the desktop icon, your Reflection session will start and the macro will run, prompting you to login.

Related:

Published Application Fails to Launch Outside of Desktop Session

Workarounds

Complete the following steps as a workaround for the issue:

  1. Create the user profile by first launching a full desktop session.

  1. Start the runonce.exe file together with the /AlternateShellStartup switch.

    User-added image

    1. In the server Group Policy Management Console, navigate to Local Computer Policy > User Configuration > Windows Settings.

    2. Click Scripts (Logon/Logoff), and then double-click Logon.

    3. Click Add.

    4. In the Script name box, type runonce.exe.

    5. In the Script parameters box, type /AlternateShellStartup.

    6. Click OK two times.

Another approach is to narrow down which exact run key needs to be executed to solve the profiling issue.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Isolate the process by removing the values from the run key. Delete the profile and launch a published desktop session, then remove another value, delete the profile and launch a desktop session. Repeat the process until the application does not start even in published desktop mode. Once the required process is isolated, put back everything into the run key and modify the login script to execute only the one needed process instead of the runonce command.

User-added image

Related: