Ensuring Endpoint Governance for Today’s Digital Workspaces

Gil Cattelain

Modern enterprise productivity is driven by an ability to work effectively from anywhere and on any device.  No longer are employees tied to desktops and laptops.  Rather, thanks to the emergence of digital workspaces, users can have access to their corporate resources from anywhere and on any mobile device. The burden to deliver these digital …

+read more

The post Ensuring Endpoint Governance for Today’s Digital Workspaces appeared first on Cool Solutions. Gil Cattelain

Related:

Check out what’s new in the latest versions of Service Desk and #ZENworks Mobile Workspace

jblackett

Join us for the ZENworks community webinar on November 14th @ 9:00 Mountain Time where we’ll hear from Sudipta Roy and Vikram Goyal on these two latest updates to the Endpoint Management portfolio. Come check out the new end-user interface for ZENworks Service Desk and see how these products can help enhance you use cases. …

+read more

The post Check out what’s new in the latest versions of Service Desk and #ZENworks Mobile Workspace appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

7023364: Reflection Workspace stays open after a legacy macro “Session.Quit”

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

Environment

Reflection Desktop 16.0 or later

Situation

In Reflection macro programming from version 14.1 and earlier, the statement “Session.Quit” or “Session.Exit” would completely shut down and close the Reflection session. When this legacy macro from Reflection 14.1 is now used with Reflection Desktop, these statements do close individual sessions, but the Reflection Workspace in which sessions are now embedded remains open. Using a Reflection 14.1 macro, how can the Reflection Workspace be closed when the session closes?

Resolution

In Reflection Workspace settings, check the box for “Exit workspace when last document closed”. As long as only one session is open, the workspace window will close automatically following a Session.Quit.

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:

7023225: VBScript utility that will close all Reflection Desktop sessions

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

Environment


Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.1 and later

Situation

It is easy to start Reflection using the command-line (or .bat file) to run Attachmate.Emulation.Frame.exe and supplying the name of a session document. But how to stop all sessions started like that might not be so apparent. This VBScript provides a quick automated method of closing all Reflection Workspace windows. It will close all separate Classic-UI Reflection windows, and all Reflection Workspace Ribbon-UI windows that may have multiple sessions running.

Resolution

  1. Create and save a new text file named CloseAll.vbs.
  2. Open CloseAll.vbs in Notepad, and copy the VBScript code below to it.
  3. Save, and close Notepad.
  4. To run, just double-click CloseAll.vbs, or you can run it from a .bat file.
””””””””””””””””””””””””’

‘ CloseAll.vbs



‘ VBScript to close all sessions in all Reflection

‘ Workspace windows. This works as long as the default

‘ “AutomationServerName” has not been changed from the

‘ default value of “Reflection Workspace”.



‘ Example code provided without warranty or support.

‘ Please review and understand it before running.

”””””””””””””””””””””””””

const CloseAlwaysSave = 3

dim reflection

on error resume next

do while true

set reflection = GetObject(“Reflection Workspace”)

if err = 0 then

reflection.Close CloseAlwaysSave

Wscript.Sleep 1000 ‘wait 1 second to give R a chance to close

else

err.clear

exit do

end if

loop

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:

7022985: Demonstration of how the application.settings file gets copied from ProgramData to AppData location

1. Open Windows Explorer.

2. Navigate to the C:Users<yourusername>AppDataRoamingMicro FocusReflectionDesktopv16.1 folder.

3. Make a copy of the application.settings file and save it as “application.settings.old”.

4. Load the Reflection Workspace.

5. Modify the Trusted Locations under Reflection Workspace Settings / Specify Trusted Locations.

Add two different new lines:

“C:users%usernameDocuments” and set the Subfolders check box.

“C:users%usernameDownloads” and set the Subfolders check box.

6. Exit the Reflection Workspace.

7. Verify the application.settings file in the C:Users<yourusername>AppDataRoamingMicro FocusReflectionDesktopv16.1 folder has the current time and date.

Notice that the application.settings.old file has an older time/date.

8. Copy the application.settings file to C:ProgramDataMicro FocusReflectionDesktopv16.1 folder.

9. Navigate to the C:Users<yourusername>AppDataRoamingMicro FocusReflectionDesktopv16.1 folder.

10. Delete the application.settings file that is located here.

11. Rename the application.settings.old file to application.settings.

Basically putting back the old file that does NOT contain the “C:users%usernameDownloads” folder.

12. Load the Reflection Workspace.

13. View the Trusted Locations under Reflection Workspace Settings / Specify Trusted Locations.

14. The list should contain:

“C:users<yourusername>Documents”

“C:users<yourusername>Downloads”

Related:

Secure Hub Enrollment to XenMobile server fails after setting the Citrix Pin

Reference Logs:

” 2017-07-05T12:35:03.482+0530 “,<MAM>,INFO (4),-[SFHelper catchStoreFrontError:error:],”StoreFront detected bad credentials“,-,com.apple.root.background-qos,e127,Secure Hub,/jenkins/workspace/iOS_Secure Hub/AppStore/Me@Work/Utilities/SFHelper.m,1219

” 2017-07-05T12:35:03.482+0530 “,<CAMAUTH>,INFO (4),+[CAMAuthManager logOff:],”logOff called with completionBlock: 0x16e6eace0”,-,com.apple.root.background-qos,e127,Secure Hub,/jenkins/workspace/iOS_SDK_AuthManager_Main/AuthManager/AuthManager/CAMAuthManager.m,150

Related:

  • No Related Posts

“Access to your company network is not currently available” Error message while accessing Secure Hub XenMobile Store

Attempts to access the Store in Secure Hub causes an error “Access to your company network is not currently available”. Please find the snapshot of an error message.

User-added image

Logs

