Windows 8

  1. Device '%3' in '%1' is loaded but has a different version from the server. Server version %4 Client version %5 (Virtual machine ...
  2. Device : %1!s! (%2!s!) Condition : %3!s! Line bps : %4!-12d! Duration : %5!d! Days, %6!d! Hrs, %7!d! Mins Bytes In : %8!-12d! ...
  3. DEVICE ADDITIONAL OPTIONS The following types apply to device additional options entries. For information about data formats ...
  4. Device instance %2 of %1 was rejected because it does not support extended SRBs. The device will be accepted after a reboot. ...
  5. Device instance %2 of %1 was rejected because its supported address type does not match. The device will be accepted after ...
  6. Device instance %2 of %1 was rejected because the maximum transfer length of the underlying adapter is too low. The device ...
  7. Device metadata that contains an extension namespace has been parsed for container '%1', ExtensionNamespace = '%2', Culture ...
  8. Device Power State is the current power state of the network interface card. Power state 0 is the active operating state, ...
  9. Device Stage couldn't complete this task. The device or your computer might be busy. Try again later, or try disconnecting ...
  10. Devices are normally disabled if they are not working properly or causing a resource conflict. You cannot use a device when ...
  11. Devices policy allows an administrator to configure hardware devices, including the ability to enable or disable hardware. ...
  12. Devices: Allow undock without having to log on This security setting determines whether a portable computer can be undocked ...
  13. Devices: Allowed to format and eject removable media This security setting determines who is allowed to format and eject ...
  14. Devices: Prevent users from installing printer drivers when connecting to shared printers For a computer to print to a shared ...
  15. Devices: Restrict CD-ROM access to locally logged-on user only This security setting determines whether a CD-ROM is accessible ...
  16. Devices: Restrict floppy access to locally logged-on user only This security setting determines whether removable floppy ...
  17. Devices: Unsigned driver installation behavior This security setting determines what happens when an attempt is made to install ...
  18. device_hwid HardwareIDs of Devices to be MPIO'd, as strings of vendor8product16, delimited by a space. (Use empty string ...
  19. device_switch Whether to apply above options to all or passed-in devices. -d Parameters following this switch indicate hardware ...
  20. DFS could not access its private data from the Active Directory. Please manually check network connectivity, security access, ...
  21. DFS has recovered from an error and is able to read its private data from the Active Directory. Root %1 is now able to read ...
  22. DFS has the following stale entries in the domain cache. Please restart the DFS Namespace service on all domain controllers.%0 ...
  23. DFS is requesting the client for a larger buffer for trusted domain information. Some Win98 clients may not be able to access ...
  24. DFS link %1 was marked incorrectly as a DFS root. The DFS namespace is operational on this server. If this namespace is hosted ...
  25. DFS metadata is not consistent between domain controllers and the PDC emulator. Check Active Directory Domain Services (AD ...
  26. DFS metadata object %1 is empty in the metadata for DFS root %2. The DFS namespace is operational on this server. If this ...
  27. DFS Namespace aggregates the files from multiple file servers into a single, global namespace for users.Enabling this role ...
  28. DFS Namespaces enables you to group shared folders located on different servers into one or more logically structured namespaces. ...
  29. DFS Namespaces site awareness will behave incorrectly, with the namespace server potentially providing referrals to client ...
  30. DFS Replication cannot replicate files in the replicated folders listed above because the staging folder at cannot be opened. ...
  31. DFS Replication cleaned up the staging folder for the replicated folder '{0}' that belongs to the replication group '{1}' ...
  32. DFS Replication does not replicate certain files in the replicated folders listed above because they have temporary attribute ...
  33. DFS Replication experienced a large number of replication conflicts in the replicated folder '{0}' that belongs to the replication ...
  34. DFS Replication failed to clean up old staging files. As a result, some large files might fail to replicate, and the replicated ...
  35. DFS Replication is a multimaster replication engine that enables you to synchronize folders on multiple servers across local ...
  36. DFS Replication is a new replication technology that keeps folders synchronized on multiple servers. The following figure ...
  37. DFS Replication provides for the configuration, management, monitoring, and replication of large quantities of data over ...
  38. DFS Replication reporting mechanism cannot access the WMI (Windows Management Instrumentation) namespace to retrieve certain ...
  39. DFS Replication will attempt to recover from this problem automatically on volume , but replication will not take place until ...
  40. DFS was unable to resynchronize this root target for root: %1. This may lead to inaccessability of portions of the DFS namespace. ...
  41. DFSN service completed performing refresh of metadata for namespace %1 with status %4. Time taken to perform this operation ...
  42. DFSN service has failed to deleted DFS reparse point %1 on volume %3 with status %4. The service attempted to delete this ...
  43. DFSN service has started performing complete refresh of metadata for namespace %1. This task can take time if the namespace ...
  44. DFSN service has successfully deleted DFS reparse point %1 on volume %3. The reparse point was deleted because it was not ...
  45. DFSR Failover Cluster Resource '%4!s!' is in process of being moved to some other node. The DFS Replication Service will ...
  46. DFSR has detected that the SYSVOL migration global state is set to %1!s! and the current local state is %2!s!. DFSR has started ...
  47. DFSR has detected that the SYSVOL migration global state is set to %1!s! and the current local state is %2!s!. This is an ...
  48. DFSR has now started the process of redirecting replication of the SYSVOL share on Domain Controller %2!s!. NTFRS will continue ...
  49. DFSR has started preparing the Domain Controller %1!s! for migration. DFSR will now create the SYSVOL_DFSR folder, create ...
  50. DFSR has successfully created the SYSVOL_DFSR folder. DFSR is currently waiting for initial sync to complete. During the ...
  51. DFSR has successfully migrated the Domain Controller %1!s! to the 'ELIMINATED' state. DFSR has disabled NTFRS service. Additional ...
  52. DFSR has successfully migrated the Domain Controller %3!s! to the 'ELIMINATED' state. NTFRS is no longer replicating the ...
  53. DFSR has successfully migrated the Domain Controller %3!s! to the 'PREPARED' state. TO CONTINUE MIGRATION: If you choose ...
  54. DFSR has successfully migrated the Domain Controller %3!s! to the 'REDIRECTED' state. DFSR is now replicating the SYSVOL_DFSR ...
  55. DFSR has successfully rolled back migration on the Domain Controller %2!s! to the 'START' state. The SYSVOL_DFSR folder has ...
  56. DFSR Migration was unable to delete the DFSR local settings on the Domain Controller %1!s!. This could be because DFSR was ...
  57. DFSR Migration was unable to delete the NTFRS local settings on Domain Controller %1!s!. This could be because DFSR was unable ...
  58. DFSR Migration was unable to delete the SYSVOL folder located at %1!s!. This may occur due to sharing violations. Additional ...
  59. DFSR Migration was unable to delete the SYSVOL_DFSR folder located at %1!s!. This may occur due to sharing violations. Additional ...
  60. DFSR Migration was unable to rollback migration on the Domain Controller %1!s! to the 'PREPARED' state. This could be because ...
  61. DFSR Migration was unable to transition to the 'ELIMINATED' state for Domain Controller %1!s!. DFSR will retry the next time ...
  62. DFSR Migration was unable to transition to the 'PREPARED' state for Domain Controller %1!s!. DFSR will retry the next time ...
  63. DFSR was unable to copy the contents of the SYSVOL share located at %1!s! to the SYSVOL_DFSR folder located at %2!s!. This ...
  64. DFSR was unable to create the SYSVOL_DFSR folder at %1!s!. This could be due to lack of availability of disk space. Additional ...
  65. DFSR was unable to redirect the replication of the SYSVOL share on Domain Controller %3!s! from folder %1!s! to %2!s!. This ...
  66. DFSR will now migrate the Domain Controller %2!s! to the 'ELIMINATED' state. Please note that hereafter it is not possible ...
  67. DFSR will now rollback the migration process on the Domain Controller %3!s! to the 'PREPARED' state. After rollback to the ...
  68. DFSR will now rollback the migration process on the Domain Controller %3!s! to the 'START' state. DFSR will delete the SYSVOL_DFSR ...
  69. Dfsutil /DisplayDfsPath can be used to resolve a DfsPath to a destination UNC path. The DfsPath can be a domain based or ...
  70. DfsUtil: Failed to enumerate at level 6. Attributes such as INSITE, SITECOSTING and ROOTSCALABILITY may not be backed up ...
  71. DHCID DHCID Record. This RR is used to resolve the conflict of fully qualified domain names which may arise among DHCP clients ...
  72. DHCP Allocator Configuration Information - Scope Network : %1!s! Scope Mask : %2!s! Lease Time (minutes) : %3!s! Logging ...
  73. DHCP client request from %1 was dropped since the applicable IP address ranges in scope/superscope %2 are out of available ...
  74. DHCP client request from {0} was dropped since the applicable IP address ranges in scope/superscope {1} are out of available ...
  75. DHCP failed to authorize this server. Verify that Active Directory Domain Services is available and that you have sufficient ...