Target device fails to boot with “vDisk is locked. 0xffff800c”

When a target device boots up with the assigned vdisk, a lock gets created on that vdisk. The locked vDisk icon appears with a small lock on it.

Under certain circumstances the locks are not released properly. In cases where a target device tries and fails to boot with a specific vdisk, the locks do not get released properly. If the same target device boots again, the same lock is used and no problem occurs.


  • No Related Posts

Disable Log without Response Rule

I need a solution


I have a policy name is File A with rule to detect by keyword. I want to monitor and block when endpoint copy file A to USB and HTTP/HTTPs so I enable option Removable Device and HTTPS, HTTP on Agent Configuration. I config Response Rule with Endpoint Prevention: Block when any protocol as Removable Device, HTTPS, HTTP, everything is okay.  But I have another policy name File B to classify another file and I want to monitor when it is copied to network file server –> I enable option Copy to Network Share on Agent Configuration. And DLP Agent still sent the log of File A when I copy it to File Server. How can I disable it because I only need log of File B when It is copied to File Server ?

Thank in advance.



large file being blocked by SPE

I need a solution

Hi, I am running SPE 8.0 on Windows 2016 server. We have some large zip files that are blocked by SPE. When copying the files from the NAS to the local server, it always denid access. The zip files are not encrypted and the Maximum extract size of file settings under the container handling policy has exceeed the actual file size. There is file size limit set for scanning. The old part is even if I configured the container handling to log only and it still blocked access to the file (unless I disabled the scanning on the NAS). Here is the errror.

ICAP protocol issue: unexpected ICAP status code 500 returned by facility spescanner:1344

Fri May  3 10:11:28 2019               MAJOR Event ID:10.34   Error occurred while scanning for viruses.



Endpoint blocking .exe files

I need a solution

I am having an issue with Endpoint Manager blocking access to .exe files.  People can’t print or run any executables.  I can’t even open the management console becasue it is blocking javaw.exe from running or accessing any files.  How can I disable this so I can get into the manager and fix this issue?



  • No Related Posts

Understanding SKM mode

I need a solution

Sorry but I am new to PGP technology,

I have created and tested the group key function for file share which uses SKM mode (server key mode). As these keys are stored on the SEM server, i just wanted to know if the user of the allowed AD group is given access to a file share folder, how this SKM works?

will the private key gets tranfered to the allowed user system and unlock the folder for him? what exactly happens in the background?



  • No Related Posts

ECS: How to mount NFS share on Windows client

Article Number: 503490 Article Version: 3 Article Type: How To

Elastic Cloud Storage,ECS Appliance

Issue: How to mount NFS share on Windows client


1. Make sure you have install the NFS service. You can verify it by checking below steps:

Open Widnows regedit, Start–>Run–>Regedit,


If you can see the ClientForNFS, then it means that you have install the NFS service.

If you did not install it, Contal panel–> Turn Widnows feature on or off, Check the check-box for Service for NFS. Then Windows will install it.

2. On the ECS side, configure the NFS share. Please refer to Administration guide, search for NFS part

3. In windows regedit, need New DWORD (32-bit) AnonymousUid and AnonymousGid to be 0 (or other UID/GID you use to map in the ECS) under below path:


4. Mount the NFS share on your windows CMD line:

mount -o “nolock,sec=sys” 10.x.x.x:/<Namespace name you used>/<Bucket name you used> <Windows path>:

eg: C:Userszhangw10>mount -o “nolock,sec=sys” 10.x.x.x:/walkerns/walkernfs y:

10.x.x.x = Public IP of ECS node.

5. Please be noted that each time when you Windows restarts, you need to re-mount the NFS share


  • No Related Posts

EXE files locked on network share

I need a solution

Hi everyone

I have this weird problem and was wondering if anyone had any ideas where to go next.

In short, when I access network share EXE files get locked. If I try deleting any EXE (from Windows Explorer for example) it dissappears for a couple of seconds (or until Refresh) and then reappears. Cannot move it, cannot rename it. Only when I logoff (and, I guess, network connections get cut off) files are deleted.

If I try deleting these files locally (on the computer hosting network share) I get “File access denied” error. Unlocker/IObit Unlocker both report file(s) not in use, but cannot delete them, only after unlocking with Open File List utility (OFL.exe) file(s) can be deleted locally. Sometimes even OFL cannot unlock them, for example if I try deleting/refreshing few times.

Went through network share permissions/ACLs first, although nothing was changed to trigger this. Tried couple of other things, but only after CleanWipe-ing this particular computer (my admin workstation) things went back to normal. SEP client reinstallation reintroduced the issue. I tried to vary policies, our standard, SEP default, all off, tried unmanaged, tried disabling everything possible and its always the same. After that I went with second CleanWipe with thorough registry clean. Reinstalled the client, nothing is changed.

