When and How to Whitelist / Blacklist Apps for iOS Devices using #ZENworks

Some time back, a discussion with one of my colleagues got me thinking on the importance of blacklisting or whitelisting of applications on devices and its current relevance. To provide some background, some years back, the MDM capabilities offered by Operating Systems were not that …

+read more

The post When and How to Whitelist / Blacklist Apps for iOS Devices using #ZENworks appeared first on Cool Solutions. gvikram

Related:

  • No Related Posts

Wanna read information from #ZENworks using REST?

jblackett

Greetings from Malaysia! This week I’ve been doing some more exploring with ZENworks Reporting in my hotel time and I found that there’s a great solution available for those of you who want to get some data programmatically for integration with some other application in your environment. ZENworks Reporting provides a REST interface that makes …

+read more

The post Wanna read information from #ZENworks using REST? appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

NS12.0 add cluster node, node sync stuck in “IN PROGRESS” state

Synchronization stuck due to new added node cannot establish TCP Connection to CCO.

in ns.log, you may see the following logs for this problem.

Enable debug log on Netscaler through System>Auditing>Syslog settings, You can get more detailed logs about the synchronization process.

Refer log pattern:

cat /var/log/ns.log |grep cluster

Jul 11 15:13:00 <local0.info> ns [1510]: cld_fullsync_req_handler(): Received config sync START message from Clusterd (sync_id=2)

Jul 11 15:13:00 <local0.info> ns [22327]: cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]

Jul 11 15:13:00 <local0.info> ns [22327]: cld_fullsync_req_handler(): Sync FAILURE sent to clusterd for sync_id=2

Jul 11 15:13:00 <local0.info> 172.16.1.73 07/11/2018:07:13:00 GMT 2-PPE-2 : default CLUSTERD Message 1394 1531293180485406 : “REC: status FAILURE from client CFSYNCD for ID 2 “

cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]

After check, customer found it was caused by backplane switch jumbo frame setting.

Related:

  • No Related Posts

Using #ZENworks Reporting to Generate Ad Hoc Reports when the Domain Doesn’t Expose What you Want

jblackett

At the moment I’m on the road in Asia training partners and I had a few minutes to share something I learned last week that I think will be interesting to everyone. I was in Taiwan doing partner training on ZENworks Reporting and a partner asked me how he could get the same Patch Compliance …

+read more

The post Using #ZENworks Reporting to Generate Ad Hoc Reports when the Domain Doesn’t Expose What you Want appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

ZENworks 2017 Update 3 Increases Unified Endpoint Management Capabilities

Gil Cattelain

In a mobile-focused business world, an IT team’s ability to efficiently manage all the endpoints in an enterprise is critical to operational success across the business. Whether you’re managing a corporate-owned, BYOD, or hybrid environment, a complete, integrated suite of endpoint management tools streamlines the process for IT and ensures devices are secure, compliant, and provide …

+read more

The post ZENworks 2017 Update 3 Increases Unified Endpoint Management Capabilities appeared first on Cool Solutions. Gil Cattelain

Related:

  • No Related Posts

Response Rule: unable to send “Destination” information to the syslog or mail notification

I need a solution

We have created a response rule to send the incident notification to the Syslog server and over an e-mail as well. This working well, however, it does not send the Destination (to which file was uploaded or transferred). 

Below are the variables used in the response rule: (however, I tried with each and every “Insert Variable” but no luck)

Incident ID: $INCIDENT_ID$
File Name: $FILE_NAME$
File Full Path: $PATH$
Subject: $SUBJECT$
Machine Name: $ENDPOINT_MACHINE$
Sender: $SENDER$
Recipients: $RECIPIENTS$
Severity: $SEVERITY$
Match Count: $MATCH_COUNT$
Protocol: $PROTOCOL$
Policy Name: $POLICY$
Policy Rules: $RULES$
Destination: $TARGET$

Is it achievable and how?

0

Related:

  • No Related Posts

Restrict LDAP users on ZENworks Reporting

Ron van Herk

I like using ZENworks Reporting to generate custom reports for ZENworks Configuration Management or for ZENworks Service Desk but there has been one thing I found very annoying, the ability to manage LDAP users and the Roles within ZENworks Reporter. The ZENworks Reporter appliance configuration makes it very easy to add an LDAP source to …

+read more

The post Restrict LDAP users on ZENworks Reporting appeared first on Cool Solutions. Ron van Herk

Related:

  • No Related Posts

Enrolling existing devices to the Apple Device Enrollment Program for simplified provisioning with #ZENworks

jblackett

Introduction As I am sure you are aware, using the Apple Device Enrollment Program (DEP) to enroll devices simplifies the process of provisioning devices with ZENworks and allows you to perform over-the-air supervision of the device. Supervising an iOS device opens a variety of additional settings and profiles that can be applied to restrict the …

+read more

The post Enrolling existing devices to the Apple Device Enrollment Program for simplified provisioning with #ZENworks appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

Q3 2018 – #ZENworks Community Webinars Announcement

jblackett

I am pleased to announce the next quarter’s ZENworks Community Webinars. This quarter we are trying to broaden our webinars to look not only at ZENworks but also at solutions from our partners and other groups within Micro Focus we think might be interesting to you based on the problems they solve. We’ll be interested …

+read more

The post Q3 2018 – #ZENworks Community Webinars Announcement appeared first on Cool Solutions. jblackett

Related:

  • No Related Posts

“No Syslog box in the dropdown options”.configuring VNX block only array to send logs to syslog server

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



Unisphere for VNX

Customer could not get past step 2c in the attached document.

It was determined that they did not have a host agent installed on the appliance or workstation that they wanted to use as the syslog server. (It was also confirmed that they could not install a Host agent on the server due to security considerations.)

Install the appropriate host agent on the syslog server.

You can find the host agent with the following search:

Here’s a link with additional instructions:

https://support.emc.com/search/

Type in Unisphere Host Agent in the (Scope by Product) search box, leave ‘All support’ default in the ‘Scope by resource’ box and most importantly, click on the ‘Advanced Options’ tab over on the lower right. (otherwise a completely different and larger list will populate in findings as it doesn’t do a ‘full text’ search.)

search page screenshot

This search can be modified to find either Windows specific or Unix and other OS versions of the host agents as well. Here are some of the common ones:

ie;

Unisphere Host Agent for Windows 32 and 64-bit

Unisphere Host Agent (Linux x64)

Unisphere Host Agent for Linux x86

Unisphere Host Agent (Solaris x64)

Unisphere Host Agent (Solaris SPARC)

Unisphere Host Agent for AIX

Unisphere Host Agent for HP-UX

*Note: Purposely I left out the version number in all of these, and tested search functionality and they all pull up the latest and older versions of each type.

On a block only array, a host agent must be installed on the syslog server.


>> Here’s a questionnaire that you can provide to customer to determine their set up status:

1. Do you have a Host agent installed on the system (workstation) that you are going to be using as the Centralized Monitor station?

2. What is the Host agent type and version?

3. What is the OS and version on the Portal system or workstation (or VNX array) that you have designated?

4. Have you added the Portal IP address(es) to the Host Agent config file?

5. Could you verify that the other systems or workstations that you expect to see in the Available systems dropdown are not already functioning as portals? Can you also verify that they are running Unisphere for Windows?

6. *If* you are using VNX as the portal, do you have more than 20 hosts attached to the array? Note: the attached document states -> IMPORTANT: Do not use as a portal a VNX system that has more than 20 attached hosts.

.

Related:

  • No Related Posts