2017-08-04T16:21:53.886+0200 “,X1AuthController,INFO (4),-[AuthController getCertificateForURL:callback:],“Providing the certificate to Auth Manager.”,-,com.apple.root.default-qos,45a7,Secure Hub,/jenkins/workspace/iOS_Secure Hub/AppStore/Me@Work/Me@Work/X1Auth/AuthController.m,1337

” 2017-08-04T16:21:53.886+0200 “,<CAMAUTH>,INFO (4),__87-[CAMAuthController getClientCertCredentialsForURL:isAuthenticatingToGateway:callback:]_block_invoke,”returned with credential(0x170019f40), ID(fc03791dabcd4ebd28653561c94a4b3ca5a9adf4), error((null)), callback(0x16df86cc8)”,-,com.apple.root.default-qos,45a7,Secure Hub,/jenkins/workspace/iOS_SDK_AuthManager_Main/AuthManager/AuthManager/CAMAuthController.m,97

” 2017-08-04T16:21:53.886+0200 “,<CAMAUTH>,INFO (4),__RespondToClientCertChallenge_block_invoke,“Request #31 providing client cert (0x170019f40) for certificate auth challenge”,-,com.apple.root.default-qos,45a7,Secure Hub,/jenkins/workspace/iOS_SDK_AuthManager_Main/AuthManager/AuthManager/CAMAsyncHTTPImpl.m,275

” 2017-08-04T16:21:53.937+0200 “,<MDM>,DEBUG1 (6),-[MdmStatusData authenticationRequiredAfter:],”authenticationRequiredAfter: Authentication still valid (704 background time vs. 0 allowed)”,Active,com.apple.main-thread,403,Secure Hub,/jenkins/workspace/iOS_Secure Hub/AppStore/MDM/Common/Source/AppSupport/MdmStatusData.m,2008

” 2017-08-04T16:22:17.965+0200 “,WHGenericVault,INFO (4),__32-[WHGenericVault isUserEnrolled]_block_invoke,”User is MDM enrolled: 1”,-,com.citrix.GenericVaultQueue,c

Related:

  • No Related Posts

7021826: Changing the Reflection X Advantage Data Folder Location

To use default settings:

Start X Manager. Reflection X Advantage will create the new directory if it doesn’t already exist and create all required files.

To use your existing settings:

Locate the default data folder. Copy the cache, conf, db, logs, and migration subfolders (if present) and all of their contents to the new data folder. Then start X Manager.

Note: Other subfolders in the default data folder may be present. These are used by other Reflection applications, including the Reflection Workspace, the Reflection FTP Client, and additional Reflection utilities. Changing the rxmgr.alp file does not affect the data location used by these applications.

Related:

7021466: Capturing Logs in Reflection and InfoConnect Desktop

Enabling and Viewing Logs

To enable and view logging, follow these steps:

  1. Open the Reflection or InfoConnect Workspace and go to the Workspace Settings > Configure Workspace Attributes.
  2. Under Logging, check the box that says “Enable event logging” as shown below:
View Full Size

Figure 1: Enable Event Logging – Reflection Workspace
Figure 1: Enable Event Logging – Reflection Workspace
  1. Close the entire Workspace.

The next steps depend on which product you are using.

Reflection Desktop or InfoConnect Desktop Products

Beginning in version 16.0, the log is output as a text file.

  1. Re-open the Workspace and a host session. Perform the action you want to log.
  2. The log file called “workspace.log” will be automatically created and stored in the C:Users<username>DocumentsMicro FocusReflectionLogs folder by default. A text editor can be used to examine these files for detailed events.

Reflection 2014 or 2011 Products

In Reflection 2014 or 2011, information is output to the Windows event log.

  1. In the Reflection installation folder (typically C:Program Files (x86)AttachmateReflection), open the Attachmate.Emulation.Frame.exe.config file in a text editor (running as Administrator if on Windows 7 or later) and change the EventViewerLog value from 1 to 4.
...

<system.diagnostics>

<switches>

<!--

Trace Levels

0 Off

1 Error

2 Warning

3 Info

4 Verbose

-->

<add name="EventViewerLog" value="4" />

</switches>

</system.diagnostics>

...
  1. Re-open the Reflection Workspace and a host session. Perform the action you want to log.
  2. In the Windows Start menu Search box, enter eventviewer to open the Windows Event Viewer.
  3. Under Applications and Services Logs, select Reflection Workspace to view the captured log entries.

View Full Size

Figure 2: Event Viewer – Reflection Workspace

Figure 2: Event Viewer – Reflection Workspace

Related:

  • No Related Posts

Provisioning Services target device fails to boot in read/write mode on Hyper-v

This issue will be resolved in a future version of RES ONE Workspace. The below workarounds should help resolve the issue.

Note: If you wish to go for solution 1 you will need to contact RES Workspace support to download the driver.

Workaround:

Choose one of the following workaround to solve this issue:

Workaround 1:

Replace the TDI based RES ONE Netguard driver with the WFP based RES ONE Workspace Netguard driver

– First extract the driver from the MSI package of RES-ONE-Workspace-2016-SR1.msi (use 7zip or peazip to extract the MSI and afterwards the disk1.cab and copy the file netguard_amd64.sys (64-Bit Version), netguard.sys (32-Bit Version) or the RES Support engineer will provide you with a suitable version of the file.

– Replace the file on the designated system in folder C:windowsSystem32Drivers (32-bit system) and C:WindowsSysWOW64drivers (64-bit system)

– Reboot the system


Workaround 2:

Disable the RES Netguard driver in the registry via the following setting and restart the machine:

Key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesRES NetGuard

Value: START

Type: REG_DWORD

Data: 3

NOTE:

This only applies to environments where the RES ONE Workspace Network security is NOT in use.

Related: