Start a Conversation

Unsolved

Closed

PT

42 Posts

1914

March 23rd, 2021 03:00

PowerStore: Top Services Topics

 

This document contains the list of Top Services Topics for PowerStore, identified by DELL EMC Support as the most Trending Topics for the month of May 2023

 

PowerStore: Unable to use SDNAS SMB shares for Windows RDS User Profile Disks

In Windows, User Profile Disks (UPD) for Remote Desktop Services (RDS) can be located on a remote SMB share. However, for SDNAS, and almost all non-Windows NAS providers

 

PowerStore: How to modify the NAS server to change its computer account regularly password

Some security audit tools may report that a PowerStore NAS server does not regularly change its computer account password. By default, the PowerStore NAS server does not change

 

PowerStore - NVMe Expansion drive may appear offline or missing following drive replacement

Replacing a drive in an NVMe enclosure requires waiting 10 minutes before adding the replacement drive.

 

PowerStore: PUHC fails on a PowerStore X for "Could not delete /tmp/puhc in ESX. Error code 255 Output "". Please call Support. (tmp_delete_failed_esx)"

PUHC fails on a PowerStore X while checking for VMs in Local Datastore on ESXi host. Could not delete /tmp/puhc in ESX. Error code 255 Output "".

 

PowerStore: TLS Encryption error encountered when trying to add or modify Remote Syslog Server

The PowerStore Manager user interface (UI) reports a TLS Encryption error when you try to create or modify a Remote Syslog Server using one-way authentication (Server CA Certificate) 

 

PowerStore: Replication target consumes more space than the source

Replication destination for block or NAS may consume more space than the source system.

 

PowerStore: SAS topology change may lead to node reboot

A change in the SAS topology (such as LCC disconnect, cable disconnect, several drives removed and more) may under rare instances lead to a node reboot.

 

PowerStore: Node may reboot due to I/O bursts during TCP replication

Due to a software issue, node may reboot due to I/O bursts during TCP replication.

 

No Responses!
No Events found!

Top