%11Deployment "%1" from site "%2" was rejected because the deployment has expired.%12 Possible cause: The client received the deployment but rejected it because the deployment expiration date is past. Solution: If the client should accept the deployment, you can extend the life of the deployment by changing the expiration date and time or disabling expiration on the Schedule tab of the deployment's properties. Changes to the Deployment's Properties dialog box will not be detected until the client receives updated policy.%0
Deleting this operating system upgrade package will affect all related objects. It is recommended that you review the effects ...
Deleting this task sequence will affect all related objects. It is recommended that you review the effects of this deletion ...
Delta discovery finds resources in Active Directory Domain Services that are new or modified since the last discovery cycle. ...
Deployment "%1" from site "%2" was rejected because the client's platform is not supported.%12 Possible cause: The client ...
Deployment "%1" from site "%2" was rejected because the deployment has expired.%12 Possible cause: The client received the ...
Deployment "%1" was received from site "%2".%12 The client passes any supported platform requirements and Configuration Manager ...
Deployment schedules determine when software updates will be available and when software update installation will be enforced ...
Desired configuration management allows administrators to define best practice configurations and evaluate computers against ...
Despooler failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either missing or ...