DFS vs DFS-R

I have read that it is possible to have DFS-R - replicating of folders -  without actually setting up a DFS name space.
Is that correct?
If correct, what would be gained or lost by doing the two in conjunction/separately?
I guess I'm asking is there any synergy between the two - is DFS-R better in some way if DFS is in place?  Is there a downside to DFS-R if DFS is in place? I understand the benefits of each on their own - just not sure what they bring to the table for
each other. 

Hi,
I would like to confirm what is the current situation? Have you resolved the problem?
If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • Error message when mapping to a network drive of a DFS share on Windows 7

    Hi,
    We are getting the following error when mapping to a network drive of a DFS share on Windows 7:
    “The mapped network drive could not be created because the following error has occurred:
    A specified logon session does not exist. It may already have been terminated."
    In our case, the user logs on his workstation using his regular domain account, then maps to the network DFS share using the service account of an application.
    There is a fix from Microsoft (MS KB968264). But this fix requires disabling the "Network access: Do not allow storage of credentials or .NET Passports for network authentication” property. This is against the Microsoft own best practices (Network access:
    “Do not allow storage of passwords and credentials for network authentication” should be set to
    ENABLED), and is NOT acceptable for us for obvious security reasons.
    Question: Does anyone know an alternative fix to this issue that does not introduce security risks?
    Thank you in advance!
    Mdjona

    Again I have tried this, but in my program if I try to save to the a drive when no disk is inserted, the JOptionPane i want to display is not coming up.
    the system prints out
    java.io.FileNotFoundException: A:\image.jpg <The device is not ready>
    If that makes any sense to you

  • Drive Map to DFS Folder Getting Lost

    We had a problem yesterday morning with every user (about a dozen) in one of our small branch offices being unable to access a certain network share.
    Their T: drive, which is the one they had a problem with, is mapped to this:
    \\domain.com\namespace\OfficeShare1
    which is a DFS folder that simply points to:
    \\2012FileServer\OfficeShare1
    That is a Server 2012 R2 server.
    This share is only a few weeks old, and has been working fine for them until today. We have other offices that have their own shares on the same server, and mapped to a DFS folder the same way, and those have been working OK (as far as I know).
    The PCs are all running Windows 7.
    Their S: drive is mapped to
    \\2003FileServer\CompanyShare
    which is a MS Server 2003 server. They had no problems with accessing this, ever.
    Going to Computer > Map network drive, I could see the label for \OfficeShare1 was still attached to T:, but the path was empty. The T: drive appeared in the Computer window, but was showing as disconnected, and double-clicking it would throw an error about
    the path being unavailable.
    Typing \\domain.com\namespace\OfficeShare1 in the address bar would cause the Computer window to hang before erroring-out. Thus, re-creating the drive map would not work.
    After trying that, a user could go to \\domain.com\namespace and that would work fine. From there, they could go to the \OfficeShare1 folder without any errors.
    If they then went back into Computer, their T: drive would again be working, without having to re-create the mapping.
    Also, even though users couldn't browse directly to \\domain.com\namespace\OfficeShare1,without first browsing \\domain.com\namespace, they could browse directly to \\2012FileServer\OfficeShare1.
    I've seen a few other users outside the aforementioned office who had the issue, but this is the first opportunity I've had to get more information on it before the client PC was rebooted. Some of those users who have had this issue, also have an X: drive,
    which is mapped to:
    \\domain.com\namespace\DeptShare1
    But this is a CIFS share. And like the share on the 2003 server, no user has experienced the issue with this share.
    It has only happened with the shares on the Server 2012 system. And it has been kinda rare (currently less than 75 users who could potentially experience it).
    All drives are mapped via Group Policy. Users do have a script they can run to re-create drive maps.
    It's probably some connectivity issue that causes the drive to get disconnected (wifi signal drops, VPN gets disconnected, etc). But I'm not sure why the problem persists after connectivity is restored, why the path disappears from the mapping, and why only
    with this one drive. The servers hosting those shares are all in the same subnet, same data center.
    I'm about to migrate about a share accessed by 500 users to this 2012 system, and I can't until I get this figured out. My hunch is that something in the Windows 7 client PC is getting... lost. It's only happening to drives that map to DFS folders in that namespace
    that point to shares on that 2012 server (no one has a drive that maps directly to the shares on that server). The share itself doesn't appear  to actually go offline or anything like that. And this morning is the first time I've seen it happen to multiple
    people at once.
    Weird.
    Any help is appreciated.
    Thanks!

    Hi,
    Is there any error message in the Event Log? Do you add more than one namespace server in the DFS namespace? Since the server hangs when you access the DFS link, you could refer to the article below to establish connectivity with the target computer and shared
    folder.
    Troubleshooting Dfs Problems
    http://technet.microsoft.com/en-us/library/cc962144.aspx
    Best Regards,
    Mandy
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • DFS replication stopped working and cannot be debugged because WMI repository cannot be accessed

    Hello,
    two days ago our DFS replication suddendly stopped working sometime around midnight local time. At least this is what our second domain controller is reporting. Event log is flooded with event id 5002 from DFSR. It is unclear what caused this sudden problem
    and even worse, how to solve it. First thing I tried was to perform propagation tests. According to propagation report none of them was successful. Creating an integrity report brought me to another problem: It fails with two errors. First it is unable to
    connect to the other DC. Second it is unable to access local WMI repository. This is true for both machines.
    First I tried to find information on possible problems with WMI. WMIdiag provided a lot of information. However, opinions I found on the net largely disagree whether output from WMIdiag is useful or not. Yet I tried to re-compile .mof files and rebuild the
    repository. So far, nothing changed. This is my output from WMIdiag:
    34309 13:02:46 (0) ** WMIDiag v2.1 started on Donnerstag, 22. Mai 2014 at 12:49.
    34310 13:02:46 (0) **
    34311 13:02:46 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    34312 13:02:46 (0) **
    34313 13:02:46 (0) ** This script is not supported under any Microsoft standard support program or service.
    34314 13:02:46 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    34315 13:02:46 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    34316 13:02:46 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    34317 13:02:46 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    34318 13:02:46 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    34319 13:02:46 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    34320 13:02:46 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    34321 13:02:46 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    34322 13:02:46 (0) ** of the possibility of such damages.
    34323 13:02:46 (0) **
    34324 13:02:46 (0) **
    34325 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34326 13:02:46 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    34327 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34328 13:02:46 (0) **
    34329 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34330 13:02:46 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'COM\ABCDEF' on computer 'DC2'.
    34331 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34332 13:02:46 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    34333 13:02:46 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
    34334 13:02:46 (0) ** - Shutdown on 01 April 2014 10:20:54 (GMT-0).
    34335 13:02:46 (0) **
    34336 13:02:46 (0) ** System drive: ....................................................................................................... C: (Datenträgernr. 0 Partitionsnr. 1).
    34337 13:02:46 (0) ** Drive type: ......................................................................................................... SCSI (Adaptec Array SCSI Disk Device).
    34338 13:02:46 (0) ** There are no missing WMI system files: .............................................................................. OK.
    34339 13:02:46 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    34340 13:02:46 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    34341 13:02:46 (0) ** AFTER running WMIDiag:
    34342 13:02:46 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
    34343 13:02:46 (0) ** - Disk free space on 'C:': .......................................................................................... 10665 MB.
    34344 13:02:46 (0) ** - INDEX.BTR, 4276224 bytes, 22.05.2014 12:52:30
    34345 13:02:46 (0) ** - MAPPING1.MAP, 67248 bytes, 22.05.2014 12:52:30
    34346 13:02:46 (0) ** - MAPPING2.MAP, 67168 bytes, 22.05.2014 12:48:33
    34347 13:02:46 (0) ** - OBJECTS.DATA, 23126016 bytes, 22.05.2014 12:52:30
    34348 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34349 13:02:46 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
    34350 13:02:46 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
    34351 13:02:46 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
    34352 13:02:46 (0) ** => This will prevent any WMI remote connectivity to this computer except
    34353 13:02:46 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
    34354 13:02:46 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
    34355 13:02:46 (0) ** - 'Windows Management Instrumentation (WMI-In)'
    34356 13:02:46 (0) ** - 'Windows Management Instrumentation (ASync-In)'
    34357 13:02:46 (0) ** Verify the reported status for each of these three inbound rules below.
    34358 13:02:46 (0) **
    34359 13:02:46 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
    34360 13:02:46 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
    34361 13:02:46 (0) ** - You can adjust the configuration by executing the following command:
    34362 13:02:46 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
    34363 13:02:46 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
    34364 13:02:46 (0) ** You can also enable each individual rule instead of activating the group rule.
    34365 13:02:46 (0) **
    34366 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34367 13:02:46 (0) ** DCOM Status: ........................................................................................................ OK.
    34368 13:02:46 (0) ** WMI registry setup: ................................................................................................. OK.
    34369 13:02:46 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    34370 13:02:46 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    34371 13:02:46 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    34372 13:02:46 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
    34373 13:02:46 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
    34374 13:02:46 (0) ** this can prevent the service/application to work as expected.
    34375 13:02:46 (0) **
    34376 13:02:46 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    34377 13:02:46 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    34378 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34379 13:02:46 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    34380 13:02:46 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    34381 13:02:46 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    34382 13:02:46 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    34383 13:02:46 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    34384 13:02:46 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    34385 13:02:46 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 1 WARNING(S)!
    34386 13:02:46 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1, replprov.dll
    34387 13:02:46 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
    34388 13:02:46 (0) ** This can be due to:
    34389 13:02:46 (0) ** - the de-installation of the software.
    34390 13:02:46 (0) ** - the deletion of some files.
    34391 13:02:46 (0) ** => If the software has been de-installed intentionally, then this information must be
    34392 13:02:46 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
    34393 13:02:46 (0) ** the provider registration data.
    34394 13:02:46 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1' DELETE'
    34395 13:02:46 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
    34396 13:02:46 (0) ** You can retrieve the missing file from:
    34397 13:02:46 (0) ** - A backup.
    34398 13:02:46 (0) ** - The Windows CD.
    34399 13:02:46 (0) ** - Another Windows installation using the same version and service pack level of the examined system.
    34400 13:02:46 (0) ** - The original CD or software package installing this WMI provider.
    34401 13:02:46 (0) **
    34402 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34403 13:02:46 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    34404 13:02:46 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    34405 13:02:46 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    34406 13:02:46 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    34407 13:02:46 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
    34408 13:02:46 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    34409 13:02:46 (0) **
    34410 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34411 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
    34412 13:02:46 (0) ** - REMOVED ACE:
    34413 13:02:46 (0) ** ACEType: &h0
    34414 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34415 13:02:46 (0) ** ACEFlags: &h0
    34416 13:02:46 (0) ** ACEMask: &h7
    34417 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34418 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34419 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34420 13:02:46 (0) **
    34421 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34422 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34423 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34424 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34425 13:02:46 (0) **
    34426 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34427 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
    34428 13:02:46 (0) ** - REMOVED ACE:
    34429 13:02:46 (0) ** ACEType: &h0
    34430 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34431 13:02:46 (0) ** ACEFlags: &h0
    34432 13:02:46 (0) ** ACEMask: &h7
    34433 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34434 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34435 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34436 13:02:46 (0) **
    34437 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34438 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34439 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34440 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34441 13:02:46 (0) **
    34442 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34443 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    34444 13:02:46 (0) ** - REMOVED ACE:
    34445 13:02:46 (0) ** ACEType: &h0
    34446 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34447 13:02:46 (0) ** ACEFlags: &h0
    34448 13:02:46 (0) ** ACEMask: &h7
    34449 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34450 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34451 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34452 13:02:46 (0) **
    34453 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34454 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34455 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34456 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34457 13:02:46 (0) **
    34458 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34459 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34460 13:02:46 (0) ** - REMOVED ACE:
    34461 13:02:46 (0) ** ACEType: &h0
    34462 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34463 13:02:46 (0) ** ACEFlags: &h0
    34464 13:02:46 (0) ** ACEMask: &h1F
    34465 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34466 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34467 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34468 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34469 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34470 13:02:46 (0) **
    34471 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34472 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34473 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34474 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34475 13:02:46 (0) **
    34476 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34477 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    34478 13:02:46 (0) ** - REMOVED ACE:
    34479 13:02:46 (0) ** ACEType: &h0
    34480 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34481 13:02:46 (0) ** ACEFlags: &h0
    34482 13:02:46 (0) ** ACEMask: &h1F
    34483 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34484 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34485 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34486 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34487 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34488 13:02:46 (0) **
    34489 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34490 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34491 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34492 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34493 13:02:46 (0) **
    34494 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34495 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
    34496 13:02:46 (0) ** - REMOVED ACE:
    34497 13:02:46 (0) ** ACEType: &h0
    34498 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34499 13:02:46 (0) ** ACEFlags: &h0
    34500 13:02:46 (0) ** ACEMask: &h1F
    34501 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34502 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34503 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34504 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34505 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34506 13:02:46 (0) **
    34507 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34508 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34509 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34510 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34511 13:02:46 (0) **
    34512 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34513 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34514 13:02:46 (0) ** - REMOVED ACE:
    34515 13:02:46 (0) ** ACEType: &h0
    34516 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34517 13:02:46 (0) ** ACEFlags: &h0
    34518 13:02:46 (0) ** ACEMask: &h1F
    34519 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34520 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34521 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34522 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34523 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34524 13:02:46 (0) **
    34525 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34526 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34527 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34528 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34529 13:02:46 (0) **
    34530 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34531 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
    34532 13:02:46 (0) ** - REMOVED ACE:
    34533 13:02:46 (0) ** ACEType: &h0
    34534 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34535 13:02:46 (0) ** ACEFlags: &h0
    34536 13:02:46 (0) ** ACEMask: &h1F
    34537 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34538 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34539 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34540 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34541 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34542 13:02:46 (0) **
    34543 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34544 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34545 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34546 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34547 13:02:46 (0) **
    34548 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34549 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    34550 13:02:46 (0) ** - REMOVED ACE:
    34551 13:02:46 (0) ** ACEType: &h0
    34552 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34553 13:02:46 (0) ** ACEFlags: &h0
    34554 13:02:46 (0) ** ACEMask: &hB
    34555 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34556 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34557 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34558 13:02:46 (0) **
    34559 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34560 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34561 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34562 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34563 13:02:46 (0) **
    34564 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34565 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34566 13:02:46 (0) ** - REMOVED ACE:
    34567 13:02:46 (0) ** ACEType: &h0
    34568 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34569 13:02:46 (0) ** ACEFlags: &h0
    34570 13:02:46 (0) ** ACEMask: &h1F
    34571 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34572 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34573 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34574 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34575 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34576 13:02:46 (0) **
    34577 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34578 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34579 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34580 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34581 13:02:46 (0) **
    34582 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34583 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    34584 13:02:46 (0) ** - REMOVED ACE:
    34585 13:02:46 (0) ** ACEType: &h0
    34586 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34587 13:02:46 (0) ** ACEFlags: &h0
    34588 13:02:46 (0) ** ACEMask: &h1F
    34589 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34590 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34591 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34592 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34593 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34594 13:02:46 (0) **
    34595 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34596 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34597 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34598 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34599 13:02:46 (0) **
    34600 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34601 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
    34602 13:02:46 (0) ** - REMOVED ACE:
    34603 13:02:46 (0) ** ACEType: &h0
    34604 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34605 13:02:46 (0) ** ACEFlags: &h0
    34606 13:02:46 (0) ** ACEMask: &h1F
    34607 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34608 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34609 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34610 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34611 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34612 13:02:46 (0) **
    34613 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34614 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34615 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34616 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34617 13:02:46 (0) **
    34618 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34619 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
    34620 13:02:46 (0) ** - REMOVED ACE:
    34621 13:02:46 (0) ** ACEType: &h0
    34622 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34623 13:02:46 (0) ** ACEFlags: &h0
    34624 13:02:46 (0) ** ACEMask: &h1F
    34625 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34626 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34627 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34628 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34629 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34630 13:02:46 (0) **
    34631 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34632 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34633 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34634 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34635 13:02:46 (0) **
    34636 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34637 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
    34638 13:02:46 (0) ** - REMOVED ACE:
    34639 13:02:46 (0) ** ACEType: &h0
    34640 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34641 13:02:46 (0) ** ACEFlags: &h0
    34642 13:02:46 (0) ** ACEMask: &h1F
    34643 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34644 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34645 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34646 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34647 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34648 13:02:46 (0) **
    34649 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34650 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34651 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34652 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34653 13:02:46 (0) **
    34654 13:02:46 (0) **
    34655 13:02:46 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    34656 13:02:46 (0) ** DCOM security error(s) detected: .................................................................................... 14.
    34657 13:02:46 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    34658 13:02:46 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    34659 13:02:46 (0) **
    34660 13:02:46 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    34661 13:02:46 (0) ** Overall WMI security status: ........................................................................................ OK.
    34662 13:02:46 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    34663 13:02:46 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
    34664 13:02:46 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    34665 13:02:46 (0) ** 'select * from MSFT_SCMEventLogEvent'
    34666 13:02:46 (0) **
    34667 13:02:46 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    34668 13:02:46 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    34669 13:02:46 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    34670 13:02:46 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    34671 13:02:46 (0) ** - ROOT/SERVICEMODEL.
    34672 13:02:46 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    34673 13:02:46 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    34674 13:02:46 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    34675 13:02:46 (0) ** i.e. 'WMIC.EXE /NODE:"ISWDC2" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    34676 13:02:46 (0) **
    34677 13:02:46 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    34678 13:02:46 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    34679 13:02:46 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
    34680 13:02:46 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34681 13:02:46 (0) ** MOF Registration: ''
    34682 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34683 13:02:46 (0) ** MOF Registration: ''
    34684 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34685 13:02:46 (0) ** MOF Registration: ''
    34686 13:02:46 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34687 13:02:46 (0) ** MOF Registration: ''
    34688 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34689 13:02:46 (0) ** MOF Registration: ''
    34690 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34691 13:02:46 (0) ** MOF Registration: ''
    34692 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34693 13:02:46 (0) ** MOF Registration: ''
    34694 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34695 13:02:46 (0) ** MOF Registration: ''
    34696 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34697 13:02:46 (0) ** MOF Registration: ''
    34698 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34699 13:02:46 (0) ** MOF Registration: ''
    34700 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34701 13:02:46 (0) ** MOF Registration: ''
    34702 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34703 13:02:46 (0) ** MOF Registration: ''
    34704 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34705 13:02:46 (0) ** MOF Registration: ''
    34706 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34707 13:02:46 (0) ** MOF Registration: ''
    34708 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34709 13:02:46 (0) ** MOF Registration: ''
    34710 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34711 13:02:46 (0) ** MOF Registration: ''
    34712 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34713 13:02:46 (0) ** MOF Registration: ''
    34714 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34715 13:02:46 (0) ** MOF Registration: ''
    34716 13:02:46 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34717 13:02:46 (0) ** MOF Registration: ''
    34718 13:02:46 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34719 13:02:46 (0) ** MOF Registration: ''
    34720 13:02:46 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34721 13:02:46 (0) ** MOF Registration: ''
    34722 13:02:46 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34723 13:02:46 (0) ** MOF Registration: ''
    34724 13:02:46 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34725 13:02:46 (0) ** MOF Registration: ''
    34726 13:02:46 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34727 13:02:46 (0) ** MOF Registration: ''
    34728 13:02:46 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34729 13:02:46 (0) ** MOF Registration: ''
    34730 13:02:46 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34731 13:02:46 (0) ** MOF Registration: ''
    34732 13:02:46 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34733 13:02:46 (0) ** MOF Registration: ''
    34734 13:02:46 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34735 13:02:46 (0) ** MOF Registration: ''
    34736 13:02:46 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34737 13:02:46 (0) ** MOF Registration: ''
    34738 13:02:46 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34739 13:02:46 (0) ** MOF Registration: ''
    34740 13:02:46 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34741 13:02:46 (0) ** MOF Registration: ''
    34742 13:02:46 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34743 13:02:46 (0) ** MOF Registration: ''
    34744 13:02:46 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    34745 13:02:46 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    34746 13:02:46 (0) ** You can refresh the WMI class provider buffer with the following command:
    34747 13:02:46 (0) **
    34748 13:02:46 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
    34749 13:02:46 (0) **
    34750 13:02:46 (0) ** WMI MOF representations: ............................................................................................ OK.
    34751 13:02:46 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    34752 13:02:46 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    34753 13:02:46 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    34754 13:02:46 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    34755 13:02:46 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34756 13:02:46 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34757 13:02:46 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    34758 13:02:46 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34759 13:02:46 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34760 13:02:46 (0) **
    34761 13:02:46 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    34762 13:02:46 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    34763 13:02:46 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    34764 13:02:46 (0) ** WMI static instances retrieved: ..................................................................................... 1822.
    34765 13:02:46 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    34766 13:02:46 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    34767 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34768 13:02:46 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    34769 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
    34770 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
    34771 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
    34772 13:02:46 (0) **
    34773 13:02:46 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    34774 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
    34775 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
    34776 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
    34777 13:02:46 (0) **
    34778 13:02:46 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    34779 13:02:46 (0) ** => This error is typically a WMI error. This WMI error is due to:
    34780 13:02:46 (0) ** - a missing WMI class definition or object.
    34781 13:02:46 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    34782 13:02:46 (0) ** You can correct the missing class definitions by:
    34783 13:02:46 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    34784 13:02:46 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    34785 13:02:46 (0) ** (This list can be built on a similar and working WMI Windows installation)
    34786 13:02:46 (0) ** The following command line must be used:
    34787 13:02:46 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
    34788 13:02:46 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    34789 13:02:46 (0) ** with WMI by starting the ADAP process.
    34790 13:02:46 (0) ** - a WMI repository corruption.
    34791 13:02:46 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    34792 13:02:46 (0) ** to validate the WMI repository operations.
    34793 13:02:46 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    34794 13:02:46 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    34795 13:02:46 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
    34796 13:02:46 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    34797 13:02:46 (0) ** the WMI repository must be reconstructed.
    34798 13:02:46 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    34799 13:02:46 (0) ** otherwise some applications may fail after the reconstruction.
    34800 13:02:46 (0) ** This can be achieved with the following command:
    34801 13:02:46 (0) ** i.e. 'WMIDiag ShowMOFErrors'
    34802 13:02:46 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    34803 13:02:46 (0) ** ALL fixes previously mentioned.
    34804 13:02:46 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    34805 13:02:46 (0) **
    34806 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34807 13:02:46 (0) ** WMI Registry key setup: ............................................................................................. OK.
    34808 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34809 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34810 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34811 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34812 13:02:46 (0) **
    34813 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34814 13:02:46 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    34815 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34816 13:02:46 (0) **
    34817 13:02:46 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ABCDEF\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_ISWDC2_2014.05.22_12.49.13.LOG' for details.
    34818 13:02:46 (0) **
    34819 13:02:46 (0) ** WMIDiag v2.1 ended on Donnerstag, 22. Mai 2014 at 13:02 (W:89 E:52 S:1).
    There are a lot of error in the report and I don't know, whether they are relevant or how to solve them. To my current knowledge, I need to solve at least some of them so that I can access the local WMI repository again and get replication back working.
    But after hours of research I am stuck. Any hints are greatly appreciated.
    Regards,
    Oliver

    I don't know why, but soon after posting this, I found a solution to the problem. The WMI part was solved in this thread:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
    The relevant portion is this:
    Open a CMD prompt in %windir%\system32\wbem
    mofcomp dfsrprovs.mof
    net stop winmgmt
    net start winmgmt
    net start iphlpsvc
    net stop dfsr
    net start dfsr
    I don't know why recompiling of all mof did not solve the problem, but the solution above did. Restarting the DCs solved the communication issue. I don't know why the primary DC forgot about the WMI DFS provider or why communication failed. However, it is
    working again, it seems.

  • Excel 2010 "Open" dialog box slow over DFS share

    Hi everyone,
    We're having some issues with clients using Windows XP and Office 2010. We have recently migrated from some Novell OES file server to a Win 2008R2 file server with DFS. When the users try to open any file from this new FS directly from Excel's "Open
    file" dialog box, when they "surf" through folders in this new fs, it takes aprox. 45sec~1min to populate folders. It doesn't occur if users search files using Windows Explorer, it only occurs directly from Office apps. Neither occurs in PCs
    using Windows 7.
    Thanks in advance!
    Matias

    Hi,
    The issue may be caused by the SMB. As far as I know, Windows Xp supports SMBv1 and the Windows server 2008 R2 supports SMBv2. Thus, I recommend we try to disable SMBv2 in Windows server 2008 R2 to test:
    To enable or disable SMBv2 on the SMB server, configure the following registry key:
    Registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    Registry entry:  SMB2
    REG_DWORD: 0 = Disabled
    REG_DWORD: 1 = Enabled
    Default: 1 = Enabled
    http://support.microsoft.com/kb/2696547/en-us
    Note: Backup the registry key before you modify.
    Regards,
    George Zhao
    TechNet Community Support

  • DFS Folder Target to Samba Share not working

    Hello folks,
    I'm on Server 2012 R2. I'm using a DFS Namespace that is configured as standalone server (i.e. not a domain-based namespace). The Namespace is the IP address of the server. I have also tried this with the hostname of the server and I get the same results.
    Here's my problem:
    I've created a folder target within DFS that points to a samba share on a linux-based NAS. The samba share is a 'cloud storage' share hosted by my server host, so I'm not entirely sure what specific technology it is. It does not have a public ACL - it requires
    authentication and I cannot change that. I can connect to the Namespace fine from other servers. However, when I try to open the folder target, it tells me "Logon failure: unknown user name or bad password". Then, if I right-click the folder, select
    Properties then the DFS tab, I see that the path is Active. If I click Check Status, I get Okay, and when I exit, the folder is now navigable and I have no problems browsing the folders. Sometimes when I close Explorer, the share will still be accessible when
    I reopen Explorer and browse to it, but most of the time when I close and reopen, the same error is displayed and I have to Check Status again to regain access. If I logout of the session, log back in and try again, it always gives me the error until I Check
    Status again.
    The idea is to access this share from multiple instances of IIS, so obviously requiring user intervention is not going to be suitable. I have added a local user to the DFS server that matches the valid credentials on the samba share, and I've also added
    them to all the servers trying to use this share. I've confirmed that all servers can browse directly to the share. I do notice that when I browse directly to the samba share after having not used it for some time (30 minutes or one hour), it takes longer
    than expected to open - maybe 10 seconds. Could this lag be causing the issue? There are no errors or warnings in the logs on the DFS server. Any ideas what this could be? Have I missed something? Massive thanks for any guidance!

    Hi,
    Thanks for your posting.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Unable to mount dfs volume from Windows Server 2008 R2

    I am trying to use Finder|Go|Connect to Server to connect to a DFS volume shared by a Windows Server 2008 R2 machine.  I get the following errors:
    A dialog box that says, "There was a problem connecting to the server "server name".  Contact your system administrator for more information"
    Messages in the log:
    PM kernel: smb_ntstatus_error_to_errno: Couldn't map ntstatus (0xc0000225) to errno returning EIO
    PM NetAuthSysAgent: checkForDfsReferral: mounting dfs url failed , syserr = Input/output error
    PM NetAuthSysAgent: smb_mount: mount failed to <server name>, syserr = Input/output error
    I've seen a reference to this article (https://discussions.apple.com/thread/3258472) to fix similar problems but that seems only to apply to Mac-based servers not Windows servers.
    I called AppleCare but they said they are unable to troubleshoot a problem originating on a Windows Server. 
    The Mac is running 10.7.4 but the problem happens on 10.7.3 as well.
    I can connect to non-DFS volumes from other Windows Servers with no issue. 

    After some more digging around I found out that it works when using the cifs: prefix instead of the smb: prefix in Finder|Go|Connect to Server. 
    So instead of using the name smb://servername.company.com I use the name cifs://servername.company.com. 

  • Lion 10.7.2 DFS share access issue

    hi
    i have a macbook air running 10.7.2 and we have a DFS file server running windows 2008 r2
    our name space is domain based and i can access the file server using \\domain.com\uk\data and \\domain\uk\home\xxx (where xxx is the username)
    the first is the shared data drive and the 2nd is the users home drive
    all works beautifully when i am connected via the ethernet. as soon as i move onto the internal wifi (sits on the same network as the ethernet lan and has full access to all network resource, our windows 7 laptops can access all shares just fine) i can all of a sudden no longer access the DFS share \\accel.com\uk\data
    it either says it cannot find it or a username and password box comes up (i am using centrify to leverage our AD user accounts on our mac's) when i enter my username and password it does not accept it. I have the same issue when i am outside of the office and vpn's in.
    this evening i discovered that i have no problems accessing our DFS share if i enter \\domain.com\uk and i am presented with the folder UK on my dekstop and when i click on it i can see the DATA and HOME drive subfolder
    when i now go to the finder and click on connect to server SMB://domain.com/uk/home/xxx it connects fine
    so it seems that the /uk/ bit of the DFS path is confusing the mac client when not connected via the ethernet lan cable.
    i have tried to mount via the cli but it comes up with no route to host and the console log displays something similar
    at least i have a work around now but does anyone know if this is an issue with my name space setup or whether this is a bug (i presume bug as windows 7 clients have no issue with this namespace but i am not taking anything for granted :-) )
    thank you
    ps i found this post but it is slightly different to the issue i am having https://discussions.apple.com/message/16187498#16187498

    The issue has previously hit Apple TV owners. I think people came to the conclusion that it was a HDMI handshake problem. Basically the process where the device and TV greet each other, make up some rules about communicationg and what their secret key is and so on.
    I haven't tried this yet, but my local service center says that basically I can do one of two things:
    - Downgrade to 10.7 and then download the 10.7.1 update from Apples website. To do this without having a Mac OS X Lion disc, you can hold down CMD + R when the computer boots to be able to access the recovery partition on newer Macs that come without the OS disc.
    or..
    - Put something in between the computer and TV. For example, if you're using an amplifier as a part of your home theather set up, this will probably work. The service guy said he has his Mini connected to the amplifier, which in turn is connected to speakers and a projector. The inverted colors still appear, but only once per night (i.e. after the first problem is reset by resetting the link then it's fine).
    For now, I'll do my little dance of changing the source on the TV from HDMI 1 to HDMI 2 and then back again to reset the link... But, I'll probably try downgrading in a few days.

  • Multiple Forest DNS queries, and DFS

    Setup:
    2 physical servers hosting several virtual machines with 3 forests (domains) and 3 subnets.  The physical server has 4 NICs, each forest/subnets has its own dedicated NIC via virtual switch (so 1 NIC is empty).  Each NIC connects to a switch to
    allow workstations and other devices to connect to their proper forest/subnet directly.  These switches then connect to the sonicwall (firewall/router) in an individual port.  Each port has proper subnet defined in it.
    The 3 forests are c.com, l.lan, and w.web named.  c.com and l.lan use a 10.x.x.x/255.255.0.0 subnet.  w.web uses 192.168.x.x/255.255.0.0 subnet.  There are no trusts setup.
    I can ping from one forest/subnet to the other using IP address without issue so the IP routes are fine.  I can ping via FQDN without issue if I setup a forwarder, conditional forwarder, or stub zone.  Sometimes using just the forwarder, FQDN does
    NOT resolve.  Conditional and Stub seems to resolve always. 
    I can get c.com and w.web to resolve single-name (host name) addresses, but at the moment (transitioning) they are on the same subnet.  From some research, I can use single-name resolution if I setup a GlobalNameZone as well, which I might need to do.
    So my question is which is best practice and most reliable way to setup these different forests and subnets to perform DNS resolution?  I tried forwarders, but it wasn't always reliable.  I suspected caching as an issue, but after a flush, a FQDN
    would sometimes resolve and sometimes not.  Conditional and Stub seem to work okay, but I'm not sure about what's best.
    I've spent most of the day researching this, and nothing was every really definitive and sometimes even contradictory.  Previously the DNS Forwarders worked fine for us, but that was on the same subnet.  Differing subnets seems to break the internal-to-internal
    forwarding.
    Additionally the w.web domain has a domain level DFS.  Neither of the other forests can access it via the
    \\w.web\data address.  Though they can access it if I point them directly to the server hosting the DFS namespace.

    Windows Server doesn't work well with DNS Search Suffixes defined in DHCP scopes from what I read.
    http://technet.microsoft.com/en-us/library/dd572752(v=office.13).aspx
    Details how to set it up on Windows Server DHCP
    http://social.technet.microsoft.com/Forums/en-US/2eed4d4f-8d1b-4989-ac49-d95e08b7d54a/dhcp-dns-suffix-search-list-supported?forum=winserverNIS
    Details how Windows Server does not support it though.
    http://technet.microsoft.com/en-us/library/bb847901(v=exchg.150).aspx
    Details how to use Group Policy to deploy it.
    How I fixed this:
    1) Open Group Policy for the domain.
    2) Edit the "Default Domain Policy" to include DNS Suffix search for current domain and all other domains.
    3) Set normal forwarders on domain's DNS servers.
    4) Repeat on all domain.
    This partially fixed my problem.  Things were resolving more reliably, but there would be a failure once in a while as well.  I corrected this by adding a conditional forwarder along with the normal forwarder.
    Now I get full resolution of all items.  Additionally, I do not have to use the FQDN for my machines.  Just hostname resolves just fine.  HOWEVER I would suggest to anyone setting up machines to use FQDN where possible, don't be lazy. 
    This means I will not have to setup a GlobalName zone either.  Though I may do it for the experience.
    Another problem though is this only works on Windows machines.  Mobile phones (such as Android and iPhone) and other such devices will not know about the DNS Suffix search.  Fortunately most of those devices required the internet FQDN for services
    to work anyway, and when behind the firewall via WiFi or like, they'll be able to still resolve the internet FQDN of devices since we're using a split-brain DNS for that domain.

  • One folder inside a DFS share not showing on some computers

    This is a really odd one, here is my config
    Server1\share1
    server2\share1
    and recently added
    server3\share1
    server 1 and 3 are in the same site, and server 2 is in a separate site
    I have recently added server3\share1 to the site, but I am forcing server1 as the first referral in DFS
    now here is my issue:
    I have \\company\dfs\share1 that points to share1 in each of the servers
    I have some folders:
    \\company\dfs\share1\departmet\
    \\company\dfs\share1\users\
    \\company\dfs\share1\departmet\folder1
    \\company\dfs\share1\departmet\folder2
    \\company\dfs\share1\departmet\folder3
    now on some PC's folder1 appears to be empty when server1 set set as the active DFS referal, but all other folders and files under share1 will still be populated, only the files under folder1 seem to be gone, if I change the DFS referral to another server,
    the files will appear, and if i look at the server share path, the files are there and replicating as expected, so nothing is actually missing
    and this only happens on some PC's not all, and only to folder1, everything else works as normal
    I added server3 about 3 weeks ago, but this issue has only just occurred, so may not be related, but before server3 was added there were no other options for DFS referrals this site, and i have only ever seed this sort of thing happen when there are multiple
    DFS referrals to choose form
    can anyone shed some light on this?

    Hi,
    It seems that you enable Access Based Enumeration on the DFS namespace. When users on some PC's did not have permission to access the folder 1 on the server1, the folder 1 appears to be empty when the server1 is set as the active DFS referral. You could give
    the users full control permissions to access the folder1 on the server1 to check if the issue still exists.
    Using ABE with DFS
    http://blogs.technet.com/b/askds/archive/2011/01/25/using-abe-with-dfs.aspx
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Is It Possible to Add a Fileserver to a DFS Replication Group Without Connectivity to FSMO Roles Holder DC But Connectivity to Site DC???

    I apologize in advance for the rambling novella, but I tried to include as many details ahead of time as I could.
    I guess like most issues, this one's been evolving for a while, it started out with us trying to add a new member 
    to a replication group that's on a subnet without connectivity to the FSMO roles holder. I'll try to describe the 
    layout as best as I can up front.
    The AD only has one domain & both the forest & domain are at 2008R2 function level. We've got two sites defined in 
    Sites & Services, Site A is an off-site datacenter with one associated subnet & Site B with 6 associated subnets, A-F. 
    The two sites are connected by a WAN link from a cable provider. Subnets E & F at Site B have no connectivity to Site A 
    across that WAN, only what's available through the front side of the datacenter through the public Internet. The network 
    engineering group involved refuses to route that WAN traffic to those two subnets & we've got no recourse against that 
    decision; so I'm trying to find a way to accomplish this without that if possible.
    The FSMO roles holder is located at Site A. I know that I can define a Site C, add Subnets E & F to that site, & then 
    configure an SMTP site link between Sites A & C, but that only handles AD replication, correct? That still wouldn't allow me, for example, 
    to enumerate DFS namespaces from subnets E & F, or to add a fileserver on either of those subnets as a member to an existing
    DFS replication group, right? Also, root scalability is enabled on all the namespace shares.
    Is there a way to accomplish both of these things without transferring the FSMO roles from the original DC at Site A to, say, 
    the bridgehead DC at Site B? 
    When the infrastructure was originally setup by a former analyst, the topology was much more simple & everything was left
    under the Default First Site & no sites/subnets were setup until fairly recently to resolve authentication issues on 
    Subnets E & F... I bring this up just to say, the FSMO roles holder has held them throughout the build out & addition of 
    all sorts of systems & I'm honestly not sure what, if anything, the transfer of those roles will break. 
    I definitely don't claim to be an expert in any of this, I'll be the first to say that I'm a work-in-progress on this AD design stuff, 
    I'm all for R'ing the FM, but frankly I'm dragging bottom at this point in finding the right FM. I've been digging around
    on Google, forums, & TechNet for the past week or so as this has evolved, but no resolution yet. 
    On VMs & machines on subnets E & F when I go to DFS Management -> Namespace -> Add Namespaces to Display..., none show up 
    automatically & when I click Show Namespaces, after a few seconds I get "The namespaces on DOMAIN cannot be enumerated. The 
    specified domain either does not exist or could not be contacted". If I run a dfsutil /pktinfo, nothing shows except \sysvol 
    but I can access the domain-based DFS shares through Windows Explorer with the UNC path \\DOMAIN-FQDN\Share-Name then when 
    I run a dfsutil /pktinfo it shows all the shares that I've accessed so far.
    So either I'm doing something wrong, or, for some random large, multinational company, every sunbet & fileserver one wants 
    to add to a DFS Namespace has to be able to contact the FSMO roles holder? Or, are those ADs broken down with a child domain 
    for each Site & a FSMO roles holder for that child domain is located in each site?

    Hi,
    A DC in siteB should helpful. I still not see any article mentioned that a DFS client have to connect to PDC every time trying to access a DFS domain based namespace.
    Please see following article. I pasted a part of it below:
    http://technet.microsoft.com/en-us/library/cc782417(v=ws.10).aspx
    Domain controllers play numerous roles in DFS:
    Domain controllers store DFS metadata in Active Directory about domain-based namespaces. DFS metadata consists of information about entire namespace, including the root, root targets, links, link targets, and settings. By default,root servers
    that host domain-based namespaces periodically poll the domain controller acting as the primary domain controller (PDC) emulator master to obtain an updated version of the DFS metadata and store this metadata in memory.
    So Other DC needs to connect PDC for an updated metadata.
    Whenever an administrator makes a change to a domain-based namespace, the
    change is made on the domain controller acting as the PDC emulator master and is then replicated (via Active Directory replication) to other domain controllers in the domain.
    Domain Name Referral Cache
    A domain name referral contains the NetBIOS and DNS names of the local domain, all trusted domains in the forest, and domains in trusted forests. A
    DFS client requests a domain name referral from a domain controller to determine the domains in which the clients can access domain-based namespaces.
    Domain Controller Referral Cache
    A domain controller referral contains the NetBIOS and DNS names of the domain controllers for the list of domains it has cached. A DFS client requests a domain controller referral from a domain controller (in the client’s domain)
    to determine which domain controllers can provide a referral for a domain-based namespace.
    Domain-based Root Referral Cache
    The domain-based root referrals in this memory cache do not store targets in any particular order. The targets are sorted according to the target selection method only when requested from the client. Also, these referrals are based on DFS metadata stored
    on the local domain controller, not the PDC emulator master.
    Thus it seems to be acceptable to have a disconnect between sites shortly when cache is still working on siteB.
    If you have any feedback on our support, please send to [email protected].

  • VSS on DFS Server

    We have two Physical Windows 2012 R2 Storage Edition configured as DFS.
    Server B is read only and nobody can access it, all the clients conntect to server A.
    On both server we have activated VSS
    We have 6 TB of shared data on the server.
    One share is very large 3TB and its staging area is 1 TB large.
    In DFS event log I see 4202 error for this share.
    VSS are scheduled at 10 am and 15 pm and stored on a different disk partition 1,5 TB large.
    When VSS start and for an hour long server A:
    - stop responding to user interfaces
    - windows 2003, 2003 R2, xp client can't connect anymore to the shares
    - windows 2008, vista or higher access to share is very slow
    Any ideas?

    Hi,
    Sorry for the delay.
    If you can access the shared folder using IP address, you could enable NetBIOS over TCP/IP on server to see if the issue still exists. 
    For more detailed information, please see:
    Error : No network provider accepted the given network path" when trying to access server via UNC
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/5c21fd13-41d7-452e-a9c7-8dc58d12c5b5/error-no-network-provider-accepted-the-given-network-path-when-trying-to-access-server-via-unc?forum=winserverfiles
    Best Regards,
    Mandy
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • BSOD on Server 2012 running dfs namespace and dfs replication roles with deduplication

    Hello,
    I have recently setup 2 dfsn & dfsr servers, both 2012 one physical the other virtual.
    The idea is to have one server as primary and the other as a failover \ DR.
    The primary server is virtual and connects via mpio \ iscsi to a dell san, using the provided dell DSM Drivers.
    The secondary server is physical with local disk for storage.
    I copy files to a namespace setup to always prefer the primary server, these files are then replicated across to the secondary.
    I have also turned on deduplication on both servers to get the most out of the available storage.
    This has been working well for 6 months or so, there have however been 2-3 occasions where the primary virtual server has crashed and blue screened causing the DFSR database to undergo a full consistency check.
    The bug check errors i have managed to extract from the Memory.dmp and mini dump are as follows:
    *                        Bugcheck Analysis                                   
    REFERENCE_BY_POINTER (18)
    Arguments:
    Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
    Arg2: fffffa80379a3070, Object whose reference count is being lowered
    Arg3: 0000000000000002, Reserved
    Arg4: ffffffffffffffff, Reserved
        The reference count of an object is illegal for the current state of the object.
        Each time a driver uses a pointer to an object the driver calls a kernel routine
        to increment the reference count of the object. When the driver is done with the
        pointer the driver calls another kernel routine to decrement the reference count.
        Drivers must match calls to the increment and decrement routines. This bugcheck
        can occur because an object's reference count goes to zero while there are still
        open handles to the object, in which case the fourth parameter indicates the number
        of opened handles. It may also occur when the object?s reference count drops below zero
        whether or not there are open handles to the object, and in that case the fourth parameter
        contains the actual value of the pointer references count.
    Debugging Details:
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x18
    PROCESS_NAME:  dfsrs.exe
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff800999ee0d7 to fffff8009985a440
    STACK_TEXT:  
    fffff880`0bf3fb48 fffff800`999ee0d7 : 00000000`00000018 00000000`00000000 fffffa80`379a3070 00000000`00000002 : nt!KeBugCheckEx
    fffff880`0bf3fb50 fffff800`99c33529 : fffffa80`379a3070 fffff8a0`0244adc0 00000000`000017e4 0000001b`930b60d8 : nt! ?? ::FNODOBFM::`string'+0x38605
    fffff880`0bf3fb90 fffff800`99859453 : fffffa80`4063db00 fffffa80`4063db00 fffff880`0bf3fcc0 00000000`00000001 : nt!NtClose+0x239
    fffff880`0bf3fc40 000007ff`5e8d2cda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    0000001b`9069f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`5e8d2cda
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+38605
    fffff800`999ee0d7 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+38605
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
    IMAGE_VERSION:  6.2.9200.16628
    BUCKET_ID_FUNC_OFFSET:  38605
    FAILURE_BUCKET_ID:  0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_
    BUCKET_ID:  0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x18_over_dereference_nt!_??_::fnodobfm::_string_
    FAILURE_ID_HASH:  {eaf19261-0688-f327-a17d-6f7960ac4ebd}
    Followup: MachineOwner
    rax=0000000000000000 rbx=ffffffffffffffff rcx=0000000000000018
    rdx=0000000000000000 rsi=fffffa80379a3070 rdi=00000000fffc000c
    rip=fffff8009985a440 rsp=fffff8800bf3fb48 rbp=fffffa80379a3040
     r8=fffffa80379a3070  r9=0000000000000002 r10=fffffa8030d89190
    r11=fffffa804063db00 r12=00000000000017e4 r13=0000000000000000
    r14=fffff8a00a548f90 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
    nt!KeBugCheckEx:
    fffff800`9985a440 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`0bf3fb50=0000000000000018
    Child-SP          RetAddr           : Args to Child                                                          
    : Call Site
    fffff880`0bf3fb48 fffff800`999ee0d7 : 00000000`00000018 00000000`00000000 fffffa80`379a3070 00000000`00000002 : nt!KeBugCheckEx
    fffff880`0bf3fb50 fffff800`99c33529 : fffffa80`379a3070 fffff8a0`0244adc0 00000000`000017e4 0000001b`930b60d8 : nt! ?? ::FNODOBFM::`string'+0x38605
    fffff880`0bf3fb90 fffff800`99859453 : fffffa80`4063db00 fffffa80`4063db00 fffff880`0bf3fcc0 00000000`00000001 : nt!NtClose+0x239
    fffff880`0bf3fc40 000007ff`5e8d2cda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0bf3fc40)
    0000001b`9069f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`5e8d2cda
    start             end                 module name
    fffff800`987b1000 fffff800`987ba000   kd       kd.dll       Thu Jul 26 03:30:34 2012 (5010ABCA)
    fffff800`99800000 fffff800`99f4c000   nt       ntkrnlmp.exe Sat Jun 01 04:13:17 2013 (51A966CD)
    fffff800`99f4c000 fffff800`99fb8000   hal      hal.dll      Wed Oct 24 04:03:21 2012 (50875A79)
    fffff880`00a00000 fffff880`00a34000   ataport  ataport.SYS  Thu Jul 26 03:29:04 2012 (5010AB70)
    fffff880`00a34000 fffff880`00a51000   lsi_sas  lsi_sas.sys  Fri May 11 20:40:21 2012 (4FAD6B25)
    fffff880`00a51000 fffff880`00a5e000   serenum  serenum.sys  Thu Jul 26 03:30:13 2012 (5010ABB5)
    fffff880`00a5e000 fffff880`00a6c000   fdc      fdc.sys      Thu Jul 26 03:30:15 2012 (5010ABB7)
    fffff880`00a7b000 fffff880`00adb000   volmgrx  volmgrx.sys  Thu Jul 26 03:29:59 2012 (5010ABA7)
    fffff880`00adb000 fffff880`00ae4000   intelide intelide.sys Thu Jul 26 03:29:52 2012 (5010ABA0)
    fffff880`00ae4000 fffff880`00af3000   PCIIDEX  PCIIDEX.SYS  Thu Jul 26 03:29:09 2012 (5010AB75)
    fffff880`00af3000 fffff880`00b56000   md3dsm   md3dsm.sys   Wed Aug 22 22:14:46 2012 (50354BC6)
    fffff880`00b56000 fffff880`00b87000   msdsm    msdsm.sys    Sat Oct 05 04:32:09 2013 (524F8839)
    fffff880`00b87000 fffff880`00ba0000   vmci     vmci.sys     Tue May 01 02:14:27 2012 (4F9F38F3)
    fffff880`00ba0000 fffff880`00bb5000   vsock    vsock.sys    Fri Aug 30 20:25:34 2013 (5220F1AE)
    fffff880`00bb5000 fffff880`00bcf000   mountmgr mountmgr.sys Thu Jul 26 03:29:33 2012 (5010AB8D)
    fffff880`00bcf000 fffff880`00bd9000   atapi    atapi.sys    Thu Jul 26 03:30:33 2012 (5010ABC9)
    fffff880`00bd9000 fffff880`00bf0000   vmxnet3n61x64 vmxnet3n61x64.sys Fri Sep 27 10:40:11 2013 (5245527B)
    fffff880`00bf0000 fffff880`00bfa000   pnpmem   pnpmem.sys   Thu Jul 26 03:30:11 2012 (5010ABB3)
    fffff880`00c40000 fffff880`00c9f000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Thu Jul 26 03:30:12 2012 (5010ABB4)
    fffff880`00c9f000 fffff880`00cfb000   CLFS     CLFS.SYS     Thu Jul 26 03:29:39 2012 (5010AB93)
    fffff880`00cfb000 fffff880`00d1e000   tm       tm.sys       Thu Jul 26 03:29:01 2012 (5010AB6D)
    fffff880`00d1e000 fffff880`00d33000   PSHED    PSHED.dll    Thu Jul 26 05:53:53 2012 (5010CD61)
    fffff880`00d33000 fffff880`00d3d000   BOOTVID  BOOTVID.dll  Thu Jul 26 03:30:22 2012 (5010ABBE)
    fffff880`00d3d000 fffff880`00dbc000   CI       CI.dll       Thu Mar 28 03:30:42 2013 (5153B962)
    fffff880`00dbc000 fffff880`00de1000   rasl2tp  rasl2tp.sys  Thu Jul 26 03:23:16 2012 (5010AA14)
    fffff880`00e00000 fffff880`00e49000   spaceport spaceport.sys Sat Oct 05 04:32:08 2013 (524F8838)
    fffff880`00e49000 fffff880`00e61000   volmgr   volmgr.sys   Thu Jul 26 03:29:22 2012 (5010AB82)
    fffff880`00e61000 fffff880`00ea9000   vm3dmp   vm3dmp.sys   Wed Oct 09 05:25:53 2013 (5254DAD1)
    fffff880`00eb5000 fffff880`00f41000   cng      cng.sys      Thu Oct 11 06:17:34 2012 (5076566E)
    fffff880`00f41000 fffff880`00f5b000   raspppoe raspppoe.sys Thu Jul 26 03:24:55 2012 (5010AA77)
    fffff880`00f5c000 fffff880`00f99000   mpio     mpio.sys     Sat Sep 28 04:37:24 2013 (52464EF4)
    fffff880`00f99000 fffff880`00fd3000   md3utm   md3utm.sys   Wed Aug 22 22:14:56 2012 (50354BD0)
    fffff880`00fd3000 fffff880`00fef000   intelppm intelppm.sys Tue Nov 06 03:55:02 2012 (50988A16)
    fffff880`01000000 fffff880`0106d000   ACPI     ACPI.sys     Thu Sep 20 07:09:16 2012 (505AB30C)
    fffff880`01075000 fffff880`010d8000   msrpc    msrpc.sys    Thu Jul 26 03:28:37 2012 (5010AB55)
    fffff880`010d8000 fffff880`0119a000   Wdf01000 Wdf01000.sys Sat Jun 22 04:13:05 2013 (51C51641)
    fffff880`0119a000 fffff880`011aa000   WDFLDR   WDFLDR.SYS   Sat Jun 22 04:14:38 2013 (51C5169E)
    fffff880`011aa000 fffff880`011c1000   acpiex   acpiex.sys   Thu Jul 26 03:25:57 2012 (5010AAB5)
    fffff880`011c1000 fffff880`011cc000   WppRecorder WppRecorder.sys Thu Jul 26 03:29:07 2012 (5010AB73)
    fffff880`011cc000 fffff880`011d6000   WMILIB   WMILIB.SYS   Thu Jul 26 03:30:04 2012 (5010ABAC)
    fffff880`011d6000 fffff880`011f7000   raspptp  raspptp.sys  Thu Jul 26 03:23:13 2012 (5010AA11)
    fffff880`01400000 fffff880`0140d000   vdrvroot vdrvroot.sys Thu Jul 26 03:27:29 2012 (5010AB11)
    fffff880`0140d000 fffff880`01424000   pdc      pdc.sys      Fri Mar 01 04:58:34 2013 (5130357A)
    fffff880`01424000 fffff880`0143e000   partmgr  partmgr.sys  Wed Jan 09 04:01:42 2013 (50ECEBA6)
    fffff880`01444000 fffff880`0153f000   NDIS     NDIS.SYS     Sat Jun 15 06:11:35 2013 (51BBF787)
    fffff880`0153f000 fffff880`015ae000   NETIO    NETIO.SYS    Thu Oct 11 06:16:20 2012 (50765624)
    fffff880`015ae000 fffff880`015b8000   msisadrv msisadrv.sys Thu Jul 26 03:28:02 2012 (5010AB32)
    fffff880`015b8000 fffff880`015f5000   pci      pci.sys      Thu Jul 26 03:27:43 2012 (5010AB1F)
    fffff880`01800000 fffff880`01816000   datascrn datascrn.sys Thu Jul 26 03:29:13 2012 (5010AB79)
    fffff880`01816000 fffff880`01824000   cbafilt  cbafilt.sys  Thu Jul 26 03:29:05 2012 (5010AB71)
    fffff880`01824000 fffff880`0186c000   msiscsi  msiscsi.sys  Mon Feb 03 16:23:09 2014 (52EFC26D)
    fffff880`0186c000 fffff880`01877000   kdnic    kdnic.sys    Thu Jul 26 03:27:41 2012 (5010AB1D)
    fffff880`01877000 fffff880`01889000   umbus    umbus.sys    Thu Jul 26 03:27:39 2012 (5010AB1B)
    fffff880`01889000 fffff880`018a9000   i8042prt i8042prt.sys Thu Jul 26 03:28:50 2012 (5010AB62)
    fffff880`018a9000 fffff880`018b8000   kbdclass kbdclass.sys Thu Jul 26 03:28:47 2012 (5010AB5F)
    fffff880`018b8000 fffff880`018c7000   mouclass mouclass.sys Thu Jul 26 03:28:47 2012 (5010AB5F)
    fffff880`018c7000 fffff880`018e5000   parport  parport.sys  Thu Jul 26 03:29:53 2012 (5010ABA1)
    fffff880`018e5000 fffff880`018fd000   serial   serial.sys   Thu Jul 26 03:30:01 2012 (5010ABA9)
    fffff880`018fd000 fffff880`01952000   storport storport.sys Mon Feb 03 16:23:24 2014 (52EFC27C)
    fffff880`01952000 fffff880`019b2000   fltmgr   fltmgr.sys   Thu Jul 26 03:30:09 2012 (5010ABB1)
    fffff880`019b2000 fffff880`019e0000   quota    quota.sys    Thu Jul 26 03:29:14 2012 (5010AB7A)
    fffff880`019e0000 fffff880`019f4000   dfsrro   dfsrro.sys   Thu Jul 26 03:29:13 2012 (5010AB79)
    fffff880`019f4000 fffff880`01a00000   BATTC    BATTC.SYS    Thu Oct 11 06:19:58 2012 (507656FE)
    fffff880`01a00000 fffff880`01a2c000   tunnel   tunnel.sys   Thu Jul 26 03:23:04 2012 (5010AA08)
    fffff880`01a2c000 fffff880`01a3b000   CompositeBus CompositeBus.sys Thu Jul 26 03:28:03 2012 (5010AB33)
    fffff880`01a3b000 fffff880`01a45000   vmgencounter vmgencounter.sys Thu Jul 26 03:27:58 2012 (5010AB2E)
    fffff880`01a45000 fffff880`01c2a000   Ntfs     Ntfs.sys     Sun Jan 26 23:28:35 2014 (52E59A23)
    fffff880`01c2a000 fffff880`01c45000   ksecdd   ksecdd.sys   Thu Sep 20 07:09:16 2012 (505AB30C)
    fffff880`01c45000 fffff880`01c56000   pcw      pcw.sys      Thu Jul 26 03:28:44 2012 (5010AB5C)
    fffff880`01c56000 fffff880`01c60000   Fs_Rec   Fs_Rec.sys   Thu Jul 26 03:30:08 2012 (5010ABB0)
    fffff880`01c60000 fffff880`01c8f000   ksecpkg  ksecpkg.sys  Thu Oct 11 06:16:46 2012 (5076563E)
    fffff880`01c8f000 fffff880`01cc0000   cdrom    cdrom.sys    Thu Jul 26 03:26:36 2012 (5010AADC)
    fffff880`01cc0000 fffff880`01d2b000   dedup    dedup.sys    Sat Oct 05 04:31:38 2013 (524F881A)
    fffff880`01d2b000 fffff880`01d3a000   vmrawdsk vmrawdsk.sys Sun Dec 15 03:36:38 2013 (52AD23C6)
    fffff880`01d3a000 fffff880`01d47000   BasicRender BasicRender.sys Thu Jul 26 03:28:51 2012 (5010AB63)
    fffff880`01d47000 fffff880`01d53000   mssmbios mssmbios.sys Thu Jul 26 03:29:19 2012 (5010AB7F)
    fffff880`01d53000 fffff880`01d64000   discache discache.sys Thu Jul 26 03:28:23 2012 (5010AB47)
    fffff880`01d64000 fffff880`01d85000   dfsc     dfsc.sys     Wed Jan 15 23:42:58 2014 (52D71D02)
    fffff880`01d85000 fffff880`01d91000   ndistapi ndistapi.sys Thu Sep 20 07:09:19 2012 (505AB30F)
    fffff880`01d91000 fffff880`01dc0000   ndiswan  ndiswan.sys  Thu Jul 26 03:23:13 2012 (5010AA11)
    fffff880`01dc0000 fffff880`01dde000   rassstp  rassstp.sys  Thu Jul 26 03:23:59 2012 (5010AA3F)
    fffff880`01dde000 fffff880`01df6000   AgileVpn AgileVpn.sys Thu Jul 26 03:23:11 2012 (5010AA0F)
    fffff880`01df6000 fffff880`01dfc400   CmBatt   CmBatt.sys   Thu Jul 26 03:29:20 2012 (5010AB80)
    fffff880`01e00000 fffff880`01e54000   CLASSPNP CLASSPNP.SYS Sat Jun 29 04:07:45 2013 (51CE4F81)
    fffff880`01e54000 fffff880`01e68000   crashdmp crashdmp.sys Fri Aug 30 04:11:28 2013 (52200D60)
    fffff880`01e75000 fffff880`01e7e000   Null     Null.SYS     Thu Jul 26 03:30:16 2012 (5010ABB8)
    fffff880`01e81000 fffff880`020ba000   tcpip    tcpip.sys    Wed Jan 22 04:28:22 2014 (52DF48E6)
    fffff880`020ba000 fffff880`02122000   fwpkclnt fwpkclnt.sys Fri Mar 01 04:55:54 2013 (513034DA)
    fffff880`02122000 fffff880`0213d000   wfplwfs  wfplwfs.sys  Thu Oct 10 04:32:19 2013 (52561FC3)
    fffff880`0213d000 fffff880`02191000   volsnap  volsnap.sys  Sat Jun 01 04:10:22 2013 (51A9661E)
    fffff880`02191000 fffff880`021a8000   mup      mup.sys      Thu Jul 26 03:30:00 2012 (5010ABA8)
    fffff880`021a8000 fffff880`021b4000   npsvctrig npsvctrig.sys Thu Jul 26 03:27:33 2012 (5010AB15)
    fffff880`021b4000 fffff880`021d0000   disk     disk.sys     Sat Oct 12 07:31:15 2013 (5258ECB3)
    fffff880`021ed000 fffff880`021ff000   dfs      dfs.sys      Thu Jul 26 03:28:21 2012 (5010AB45)
    fffff880`03800000 fffff880`03863000   mrxsmb   mrxsmb.sys   Tue Feb 05 22:29:08 2013 (511187B4)
    fffff880`0389c000 fffff880`038eb000   ks       ks.sys       Sat Feb 02 07:25:50 2013 (510CBF7E)
    fffff880`038eb000 fffff880`038f6000   rdpbus   rdpbus.sys   Thu Jul 26 03:28:19 2012 (5010AB43)
    fffff880`038f6000 fffff880`0390a000   NDProxy  NDProxy.SYS  Tue Apr 09 03:33:41 2013 (51637E05)
    fffff880`0390a000 fffff880`03915000   flpydisk flpydisk.sys Thu Jul 26 03:30:15 2012 (5010ABB7)
    fffff880`03915000 fffff880`03922000   dump_diskdump dump_diskdump.sys Thu Jul 26 03:29:58 2012 (5010ABA6)
    fffff880`03922000 fffff880`0393f000   dump_LSI_SAS dump_LSI_SAS.sys Fri May 11 20:40:21 2012 (4FAD6B25)
    fffff880`0393f000 fffff880`03947000   HIDPARSE HIDPARSE.SYS Sat Jun 29 04:08:18 2013 (51CE4FA2)
    fffff880`03947000 fffff880`03955000   monitor  monitor.sys  Fri Mar 01 04:56:18 2013 (513034F2)
    fffff880`03955000 fffff880`0397d000   luafv    luafv.sys    Thu Jul 26 03:29:13 2012 (5010AB79)
    fffff880`0397d000 fffff880`03991000   lltdio   lltdio.sys   Thu Jul 26 03:24:02 2012 (5010AA42)
    fffff880`03991000 fffff880`039a9000   rspndr   rspndr.sys   Thu Jul 26 03:24:06 2012 (5010AA46)
    fffff880`039a9000 fffff880`039c9000   bowser   bowser.sys   Thu Jul 26 03:28:01 2012 (5010AB31)
    fffff880`039c9000 fffff880`039e0000   mpsdrv   mpsdrv.sys   Thu Oct 31 03:42:19 2013 (5271D19B)
    fffff880`03c00000 fffff880`03c73000   rdbss    rdbss.sys    Sat May 04 05:47:00 2013 (518492C4)
    fffff880`03c73000 fffff880`03c8d000   wanarp   wanarp.sys   Tue Apr 09 03:31:00 2013 (51637D64)
    fffff880`03c8d000 fffff880`03c9b000   nsiproxy nsiproxy.sys Thu Jul 26 03:25:00 2012 (5010AA7C)
    fffff880`03c9b000 fffff880`03ca3000   vmmouse  vmmouse.sys  Mon Jun 04 10:34:25 2012 (4FCC8121)
    fffff880`03ca3000 fffff880`03e0c000   dxgkrnl  dxgkrnl.sys  Thu Sep 19 04:16:23 2013 (523A6C87)
    fffff880`03e0c000 fffff880`03e1d000   watchdog watchdog.sys Thu Jul 26 03:29:05 2012 (5010AB71)
    fffff880`03e1d000 fffff880`03e6b000   dxgmms1  dxgmms1.sys  Wed Jan 09 03:58:58 2013 (50ECEB02)
    fffff880`03e6b000 fffff880`03e7c000   BasicDisplay BasicDisplay.sys Thu Jul 26 03:29:08 2012 (5010AB74)
    fffff880`03e7c000 fffff880`03e8e000   Npfs     Npfs.SYS     Thu Jul 26 03:30:26 2012 (5010ABC2)
    fffff880`03e8e000 fffff880`03e9a000   Msfs     Msfs.SYS     Thu Jul 26 03:30:24 2012 (5010ABC0)
    fffff880`03e9a000 fffff880`03ebc000   tdx      tdx.sys      Thu Jul 26 03:24:58 2012 (5010AA7A)
    fffff880`03ebc000 fffff880`03eca000   TDI      TDI.SYS      Thu Jul 26 03:27:59 2012 (5010AB2F)
    fffff880`03eca000 fffff880`03ed6000   ws2ifsl  ws2ifsl.sys  Thu Sep 20 07:09:50 2012 (505AB32E)
    fffff880`03ed6000 fffff880`03f2e000   netbt    netbt.sys    Thu Jul 26 03:24:26 2012 (5010AA5A)
    fffff880`03f2e000 fffff880`03fc4000   afd      afd.sys      Wed Sep 04 04:11:20 2013 (5226A4D8)
    fffff880`03fc4000 fffff880`03fee000   pacer    pacer.sys    Thu Jul 26 03:23:05 2012 (5010AA09)
    fffff880`03fee000 fffff880`03ffe000   netbios  netbios.sys  Thu Jul 26 03:28:19 2012 (5010AB43)
    fffff880`03ffe000 fffff880`03fff480   swenum   swenum.sys   Thu Jul 26 03:28:53 2012 (5010AB65)
    fffff880`0ac00000 fffff880`0acdf000   HTTP     HTTP.sys     Fri Mar 15 00:17:15 2013 (5142688B)
    fffff880`0acdf000 fffff880`0ace7000   vmmemctl vmmemctl.sys Sun Dec 15 03:36:24 2013 (52AD23B8)
    fffff880`0acf8000 fffff880`0ad43000   mrxsmb10 mrxsmb10.sys Thu Jul 26 03:23:06 2012 (5010AA0A)
    fffff880`0ad43000 fffff880`0ad7e000   mrxsmb20 mrxsmb20.sys Tue Feb 05 22:28:36 2013 (51118794)
    fffff880`0b200000 fffff880`0b20d000   condrv   condrv.sys   Thu Jul 26 03:30:08 2012 (5010ABB0)
    fffff880`0b20d000 fffff880`0b2ae000   srv2     srv2.sys     Tue Apr 09 03:33:02 2013 (51637DDE)
    fffff880`0b2cd000 fffff880`0b399000   peauth   peauth.sys   Tue Apr 09 03:32:01 2013 (51637DA1)
    fffff880`0b399000 fffff880`0b3a4000   secdrv   secdrv.SYS   Wed Sep 13 14:18:38 2006 (4508052E)
    fffff880`0b3a4000 fffff880`0b3e8000   srvnet   srvnet.sys   Tue Apr 09 03:31:13 2013 (51637D71)
    fffff880`0b3e8000 fffff880`0b3fa000   tcpipreg tcpipreg.sys Thu Jul 26 03:23:13 2012 (5010AA11)
    fffff880`0b4e3000 fffff880`0b570000   srv      srv.sys      Thu Jul 26 03:25:28 2012 (5010AA98)
    fffff880`0b570000 fffff880`0b57b000   rdpvideominiport rdpvideominiport.sys Fri Oct 12 06:48:28 2012 (5077AF2C)
    fffff880`0b57b000 fffff880`0b5ac000   rdpdr    rdpdr.sys    Thu Jul 26 03:25:18 2012 (5010AA8E)
    fffff880`0b5ac000 fffff880`0b5b9000   terminpt terminpt.sys Thu Jul 26 03:28:53 2012 (5010AB65)
    fffff960`00118000 fffff960`00508000   win32k   win32k.sys   Sat Feb 08 04:34:05 2014 (52F5B3BD)
    fffff960`006cb000 fffff960`006d4000   TSDDD    TSDDD.dll    Thu Jul 26 03:30:25 2012 (5010ABC1)
    fffff960`00879000 fffff960`008af000   cdd      cdd.dll      Thu Jul 26 05:49:37 2012 (5010CC61)
    fffff960`00a21000 fffff960`00a60000   RDPUDD   RDPUDD.dll   Fri Oct 12 06:50:01 2012 (5077AF89)
    Unloaded modules:
    fffff880`01e68000 fffff880`01e75000   dump_storport.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000D000
    fffff880`021d0000 fffff880`021ed000   dump_LSI_SAS.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0001D000
    fffff880`021a8000 fffff880`021b4000   hwpolicy.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`00f41000 fffff880`00f5c000   sacdrv.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0001B000
    fffff880`00c33000 fffff880`00c40000   ApiSetSchema.dll
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000D000
    I have searched for others having a similar problem but have not managed to find much.
    The memory dump at the time of the crash does seem to hint at a problem with DFSR.exe.
    The setup seems to be running fine again now and is going through its consistency checks, it is just a major inconvenience and will only get worse as the DFS becomes busier and approaches capacity.
    The plan was to put this setup into production however with the unpredictability of blue screen reboots I cannot see this happening until I can find a fix or work around.
    I have yet to see this problem occur on the other (physical) server, this is pretty much identical in configuration apart from its storage access.
    My thoughts are a possible bug in the DFSR component or a bug in the DSM Drivers used for the iSCSI SAN connection or maybe a combination of the two.
    Any help, thoughts or suggestions greatly appreciated
    Thanks

    Hi,
    Please install the current version of Dfssvc.exe Dfsc.sys Dfsrs.exe for Windows Server 2012.
    List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2012 and Windows Server 2012 R2
    http://support.microsoft.com/kb/2951262
    The issue may be due to the DFSRoot folder has lost NTFS permission. Some reasons why DFS root lose ACLs Links are listed in the article below:
    How to implement Windows Server 2003 Access-based Enumeration in a DFS environment
    http://support.microsoft.com/kb/907458/en-us
    You could use dfsutil to set NTFS permission: dfsutil property ACL \\DFS-namespace
    Using the Windows Server 2008 DFSUTIL.EXE command line to manage DFS-Namespaces
    http://blogs.technet.com/b/josebda/archive/2009/05/01/using-the-windows-server-2008-dfsutil-exe-command-line-to-manage-dfs-namespaces.aspx
    To narrow down the issue, you could remove the DFS role to check if the issue related to the dfs namespace and dfs replication roles.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Cannot access local DFS shares while VPN is active

    Hi
    We use Windows Server 2008 Standard as a domain controller. It also hosts DFS. Although the namespaces are hosted on the server, the data is stored on a Windows 2008 Storage Server. We do not use DFS replication.
    I have several DFS shares mapped on my Windows 7 client, which has just replaced my XP client, and can access them without any problems.
    However, as soon as I connect to a remote network (located on a different domain - it has nothing to do with our network at all), I am unable to access our DFS shares. If I try to access a DFS share an error message pops up stating:
    Location is not available
    Logon failure: unknown user name or bad password.
    The first time I connected the VPN a network dialog popped up asking what type of network it was and I chose Work. After connecting via the VPN I use remote desktop to carry out daily maintenance on a server on the remote network.
    Other local resources are available. I can ping machines via IP, name and FQDN. I can access the same DFS shares using UNC paths. So, although I receive the error message described above when accessing AD-name.local-backslash-share-name1 I have no trouble
    accessing server-name-backslash-share-name1
    As soon as I close the VPN connection normal functionality is restored and I can again access the DFS shares without any problems.
    Can someone help me fix this, please? When this was setup on my XP machine I never experienced this problem.
    Also, is there a way of typing LAN addresses without the forum software converting them to a customised hyperlink? Thanks!

    Thank you, fupin
    Sabrina's suggestion to edit the pbk file worked. I changed the setting from 1 to 0 and connected to the remote network via the VPN and am still able to access the local DFS shares.
    As per the OPs comments, the username and password I am using for the remote network are both different from the credentials I am using on the local network.
    ... take the steps in the KB 822707 to resolve it:
    1). Locate the .pbk file that contains the entry that you dial. To do so, click Start, click Search, type *.pbk in the All or part of the file name box, and then
    click Search.
    2). Open the file in Notepad.
    3). Locate the following entry: UseRasCredentials=1
    4). Modify the entry to the following: UseRasCredentials=0
    5). On the File menu, click Save, and the click Exit.
    Cheers!

  • Connection to the deployment share could not be made (DFS share, works fine on site A, not on Site B)

    I'm trying to isolate this problem with MDT..., unable to find a solution matching this error.
    We have two sites, with a DFS replica between the servers, which works fine. 
    Server A: Windows 2012 R2 standard
    Windows Automated Installation Kit for Windows 7 
    MDT 2012, Update 1 
    WDS configured for PXE boot 
    Distributed File Share
    Server B: Windows 2008 R2 Standard 
    MDT 2012, Update 1 
    WDS configured for PXE boot 
    Distributed File Share
    The local path on both servers is on E:\DFS-Deploymentshare
    The DFS path is \\domain.com\it\deploymentshare
    When deploying on Site A, the deployment run smooth without problems.
    When deploying on Site B, the deployment fails to create connection to the share. 
    A connection to the deployment share (\\domain.com\it\deploymentshare) could not be made.
    Connection OK. Possible cause: invalid credentials.
    Pressing F8, to reach a command prompt. "ipconfig" shows an IP-address. I can PING the deployment server. I can mount the Deployment share using "net use" and providing the username/password added in the bootstrap.ini and "retry"
    in the message box and the deployment continues.
    In the BDD log i get this timeout:
    <![LOG[Unable to connect to \\domain.com\it\deplomentshare. Sleeping for 5 seconds. 
    <![LOG[<Message containinng password has been suppressed>
    <![LOG[Access is denied.
    However everything is the same both in site A and B so this seems very strange!
    The complete system has worked this way before.
    Bootstrap.ini contains: 
    DeployRoot=\\domain.com\it\deploymentshare 
    UserDomain="domain" 
    UserID="mdt-account" 
    UserPassword="password" 
    I've been trying all I can think of, but Im still faced with this error and to keep in mind the same share working on another site.

    Ok, so by the sounds of it, there is something wrong with the share permissions (especially if your account works fine but the MDTserviceaccount does not work even when part of Domain Admins).
    So you need to do the following:
    Start in Site A:
    Boot into WinPE on a workstation in site A
    Ping server-a
    Ping server-b
    Run "net use * \\server-a\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
    Type in the password for MDTserviceaccount when prompted
    Browse to the newly mapped drive and list the files/folders
    Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
    If all that works, then you can move to site B
    Start in Site B:
    Boot into WinPE on a workstation in site B
    Ping server-a
    Ping server-b
    Run "net use * \\server-b\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
    Type in the password for MDTserviceaccount when prompted
    Browse to the newly mapped drive and list the files/folders
    Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
    By going through all of the above, you should be able to see where the problem lies.
    If all of the above works with no problems, then you have the details incorrectly specified in the BootStrap.ini (or possibly CustomSettings.ini). Confirm that you have the following specified in the relevant ini file:
    DeployRoot
    UserID
    UserDomain
    UserPassword
    You can have a look in the help file if you need to confirm that these properties are configured correctly. Look under
    Toolkit Reference - Properties - Property Definition in the help file.
    Both Site A and Site B is successfully
    I have changed the Password of deployuser to test if it is correct. and i have copy/pasted the password into the DC when changing the password.
    I have tested the password by logging on to a client-pc with the deployuser as username and the temp password "Pa$$w0rd" successfully.
    Both UserID, UserDomain and UserPassword is entered after the help file for Property Definition.
    Please see the Bootstrap.ini and Customsettings.ini (NB! Servernames, Domainname and Passwords are fictive.)
    http://1drv.ms/1tGDlUt

  • Server 2008 R2 DFS Drop Outs

    I have a problem with a Server 2008R2 running DFS, 3 out of 4 Folders drop out - I just can't figure out what on earth is going on.
    It is a Domain based DFS, the namespace is called 'dfs' - e.g.
    \\domain\dfs, I have 4 Folders called "MyDocs", "Home", "Shared" and "Software" - all of these have a cache duration of 1800 seconds.
    "MyDocs" is used with My Documents Folder Redirection, Home, Shared and Software are used with Group Policy Preference based drive mappings.
    The problem I have is the Home, Shared and Software Folders simply disappear, thus mapped drives become unavailable. The problem can occur as frequently as every 5 minutes or if I'm lucky, I'll get half an hour of solid reliable DFS usage.
    I half suspect I'm not having a problem with the MyDocs Folder because it's linked to Offline files and Windows 7 Offline Files uses background sync.
    One thing I will point out, the problem only surfaced after I upgraded my Lenovo laptop to Windows 7 Ultimate x64 SP1, it did not exist when I was running Windows 7 Professional x64 (no SP). Another laptop on the network (Sony VAIO - differnet
    WLAN NIC), it's still running Windows 7 x64 Professional (no SP), uses the same WLAN and it never has a problem.
    I have spent months investigating the potential for this to be a WLAN card (Intel Centrino 6200) and I have noticed other people reporting similar mapped network drive issues on the Lenovo forums (also using these Centrino model WLAN
    cards).
    The problem occurs almost immediately if I try to transfer a large amount of data over the WLAN, e.g. don't bother trying to copy an ISO as will cause the DFS Folders (Home/Software/Shared) to drop-out almost immediately and the copy borkes out. The problem
    does not occur if I transfer the same ISO over wired LAN ethernet.
    I can't get past the fact that this problem didn't occur when running Win 7 Pro with no SP1, I'm not 100% inclined to think this is a hardware or WLAN card issue.
    I have screwed around with WLAN drivers, power management settings etc etc etc, jack of that. It's achieved nothing.
    I have installed KB983620 but this has had no effect.
    A few things I have noticed:
    * When the DFS Folders come back online, the Application Experience service on the Windows 7 client has literally just (re)started. As a test, sometimes I'll manually restart it and the Folders will reappear almost immediately after (doesn't
    work every time).
    * Restarting the TCP/IP NetBIOS Helper Service can help force the Folders to come back online (also doesn't work every time)
    * Repeatedly browsing the still functional MyDocs DFS Folder (which never drops out) can help prompt the other DFS Folders to reappear (also doesn't work every time)
    * I have noticed when the 3 DFS Folders are not available via
    \\domain.local\dfs\, they will be available via
    \\domain\dfs and vice versa
    * If I run dfsutil /pktinfo - when the 3 Folders are unavailable, the TTL for Home, Shared, Software is sitting at 0 (MyDocs on the other hand is not, it's still counting down). When things are functioning properly, the TTL is counting down for all
    of them from 1800, when it reaches 0, it starts from 1800 again.
    Any ideas?
    Ben

    Hello Ben,
    From your explanation it seems it is wireless issue? can you look in to the event logs of the machine affected and see what event ID is being reported? Also, possibility might be DNS because you said it works with
    \\domain\dfs but fails with
    \\domain.local\dfs?
    Can you check your wireless settings to see what is the max data size that can go through if there are such restrictions
    Isaac Oben MCITP:EA, MCSE,MCC
    View my MCP Certifications
    Hi Isaac
    Thanks for the reply.
    At first and over the past few weeks I've been thoroughly investigating the possibility this is a Wireless issue. Messing around with drivers (Lenovo, Intel, versions, settings, I've tried it all). But there are some factors I can't ignore that lead
    me to think maybe this is not specifically a Wireless issue.
    The problem only started after I upgraded to Windows 7 Ultimate with Service Pack 1 - the problem never occured with Windows 7 Professional (no SP, both x64)
    When I first started troubleshooting I was using
    \\domain\dfs, but then I realised when I was having the problem I could still access the folders via
    \\domain.loca\dfs. Now I've realised it's a case of when fqdn is working, non-fqdn might not be and when non-fqdn is working, fqdn might not be and sometimes both are not.
    No specific events are being generated. Any suggestions?
    Any idea where I check max data rate?
    Thanks,
    ben

Maybe you are looking for

  • Registry error after launching Photoshop 6

    I have a user who is getting a dialog box that says Registry editing has been disabled by your administrator.  This started happening after I copied the original user profile who had had administrator access to a new profile with power user access. 

  • Selecting and moving clips to the right of the TCI

    Is there a way to be able to move the editted clips that are to the right of my current TCI, and keep the edits as they are? I'm looking for a ripple delete with more control if that makes sense. My old editting software had a group tool which alowed

  • Linking between Material GR and Service Entry Sheets

    Hi!, We have two separate Quantity Contracts. One for supply of Material X and another for transportation service for transporting material X. Now the transportation vendor shall have to be paid as per the exact Goods Receipts quantity done for Mater

  • Upload control in Visual Composer

    Hi guys, We here are wondering whether an upload control is something that's needed or not. We are considering implementing this for EhP2. Can you please comment on this? Do you find such control helpful? Thanks, Natty

  • Authentication error on Job submit from EM (VNI 2015)

    we have oracle 8.1.7 on windows 2000 advance server recently updated with patch 8.1.7.2.1 and 8.1.7.2.5. Here is my SQLnet.ora file: NAMES.DEFAULT_DOMAIN = hq.xxx.net SQLNET.AUTHENTICATION_SERVICES= (NTS) NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOST