Hi Guys. Got a interesting problem

We have upgraded windows 7 machine to windows 10 via flash drive using the following command. Upgrades are successfuland everything else works fine except the work folders

.\setup.exe" /auto upgrade /migratedrivers all /dynamicupdate disable /showoobe none 

We are getting the following errors on the Client machines

Event 10

Configuration of Work Folders through Group Policy failed. 

Error: (0x80004005) Unspecified error

Event 517 

Sync Share discovery failed. Server URL: https://workfolders.contoso.com; Partnership type: User Data; Error: (0x80004005) Unspecified error

Event 516

Server discovery on https://workfolders1.assetfin-coastal.co.za failed with (0x80004005) Unspecified error

Freshly build windows 10 machines connect and synchronize with the folders share perfectly find with NO problems.

Only Windows 7 machines being upgraded refuse to setup/connect with their workfolders.

As a further test. i can confirm that the users sync share is configured correctly since that user account can log into a different freshly built windows 10 and connect successfully.

I have also tried to disable and re-enable the workfolders feature. 

I have also tried running a sfc /scannow which completed without any problems

I have also made sure the machines are fully patched/updated

Advice would be greatly appreciated 

We have an Scale-out File server with 2 nodes.

If node 1 is active, Node 2 has an offline disk in disk management. When a failover happens the disk on node 1 will become offline and the disk on node 2 will become online.

Our problem is that someone removed the offline disk from (inactive) node 2 by ejecting it in Disk Management on node 2.

Now we want to get this disk back on node 2. What should we do to resolve this issue

Dear Support, 

We cannot find the hotfix (KB2679054) to release the free disk space not reallocated to a disk quota when we delete files in Windows Server. 

Could we only be able to run the command "Dirquota quota scan" to update regularly for maintenance purpose?

Reference:
Free disk space is not reallocated to a disk quota when you delete files in Windows Server 2008 R2 
https://support.microsoft.com/zh-hk/help/2679054/free-disk-space-is-not-reallocated-to-a-disk-quota-when-you-delete-fil
Symptoms 
Assume that you configure a disk quota for a volume on a computer that is running Windows Server 2008 R2. When you delete some files on the volume, the disk space that you free by deleting the files is not added to the available memory in the quota.
Cause 
This issue occurs because the file context structure is not filled in correctly when you delete the files.
Resolution 
To resolve this issue, we have released a hotfix for Windows Server 2008 R2.
Note 
After you apply this hotfix on computers where the issue has occurred, you have to run the following Dirquota quota scan command to reallocate free disk space:
Dirquota quota scan /Path: <Path>

Workaround
To work around this issue, run the following command to reallocate free disk space:
Dirquota quota scan /Path: <Path>

Thanks!

Best Regards, 
Daniel

I've been tracking a bug with DFS for about a year now. Randomly DFS will stop replicating certain files with an error code 4406 in the event viewer. It seems to happen only in 2016. If you dig further into it and look at the DFS logs you'll see something like "[WARN] Join::SubmitUpdate Not replicating reparse point that cannot be marshaled." It seems to happen for PDF and Excel files more often than others. If you look at the files they will have 0x620 attributes which means Sparse File, Reparse Point, Archive. The reparse point tag will be 0x80000013 which is IO_REPARSE_TAG_DEDUP. None of this is unusual and there are many files with those attributes that replicate normally. Opening the file, changing something, undoing the change and saving it will solve the issue and the files will be replicated again. If the file is not re-opened with in DFS conflict resolution algorithms timeout the file will be disappear and be moved to the conflictanddeleted folder. 

Why put this here? Because there are no real avenues to report a bug to MS. They are too big to care. I don't have a work around for the issue other than getting email alerts on 4406 and then opening the file and changing something then undoing it and then saving it. It seems to happen more frequently the longer a server has been up so I also recommend rebooting frequently. Anyway here are my debug DFS-R logs. If you find something out of the ordinary let me know.

