We are trying to configure new file server mirrors with DFS + DFSR on them and our existing file servers in our three environments. Sandbox-Dev-Live. All are under the same domain. I was able to successfully create a namespace from the "new" sandbox-FS02, \\domain.net\sbox\, and had no issues getting replication up and running and all was looking sunny and easy.

In "dev", however, things are not so easy. When attempting to create the \\domain.net\dev namespace, I receive an error error on both dev-fs01 and dev-fs02. For the sake of simplicity here I'm leaving everything default. Not changing anything with shared folder location, details, or path. The shared folder does not exist before creation. Default path of C:\DFSRRoots\Dev is being used. "All Users have Read-Only Permissions" is checked. Domain based, with 2008 mode checked. 

The namespace in question has never been successfully created and there are no associated registry entries for the namespace on any DC.

The error in question is as follows:

"\\domain.net\dev: The namespace server \\dev-fs01 cannot be added. The specified server cannot perform the requested operation".

There is no associated EventViewer Log Error, on either file server or any domain controller within the domain.

I have done a lot of troubleshooting already in terms of network connectivity between the servers and the PDC, permissions, verifying NETLOGON shares, AD replication... out of ideas at this point. I can provide any (sanitized) information that is desired about the environment or the error.

I'm having a failover cluster with 2 servers. Both servers have 2 disks; 1 800GB for data and 1 20GB for logs. Of course these are GPT disks and I'm able to build a cluster and create a file server role.

I've used Storage Replica to replicate the 800GB disks. This works and I can host the file server role on both nodes in the cluster. I've created a share on the fileserver role and added some data to this share. No problems so far.

Now I want to copy more data to the fileserver role, but when doing to the replication will fail after having copied some GBs of data.

The event log of the cluster gives the following error:

Cluster resource '29382f4b-948c-4768-acc6-10fea296553a' of type 'Storage Replica' in clustered role 'SR Group 1' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

I can bring the disks online again and start the Storage Replica role, but I don't want it to fail.

In case someone wonders; I did run the "Validate Cluster..." wizard and I passed it.

Hi There,

I have a file server running on Windows 2008 R2. I have to install the role FSRM MANAGEMENT.

But when I try to install i find the error: the request to add or remove  on specified server failed. the system cannot find the specified file. I found in the logs the error that is given below :

log name: setup

sorce servicing

event id: 11

Event ID:      11
Task Category: (1)
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      SRVFC003.ENANA.NET
Description:
Update FSRM-Management of package FSRM-All failed to be turned on. Status: 0x80070002.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Servicing" Guid="{BD12F3B8-FC40-4A61-A307-B7A013A069C1}" />
    <EventID>11</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2019-03-31T00:47:23.860591100Z" />
    <EventRecordID>371</EventRecordID>
    <Correlation />
    <Execution ProcessID="5356" ThreadID="6652" />
    <Channel>Setup</Channel>
    <Computer>SRVFC003.ENANA.NET</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <CbsUpdateChangeState xmlns="http://manifests.microsoft.com/win/2004/08/windows/setup_provider">
      <UpdateName>FSRM-Management</UpdateName>
      <PackageIdentifier>FSRM-All</PackageIdentifier>
      <ErrorCode>0x80070002</ErrorCode>
      <Client>DISM Package Manager Provider</Client>
    </CbsUpdateChangeState>
  </UserData>
</Event>

Is there any way to fix this issue? Thanks in advance for your help.

Hi All

I am using a 3rd party app PDFTK.exe to combine pdf files into one pdf file.  The app works without incident on a Server 2012 R2 system (app is running from the Sever on a workstation in a client/server environment) but does not work on the Server 2008 R2 system.  The difference between the two setups (in the PDFTK folder permissions) is the presence of the ALL APPLICATIONS PACKAGES group on the 2012 R2 server and the absence of this group in the 2008 R2 system.  Since the error message is logon failure when invoking the PDFTK app on the 2008 R2 system I am assuming this missing group (on the 2008 R2 system) is the culprit.  I have looked in vain for the procedure regarding the adding of this group but none of the procedures found has worked.  Is it the case that this group does not exist on Server 2008 R2 and my "logon failure" is not being caused by this "missing group"?  I should also add, the PDFTK app is being invoked from a vb.net program (same environment on both Servers)  One other note if I run the vb.net program directly on the Server 2008 R2 system PDFTK works without issue.  Any insights would be greatly appreciated.

