Windows 7
- Administration tools for Windows Network Load Balancing (NLB) to manage remote and local clusters. If this rule is disabled, ...
- Administrator permissions are needed to use the selected options. Use an administrator command prompt to complete these tasks. ...
- Administrator privileges are required to use the NAP Client Configuration. Please log on to the computer with an administrator ...
- Administrator privileges are required to use the Network Policy Server. Please log on to the computer with an administrator ...
- Administrator recovered system from CrashOnAuditFail. LSA will now accept non-administrative logons. Some auditable activity ...
- Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some ...
- Administrators have complete access to the computer and can make any desired changes. Based on notification settings, administrators ...
- Administrators have complete access to the computer and can make any desired changes. Based on notification settings, administrators ...
- Administrators have complete access to the computer and can make any desired changes. Based on notification settings, administrators ...
- Administrators use the Computer Configuration node in Group Policy to set policies that are applied to computers, regardless ...
- Administrators use the User Configuration node in Group Policy to set policies that are applied to users, regardless of which ...
- Administrators use this extension to specify scripts that are run when the user logs on or off the computer. Scripts run ...
- Administrators use this extension to specify scripts that are to run during computer startup or shutdown. Scripts run in ...
- Adprep attempted to create the Active Directory Domain Services object %1. Status/Consequence The object exists so Adprep ...
- Adprep can only run forest update,domain update or read only DC update one at a time. Status/Consequence Adprep has stopped ...
- Adprep cannot run on this platform because it is not an Active Directory Domain Controller. Status/Consequence Adprep stopped ...
- Adprep checked to verify whether operation %1 has completed. Status/Consequence The operation GUID already exists so Adprep ...
- Adprep completed with errors. Not all partitions are updated. See the ADPrep.log in the %1 directory for more information. ...
- Adprep could not complete the RODCPREP. No partitions were changed. Status/Consequence The Active Directory Domain Services ...
- Adprep could not contact the Domain Naming FSMO to read the partitions. The Domain Naming FSMO must be reachable for this ...
- Adprep could not contact the Infrastructure FSMO for domain %1. The Infrastructure FSMO must be reachable for this operation ...
- Adprep detected that another instance of Adprep is running. Status/Consequence Adprep has stopped without making changes. ...
- Adprep detected that the domain is not in native mode Status/Consequence Adprep has stopped without making changes. User ...
- Adprep detected that the logon user doesn't have SeSecurityPrivilegeEnabled Status/Consequence Adprep has stopped without ...
- Adprep detected that the logon user is not a member of %1\Domain Admins Group. Status/Consequence Adprep has stopped without ...
- Adprep detected that the logon user is not a member of the following group: %1\Domain Admins Group. Status/Consequence Adprep ...
- Adprep detected that the logon user is not a member of the following group: Enterprise Admins group. Status/Consequence Adprep ...
- Adprep detected that the logon user is not a member of the following group: Enterprise Admins Group. Status/Consequence Adprep ...
- Adprep detected that the logon user is not a member of the following group: Schema Admins Group. Status/Consequence Adprep ...
- Adprep detected that the logon user is not a member of the following groups: Enterprise Admins Group and %1\Domain Admins ...
- Adprep detected that the logon user is not a member of the following groups: Enterprise Admins Group and Schema Admins Group. ...
- Adprep detected that the logon user is not a member of the following groups: Enterprise Admins Group, Schema Admins Group ...
- Adprep detected that the logon user is not a member of the following groups: Schema Admins Group and %1\Domain Admins Group. ...
- Adprep did not attempt to add Anonymous Logon SID to Pre-Windows 2000 Compatible Access group because Everyone is not a member ...
- ADPREP does not permit forest and domain preparation on Windows Server 2003 Beta 2 Active Directory Domain Controllers. Status/Consequence ...
- Adprep failed in the attempt to add the Anonymous Logon SID to the Pre-Windows 2000 Compatible Access group. Status/Consequence ...
- Adprep failed to verify the consistency of Win2K schema. Status/Consequence The Active Directory Domain Services schema is ...
- Adprep failed to verify whether a conflict exists with the Exchange schema. Status/Consequence The Active Directory Domain ...
- Adprep failed to verify whether schema master has completed a replication cycle after last reboot. Status/Consequence The ...
- Adprep failed while performing Exchange schema check. Status/Consequence The Active Directory Domain Services schema is not ...
- Adprep finished successfully. Status/Consequence This Active Directory Domain Controller, the schema master, and the infrastructure ...
- Adprep has detected that Microsoft Windows Services for UNIX (SFU) is installed in this forest. Before proceeding with adprep ...
- Adprep modified the default security descriptor on object %1. Status/Consequence Adprep merged the existing default security ...
- Adprep must wait for replication to complete. Status/Consequence Domain-wide information has already been updated on the ...
- Adprep must wait for replication to complete. Status/Consequence Forest-wide information has already been updated on the ...
- Adprep requires Windows 2000 Service Pack 4 (SP4) or later to run. Status/Consequence Adprep can not run on this machine. ...
- Adprep successfully added the Anonymous Logon SID to the Pre-Windows 2000 Compatible Access group. Status/Consequence For ...
- Adprep successfully completed. User Action You can proceed to install Windows Server 2008 R2 on the Active Directory Domain ...
- Adprep successfully determined whether Microsoft Windows Services for UNIX (SFU) is installed or not. If adprep detected ...
- Adprep successfully modified the security descriptor on object %1. Status/Consequence Adprep merged the existing security ...
- Adprep successfully set the domain Update revision attribute to %1 on object %2. Status/Consequence Adprep updates the domain ...
- Adprep successfully set the forest Update revision attribute to %1 on object %2. Status/Consequence Adprep updates the forest ...
- Adprep successfully upgraded the schema using schupgr.exe. Status/Consequence The schema information on schema master has ...
- Adprep verified the state of operation %1. Status/Consequence The operation has not run or is not currently running. It will ...
- ADPREP WARNING: Before running adprep, all Windows 2000 Active Directory Domain Controllers in the forest should be upgraded ...
- Adprep was unable to add member %1 to object %2. User Action Check the log file ADPrep.log in the %3 directory for more information. ...
- Adprep was unable to add the application-defined HandlerRoutine function that handles CTRL+C and other signals. Status/Consequence ...
- Adprep was unable to check the current user's group membership. Status/Consequence Adprep has stopped without making changes. ...
- Adprep was unable to check the domain update status. Status/Consequence Adprep queries the directory to see if the domain ...
- Adprep was unable to check the forest update status. Status/Consequence Adprep queries the directory to see if the forest ...
- Adprep was unable to check the version of the operating system on this computer. Status/Consequence Adprep has stopped without ...
- Adprep was unable to complete because the call back function failed. Status/Consequence Error message: %1 User Action Check ...
- Adprep was unable to complete this operation. User Action Check the log file, ADPrep.log in the %1 directory for more information. ...
- Adprep was unable to construct a distinguished name for an object. Status/Consequence This operation failed because a buffer ...
- Adprep was unable to copy file %1 from installation point to local machine under directory %2. User Action Check the log ...
- Adprep was unable to copy setup files from installation point to local machine. Status/Consequence Adprep has stopped without ...
- Adprep was unable to create the log file %1. Status/Consequence Adprep has stopped without making changes. Adprep uses the ...
- Adprep was unable to create the object %1 in Active Directory Domain Services. Status/Consequence This Adprep operation failed. ...
- Adprep was unable to delete the object %1 in Active Directory Domain Services. Status/Consequence This Adprep operation failed. ...
- Adprep was unable to determine whether Microsoft Windows Services for UNIX (SFU) is installed in this forest or not. Status ...
- Adprep was unable to extend the schema. Status/Consequence The schema master did not complete a replication cycle after the ...
- Adprep was unable to extend the schema. Status/Consequence There is a schema conflict with Exchange 2000. The schema is not ...
- Adprep was unable to initialize global variables. Status/Consequence Usually this means system resources are unavailable. ...
- Adprep was unable to make an LDAP connection to the Active Directory Domain Controller %1. Status/Consequence Adprep requires ...
- Adprep was unable to modify some attributes on object %1. User Action Check the log file ADPrep.log in the %2 directory for ...