20190918 08:05:50.531 7832 USNC  2618 UsnConsumer::UpdateIdRecord LDB Updating ID Record:+	fid                             0x600000000F79C+	usn                             0x5fc561948+	uidVisible                      1+	filtered                        0+	journalWrapped                  0+	slowRecoverCheck                0+	pendingTombstone                0+	internalUpdate                  0+	dirtyShutdownMismatch           0+	meetInstallUpdate               0+	meetReanimated                  0+	recUpdateTime                   20190917 12:37:08.437 GMT+	present                         1+	nameConflict                    0+	attributes                      0x620+	ghostedHeader                   0+	data                            0+	gvsn                            {FBAFB489-1FC7-4466-9505-E7812C68A131}-v765616+	uid                             {FBAFB489-1FC7-4466-9505-E7812C68A131}-v763880+	parent                          {CF106D0C-E94A-4595-8260-96A5B1275B32}-v26541+	fence                           Default (3)+	clockDecrementedInDirtyShutdown 0+	clock                           20190918 12:05:50.531 GMT (0x1d56e1969c8ecbd)+	createTime                      20190220 21:28:33.358 GMT+	csId                            {968DA157-F243-4F5D-919F-D32F30DA67F7}+	hash                            00000000-00000000-00000000-00000000+	similarity                      00000000-00000000-00000000-00000000+	name                            JOBLIST.xls+	
20190918 08:05:50.531 7832 USNC  2621 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD:+	USN_RECORD:+	RecordLength:        88+	MajorVersion:        2+	MinorVersion:        0+	FileRefNumber:       0x600000000F79C+	ParentFileRefNumber: 0x2000000004F4B+	USN:                 0x5fc561948+	TimeStamp:           20190918 08:05:50.531 Eastern Standard Time+	Reason:              Basic Info Change Close Data Overwrite Reparse Point Change +	SourceInfo:          0x0+	SecurityId:          0x0+	FileAttributes:      0x620+	FileNameLength:      22+	FileNameOffset:      60+	FileName:            JOBLIST.xls+	
20190918 08:05:50.546 6404 OUTC  2882 OutConnectionContentSetContext::TransportRequestVvUp Received request for VvUp csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1} rgName:domain.local\dfs\shared  ptr:0000020FC2127FA0
20190918 08:05:50.546 6404 SRTR  2353 SERVER_RequestVersionVector Sent requested version vector. connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} seqNumber:28 requestType:REQUEST_NORMAL_SYNC changeType:all
20190918 08:05:50.546 8284 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1}
20190918 08:05:50.546 8284 OUTC  2882 OutConnectionContentSetContext::TransportRequestVvUp Received request for VvUp csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF} rgName:domain.local\dfs\shared  ptr:0000020FC2127BE0
20190918 08:05:50.546 8284 SRTR  2353 SERVER_RequestVersionVector Sent requested version vector. connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} seqNumber:25 requestType:REQUEST_NORMAL_SYNC changeType:all
20190918 08:05:50.546 6404 OUTC  2882 OutConnectionContentSetContext::TransportRequestVvUp Received request for VvUp csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D} rgName:domain.local\dfs\shared  ptr:0000020FC0776800
20190918 08:05:50.546 6404 SRTR  2353 SERVER_RequestVersionVector Sent requested version vector. connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} seqNumber:27 requestType:REQUEST_NORMAL_SYNC changeType:all
20190918 08:05:50.546 6404 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{6A1762D1-F10E-4B7D-8937-485CDED95B2C}
20190918 08:05:50.562 6404 SRTR  1113 SERVER_RequestUpdates Processing RequestUpdates call. connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} credits:32 requestType:all
20190918 08:05:50.562 6404 OUTC  2814 OutConnectionContentSetContext::TransportRequestUpdates Received request for updates csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1} rgName:domain.local\dfs\shared  ptr:0000020FC2127FA0
20190918 08:05:50.562 6404 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{B0B1DBC8-3601-4E8B-A16D-429D9CE9CAF1}
20190918 08:05:50.562 6404 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF}
20190918 08:05:50.562 6212 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D}
20190918 08:05:50.562 6212 OUTC  2882 OutConnectionContentSetContext::TransportRequestVvUp Received request for VvUp csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{6A1762D1-F10E-4B7D-8937-485CDED95B2C} rgName:domain.local\dfs\shared  ptr:0000020FC2127DC0
20190918 08:05:50.562 6212 SRTR  2353 SERVER_RequestVersionVector Sent requested version vector. connId:{6A1762D1-F10E-4B7D-8937-485CDED95B2C} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} seqNumber:25 requestType:REQUEST_NORMAL_SYNC changeType:all
20190918 08:05:50.562 6212 SRTR  1113 SERVER_RequestUpdates Processing RequestUpdates call. connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} credits:32 requestType:all
20190918 08:05:50.562 6404 SRTR  1113 SERVER_RequestUpdates Processing RequestUpdates call. connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} credits:32 requestType:all
20190918 08:05:50.562 8284 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D}
20190918 08:05:50.562 6404 OUTC  2814 OutConnectionContentSetContext::TransportRequestUpdates Received request for updates csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{820A5C3D-8CA4-4DD3-9681-45E4FDA46C8D} rgName:domain.local\dfs\shared  ptr:0000020FC0776800
20190918 08:05:50.562 6212 OUTC  2814 OutConnectionContentSetContext::TransportRequestUpdates Received request for updates csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF} rgName:domain.local\dfs\shared  ptr:0000020FC2127BE0
20190918 08:05:50.562 4264 SRTR  2442 SERVER_AsyncPoll Processing AsyncPoll call. connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF}
20190918 08:05:50.577 6588 JOIN  1104 [WARN] Join::SubmitUpdate Not replicating reparse point that cannot be marshaled. connId:{EBCF5C4A-030B-494C-8D8C-5B048AF63CAF} csId:{968DA157-F243-4F5D-919F-D32F30DA67F7} csName:shared record:+	fid                             0x600000000F79C+	usn                             0x5fc561948+	uidVisible                      1+	filtered                        0+	journalWrapped                  0+	slowRecoverCheck                0+	pendingTombstone                0+	internalUpdate                  0+	dirtyShutdownMismatch           0+	meetInstallUpdate               0+	meetReanimated                  0+	recUpdateTime                   20190918 12:05:50.531 GMT+	present                         1+	nameConflict                    0+	attributes                      0x620+	ghostedHeader                   0+	data                            0+	gvsn                            {FBAFB489-1FC7-4466-9505-E7812C68A131}-v765616+	uid                             {FBAFB489-1FC7-4466-9505-E7812C68A131}-v763880+	parent                          {CF106D0C-E94A-4595-8260-96A5B1275B32}-v26541+	fence                           Default (3)+	clockDecrementedInDirtyShutdown 0+	clock                           20190918 12:05:50.531 GMT (0x1d56e1969c8ecbd)+	createTime                      20190220 21:28:33.358 GMT+	csId                            {968DA157-F243-4F5D-919F-D32F30DA67F7}+	hash                            00000000-00000000-00000000-00000000+	similarity                      00000000-00000000-00000000-00000000+	name                            JOBLIST.xls+	
20190918 08:05:50.577 6588 EVNT  1194 EventLog::Report Logging eventId:4406 parameterCount:7
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter1:968DA157-F243-4F5D-919F-D32F30DA67F7
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter2:JOBLIST.xls
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter3:D:\SHARED
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter4:shared
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter5:domain.local\dfs\shared
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter6:4F01BA20-918B-44F0-8A13-5D2B1B65EDF4
20190918 08:05:50.577 6588 EVNT  1214 EventLog::Report         eventId:4406 parameter7:5B77BDA4-9DB1-48DF-B470-AAF6E649648C
20190918 08:05:50.577 6588 JOIN  1201 Join::SubmitUpdate LDB Updating ID Record:+	fid                             0x600000000F79C+	usn                             0x5fc561948+	uidVisible                      1+	filtered                        0+	journalWrapped                  0+	slowRecoverCheck                0+	pendingTombstone                0+	internalUpdate                  0+	dirtyShutdownMismatch           0+	meetInstallUpdate               0+	meetReanimated                  0+	recUpdateTime                   20190918 12:05:50.531 GMT+	present                         1+	nameConflict                    0+	attributes                      0x620+	ghostedHeader                   0+	data                            0+	gvsn                            {FBAFB489-1FC7-4466-9505-E7812C68A131}-v765616+	uid                             {FBAFB489-1FC7-4466-9505-E7812C68A131}-v763880+	parent                          {CF106D0C-E94A-4595-8260-96A5B1275B32}-v26541+	fence                           Default (3)+	clockDecrementedInDirtyShutdown 0+	clock                           20190918 12:05:50.531 GMT (0x1d56e1969c8ecbd)+	createTime                      20190220 21:28:33.358 GMT+	csId                            {968DA157-F243-4F5D-919F-D32F30DA67F7}+	hash                            00000000-00000000-00000000-00000000+	similarity                      00000000-00000000-00000000-00000000+	name                            JOBLIST.xls+	

Work Folder issue: MS Enterprise clients environment using AD FS and Work Folder synchronization.

Client would not able to access the Work Folders files occasionally. Sync the Work Folders would be end with error: 

Error code:

Sync status: Sync stopped. A problem occurred <o:p></o:p>

 Authentication method: ADFS <o:p></o:p>

 Error code: The server is too busy to handle sync requests. (‪0x80c8003e)<o:p></o:p>

<o:p></o:p>

Tapped to sync but no avail no server response. Manage credentials password need is working. 

Any advice would be appreciated.

Thanks,

i have 2 domain controller with same model HP DL 380 G6 with server 2003. PDC and AD DC.My AD DC become unserviceable due to hardware issue.now i have DL380 G9 model with different hardware. now i want to use this as a AD DC with DL 380 G6 PDC.

the issue is i have very important applications on old hard drive of DL 380 G6 with server 2003.

i tried to install serevr 2003 on new AD DC but failed, minimum server 2012 should install on it.

how i can recover all settings of old hard drives in to new machine?

Hi,

Thinking I've missed something here. We're running Windows Server 2019 (latest update, but it was not working on previous updates). I try to run the Least Recently Accessed files report in FSRM like I've done on previous servers and I hit the same error each time:

This File Server is currently configured to not track last access time for files, therefore the last access time might be inaccurate for some or all the files on NTFS volumes

