I think these are related to Window Search but I am not sure. They were in a file called VOLSHEXT.LOG. I searched the internet could not find anything and also no entries in the Event-log. Could someone at Microsoft let me know what this error is?
[3256:1520] 06/19/2014-15:08:37.964 [error:wsearchapis.cpp:218] GetVolumeWSearchInformation: (0x80070032)
[3256:1520] 06/19/2014-15:08:37.964 [error:wsearchapis.cpp:271] GetVolumeWSearchInformation: 0x80070032 (0x80070032)
Hi All,
We have Work Folders successfully set up on our domain. A non domain joined client can connect and gain access to their work folder share without issue.
I am now in the process of setting up domain connected laptops that will be used by staff. These laptop will have restrictions on them and the users that logon will not have admin privileges.
The work folder server has the device policies of:
We are using Windows 8.1 enterprise clients, with the latest patches. If I turn off the "Automatically lock screen...." policy, a domain user can successfully sync their work. If I turn it back on they get the below error:
"Make sure that your account is an administrator on the PC and that all administrator accounts on this PC have a password."
I have set the group polices that I believe might effect this message, but have yet to get a successful sync. Could someone give me the exact group policies I would need to set for client to meet the security requirements.
hi
my windows 7 pro laptop freezes every time i go online why?
please give me a solution to fix this
Running Windows 7 Pro (x64) and also have an external drive plugged into it. In this external drive we have a folder that we share out to the employees at that location. Every so often after the machine reboots the folder decides to unshare itself and we have to manually go in and share it back out.
I would like to know what's causing this to happen and maybe some advice on how to fix it.
Thanks in advance
I am having difficulty tracking down the following error I receive with dfsdiag.
DFS seems to be working fine despite the errors above (the paths point to my two folder targets). Also, the namespace is not standalone, it's domain-based.
Any ideas on how to get to the bottom of these errors?
TIA!
Hi.
There was anoying feature (some call it bug) when Windows 2008 R2 UAC blocks folder acces if You are member of local Administrators group and NTFS ACL is allowing only Adminitrators and other users /groups, but not You. There was possible to avoid this via turning off UAC and rebooting computer.
Now, with Windows server 2012 (RTM, VL) problem is worse. You can turn off UAC (and reboot,i hope it does full reboot) but nothing changes. Still You are prompted
"You don't currently have permissions to access this folder. Click Continue to permanently get access to this folder. Continue(with Shield mark) Cancel"
And if i click continue, my account is added to folder ACL. Havent found any way to bypass it.
This is idiotic. If we have multiple admisnitrators every admin SID is added (at some point). And people are coming and leaving - and ACE's remain. And btw - how it is related with "Use groups for granting permissions" best practice ? Only way is to create "File Administrators group" , make administrators member of this group and add this group to ACL. Lot, of lots of pointless work.
Dear MS - how should we resolve it? Any secret policy/registry key, hotfix coming ?
Hi,
I am new to this forum, but I have been reading a lot of the posts on here in an attempt to fix a problem I have.
I have a Windows Server 2008 R2 RAID-5 array. It is made up of 5 2TB disks.
Recently the array failed. I cannot remember the original error message now, I think it was "Failed Redundancy". I have used a Western Digital disk tool to determine that one of the disks is not operating well, but the other 4 are.
I removed the faulty disk, and replaced it with a new one. At this point, disk manager shows 4 Failed, online disks, one unallocated disk and one missing disk. It would not let me repair the array in this state - it was unhappy that the original failed disk was missing.
Today I have plugged the failed disk back in, along with two new drives. In that situation, I do get the "Repair volume" option, but each time I use it, it takes one seemingly healthy disk out of the array and uses one of the new disks. When it has finished, the disk that I think is failing is still in the array, and the array as a whole has a status of "At risk". Upon a reboot, it usually resorts back to "Failed Redundancy" and shows the newly added disk as the cause of the problem. It does this regardless of which of the two new disks I use to repair it.
I have no idea what is going on at this point! I would have thought it would remove the disk that I think is faulty and use one of the new ones and the status would be "Healthy". Instead, each time I try a repair, a different drive has the warning symbol next to it in disk manager, and it is always in Failed Redundancy or At Risk state.
I need some advice!
Thanks for your time,
Paul
Hi All,
Can anyone here share some best practice for building Windows Server 2012 R2 File Server for 1000+ users ?
initially the home drive H:\ will be 2 TB NTFS and the file share S:\ drive will be 4 TB NTFS minimum.
I'll enable the De-duplication, Compressionand the drive encryption (Bit locker) for added security mandated by the PCI-DSS compliance. On top of this, does the De-Duplication feature still works with Symantec Enterprise Vaultfile archiving for all files not accessed in the past 2 years as well ?
Note: The server will be deployed on VMware virtual machine.
/* Server Support Specialist */
I have a storage pool made up from 7 physical desktop drives all attached to the motherboard SATA ports.
Seagate 4TB (x4)
Western Digital 2TB (x1)
Western Digital 500GB (x2)
Pool size: 17.3TB (as repored by Win)
The problem seems to be with Thin disks, they use up free pool space when i copy files to the virtual disk but when i delete the files only part of the allocated space is returned. To test this out more thoroughly i created a new "2-Way Mirror Thin ReFS" disk and copied about 650GB to it, waited until next day, and promptly deleted it all. The virtual disk was now empty, yet it still allocated about 680GB from the pool which would not be returned until the virtual disk itself was deleted.
My largest virtual storage disk (2-Way Mirror Thin ReFS) now has 2TB+ "Ghost" allocation that it refuses to return to the pool and it keeps growing whenever i make any changes. The data on this virtual disk exceeds my other free disk space elsewhere so i cant move all the data off it and recreate it. I need to fix it on the fly somehow and preferably without buying a ton of new diskspace.
I tried Optimize-Volume as suggested on a bunch of google search results with the following result:
PS C:\Users\Administrator> Optimize-Volume -DriveLetter E -Verbose -ReTrim -SlabConsolidateHi,
When looking at the three maintenance tasks (schedtasks) that are employed to maintain the dedup volumes, is there an order by which they should run?
For example, should garbage collection always run before scrubbing?
Also, is it important to run all of these tasks when the disks are at their quietest?
I understand that 8.3 file naming should be disabled when using DFSR, especially with read-only replicas. And, in general, it's good practice for performance.
BUT, is it really necessary? I understand it could cause some the outgoing replication folder on a RO DFSR replica may occur, but is this really a problem? Aside from cosmetic and the fact that it takes up space...
I ask because it's enabled on all my servers, and I'm paraoid that if I enable it, it will cause some programs issues as we use a ton of different software packages for engineering, and some are quite old....
Hi,
After changing dedup schedule once we are receiving this error and not able to change it any more.
there was a problem retrieving data deduplication schedule
Glenn of xSyLent
I have two windows 7 x64 Ent non-SP1 builds. They were built with different ISOs. The ISOs are different sizes so there’s at that level something different between the two. But the difference I’ve found is how they move files around within the same volume. On build A when the contents of c:\A are moved to to c:\1 the newly moved contents of c:\1 have the inherited permission from c:\A. On build B when the contents of c:\B are moved to c:\2 the newly moved contents of c:\2 have the inherited permissions of c:\2.
First off, I’ve googled around on the Build A scenario and have found others having this result, as well as Microsoft addressing it as normal behavior (see http://support.microsoft.com/kb/310316). That said, why does my Build B act different?
The problem is that I’ve written documentation for our support groups on how to manage file shares and they are getting different results with regards to permissions depending on what desktop they’re using. A workaround to this is to edit the documentation and insist that files always be copied within the same volume then delete the source, but I’d like to know what exactly is going on.
If you’re wondering why I have and are using two different ISOs, it’s because we’re a large org with different support groups.
I put this in the server forum because despite my example above this issue is happening when files are moved within the same mapped drive (which is a windows server).
Thanks!
Failed to get exclusive lock on the Extensible Firmware Interface (EFI) system partition.
[ Name] Microsoft-Windows-Backup
[ Guid] {1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}
EventID 517
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2012-09-13T02:01:26.193377500Z
EventRecordID 134130
Correlation
- Execution
[ ProcessID] 13508
[ ThreadID] 552
Channel Application
Computer SERVER.srv.local
- Security
[ UserID] S-1-5-17
- EventData
BackupTime 2012-09-13T02:00:15.711673900Z
ErrorCode 2155348254
ErrorMessage %%2155348254
Trying to recover some deleted files that are located in the DFSRPrivate folder as Conflicted files due to an erroneous change made on the primary server in the replication group. I am getting the error shown below when I try to recover those files (which are listed in the manifest file). Is there any workaround/solution to getting these files back using this mechanism? I am trying to do recovery to a different folder so I can copy from it, but running with RestoretoOrigin gives the same error.
Alternatively, if there's a way to de-obfuscate the files in the DFSRPrivate directories, that might be a reasonable plan C.
Initially tried to do a disk based recovery from the primary server, but there are differences. Server is Windows Server 2012 R2 64 bit.
Any suggestions would be gratefully received.
PS F:\recovery> Restore-dfsrpreservedfiles -Path ".\DFSRPrivate\ConflictAndDeletedManifest.xml" -RestoreToPath F:\rd
Restore-dfsrpreservedfiles : The specified path, file name, or both are too long. The fully qualified file name must
be less than 260 characters, and the directory name must be less than 248 characters.
At line:1 char:1
+ Restore-dfsrpreservedfiles -Path ".\DFSRPrivate\ConflictAndDeletedManifest.xml" ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Restore-DfsrPreservedFiles], PathTooLongException
+ FullyQualifiedErrorId : System.IO.PathTooLongException,Microsoft.DistributedFileSystemReplication.Commands.Resto
reDfsrPreservedFilesCommand
Patrick W. Foster
Newton, MA
I think these are related to Window Search but I am not sure. They were in a file called VOLSHEXT.LOG. I searched the internet could not find anything and also no entries in the Event-log. Could someone at Microsoft let me know what this error is?
[3256:1520] 06/19/2014-15:08:37.964 [error:wsearchapis.cpp:218] GetVolumeWSearchInformation: (0x80070032)
[3256:1520] 06/19/2014-15:08:37.964 [error:wsearchapis.cpp:271] GetVolumeWSearchInformation: 0x80070032 (0x80070032)
Hi All,
is there any way how to resize virtual disk within Storage Spaces in Windows Server 2012? I have 4TB (Thin provisioned) virtual disk which contains only 400GB of data and I would like to shrink virtual disk, but resize-virtual disk in powershell gives me "not supported" error.