I have DFSR replicating folder sbetween 2 servers, at some point the replication was not working so i uninstalled DFSR on the sending member and deleted the DFSRPrivate folder.

Then installed DFSR again, recreated a replication group and added the 2 servers members.

Now if I run a health report  I get the following errors:

The DFS Replication service encountered an unsupported reparse point in replicated folder CA_FILES with local path D:\CA_FILES. This reparse point (DfsrPrivate) will not be replicated because the replication of this type of reparse point is not supported by the DFS Replication service. Event ID: 4406

The receiving member had already a copy of the folder sat some point and I am not sure how in sync it is now?

Should I clean everything again and start from scratch? 

I have recently upgraded a clients servers to Windows Server 2012 & since doing so have lost the ability to scan to folder.

Both servers are domain controllers and previously on a 2008 domain controller I would have had to make the following change to allow scan to folder:
 Administrative Tools
 Server Manager
 Features
 Group Policy Manager
 Forest: ...
 Default Domain Policy
Computer configuration
 Policies
 Windows Settings
 Security Settings
 Local Policies
 Security Options
 Microsoft Network Server: Digitally Sign Communications (Always)
 - Define This Policy
 - Disabled

However I have applied this to the Windows 2012 server but am still unable to scan, possibly due to added layers of security in server 2012. The error on the scanner is Authentication with the destination has failed check settings.
I have also tried the following at the server:
Policies -> Security Policies
Change Network Security: LAN Manager authentication level to: Send LM & NTLM - Use NTLMv2 session security if negotiated.
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients and uncheck the require 128 bit.
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers and uncheck the require 128 bit
I have created a user account on the server for the ricoh and set this in the settiings of the Ricoh and verified everything is correct.

Are there any other things I have missed?

so on the LAN we use \\domain.local\namespace for my docs and a shared folder. My docs are made available off line, shared docs are not.

servers are 2012r2 and 2016 and clients are windows 7 to windows 10.

Problem:

occasionally we gets complaints from users who can't use DFSN path to the shared folder, they have to use the UNC path i.e.,\\servername\share etc. We see this on the LAN and over VPN and haven't been able to figure it out.

Any ideas?

I am currently looking at:

- multiple file servers in the field responsible for user/departmental data

- these site file server shares have been added to DFS namespace as folder targets

- we would like to add a second replication partner/target so that there is redundancy if a file server goes down

we have stood up a few VMs to act as the second server replication partners... our storage team has provisioned us a bunch of space on the NAS (15+TB)

I am having issues working with the NAS and adding it as a replication partner... for a replication group I have

\\remotefileserver\data$

\\localNAS.domain.loc\data

is this even possible to use the NAS as a replication partner?  I have tried adding it as a network drive to the VMs that will act as replication partners, but that still does not allow me to share and add it to replication... 

the DFS management snap in bombs out when trying to setup replication and using the NAS address as a folder target

Hi,

I have a few questions about DFSR performance and rebooting a DFSR server.  

Is there a way to improve performance and speed for two Windows Server 2016 (Core) and one Windows Server 2012 R2 (GUI) DFSR servers?  It is full mesh.  Looking at the bandwidth, it's not utilizing very much (in the Kbps to low Mbps).  I came upon a performance blog for Windows Server 2008 for DFSR.  Does that still pertain to Windows Server 2016?  

Here's the link: https://blogs.technet.microsoft.com/askds/2010/03/31/tuning-replication-performance-in-dfsr-especially-on-win2008-r2/

What is the best way to reboot a DFSR and not causing the DFSR database to go into Auto Recovery?

Thank you.

I would like to query all the FSRM File Management Tasks with Powershell to come up with a report to see them all in one place.

I see the cmdlet named Get-FsrmFileManagementJob which got me started.

The problem I'm having is that the certain properties return with generic placeholder? values like this. 

Action            : MSFT_FSRMFMJAction

Condition         : {MSFT_FSRMFMJCondition, MSFT_FSRMFMJCondition}

Schedule          : MSFT_FSRMScheduledTask

How can I extract these pieces of information with Powershell to give me a full picture of my File Management Jobs?

Hi,

Home folder was working fine but when I changed my DNS ip to 8.8.8.8 to get the internet home folder disappeared and I changed to 172.18.10.39 (DNS Server) the internet is gone and I cant able to view the home foler.  Please help me

server IP - 172.18.10.39

DNS (Server) - 172.18.10.39

Client Ip- 172.18.10.39

DNS - ( I want to connect to internet and my server, when I make server DNS its not connecting to internet, please help) 

Hi,

Noticed that there seems to be a lack of tools that fully support data recovery from Storage Spaces (and S2D). There seems to be only one tool out there that may work. Most seem to support a pool that exists (healthy or degraded) for recovery. I'm looking at scenarios where a pool was deleted (no new pool as a best case scenario) and the slabs / metadata are intact (mostly or partially). These tools seem to allow creation of a Virtual RAID so that you can at least try and see the file system / files.

Limitation is that they don't know how to create a virtual pool and try and re-create volumes and file system based on a slab scan (with the exception of one tool).