I've checked the registry and NtfsDisableLastAccessUpdate is set to80000000 (I've tried 80000003 as well). I've also run the query -fsutil behavior query disablelastaccess and as expected, it is set to0(User Managed, Disabled) (as it's set to 3 (System Managed, Disabled) when I change the registry entry to 80000003).

I'm really not sure what else I've missed but nothing seems to get it working.

Any ideas?

Thanks,

Steve.

Hi,

/SaiTech

Hi,

Getting this error while coping files on a Windows Server 2012 R2.  <o:p></o:p>

"The filename would be too long for the destination folder. You can shorten the filename and try again or try a location that has a shorten path."<o:p></o:p>

Any know how to fix this issue?<o:p></o:p>

<o:p> </o:p>Thanks for the support in advance .

I used a 250GB SSD and a 2TB HDD to creat a storage tiers. Now I want to add another disk into the storage pool and extend the storage tiers. When I choose the option "extend the virtual disk", it shows "Not supported type". 

So how to add disks into an existing storage tiers in Windows Server 2016？

Thank you!

Hi Everyone,

Sorry if this has been answered, but I have been having a bit of trouble tracking down some information to verify what i have been advised for SR. I have tried looking through the docs on the MS site/Github but haven't been able to find the info I am after.

Currently we have a DFS-R server with around a number of volumes, with the largest being over just under 15TB; I would like to move these off our DFS-R setup to SR. This server has a large amount of activity as well. 

My main questions regarding this are:

* Is there a limitation around total volume size that can be attached to an SR server? I have been advised 10TB is the max per server?

* On the back of the previous question, I know in standard edition 2TB was the max size supported for a single volume, is there any limitation for Enterprise?

* Is there a max number of files that SR can accommodate? I know DFS-R has a limit.

Hi,

I have a windows server 2016 standard at a customer.
This server have file shares set up.
But when the server restart the shares do not work until I connect to server and login with my admin account.
When logged in the shares works again until the server reboots.
Any got an idea why it behave like this and how to solve it?

Thanks in regards

/Mikkel

Hi Everyone,

I have a user within the organisation that has moved a file from a folder to a newly created folder.

They seem to have lost track of where they had originally transferred the file from (original folder location).

Is there a way I could find out where the original file location?

Thanks

D

I have a Server 2019 Datacenter with 6 SAS HDD disks (4x 6TB, 2x 8TB) and 4 NVMe disks (4x 1TB).

I have created a storage pool with all the above disks and created 2 storage tiers:

New-StorageTier -StoragePoolFriendlyName Pool1 -FriendlyName SSD_Tier -MediaType SSD

New-StorageTier -StoragePoolFriendlyName Pool1 -FriendlyName HDD_Tier -MediaType HDD

I plan to create a 2-way 2-column mirror with tiered storage (all of the NVMe capacity + 10TB HDD storage):

$ssd_tier = Get-StorageTier -FriendlyName SSD_Tier
$hdd_tier = Get-StorageTier -FriendlyName HDD_Tier

New-VirtualDisk -StoragePoolFriendlyName "Pool1" -FriendlyName "2wMirrorTiered" -StorageTiers  @($ssd_tier, $hdd_tier) -StorageTierSizes (Get-StorageTierSupportedSize $ssd_tier.FriendlyName).TierSizeMax, 10TB -ResiliencySettingName  Mirror -PhysicalDiskRedundancy 1 -NumberOfColumns 2 -WriteCacheSize 10GB

Greetings,

I am working for Microsoft Partner and i am experiencing an issue with one of our customers. DFS replication had an issue with jet database and its resolved.

So replication is working fine for existing DFS replicated folders. But when i create a new folder and configure replication for this folder, i found that replication not happen.

Noting that DFS have two servers one in Main site and second in DR site. I tried to restart DFS server in DR site but still same issue.

Any thoughts?

Greetings,

I am working for Microsoft Partner and i am currently working on DFS implementation for two file servers (main site and DR site).

After creating namespace and configure replicated folders we need to do the following:

1- If we have folder under namespace "A" and we need to put this folder under namespace "B", is it possible? or i have to remove folder from name space then adding it to the name. Noting that i have so many folders needed to change its namespace.

2- if we change the existing folder namespace, is there any action needed for existing replicated folder?

Regards,

Khaled El Gazzar

I have a server (2019 Datacenter) with 6 SAS HDD disks (4x 6TB, 2x 8TB) and 4 NVMe disks (4x 1TB).

All disks are in 1 storage pool, in which I created 2 storage tiers:

New-StorageTier -StoragePoolFriendlyName Pool4K -FriendlyName SSD_Tier -MediaType SSD -NumberOfColumns 2

New-StorageTier -StoragePoolFriendlyName Pool4K -FriendlyName HDD_Tier -MediaType HDD -NumberOfColumns 2

I then created a virtual disk:

$SSD = Get-StorageTier -FriendlyName SSD_Tier
$HDD = Get-StorageTier -FriendlyName HDD_Tier

New-VirtualDisk -StoragePoolFriendlyName Pool4K -FriendlyName 2wMirrorTiered -StorageTiers $SSD, $HDD -StorageTierSizes 1840GB, 10000GB -ResiliencySettingName Mirror -PhysicalDiskRedundancy 1 -WriteCacheSize 10GB

The properties of the storage tiers and of the virtual disk are:

Is it normal that the virtual disk isn't displayed as a 2-way 2-column mirror with fixed provisioning? Is this because this is set at the level of the storage tiers?

Is there a way to keep the 'NumberOfColumns' for the 2wMirrorTiered-HDD_Tier to 2 (I have now 6 HDD, but may fill up the remaining 2 empty bays with HDD which would give a total of 8 HDD)?

Hello,

Recently I have explored AD RMS and have done some basic test configuration in Lab which I found interesting.

Further, I would like to know from people's experience, whether there is any way to use AD RMS in combination with FCI to protect Video Content (i.e. video file formats).

Thanks,

Amit Jogi

Hello,

Can you anyone help me for below,

I want to block file server access block from non-domain join computer from my network but domain joined computer want to access the same.

Regard,

Fasil CV

Fasil CV