Issue with existing drive formatted to ReFS and mounting in new server
I had a hardware failure which also took out my Server installation drive. I have new hardware and have installed Server 2022 again on new drive. I have connected a drive that I had formatted as ReFS and now it shows as RAW and Event log shows "ReFS failed to mount the volume. Version 3.14 doesn't match expected value 3.7" I have no idea what is going on here. Both installations of Server 2022 used the same media. This is getting very painful. I have connected the drive to a Windows 11 24H2 computer, and it reads fine.ReFS volume appears as RAW after rebuild of server
I had a Windows 2022 server that had a drive formatted as ReFS. The hardware failed and I had to get a new system. The Windows installation also got corrupted when the hard failed. I have the new hardware and I have installed Server 2022 again but the drive is coming up as Raw and ReFS failed to mount the volume. Version 3.14 doesn't match expected value 3.7 is appearing in the ReFS/Operational event logs. I connected the drive to a Windows 11 Pro pc and are able to view the drive. Why has this happened? Is there a way to upgrade the version of RsFS to 3.7? Is there something I have missed when building the new server?
iSCSI Target servers - high availability?
Hello, I have two VMs configured as iSCSI target servers with a 600GB VDHX file on each, and then two VMs configured as file servers in a failover cluster. The iSCSI servers should serve out the data that is shared in the failover cluster file server. I would like to also configure the iSCSI target servers in high availability mode, so that they replicate their data and if one of the iSCSI target server go down, the shares and data is still accessible. How would I go about doing this? So far I've tried setting up storage replica, but since I only have one site, it doesn't allow me to replicate to the second iSCSI disk from the one that currently has data. I also tried iSCSI Target-role in the failover cluster manager, but it puts me back at the same situation where if the storage server with the virtual iSCSI disk goes down, I lose access to all data.
Clarification on NTLM Authentication Events (Event ID 4625 & 4624) in SOC Monitoring
Hello, While monitoring authentication events in the SOC, I frequently encounter multiple failed (Event ID: 4625) and successful (Event ID: 4624) login attempts associated with NTLM authentication. Upon investigating the affected machine, I found no active NTFS shares or resources being accessed. Despite this, NTLM events continue to appear in the logs. I’m trying to understand what might be triggering these events. Could this be related to background processes, service accounts, or another NTLM authentication mechanism? Although this is a low-level incident, I’d like to fully grasp the cause to rule out any potential security concerns. I’d appreciate any insights you can provide! Thank you.
Increase the size of user profile disk in my remote desktop server
Hi all experts. I have a server for remote desktop services purposes, Windows 2016 standard, and domain joined. It is configured using User Profile Disk, and the maximum limit is set to 5GB. I want to increase the maximum limit but I can't do it under the collection's properties because that field is grayed out. My questions: How to increase the maximum limit? Please guide me and let me know how. Can I increase the maximum limit for 1 single user only? If yes, please let me know how. I found some info from the web that this can be done by the Diskpart command, is it true? If I follow the Diskpart method, do all user profiles encounter data lost? I need your guidance and input, I appreciate it. Here are some images:Write to workgroup fileserver from AzureAD joined device.
Hi, We currently have a situation where we are trying to install a program locally, but we want some of the data files (master data for projects, company settings for the most part) to be stored on a fileserver. The installer allows for this change to set UNC path to the share manually, and in our case recommends doing that. The problem we are facing occurs when trying to go on with the installation, the problem reports back that write-protection is enabled. I have the share mapped as a nettwork station, and can create folders/files through explorer. But I think the issue here is that the share mapped using the "Connect with different credential" option, which is required since the share is on a server in a workgroup and the client I'm using is joined to AzureAD. And when i run the installer for the program it is ofcourse ran with my azure user (local administrator), and I guess it tries to write to the UNC path with that user ofcourse. Is there any way i can let the program write to the share without it being to much of a security risk? The same program also has a nettwork license installed on a different workgroup server. I also had to add local users to that server and do some DCOM permission tweaking for that to work. For the license part i can authenticate with the local server user, but thats not an option when trying to install with UNC path for the file/folder structure.feature Installation Error
I am facing this issue in Windows Server 2019 STD. i am also tried to solve this issue to select sources\sxs path from the OS media but still i am getting the same error. Mistakenly i have removed .Net framework from this server and after that i am facing this issue. please help me to solve this issue.
Possible to recover permanently deleted files windows server 2016?
Hi everyone, I am currently managing a Windows Server 2016 setup and accidentally deleted some important files. Unfortunately, these files are not in the Recycle Bin, which makes me think they’ve been permanently deleted.The server holds critical business data, and recovering these files is a top priority. I have not installed or written any new data to the affected drive to avoid overwriting the lost files. Before diving into third-party tools or professional services, I want to explore any built-in methods or reliable tools recommended by the community for recovering permanently deleted files on Windows Server 2016. If you've encountered a similar issue or know of any solutions, please share your expertise! Looking forward to your advice. Thanks in advance!
Windows Server 2019 grey "X" on folders on LTO
Hi everyone We have just upgraded one of our servers from 2016 to 2019 Std. Since then when I try to copy a file to the LTO, which is directly connected to the server, icons appear with a grey "X" in the bottom left corner. I tried moving the file but the same result appears (when I move it back to the Desktop the "X" disappears). There is no cloud sync of any kind related to this server. Just to be clear, everything worked fine on 2016. Hope someone is able to help. Thank you in advance. Best regards
