API for MSP Providers

I need a solution

My company is an MSP Provider and we offer Symantec Cloud Endpointprotection to our clients.  We have hundreds of client’s utilizing this product, and we wish to continue using this product and offering to our clients, but our setup time is getting to be beyond our desired scope time frame.  We are looking for a way to utilize powershell that can connect to an API or the Partner Console itself to automate creating new clients under our Partner Portal.  We would then like the ability to be able to create the client admin and connect to the client portal with the client admin and configure the client via powershell with the hopes of finally being able to download the packages directly to our client servers. This type of functionality would greatly increase our productivity and more importantly allow us to ensure our clients are standardized with our setups across the board with no human error involvement.  I am sure other client’s would love to utilize this as well and could become an important selling tool for other MSP offerings.



  • No Related Posts

Endpoint Prevent – Copy to Share – Not Working Properly

I need a solution

Endpoint Prevent – Copy to Share – Not Working Properly

Dear DLP community

I am in a bit of a confusion here while I am currently testing out the “Copy to Share” functionality of Endpoint Prevent.
We are using DLP 14.6MP2 with also the agents running the same version.

Goal is to monitor a particular share on Windows 7 clients.
This share is mounted as a separate drive on a per-user base.

So far, nothing special. Should be possible to setup fairly easy – I thought.
Now, two days and quite some confusion and frustrating monents later, I see this might not be the case.
Of course, I assume that I am missing something.

I have activated the functionality in a test Agent Configuration. This Agent Configuration is assigned to my test workstation.
Also, I have added the file filter to include this particular share. There, I added the FQDN with share name as well as the IP of the server with the share name.
Like \servername.domainsharename* and \ipaddresssharename*

To make it effectively search for content, I created a new policy which contains a combined detection rule, a group rule and a response rule.

Detection rule:
Keyword Match AND Protocol is Copy to Network Share

Group rule:
Sender matches pattern of my test user domain name domainnameusername

Response rule:
Endpoint Prevent User Cancel when Protocol or Endpoint Monitoring is any of Copy to Network Share

The policy is active and assigned to a Policy Group that is actively assigned to my Endpoint Prevent server.

So much for the details.

What really happens now:
When I copy a file containing the defined keyword to the share I am monitoring, it gets detected. The warning pops up.
BUT: This also happens for each other network share, when I copy the test file.

What am I missing? Detailed configuration available if of any use.




  • No Related Posts

Re: Migrate Networker 8.2 on Solaris to RHEL

A pretty tough task – I doubt that you will receive a straight answer.

This is how I would proceed:

– On the target server create a fake hosts table resolving all your current NW client names.

– Copy the NW databases to the new system – different directory!!

Forget the /nsr/index directory right now – it is nice to have but not mandatory.

– Copy the NW software to the target system

– Disconnect the network of the new host completely

– Rename the target server so that it will have the exact name as before

– Install the same NW version in the same directory as on the old system

– Copying the resource files will most likely not work for all of them – just think about the different device names

– Start NW and wait until it has started successfully.

It will take a few minutes

It will take much longer if he cannot resolve the hostnames

– Make sure to get the most important resources to work.

– Finalize the NW configuration

– Make sure you can run local backups and restores

Now you may restore/move the client file index directories


– If your system runs fine, you may now try the upgrade to NW 9.x


– Now you may shutdown the old server and

– Connect the new server to join the network

Pretty much things to do. Good luck.


  • No Related Posts

Migrate Managed SEP12 Endpoints to New SEPM14 Server

I need a solution

We have about 1000 +/- SEP12 managed endpoints (mainly windows while others are mac) pointing to our SEPM12 server and we have a new SEPM14 server setup with a different name and ip address. Rather than manually upgrade the endpoints from SEP12 to SEP14, is there a way to route the SEP12 endpoints to SEPM14 and then have them upgraded to SEP14? Please note we cannot perform SEPM14 Remote Push for security reasons. Thanks!



  • No Related Posts

Re: OneFS 8.X home directory guidance

Not particularly, in general, try to consolidate down your number of shares and Drive letters from the windows servers into as simple of a folder structure as possible on Isilon. I once helped a customer migrate from 16 windows file servers with only 60TB of data, onto an Isilon cluster. There were 9,000 SMB shares covering that 60TB of data. Turns out, as you might have guessed that 8,200 of those are 1 share per user for home directories. With some powershell scripting to update AD profile paths during the cutover event, those 8,200 were cut down to just 1 share with variable expansion.