I am interested to learn more about storage spaces and know how to develop software, curious to know if anyone knows of good sources (including Microsoft) of information on the data structures of the pools and volumes and how that structure fits on physical disk?

Have performed a lot of searching and there is very little information (virtually high level details). Thought I'd reach out before trying to reverse engineer the technology.

Thanks

Tier optimization task of ReFS volume is not working in Windows Server 2016.

> Get-Volume g |Optimize-Volume -TierOptimize
Optimize-Volume : The volume optimization operation requested is not supported by the hardware backing the volume.
Activity ID: {3dbe8d23-3259-49ff-a3ec-e7f16eff301b}
    + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...age/MSFT_Volume) [Optimize-Volume], CimExcep
   tion
    + FullyQualifiedErrorId : StorageWMI 43022,Optimize-Volume

Application log:

defrag: 257

The volume Vol_Tier2 (G:) was not optimized because an error was encountered: The operation requested is not supported by the hardware backing the volume. (0x8900002A)

If I format this volume to NTFS everything works fine. Had no such problem in Server 2012 R2.

Guess defrag.exe is not working with new ReFS v3.1

I got one wired issue in our domain with multi site. Users got issues accessing the \domain.com\corpdata share intermittently. its freeze and noticed hapanning everywhere at the same time too.

So just install Wireshark on my laptop and start the capture and noticed having issue around 2.40-45 PM I have the capture saved. but try to identify with my limited knowledge but still couldn't figure this out.

error attached

link text 

Can someone help me to identify the root cause. 

As

is there any way to STOP users their Personal laptops to Windows Server 2012 
at the moment any user can browse to the Network share and as login with their username. 
This includes NON-Windows computers such as Mac & Linux

Hi all,

I see where Server 2016 has a SMB connection limit of 16+ million. We have about 35,000 users. We are looking at having one server for all of the storage. Besides space on the hard drives, is there anything that I should consider?

The server has a 10Gb nic on it. Quad core with 16GB of ram. I can add more RAM and CPUs as needed. Just curious if there are any best practices on file servers that I should follow? Or any pitfalls that may creep up?

Thank you
Charles

We've just deployed Work Folders in our organisation and so far we're loving it. It solves a lot of issues and enhances our user's experience.

I have a question about .ini files. 

We have essentially created a work folder on their laptops containing C:\Users\Username\Work Folders\...

• Documents
• Desktop
• Downloads

We've used GP to redirect their associated folders to this new location using folder redirection. This allows remote workers to save and open files without the files going over the WAN everytime as we've set it to always be available whilst offline. 

One big problem we have at the moment is with the sync icons. When I look at File Explorer, it'll show Desktop, Downloads and Documents with a BLUE Sync Arrows. If I click on those folders, everything is green ticks. This simple GUI glitch throws the user into thinking it's not synchronising correctly. My understanding of this behaviour is a result of the desktop.ini file. Work Folders ignore .ini .tmp files. So if a user has those, then the top level folder shows as continuously syncing, even though it's not. 

Now, I'm new to this feature and as far as I understand, it has been about since Windows Server 2012 R2. Does this always happen? Is it normal behaviour to show the top level folders with the blue sync arrows, even though everything inside has synced or is it a relatively new GUI bug that affects Windows 10 1803?

You can replicate this behaviour simply by adding a .ini file inside a work folder. The top-level folder will show the syncing icons. The sync control panel will show green - syncronised. 

Does anybody have a workaround so I don't throw the users experience off? I'm getting support calls because they think it' not syncing.

Thank you

Hello everyone.

I have two nodes configuration for Storage Spaces Direct.

The servers were built following the R730xd Dell Matrix Compatibility with S2D with certified components, firmwares and drivers.

Everything goes fine with its configuration until I enabled S2D and checked the Storage Tiers created:It only created Capacity Storage Tier. My current configuration per server (both identical in every component) is:

- Cache: 4 x SSD Dell Enterprise 1.98 TB

- Storage: 8 x HDD Dell Enterprise 8 TB

The cache:storage ratio is 1:2 - the one suggested by Microsoft in this scenario.

Enabling S2D shows in the final validation report that the SSD's are marked as "Disk Used for Cache memory" with an asterisk. Also after creating the pool all the disk are selected and SSD's are marked as Journal, getting all the free space for themselves, and HDD's are marked as Auto-Select with almost all the free space available.

But after this I have checked the Storage Tiers created and only Capacity is showing. No Performance Storage Tier was created for the cache SSD's. I tried creating it manually but no free space is available for this storage tier when trying to create a new virtual disk.

PS C:\Users\xx> get-storagetier -friendlyname capacity, performance | fl *


Usage                  : Data
ProvisioningType       : Fixed
AllocationUnitSize     : Auto
MediaType              : HDD
FaultDomainAwareness   : StorageScaleUnit
ColumnIsolation        : PhysicalDisk
NumberOfColumns        : Auto
NumberOfGroups         : 1
ParityLayout           :
ObjectId               : {1}\\S2D_CLUSTER\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.Object
                         806d0-73d2-4312-9a54-7238280672d4}:ST:{a39a3509-81e6-49f5-81a5-3e3228700390}{3da1103b-
                         4-8dc5-daab62bb5584}"