Respecfully,

Ideprize

Gordon Haas

Hello everybody,

I’ve reinstalled my windows 2016 1709 Server, now the files on my ntfs-volume with deduplication are not accessible.

The Server is a backup repository server, so I can’t access my backups in the moment.

Checkdisk has reported no errors, the folder structure is available, but all deduplicated files are inaccessible.

I’ve reinstalled the server with windows 2016 1607.

Does anyone know if the NTFS-dedup has changed from windows 2016 1607 to 1709?

I can’t find a 1709 iso-download in our volume-license-portal, so I can’t reinstall with 1709.

In the moment, I try to get access to the files by installing windows 2019 1809.

Any idea how to get a iso with windows Server 2016 1709? Or any Idea how to get access to the files again?

Thanks

Guido

We experienced a sudden drop in network share access in our environment today. Several of our users (100's) lost access to their day to day Data drive on their local office server. The issue was experienced across multiple office servers.

However the issue was sporadic and inconsistent, one user that couldn't access one share, the user next to them could but couldn't access the Data share on another office server.

We have multiple file servers each with multiple shares, our servers are running Server 2008 R2 and our workstations are Windows 7.

The issues was primarly experienced on the everyday 'Data' share, other shares on the same server were accessible. The folder was still accessible locally on the server and only appeared to be an issue for SMB connections.

We were able to identify a workaround by either restarting the client workstation which resolved the problem or by accessing the share using the FQDN instead of NETBIOS name.

We've troubleshooted name resolution and can confirm that Name resolution is working fine.

We've checked the Network provider order and this is also configured correctly on all file servers.

We've also ruled out the hotfix documented in KB2194664 as our servers and clients have a newer version of file mrxsmb10.sys and the hotfix is not applicable.

We performed a network capture on a file server that was receiving a connection attempt from a problem client and received the following results:

A successfull connection attempt to a share looks like this:

SMB2170 Tree Connect Request Tree: \\<SERVER>\IPC$
SMB2138 Tree Connect Response
SMB2222 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
SMB2222 Ioctl Request FSCTL_DFS_GET_REFERRALS, File: \<SERVER>\Users
TCP54 445→64647 [ACK] Seq=85 Ack=453 Win=256 Len=0
SMB2131 Ioctl Response, Error: STATUS_NOT_FOUND
SMB2172 Tree Connect Request Tree: \\<SERVER>\Users
SMB2138 Tree Connect Response

The connection attempt to the problem share looks like this:

We've raised a support ticket with Microsoft as this issue now has us completely at a loss and all current community suggestions for the 'The Network Name Cannot Be Found' error message have been thoroughly explored (name resolution, network provider order, KB2194664)

We'd appreciate any assistance anyone is able to offer

Kriss Milne | MCSE

*Please click 'Vote As Helpful' or 'Mark as Answer' if a post has helped you or answered your question*

Hi everyone,

Well, I want to know if enabling VSS snapshot on the Disks drives can handle ransomware attack, I mean if I have multiple Healthy VSS snapshots and my data is infected by ransomware, could I recover from one of healthy snapshots ?

Thank you.

I have a shared folder with specific permissions and I just wanted to customize some subfolder's permission not to inherit from the parent folders.

I have already done that using advanced>uncheck "include Inheritable permission", then I added some specific users to the list. so the users now have full permissions on the folders and sub folders but when they want to edit the folders lets say creating new files  it says "you need permission to perform this action". Not sure why with full permission, it shows this error?

any help will be appreciated!

Hi, when using Get-DfsnFolderTarget remotely such as Invoke-Command -ComputerName Servername {Get-DfsnFolderTarget \\domain\dfs\share} the following error is returned:

Get-DfsnFolderTarget : Cannot get DFS folder properties on "\\domain\dfs\share"
    + CategoryInfo          : PermissionDenied: (MSFT_DfsNamespaceFolderTarget:ROOT\Microsoft\...aceFolderTarget) [Get-DfsnFolderTarget], CimException
    + FullyQualifiedErrorId : Windows System Error 5,Get-DfsnFolderTarget

Get-DfsnFolderTarget : Access to a CIM resource was not available to the client.
    + CategoryInfo          : PermissionDenied: (MSFT_DfsNamespaceFolderTarget:ROOT\Microsoft\...aceFolderTarget) [Get-DfsnFolderTarget], CimException
    + FullyQualifiedErrorId : MI RESULT 2,Get-DfsnFolderTarget

When using New-PSSession ServerName, Enter-PSSession, Get-DfsnFolderTarget \\domain\dfs\share I get the same result.

Running the command locally does return a result. It appears all DFS cmdlets give this error. Is this a double hop problem?

After an in-place upgrade from 2016 to 2019, dedup service refuses to start with the following error. I can still access data inside the drives, but dedup doesn't work and I get errors stating the same on the server management console for files and storage.

This is the only related event error:

Event 7024

The Data Deduplication Service service terminated with the following service-specific error: 
%%2153141004

I have the server patched to the latest. Is this a known issue?

Thanks!

Hello,

we are evaluating Windows Server 2016 Storage Replica to replace a 3rd party product. We used this evaluation example to get a head start and 

https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/stretch-cluster-replication-using-shared-storage

but created a two node cluster only were both cluster nodes have its own set of iSCSI disks. We are also aware of the FAQ:

https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-frequently-asked-questions

After a few tests I came to the conclusion each SR Group / SR Partnership has its own Log disk and it's not possible to assign more than one SR Group / SR Partnership to a single Cluster Role. Is this true? I assume the Log disk can become a performance bottleneck in this case.

We try to use Powershell to configure the SR Groups and SR Partnerships. One use-case is to add an additional disk to a SR Group. I learned I do have to remove the SR Partnership before I can modify the SR Groups. Nevertheless, when trying to add another disk I get a strange error:

New-SRGroup -ComputerName SR-Eval-01 -Name SR-Group-01 -VolumeName D:,E: -LogVolumeName L:
Set-SRGroup -ComputerName SR-Eval-01 -Name SR-Group-01 -AddVolumeName F:
Set-SRGroup : Unable to add volume for replication group SR-Group-01, detailed reason: The system cannot find the
file specified.
At Line:1 char:1
+ Set-SRGroup -ComputerName SR-Eval-01 -Name SR-Group-01 -AddVolumeName ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo         : ObjectNotFound: (MSFT_WvrAdminTask:root/Microsoft/...T_WvrAdminTask) [Set-SRGroup], CimException
+ FullQualifiedErrorId : Windows System Error 2, Set-SRGroup

I tried Clear-SRMetadata already, removed the iSCSI disks, created a set of new disks, and reinstalled the Storage-Replica feature already, but it made no difference.

It would be gread if someone could provide some help for my two issues.

Kind regards,

Jiriki 

My Signature

I want to know about active directory database files. Can anyone share the list?

Thanks in Advance

I'm in the process of retiring an older DFS server that's running Windows Server 2008. Currently, I have 2 namespace servers replicating all DFS shares. DFS is setup as AD integrated with 2 sites (site A and site B). Site A is running Windows Serve 2016 and it will remain. Site B is currently running Windows Server 2008 and I have a new server running Windows Server 2016 with the DFS roles installed. Both sites are connected with a VPN tunnel of 5mbps.

My question is when I add the new namespace member, should I add each namespace share with the "Add Folder Target" option and allow the replication to complete for each folder before I add the new server as a namespace server with the "Add Namespace Server" option?  I'm trying to reduce the load on the network and I'm not in a hurry.  It's my understanding that if I add the new server as a namespace server 1st, it will automatically start to replicate all of my DFS shares and I'd like to do this in stages.

After the setup of the new Windows Server 2016 in site B, I will retire the old Server 2008 box.

Thanks for any input.

Ken

I have a couple file shares on a Server 2016 build, the users are able to access the files no problem, but when reviewing the event viewer I found this error which I am not sure what it is relating too.

Hi,

we do have an rds farm with roaming profiles (not profile disks) consisting of 6 terminal servers ("srvts001" to "srv006" 2012 R2), 2 domain controllers ("srvdc01", "srvdc02" 2012 R2), 1 SQL/Fileserver ("srvsql01" 2012 R2).

Roaming profiles are stored on srvsql01 in share RDS. Oplocks are disabled, directory caching is disabled.

Everything was running without problems for 1 or 2 years. Recently (about 2 weeks ago) users began complaining about being logged on with a temporary profile. Investigation showed a lot of open file handles from previous (no longer existing) sessions on the file server.

E.g. user1 had logged on to rds one day and logged off in the evening (not just disconnected, really logged off) and when he logs in the other day on the rds farm he is logged on with a temporary profile due to the profile service being unable to access the roaming profile as it is (event log) "in use by another process".

Looking at the fileserver's open files we can see that a lot of files of that user profile (and of other users, too!) are shown as open - all with read option and no apparent locks.

When user1 loggs off these locks stay! Manually closing the open files on the file server allows the user to log on to the rds servers normally. Subsequent logging off may or may not create those stale open file handles.

We have no clue as to when these enormous amount of open file handles (we talk about 100s of files per user) happen. It seems to be at random and not hitting every user.

Has anyone ever met a similar problem? Or at least an idea on how to prevent logged off users to still have open files on the file server?

Any answer pointing in the direction of a possible solution or source of this problem is greatly appreciated!

I have two 2019 servers with groups/partnerships replicating successfully on them.

I want to monitor their ReplicationStatusfrom a 2016 server so I installed the Storage Replica module through Server features. For some reason the get-srgroup command returns nothing when run from a 2016 targeting a 2019 one. Other commands such as get-srpartnership are working as expected in from/to the same servers.

The StorageReplica module version is the same at 1.0 on both servers.

I’m guessing this is a bug though I cannot find anything about it searching. Anyone else experienced this or have info on it?

Hello!
I need to replace our old file server. I also would like to create a domain based DFS namespace. 

The old server is running 2008 R2.
The new server will be running 2012 R2.
All server are running in Hyper-V environment.

Summary of requirements:
1. The path to files needs to be intact since we have shortcuts in mail, sharepoint and so on.
2. The permissions must not change.
3. There are too much data to copy. I would have to buy more storage and end up with a lot of unused storage after migration.
    I do have access to a NAS for temporary storage if it helps.

I had a plan but it doesn't solve the storage issue?

1. Set up a new file server with DFS.
2. Robocopy a test folder from the old fileserver to the share.
3. Create a DNS alias and test access to the share with it. The DNS alias would be changed to the old fileserver name after full      migration and keep the paths intact.
4. After verification of permissions and paths do a full robocopy.
5. Shut down the old server and update the DNS alias.
6. Update linked paths where it is possible and remove alias?

Is there a fancy way of doing this more easily?

'm trying to create a storage space, but receiving the error "The Request is Not Supported."  I've tried creating the pool using a different combination of hard drives and on two different computers.  I receive the same error with all attempts.

I've have run the command get-physicaldisk in PowerShell and all of the drives have a status of False under CanPool.  I followed up with the get-physical | FL command and it shows the "CannotPoolReason" as "Insufficient Capacity" for all of the drives.  I found some information that you needed at least 1 GB for each drive.  The minimum amount of free space on the 6 drives I'm attempting to add is 1.36 TB.  The others are all 4 or 5 TB drives.  Does anyone know how I can get these labeled as True for the CanPool status?  I feel this is the problem, but I don't know how to change the status.

We are trying to configure new file server mirrors with DFS + DFSR on them and our existing file servers in our three environments. Sandbox-Dev-Live. All are under the same domain. I was able to successfully create a namespace from the "new" sandbox-FS02, \\domain.net\sbox\, and had no issues getting replication up and running and all was looking sunny and easy.

In "dev", however, things are not so easy. When attempting to create the \\domain.net\dev namespace, I receive an error error on both dev-fs01 and dev-fs02. For the sake of simplicity here I'm leaving everything default. Not changing anything with shared folder location, details, or path. The shared folder does not exist before creation. Default path of C:\DFSRRoots\Dev is being used. "All Users have Read-Only Permissions" is checked. Domain based, with 2008 mode checked. 

The namespace in question has never been successfully created and there are no associated registry entries for the namespace on any DC.

The error in question is as follows:

"\\domain.net\dev: The namespace server \\dev-fs01 cannot be added. The specified server cannot perform the requested operation".

There is no associated EventViewer Log Error, on either file server or any domain controller within the domain.

I have done a lot of troubleshooting already in terms of network connectivity between the servers and the PDC, permissions, verifying NETLOGON shares, AD replication... out of ideas at this point. I can provide any (sanitized) information that is desired about the environment or the error.

I am migrating DFS shares on old file servers to server 2016. I can add the members based on existing memberships using powershell but when I try to set the membership to read only using powershell I get the following error:

As a work around I have been manually setting them to read only using the DFS Management pane. Can anyone explain why I would be getting this error and how to work around it? I have tried setting it to read only when I set the other DFS properties and I've also tried setting it independently in a separate command. I am using the same variables to set the other DFS properties without issue.