\cluster-scz.domain.comhome points to /ifs/accesszone/homedirs/%U

Also, never use /ifs/data, /ifs/home, or /ifs/.ifsvar to store any user data. So in general make sure you understand good tenants of Isilon filesystem design/layout.

Make sure you understand the pros/cons of using user quotas versus directory quotas for homedirs. (directory quotas will show the mapped network drive as the size of the hard quota limit). User/Group Quotas will show the mapped network drive size as the size of the cluster, though the provisioning can be done dynamically per user, which is really helpful.

Think about the data itself and the users themselves. I once came across a customer that wanted to protect the data of their VP’s and above (CxO) at a higher level than their normal users. So they created a different folder for those VIPs, and set a different filepool policy on that directory and it’s contents, I think 4x mirroring instead of N+2:1 at the time (erasure coding in the old format).

Think about self-service restore with snapshots / VSS integration. What’s makes sense for application data in other folders may not be right for homedirs.

Setup your email templates for quota notifications, (assuming you get to use quotas).

That’s all that comes to mind off the top of my head. OneFS 8.x + only introduces concepts that may be more helpful in multi-tenant homedir environments, like groupnets. But unless you have to have those, I’d avoid them.

Chris Klosterman

Principal SE, Datadobi



  • No Related Posts

Can’t find compatible Windows 10 Client

I need a solution


I am just getting started with this product, as I’m trying to help out my church with a few tecnical tasks.  We are running version 14 build 2349, (14.0.2349.0100).

We have a Windows 10 Pro workstation that I recently updated and am trying to install an endpoint manager client.  According to the endpoint server, I can create a client install package for Windows 64bit version 14.0.2349.0100, but when I attempt to install on the client, it is said to be incompatible.  

Do I need to download new client versions to the server?  Does the endpoint protection server maybe need to be updated?  Any help you can give to put me on the right track is greatly appreciated.




  • No Related Posts

7022987: Error 4701 “Server services not running”

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


Verastream Host Integrator


  • Connection attempts by a remote client fail with error ID 4701 “Server services not running.”
  • Session server log (viewed in Administrative Console; see also KB 7021303) contains error MessageID 3152 “Allocated session timed out waiting for client connection.”
  • Local connections on the server (such as with SOAP Services tester) work fine.
  • Firewall or device with Network Address Translation (NAT) may be between the server and client, or the server’s machine name may not be resolvable from the client system.


With version VHI 7.5 or higher:
  1. Temporarily stop the session server service. (See also KB 7021352.)
  2. Manually edit the %VHI_ROOT%/etc/sesssrvr.config file in a text editor to set the ApptrieveServer > Server property to the fully qualified host name or IP address as the server is known on the client’s side of the network.
  3. Save the edited file and start the session server service.


The client connector is able to establish the initial connection to the session server to request the session, and the server readies the session and tells the client the address to connect to it, but the client fails to make the secondary connection. That is, the client can’t connect to the address the server told it to use. The session server must be configured to tell clients (connectors, Design Tool, and model deployment utilities) to use a different address.


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.


  • No Related Posts

The Provisioning Server either cannot be found or shows as **down** in the Provisioning Services Console.

To resolve this issue, perform the following tasks:

1. Launch the Provisioning Services Console and verify the Provisioning Server appears as “down.” If so, verify that the Citrix PVS Stream Service is running on the Provisioning Server. For more information, see Starting, stopping, or restarting Provisioning Services

2. From the Provisioning Services Console, verify the Provisioning Server appears when the Servers node is selected. If no Provisioning Server appears, verify the database server’s IP address or FQDN is specified correctly in the Console.

3. Verify the database server is powered on and can be reached from another machine in your environment.

4. Verify that the Provisioning Server’s configuration is complete using the Provisioning Services Configuration Wizard.


  • No Related Posts

Multiple SEPM servers

I need a solution

Hi All,

We are building two new datacenters. At the moment the main DC host single SEPM server. We are looking for a solution in which a separate SEPM servers will be deployed in new DC’s so SEP client will download definitions and configuration from SEPM in the same site not from the main DC. It is preferred to have the administration of all 3 SEPM servers completed from a single location so we will not have to administrate 3 separate SEPM setups

Any recommendatoions / solutions ?!





  • No Related Posts