How to restrict workgroup computers in accessing my shared folder.

And only allow a specific system in the workgroup to have full control access to that shared folder.

Operating System :Windows Server 2003

I have DFS Management installed on a 2012 domain controller which I would like to retire.  Is there a easy way to migrate this to a new domain controller of the same 2012 OS with no downtime?  There is DFS Management installed on a 2008R2 domain controller at the other site as well.  However that one is not changing.

Hi!

We're having some strange things happening here. Maybe someone can help us what exactly is/was going on here.

1. We have to add an additional user in the NTFS ACL list for all file shares in our company (about XXXTB)

2. We're using Windows Explorer to accomplish that.

3. Every user can read in directories he/she has NO ACCESS RIGHTS to while the changes are being applied.

4. Files are also readable but at least still not writeable.

5. Affected folders and files change over time.

Has someone experienced the same issue? Does the Windows Explorer reset the ACL lists before changing them? Is there some weird caching going on?

I am wondering if anyone has setup their networks where you have a large storage array that the users desktops boot from, using iscsi, AoE, or similar. If so would I set that up with windows server 2008 r2 or 2012? Did you have any issues, or tips on setting this up? I am looking at testing this with an HP MSA60 storage array that uses sas drives, no FC.

Thank you

Hi,

I have a corporate Inventory application installed on Windows Server 2008 R2 and I need to deploy some Agents to Windows 7 Desktops.

This app requires having access to C$ and Admin$ in the Desktops, from the Server. Also the agent is installed in C:\Windows\ from a BAT Script but can be installed in C:\ or Program Files too. The agent also comes with a Service related with the processes being executed when the agent is running.

Usually I can deploy the agents from the server using Local (Desktop) or Domain Admin Account, but this time our AD Admin told me he can't provide that kind of access. It has to be a non-Admin account. When I ask him what is the right permission / mapping I should have to request to Security team in order to install the agents, he doesn't know! (It seems is not a legit AD Admin ¬¬)

