Hello,
im trying to connect two DELL R640 nodes to DELL ME4 Storage Array via iSCSI using MPIO with Round Robin Policy.
connected to iSCSI via DAS SFP+ ports with 2 paths to Array.
Windows Server 2019 Datacenter build 1809 is instaled at two nodes. Problem Exist on both nodes.
While im trying change MPIO Policy in iSCSI Initiator i get an error:
"The parameter is incorrect. The round robin policy attempts to evenly distribute incoming requests to all processing paths"
While im trying to change MPIO Policy via Disk Management, Round Robin Policy doesnt exist
Greetings,
Patrick
Running server 2016.
I have an ISCSI target that this server connects to. After a reboot, the drives do not automatically reconnect. If I disconnect them in ISCSI then reconnect, they appear fine.
When the system comes up the iSCSI init properties Target tab says it is connected. The Volumes and Devices tab has 2 long strings that should be G:\ and H:\. I click Auto Configure and the strings go away. After I disconnect and reconnect, the drives show correctly in the Volumes and Devices tab.
I cannot find anything in the event viewer that would point to what could cause this issue but I could be looking in the wrong place too.
Any suggestions?
Thanks
Charles
Hi!
I'm on Windows Server 2012 R2, and I recently found that my 2TB C:\ was running out of disk space, which was really surprising.
So I used TreeSize to find out what was taking up all the space, but still it only shows that all the files take up only about 303GB of space. Where did the remaining 1.5 TB go to?
I have 4 Windows 2019 virtual servers running in VMWare and on a single domain. (2 in one site and 2 in another geographical site). Everything has been replicating fine. I currently have 1 VMXNET network card configured on each host and everything is replicating fine but I want to optimize this configuration prior to putting it into production. I have several VLAN options at my disposal but I'm not sure what the optimal number of NICs are.
Thanks.
Hi,
We have two file severs and both of them are part of a cluster.
Both server have 10 core cpu with 12GB RAM, Running Server 2012 R2.
We keep getting call from user to say that they cant access any of the shares from this file cluster but when we switch the server from 1 to 2 it works fine until next day we get same issue again.
we have around 400 user who might be connected to these two servers.
Active node always using around 80-90% cpu memory is around 60-70%
Good day
We are in the process of configuring 6 new load balanced Terminal servers in a new datacenter environment.
We have build a NEW domain, therefor a new active directory.
Our users are used to using workfolders across their existing devices and i would like to configure workfolders for them on their terminal sessions on the new environment. I cannot seem to find the workfolders client on their terminal server sessions, but after research, ive found that there is no client for terminal users using server 2019 datacenter.
therefor i have two questions
1.) How can i get workfolders to work on server 2019?
2.1) How can i generate those workfolders folders without having users needing to log into a machine that has the profile.
2.2) Is there some sort of script or process i can run to create about 800 user workfolders?
Regards
Corné
Get-PhysicalDisk shows multiple disk with same friendly name which are not even attached [in this case EC2 instance and EBS attached] volumes.
The disk explorer, diskmgmt.msc , get-disk and get-physicaldisk output shows correct output. I am suspecting these are lingering metadata but is there a way we can remove the stale records.
There is a SCOM alert related that fires up "Windows Storport Miniport Driver has timed out a request" for the same server.
Let me know if this is a know issues and any fix are welcome
Thanks
Roushan
Hello...
Trying to generate File Server Resource Manager storage reports in CSV format in on a Server 2019 Datacenter instance fails with the message "Error generating report job with the task name 'StorageReport-QuotaOnDemand'."
Event Viewer shows it throwing two errors with eventIDs:
602 with source SRMREPORTS
Error generating report job with the task name 'StorageReport-QuotaOnDemand'.
Context:
- Exception encountered = Exception from HRESULT: 0x80131942
8242 with source SMRSVC
Reporting or classification consumer 'StorageReport-QuotaOnDemand' has failed.
If I select Report format as DHTML, HTML, XML, or TXT it works.
It's just the CSV format that's failing.
The same report configuration also worked under Server 2012r2.
Anyone else run into this?
Hey guys,
I'm in a bit of a pickle with something. Because of reasons we are scripting our own powershell module with which we can do all lun-management on our servers instead of using snapdrive for windows (not supported anymore on windows server 2019). (using the data ontap powershell toolkit for this). used protocol is iSCSI
I have run into a problem when this module is used in a clustered environment (for use with Availability groups). When we use the scripted module to create luns on storage level and then initialize them on the server, basically they get seen as shared for some reason. The thing is, in this scenario we don't need them to be shared. It's ok for these servers to have their own dedicated storage.
Because they are put to be shared, we run into the problem that disks which we create after the cluster is made, won't automatically be put online after a rebout because of the san policy.
https://support.microsoft.com/en-us/help/2849097/how-to-set-the-partmgr-attributes-registry-value-using-powershell
So there is a number of things which i can do:
-I can bypass the problem apparantly by just adding all the storage (luns) first and then forming the cluster. (disks which are added before don't have the issue)
-Maybe changing the san policy on the servers in question(in clustered environments they do say you should leave it on sharedoffline
-or maybe tweak the disks somehow maybe
Is there someone who knows how i can check if a disk is shared or not (preferably by using PS)?Maybe how i can tweak it too? What would your recommondations be?
thanks in advance guys!
Hello,
We're seeing a very odd issue. I've just setup a new 2019 Standard file share using a 2019 Standard VM. The issue we're experiencing is very specific. The issue is that all file transfers FROM the server share to a Windows 7 Professional, domain attached PC are excessively slow compared to any other OS.
I've tried simply copying files and seen between 15MB/s and 20MB/s transfers from the server to the Windows 7 client. I've tried copying files directly to the server from the client workstation and have gotten between 90MB/s and 100MB/s. From any other client OS, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012 R2, Windows 10 with varying OS revisions, this problem is non-existent.
I have tried every fix I could find online from updating network card drivers to applying registry changes. None have made a difference. This issue is specific to Windows Server 2019 running as a VM copying files to Windows 7 Professional, both OS's are fully patched. I have even attempted booting both OS's to safe mode with networking, same results. I have uninstalled all Antivirus software, same results, I have checked physical networking hardware, same results.
Just looking to see if anyone has an idea I haven't tried yet because for the moment, stepping up the migration to Windows 10 is the only foreseeable fix.
Hey All,
In an attempt to change the media type of my different VHDs, I'm making this change within the VM.
Set-PhysicalDisk -MediaType HDD -UniqueId 6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxA Set-PhysicalDisk -MediaType SCM -UniqueId 6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxF Set-PhysicalDisk -MediaType SSD -UniqueId 6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx4
But after a restart its all lost and MediaType is switched back to Unspecified.
Any advise to keep this in place.
Thanks
yup
Getting ready to set up replication from one server to another. When running the SRTopology test, it fails with a volume size not being the same error. I can't figure out how to fix it. Everything I've looked at, the drives are identical.
Server 1
Number LogicalSectorSize PhysicalSectorSize Size
------ ----------------- ------------------ ----
1 512 512 54975581388800
Server 2
Number LogicalSectorSize PhysicalSectorSize Size
------ ----------------- ------------------ ----
1 512 512 54975581388800
Allocation units used for formatting are the same..
This is on a server 2019 set of boxes.
Volume Availability Test: Volume J: exists on msfs01
Volume Availability Test: Volume Y: exists on msfs01
Volume Availability Test: Volume J: exists on msfs02
Volume Availability Test: Volume Y: exists on msfs02
Partition Style Test: Partition J: on msfs01 is a GPT-style partition
Partition Style Test: Partition Y: on msfs01 is a GPT-style partition
Partition Style Test: Partition J: on msfs02 is a GPT-style partition
Partition Style Test: Partition Y: on msfs02 is a GPT-style partition
Volume Size Test: Volume J: on msfs01 and J: on msfs02 are not the same size. Storage Replica cannot be configured to replicate unidentical volumes
File System Test: File system on volume Y: on msfs01 is NTFS
File System Test: File system on volume Y: on msfs02 is NTFS
Disk Sector Size Test: Sector size of the volume J: on msfs01 and J: on msfs02 is identical
Log Disk Sector Size Test: Sector size of the volume Y: on msfs01 and Y: on msfs02 is identical
Log Volume Free Disk Space Test: The log volume Y: in msfs01 has enough free space to hold the recommended log volume size of 8GB
Log Volume Free Disk Space Test: The log volume Y: in msfs02 has enough free space to hold the recommended log volume size of 8GB
Remote Server Management Test: Target server msfs02 can be managed remotely using WMI
SMB Connectivity Test: Firewalls are configured to allow SMB protocol traffic to and from msfs02
Network Latency Test: The roundtrip average latency between the source server msfs01 and target server msfs02 is within the recommended latency threshold of 5 milliseconds
Physical Memory Requirement Test: msfs01 meets the physical memory requirement to deploy Storage Replica
Physical Memory Requirement Test: msfs02 meets the physical memory requirement to deploy Storage Replica
I am attempting to set up a folder that is read only for general employees, but in a directory that they can create and delete folders. No matter what special permissions I assign, as long as the Delete subfolders special permission is checked in the parent directory, an employee account can delete this non deleteable folder. I have even tried explicitly denying a user all permissions but read, and they were still able to delete the folder.
Is there a way to get around the Delete subfolders permission? If I don't have it checked then employees can not delete any folders or files they make, but if I do have it checked they are able to delete the folder regardless of what permissions I have on that folder.
Thanks
Good Morning,
Is it possible to customize the e-mail that is sent to the Folder owner when a user requests access to a folder?
We’re trying to reduce the verbiage in the default notification and have it be a simple:
==Email Start==
SUBJECT: User ‘X’ is requesting access to “PATH”
BODY:
“Justification: “USER JUSTIFICATION”
Do you approve? (please specify access level [full control, read only].
==Email End==
Any help or guidance will be very much appreciated.
Thank you.
Hi,
We have DFS file server in our environment configured with File Screen using File Server Resource Manager (FSRM). We have set email notification to send email to us in case user violates the file screen rule which disallow users to save certain file types (e.g .exe, .mp3, .avi, etc) on the root drive (C:\, D:\, E:\, etc). However the problem is we receive email alert from FSRM saying "user NT AUTHORITY\System attempted to save <filename> to D:\ on the <file server name>. This file is in the "Backup Files" file group, which is not permitted on the server."
Our expectation is FSRM should said user <user id/username> attempted to save file on the D:\ drive, not user NT Authority\System. Do you guys have any experience in this? If yes, can share what is the cause of this problem and ways to resolve it. We have played around modifying the email template but still it doesn't work.
According to the Microsoft Support article(974603 How to configure FTP for IIS in a Windows Server failover cluster),I select enable Offline Files in Sync Center and run the following command at an elevated cmd prompt:
REG ADD "HKLM\System\CurrentControlSet\Services\CSC\Parameters" /v ReadOnlyCache /t REG_DWORD /d 1 /f.
Then,I restart the computer.But when I right-click the share that contains the IIS shared configuration, and there is no Always Available Offline option in node 1 computer and node 2 computer.Any ideas as to what would cause this and/or how to fix?
Thanks in advance.
Hi all,
We want to share a folder on a windows server 2019 (server named "ws1"). Shared file: \\ws1\folder
We want to access via producion servers ("ws2" and "ws3"), but not on the staging server ("ws4"). The users that use production and staging are the same users.
How can we deny the access of the "ws4" to the shared folder on "ws1"?
We try with AD security groups, but windows doesn apply computer rights over NFTS.
Thanks for your help.
Gerardo,