VDA Agent Software installation failure with either “Program cannot start, missing mfc120u.dll” or post deployment launch failure with message “Problem starting CtxLocationApi64.dll”

The MFC files are NOT available in the “Minimum” variant of the Runtime Installation.

A little background on why this issue happens.

Microsoft allows software vendors to install Microsoft VC++ (x66 / x64) Runtime libraries in either “Minimum” And / OR “Ädditional” variants for same version. Or you can say permits parallel install of both variants.

This can be checked under “Programs and Features or Appwiz.cpl”.

Note: The application vendors can also HIDE these Runtime Libarary installs by passing a argument during install, which can be checked in the Windows Registry at the following location:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall

One has to explore the random generated GUID under this Key and look for the “DisplayName”.

The Parameter “SystemComponent” with REG_DWORD 0x0 allows it to be hidden and not visible in the Programs and Features control panel applet. You can unhide by flipping the DWORD to 0x1.

VC++ Minimum Runtime by Adobe Acrobat 2015 DC

Related:

  • No Related Posts

When User Profile Manager is Enabled a Prompt Appears “How do you want to open this type of link (http) ?”

As a workaround create the initial registry FTA entries with a local policy so that the FTA choice is set when the profile is created.

1. Choose a target machine with the same OS as the VDA.

Set the file type associations as desired in control panel.

Here set HTTP and HTTPS to use Internet Explorer.

IE Default


2. Run the command Dism /Online /Export-DefaultAppAssociations:C:AppAssocAttac.xml (this will create a XML file with the configurations of default programs for different file extensions )

Create a GPO or a local policy.

3. Expand to the policy location , Computer configurationPoliciesAdministrative TemplatesWindows ComponentsFile Explorer.

4. On the right side pane select the policy “Set a default associations configuration file”

User-added image
5. Click on Enabled and then give the path of XML file in the options area.

6. Save settings and exit the policy editor enable loopback processing

7. Apply the policy to the OUs where the servers are placed.

On VDA run gpupdate /force so that changes would take effect immediately.

8. Run RSOP.msc in the servers, and make sure the policies are properly applied.

9. Launch new HDX session . Try to open the link in Outlook. There is no longer any prompt to open a http or https link whether in Outlook or Wordpad.

Related:

  • No Related Posts

7022790: “Secure Shell Server Configuration Tool has stopped working” error after clustered RSIT upgrade

Workaround:

1. In Failover Cluster Manager, expand the cluster RSIT is running under, click on Roles.

2. Select the RSIT role/Generic Service that RSIT is configured under. Take note of the IP address.

3. Right click on the same role and choose properties. Take note of the settings under both General and Failover tabs. Click OK.

4. Left pane, Storage, Disks, check if any disk(s) are currently assigned to the RSIT role.

5. Right click on the role and choose “Stop Role”.

6. Right click on role and select “Remove”.

7. On the passive server, use Control Panel to uninstall RSIT, reboot.

8. On the active server, use Control Panel to uninstall RSIT, reboot.

9. Install RSIT build 8.2.1.1100 on the passive server, reboot.

10. Verify that RSIT service is not running under Windows’ Services.

11. Install RSIT build 8.2.1.1100 on the active server, reboot.

12. Verify that RSIT service is not running under Windows’ Services.

13. In Failover Cluster Manager, expand the cluster RSIT will run under.

14. Right click on Roles and choose “Configure Role”.

15. Under “Select Role”, choose “Generic Services”. Click Next.

16. Choose “Micro Focus Reflection for Secure IT Server” from the list.

17. Enter a name for the Cluster role and the IP address it is using (Step 2).

18. When prompt to “Replicate Registry Settings”, add this HKEY_LOCAL_MACHINE key: SOFTWAREMicro FocusRSecureServer

19. Check the new RSIT role properties, match it to what was noted (step 3).

20. On the active server, ensure that the RSIT console opens.

21. Test the connect.

22. Failover to passive server, test step 20 and 21 on the new active server.

Related:

  • No Related Posts

XenApp 6.5 – Unable to install XenApp Role if TLS1.0 is disabled

1.In Control Panel, click Administrative Tools, and then double-click Local Security Policy.

2.In Local Security Settings, expand Local Policies, and then click Security Options.

3.Under Policy in the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, and then click Enabled.

4. Run gpupdate /force

Retry the installation.

NOTE: If it doesn’t work, please go to C:ProgramDataMicrosoftCryptoRSA and grant “Network Services” Read permission to “MachineKeys” folder. Then restart server to have a try.

Related:

  • No Related Posts

7022908: How to completely remove eDirectory 9 from Windows Server

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

Environment

eDirectory 9

Windows Server 2012 R2

Windows Server 2016

Situation

Scenario 1: eDirectory installation failed and left a partially installed instance behind.

Scenario 2: Currently configured instance of eDirectory needs to be uninstalled.