In Windows 2003 I used to mitigate that scenario by requesting Power Users to our AD Admin, but that permission is not able in Windows 2008. What kind of permissions do I need to request in the Windows Server 2008 R2 account, for viewing Admin Shares in the Desktops and installing the agent remotely? Also I understand User Access Control (UAC) plays some role here (I don't know if I have to request disabling UAC in the Desktops for installing the agent, for instance)

Best regards,

Alejandro

We have three 2012 Standard R2 server for DFS Service. Two server in same location and one in different location.

Server1 and Server2(Same Location)

Server3 (Different Locatin)

We are facing issue with 2012 R2 server not able to access different location(different segment ) server through UNC path, we are getting access denied .
But we are able to access UNC path in same location servers.

If we have disabled SMB 2 then we can access same server through UNC path from anywhere.

Please help me to resolve the issue.

On several of my 2k3 Servers, R2, SP2, I am trying to set Scheduled Tasks to run my NT Backups.

In using the Wizard, or not, in Backup, I get to the

"Backup Wizard - When to Back Up" screen, with the "later" radio button highlighted "Job Name" is blank, but "Start Date" is greyed out.

If I put a name in for the backup job, then click either "Set Schedule" or "Next", NTBackup closes down with no warning.

Event Viewer shows the following:

Event Type:    Error
Event Source:    Application Error
Event Category:    (100)
Event ID:    1000
Date:        5/26/2010
Time:        11:28:38 AM
User:        N/A
Computer:    ARNOLD
Description:
Faulting application ntbackup.exe, version 5.2.3790.3959, faulting module ntbackup.exe, version 5.2.3790.3959, fault address 0x0001ccc9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6e 74 62   ure  ntb
0018: 61 63 6b 75 70 2e 65 78   ackup.ex
0020: 65 20 35 2e 32 2e 33 37   e 5.2.37
0028: 39 30 2e 33 39 35 39 20   90.3959
0030: 69 6e 20 6e 74 62 61 63   in ntbac
0038: 6b 75 70 2e 65 78 65 20   kup.exe
0040: 35 2e 32 2e 33 37 39 30   5.2.3790
0048: 2e 33 39 35 39 20 61 74   .3959 at
0050: 20 6f 66 66 73 65 74 20    offset
0058: 30 30 30 31 63 63 63 39   0001ccc9

Link to http://go.microsoft.com/fwlink/events.asp. gives no information.

Have tried deleting all scheduled tasks then stopping and starting the Task Scheduler to no effect.

Hi all,

I recently installed Windows Server 2012 essentials on my home server and I'm trying to use my 3x 2TB RAID 5 array as data storage. 
I installed Windows Server on it's own 500GB HD and during the installation I provided my RAID controller driver.
Unfortunately, when I look in the installation partition manager, I don't see my RAID 5 as a whole but as 1x 2TB and 1X 1.6TB (which should be 1x 4TB).
If I don't provide my RAID controller driver during the installation, I'm seeing my 3x 2TB all separately installation partition manager.

Any thoughts of what i'm doing wrong OR what I could try.

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

Hi

I am having problem with dfsr in windows 2003r2 64 bit I also follow http://support.microsoft.com/kb/979295#work

“To work around this issue, manually perform a tombstone operation on the oldID_RECORD record and creates a new global version sequence number. To do this, follow these steps:”

What is a tombstone operation? I assume is this going through the dfsr.log?

I also could not find the event id 2212 on the upstream server like the kb suggest.

This is the log from the downstream server

Event Type:        Error

Event Source:    DFSR

Event Category:               None

Event ID:             2104

Date:                    6/02/2014

Time:                    8:34:03 AM

User:                    N/A

Computer:          ESTDC1

Description:

The DFS Replication service failed to recover from an internal database error on volume E:. Replication has been stopped for all replicated folders on this volume.

Additional Information:

Error: 9214 (Internal database error (-1078))

Volume: 8873471E-D257-11DE-B1D9-806E6F6E6963

Database: E:\System Volume Information\DFSR

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hi There,

Massive shot in the dark here but I am struggling with a pretty major issue atm.  We have a production file server that is hosted on the following:

Dell MD 3220i -> iSCSI -> Server 2008 R2 Hyper-v Cluster -> Passthrough Disk -> Server 2012 R2 File Server VM

Essentially 3 times now, roughly a month or so apart.  The file server stops accepting connections.  During this time, the server is perfectly accessible through rdp or with a simple ping.  I can browse the files on the server directly but no-one appears to be able to access the shares over SMB.  A reboot of the server fixes the issue.  

As per a KB article I removed nod antivirus from the server to rule out a conflicting filter mode driver after the second fault.  Sadly yesterday it happened again.

The only relevant errors in the servers log files are:

SMB Server Event ID 551
SMB Session Authentication Failure

Client Name: \\192.168.105.79
Client Address: 192.168.105.79:50774
User Name: HHS\H6-08$
Session ID: 0xFFFFFFFFFFFFFFFF
Status: Insufficient server resources exist to complete the request. (0xC0000205)

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled

and

SMB Server event ID 1020
File system operation has taken longer than expected.

Client Name: \\192.168.105.97
Client Address: 192.168.105.97:49571
User Name: HHS\12J.Champion
Session ID: 0x2C07B40004A5
Share Name: \\*\Subjects
File Name: 
Command: 5
Duration (in milliseconds): 176784
Warning Threshold (in milliseconds): 120000

Guidance:

The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

I have checked the underlying disk/iscsi/network hyper-v cluster for any other errors or issues, but as far as I can tell everything is fine. 

Is it possible that something else is left over from the NOD antivirus installation?  

Looking for suggestions on how to troubleshoot this further.

Thanks

Hi,

I was wondering whether you can allow users to access the target of an initial replication while the replication is still going. If so, how will dfs cope with changes and deletions on that share? Will it use USNJournal? What's the risk of a journal wrap destroying data if a lot of changes are made while initial replication is running?

Also, if something should go wrong with that initial replication how would one recover from that failure? I assume just rebuilding  the replication group will make a huge mess in such case?

Thanks in advance for your response!

S.

MCP/MCSA/MCTS/MCITP

Hi,

After run below mentioned two commands, I am able to schedule on backup Job but when I am trying to add another backup job then the same error is coming. Plz. reply with the solutions.

Cacls.exe C:\Windows\Tasks /E /G "NT AUTHORITY\SYSTEM":F

Cacls.exe C:\Windows\Tasks /E /G BUILTIN\Administrators:F

Problem with files on deduplicated volume on Windows Server 2012.

UsingWindows ServerBatskupI get an error0x80070570. Copying files manually gives me the same error. All Disks are in RAID1+0. CHKDSK and Raid utility says all is fine, no error.

PS C:\Windows\system32> Get-DedupMetadata
ПРЕДУПРЕЖДЕНИЕ: MSFT_DedupVolumeMetadata.Volume='D:' - На этом томе следует выполнить задание очистки для дедупликации д
анных.

Volume                         : D:
VolumeId                       :\\?\Volume{8623b06d-1e0f-11e3-93e7-806e6f6e6963}\
StoreId                        : {C4632BE8-34CE-4E35-9750-25869398BB5B}
DataChunkCount                 : 4321005
DataContainerCount             : 359
DataChunkAverageSize           : 65.44 KB
DataChunkMedianSize            : 0 B
DataStoreUncompactedFreespace  : 0 B
StreamMapChunkCount            : 870025
StreamMapContainerCount        : 16
StreamMapAverageDataChunkCount :
StreamMapMedianDataChunkCount  :
StreamMapMaxDataChunkCount     :
HotspotChunkCount              : 11941
HotspotContainerCount          : 2
HotspotMedianReferenceCount    :
CorruptionLogEntryCount        : 33281349
TotalChunkStoreSize            : 271.17 GB

It says I should do the cleanup job.

PS C:\Windows\system32> Start-DedupJob -Type Scrubbing -Volume D:
Start-DedupJob : MSFT_DedupVolume.Volume='D:' - HRESULT 0x8056533e, This job will not run at the scheduled
time because it requires more memory than is currently available.

Server has 20Gb free RAM. Logical disk size is 1,7TB, 990Gb of free space.

PS C:\Windows\system32> Get-DedupStatus |fl

Volume                             : D:
VolumeId                           :\\?\Volume{8623b06d-1e0f-11e3-93e7-806e6f6e6963}\
Capacity                           : 1.72 TB
FreeSpace                          : 978.61 GB
UsedSpace                          : 784.07 GB
UnoptimizedSize                    : 1.08 TB
SavedSpace                         : 321.99 GB
SavingsRate                        : 29 %
OptimizedFilesCount                : 819555
OptimizedFilesSize                 : 593.18 GB
OptimizedFilesSavingsRate          : 54 %
InPolicyFilesCount                 : 819538
InPolicyFilesSize                  : 587.46 GB
LastOptimizationTime               : 10.12.2013 18:45:19
LastOptimizationResult             : 0x00000000
LastOptimizationResultMessage      : The operation completed successfully.
LastGarbageCollectionTime          : 10.12.2013 7:01:36
LastGarbageCollectionResult        : 0x00000000
LastGarbageCollectionResultMessage : The operation completed successfully
LastScrubbingTime                  : 29.06.2013 8:18:06
LastScrubbingResult                : 0x00000000
LastScrubbingResultMessage         : The operation completed successfully

Start-DedupJob -Type Unoptimization -Volume D: stuck in 0%

PS C:\Windows\system32> Get-DedupJob |fl

Volume             : D:
VolumeId           : \\?\Volume{8623b06d-1e0f-11e3-93e7-806e6f6e6963}\
Type               : Unoptimization
ScheduleType       : Manual
StartTime          : 10.12.2013 21:53:57
Progress           : 0 %
State              : Running
Id                 : {88BD7549-632A-4330-BF86-8801DF6D07F6}
StopWhenSystemBusy : False
Memory             : 50 %
Priority           : Normal
ProcessId          : 4868
Full               : True
ReadOnly           : False

Is it a problem with deduplication? How to fix this? How can I restore the data?..

We have a software utility that we wrote and continue to maintain that performs deletion of files as one part of its functionality.  The utility needs to be able to delete any file or directory, regardless of the actual NTFS permissions, provided that the file / directory is not currently held open such that a call to CreateFileW() cannot open it exclusively for DELETE access.  To facilitate this, our utility enables the LSA privileges SE_BACKUP_NAME and SE_RESTORE_NAME and then calls CreateFileW() requesting DELETE access, no sharing, OPEN_EXISTING disposition, and specifying the flags FILE_FLAG_BACKUP_SEMANTICS and FILE_FLAG_DELETE_ON_CLOSE.  This ensures that backup semantics are used, thus allowing our enabled LSA privileges to be used to bypass NTFS permissions.  It should also be noticed that the file / directory name that is passed in to CreateFileW() is always an absolute path in either drive letter format or UNC format, and it always has the appropriate prefix applied [e.g. "\\?\" or "\\?\UNC\"] to permit the use of long names up to 32,000 Unicode wide characters in length.

This has been working successfully for many years, and even roaming user profiles can be deleted without first having to modify the NTFS permissions to make deletion of the files and directories possible.

Recently, it came to our attention that in certain customer environments where both Shadow Copies of Shared Folders is enabled and FSRM Directory Quotas are in use, that the deletion of files using this methodology is resulting in the quota utilization not being updated by the quota mini-filter driver.  However, deleting the file using the DEL command in CMD.EXE or performing a SHIFT-DELETE keystroke in the Windows Explorer [and acknowledging the permanent deletion prompt] results in deletion of the specified file with correct updating of the quota utilization.  This behavior, however, is only observed on Windows Server 2008 R2 [Enterprise] with patches applied through 4/1/2013.  Identical testing on Windows Server 2012 [Enterprise] with patches applied through 4/4/2013 does not result in manifestation of this problem.  If the Shadow Copies of Shared Folders is disabled and all previous shadow copies for the volume in question are thus deleted, then FSRM Quota utilization values are always updated correctly regardless of how the file is deleted.

I have performed extensive Google searching of the Internet and direct searching of Microsoft's Technical Support, TechNet and DeveloperNet web sites looking for information about this problem, and have not found anything at all except some old references to a problem on Windows Server 2003 R2 that had very similar symptoms.

I am interested in finding out if Microsoft or anybody else had encountered this problem, or if they can reproduce it.  Also, if there is a hot fix or some other patch available for Windows Server 2008 R2 that fixes this problem, I'd like to know how to obtain it as there doesn't seem to be a KB article in existence that refers to this problem or any such hot fix or patch.

TL;DR: Unable to map a network drive on one particular computer, except if circumventing DFS.

OK - So I have exhausted all my options in this matter, so all suggestions are welcome. 
Keep in mind the file system is DFS.

1. User has been set up the same as our other users in Active Directory.
2. Most network drives are connected via GPO. They are mapped via\\company.local\common\

3. The users' home folder is connected via setting in AD -> Profile -> Home folder -> 
Connect X: To \\company.local\homedir\username
4. When the user logs on, all network drives defined in GPO are mapped OK, but the X: which is defined via "Home folder" in AD, is not connected. When trying to map it manually, we get "Access denied".
5. If the user tries the complete path via Explorer: \\company.local\homedir\username - Error 0x80004005 Unspecified error occurs. We have googled this particular code but found nothing that applies to us.
6. If the user tries the complete path to the folder on the actual file server, circumventing DFS, the home folder is mapped OK.

Strange thing is: This only happens on this particular computer. If users logs on to another computer, in the same domain, receiving the same GPO etc. The X: is mapped fine via \\company.local\homedir\username
Also if another user logs on to the problematic computer they also cannot access their X: on \\company.local\homedir\username

So we tried updating the WLAN/LAN drivers to no avail. Might there be any settings on the network adapters that might cause this?

Kthxbai

I apologize for posting to the server area, but it is storage spaces related.

I had a drive lose power, degrade a storage space and then I plugged it back in.

The drive is physically fine, but now I cannot repair using the powershell cmdlets.

Is this in fact the same as having to replace a drive?  Do I now have to find a drive of the same size, retire the existing drive, plug in a new drive and rebuild?

If so, do I add the new drive first, then retire, then repair?

Does the repair kick off automatically, or do I have to issue a cmdlet?

The drive is largest drive in my pool and has important data on it.  Can I be sure the smaller pool drives now have all the parity data for the rebuild?