As far as I tested, none of the other SEP clients/LAN computers are affected. This one has fully updated Windows 7 Pro, 14.2 MP1 client, nothing (related to this) in Windows logs, nothing in SEP logs. I think this started happening with 14.2, but cannot say for sure.

Anyone has any idea? Seen something like this before?





  • No Related Posts

OneFS: Best practices for NFS client settings[1]

Article Number: 457328 Article Version: 8 Article Type: Break Fix

Isilon,Isilon OneFS

This article describes the best practices and recommendations for client-side settings and mount options when using the NFS protocol to connect to an Isilon cluster and applies to all currently supported versions of OneFS.

Supported Protocol Versions

At this time Isilon OneFS supports NFS versions 3 and 4. NFS version 2 has not been supported since the move to the 7.2.X code family.


NFS version 3 is the most widely used version of the NFS protocol today, and is generally considered to have the widest client and filer adoption. Here are key components of this version:

  • Stateless – A client does not technically need to establish a new session if it has the correct information to ask for files, etc. This allows for simple failover between OneFS nodes via dynamic IP pools.
  • User and Group info is presented numerically – Client and Server communicate user information by numeric identifiers, allowing the same user to possible appear as different names between client and server.
  • File Locking is out of band – Version 3 of NFS uses a helper protocol called NLM to perform locks. This requires the client to respond to RPC messages from the server to confirm locks have been granted, etc.
  • Can run over TCP or UDP – This version of the protocol can run over UDP instead of TCP, leaving handling of loss and retransmission to the software instead of the operating system. We always recommend using TCP.


NFS version 4 is the newest major revision of the NFS protocol, and is increasing in adoption. At this time NFSv4 is generally less performant than v3 against the same workflow due to the greater amount of identity mapping and session tracking work required to reply. Here are some of the key differences between v3 and v4

  • Stateful – NFSv4 uses sessions in order to handle communication, as such both client and server need to track session state to continue communicating.
    • Prior to OneFS 8.X this meant that NFSv4 clients required static IP pools on the Isilon or could encounter issues.
  • User and Group info is presented as strings – Both the client and server need to resolve the names of the numeric information stored. The server needs to lookup names to present, while the client needs to remap those to numbers on its end.
  • File Locking is in band – Version 4 no longer users a separate protocol for file locking, instead making it a type of call that is usually compounded with OPENs, CREATES, or WRITES.
  • Compound Calls – Version 4 can bundle a series of calls in a single packet, allowing the server to process all of them and reply at the end. This is used to reduce the number of calls involved in common operations.
  • Only supports TCP – Version 4 of NFS has left loss and retransmission up to the underlying operating system.

NFSv4.1 and Beyond

At this time OneFS does not support NFS version 4.1. If you need specific features of version 4.1, speak with your account team to see if that is something that we can provide via OneFS’s unique featureset as an NFS filer.

OneFS Version specific concerns

For customers that have been using Isilon OneFS since versions 7.1 or before, changes made in the 7.2.0 version of OneFS, and remaining in place until OneFS 8.1.1, might impact how clients using encoding that differs from the cluster’s are able to view and interact with directory listings. For more details review ETA 483840.

This is not an issue if you began using OneFS on version 7.2 or beyond.

Mount options

While we do not have hard requirements for mount options, we do make some recommendations on how clients connection. We have not provided specific mount strings, as the syntax used to define these options varies depending on the operating system in use. You should refer to your distribution maintainers documentation for specific mount syntax.

Defining Retries and Timeouts

While the Isilon generally replies to client communication very quickly, during instances when a node has lost power or network connectivity, it might take a few seconds for its IP addresses to move to a functional node, as such it is important to have correctly defined timeout and retry values. Isilon generally recommends a timeout of 60 seconds to account for a worst case failover scenario, set to retry two times before reporting a failure.

Soft vs Hard Mounts

Hard mounts cause the client to retry its operations indefinitely on timeout or error. This ensures that the client does not disconnect the mount in circumstances where the Isilon cluster moves IP addresses from one node to another. A soft mount will instead error out and expire the mount requiring a remount to restore access after the IP address moves.

Allowing interrupt

By default, most clients do no allow you to interrupt an input/output or I/O wait, meaning you cannot use ctrl+c, etc, to end the waiting process if the cluster is hanging, including the interrupt mount option allows those signals to pass normally instead.

Local versus Remote Locking

When mounting an NFS export, you can specify whether a like will perform its locks locally, or using the lock co-ordinator on the cluster. Most clients default to remote locking, and this is generally the best option when multiple clients will be accessing the same directory, however there can be performance benefits to performing local locking when a client does not need to share access to the directory it is working with. In addition, some databases and softwares will request you use local locking, as they have their own coordinator.