Resolution

  1. Verify that the configured instance, if any, is stopped:

    1. Open the Services.exe Utility:

      Control Panel | Administrative Tools | Services
    2. Scroll to the bottom and look for a service named “x64 NDS Server…”
    3. If it is running, click on the item in the list and click “Stop the service”.
    4. If it fails or does not stop in a timely manner (3 minutes or less), use Windows Task Manager to end the “NetIQ eDirectory Host Environment” task.

  1. Close any open eDirectory utilites, such as ndscons.exe (NetIQ eDirectory Services) or dsrepair.
  1. If the “slpd” task is running, please end the process using Windows Task Manager.

  1. Uninstall eDirectory and NICI:
  1. Open Programs and Features:

    Control Panel | View by: Small icons | Programs and Features
  2. Select “NetIQ eDirectory 9” from the list and click “Uninstall”.
  3. Once the uninstall is complete, repeat the previous step for “NICI U.S./Worldwide”.

  1. Run the eDirectory scrub utility from TID # 3004658:
  1. Follow the instructions under the “Additional Information” section.
  2. After copying the script to a file named “edirScrub.bat”, open a command prompt AS AN ADMINISTRATOR and enter one of the following commands, depending on the directory structure of your installation:

> .edirScrub.bat C:NovellNDS

OR

> .edirScrub.bat C:NetIQeDirectory

The eDirectory removal is now complete.

Note: Although unnecessary, some administrators may opt to restart the Windows server at this point.

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

Unpacks install script then deletes everything except install script and containing folders

I need a solution

(Windows Server 2003) I am currently installing Symantec Endpoint protection on a server bed.  I have installed the SEPM on the management server, then I installed SEP on the  two domain controllers.  When I try to install SEP on the SEPM server the in seems to unpack files as the progress bar fills in then once it seems to almost be done it starts deleteing the unpacked files except for some temp files and the install script and (besides the progress bar going back down to nothing then disappearing) does nothing else.  No start menu folders or icons are made and there is no program put into the control panel add/remove programs list.  When I reboot the temp files are gone and all that remains is the C:Program filesSymantecSymantec Endpoint Protection12.1.4112.4156.105Scriptsinstallscript.sis file.  How can I remembdy this situation and get the Enpoint protection manager to install properly? This happens on all remaining memeber servers.

0

Related:

  • No Related Posts

7021496: Reflection Workspace and Host Session Fails to Launch When Installed to a Network Drive

To launch Reflection, you must change the .NET Framework configuration on your workstation to grant access by following these steps:

Reflection Desktop 16, Reflection 2014, and Reflection 2011 R2 or R3 require 4.0 .NET Framework.

Reflection 2011 R1 requires 3.51 .NET Framework.

All versions of Reflection use the core functionality provided in the 2.0 .NET Framework.

  1. Obtain the .NET Framework 2.0 Software Development Kit (SDK) from http://www.microsoft.com/en-us/download/details.aspx?id=19988 and install it to your workstation.
  2. On your workstation, go to Control Panel > Administrative Tools.
  3. Select “Microsoft .NET Framework 2.0 Configuration.”
  4. Expand the tree to Runtime Security Policy > Machine > Code Groups > All_Code > LocalIntranet_Zone.
  5. In the right pane, under Tasks, click the link “Add a Child Code Group.”
  6. Enter a name for the group. Click Next.
  7. Select URL from the Condition Type drop-down list, and then click Next.
  8. In the URL field, type the path to the folder where you installed Reflection. Click Next. (For example, file://Z:/Program Files/Attachmate/Reflection2011/*)
  9. Select FullTrust from the “Use existing permission set” drop-down list.
  10. Click Next and Finish.

Workaround

To avoid this problem, install Reflection to a local drive.

Related:

  • No Related Posts

7022886: Windows 10 v1709 Reports “Failed to Get Network Providers” under Advanced Settings of Network Connections

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

Environment

ZENworks Configuration Management

Situation

The “Provider Order” dialogue under Advanced Settings under Network Connections returns “Failed to get network providers”.
There are no other known issues associated with this issue at this time.

Resolution

Note: Only Create the ‘Devicename’ value specified below, if they keys under which it is to be created already exist.
Manually add a REG_SZ value named “DeviceName” under [HKEY_LOCAL_MACHINESystemCurrentControlSetServicesZenCredManagerNetworkProvider] and set the value to “DeviceZenCredManager”

Manually add a REG_SZ value named “DeviceName” under [HKEY_LOCAL_MACHINESystemCurrentControlSetServicesLCredMgrNetworkProvider] and set the value to “DeviceLCredMgr”

If the FDE Spoke is installed, the following may be necessary.

Note: Only Create the ‘Devicename’ value specified below, if they keys under which it is to be created already exist.
Manually add a REG_SZ value named “DeviceName” under [HKEY_LOCAL_MACHINESystemCurrentControlSetServicesPBACredManNetworkProvider] and set the value to “DevicePBACredMan”

Cause

The “DeviceName” value is defined as an Optional Attribute for Credential Providers.
Despite still being documented as optional by Microsoft in Windows 10 1709, when it is not defined it can impact the “Change Provider Order” starting in Windows 10 1709.

Status

Reported to Engineering

Additional Information

The OES Client may also cause the issue and requires a similar update to the registry.
Note: Other Credential Providers may cause the similar issue, so if the changes above do not resolve the issue….check for other 3rd party providers that may need similar entries created.

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