PassThroughClass       :
PassThroughIds         :
PassThroughNamespace   :
PassThroughServer      :
UniqueId               : {3da1103b-921a-4ef4-8dc5-daab62bb5584}
AllocatedSize          : 0
Description            :
FootprintOnPool        : 0
FriendlyName           : Capacity
Interleave             : 262144
NumberOfDataCopies     : 2
PhysicalDiskRedundancy : 1
ResiliencySettingName  : Mirror
Size                   : 0
PSComputerName         :
CimClass               : ROOT/Microsoft/Windows/Storage:MSFT_StorageTier
CimInstanceProperties  : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties    : Microsoft.Management.Infrastructure.CimSystemProperties

Usage                  : Data
ProvisioningType       : Fixed
AllocationUnitSize     : Auto
MediaType              : SSD
FaultDomainAwareness   : StorageScaleUnit
ColumnIsolation        : PhysicalDisk
NumberOfColumns        : Auto
NumberOfGroups         : 1
ParityLayout           :
ObjectId               : {1}\\S2D_CLUSTER\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.Object
                         806d0-73d2-4312-9a54-7238280672d4}:ST:{a39a3509-81e6-49f5-81a5-3e3228700390}{c31c5599-
                         6-ae68-dbcb568704df}"
PassThroughClass       :
PassThroughIds         :
PassThroughNamespace   :
PassThroughServer      :
UniqueId               : {c31c5599-f6e4-4b76-ae68-dbcb568704df}
AllocatedSize          : 0
Description            :
FootprintOnPool        : 0
FriendlyName           : Performance
Interleave             : 262144
NumberOfDataCopies     : 2
PhysicalDiskRedundancy : 1
ResiliencySettingName  : Mirror
Size                   : 0
PSComputerName         :
CimClass               : ROOT/Microsoft/Windows/Storage:MSFT_StorageTier
CimInstanceProperties  : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties    : Microsoft.Management.Infrastructure.CimSystemProperties

Could anyone help me out with this issue?

Thanks in advance.

I have an iSCSI vhdx file on a NAS server running DFS replication to a second Windows 2016 storage server running DFS replication. I have been successfully replicating the vhdx file between the servers for a couple of weeks. I have a mirror image of the files on each server. I am now getting sharing violation errors and the replication is not running. I Googled and read that the VHDX file is an open file and DFS cannot replicate open files - I don't understand why replication worked for a period of time and has now stopped working. Is this valid information? If so, what other Windows 2016 storage server apps/tools can I utilize to perform the replication? 

Thanks, 

Milty 

Update: I deleted the replication group and recreated it - at the moment replication is working - all files are mirrored on each NAS but I am still concerned with the Google hits that state you can't use DFS to replicate vhdx files. So, I am still looking for input from the forum. 

milty60

Hi all,

Had a question I was hoping you might be able to help me with - I've done some research but have come up empty handed. Is there a way to tell what clients are accessing files/folders through DFS. To give a backstory, we are in the process of doing a domain consolidations from a M&A. This company extensively used their DFS name space everywhere (application configuration, drive mappings, printer configurations for scanning, etc). Management does not want to keep the AD environment up serving DFS, since there is no easy way to move the name space to another domain I need to get rid of it in the AD that will be shutting down.

I'd like to have an idea of what devices are using the name space to access files, is there some kind of logging or utility I can use? For example with DNS, I would turn on DNS debug logging to see what devices are sending queries then go address those devices. Would like to do the same with DFS.

Any feedback is appreciated!

I have several quota templates configured for different user's home folder, so user can't use over the quota template limits which they belong to. Recently, I found more and more users have space usage issue after they reached quota templates limits. 

For example, userA is belong to 1GB template for his folder. He ran out of space, so he deleted all his files, but it still shows o space on client side. Also under File Server Resource console, I still see userA used 100% of his space. To help userA gets back his space, I will have to delete userA's template, and re-apply it. Can someone tell me why this happened? Thanks!

I believe I am seeing a problem with ISCSI Initiator.  When a Command PDU that's sent by ISCSI Initiator is rejected by my target (Reject PDU), it appears ISCSI Initiator retries the same Command PDU but fails to increment CmdSN.  So my ISCSI target, seeing an "old" CmdSN, simply drops it which eventually leads to Task management by ISCSI Initiator.

Here the order I observe:

1. ISCSI Initiator issues command PDU with CmdSN 0x50.

2. Target rejects with Reject PDU, ExpCmdSn in Reject PDU is 0x51.

3. ISCSI Initiator retries command PDU again with CmdSN 0x50.  (against spec)

4. Target ignores the retry.

5. ISCSI Initiator issues LUN Reset because target never responds.  LUN Reset has CmdSN 0x51.

6. Target processes LUN Reset.

I believe this is a problem with ISCSI Initiator as commands, even retried commands, should never repeat CmdSNs.  Is anyone else seeing an issue like this?  Is there a method to formally file a bug against this?