%11The sender cannot connect to site "%1" over RAS.%12 Possible cause: Remote site server "%2" might be down. Solution: Verify that remote site server "%2" is connected to the network and functioning properly. Possible cause: Remote site server "%2" might not be running RAS Server Service. Solution: Verify that remote site server "%2" is running RAS Server Service. Possible cause: The phone book entry "%3" in the default phone book might not contain the correct information. Solution: Verify that the phone book entry "%3" contains valid information. Possible cause: Share "%4" might not be accessible. Solution: Verify that share "%4" is visible and that the address connection account has the necessary permissions to access the share. For a detailed explanation of the RAS error code, see the Windows NT documentation.%0
The selected task sequence uses an invalid package or application reference. Use task sequence editor to correct the error ...
The selected updates exceeds the maximum number allowed for a single deployment. Reduce the selected updates to {0} or less ...
The sender cannot connect to remote site "%1" over the LAN.%12 Possible cause: Remote site server "%2" might not be connected ...
The sender cannot connect to remote site "%1" over the LAN.%12 Possible cause: Remote site server "%2" might not be connected ...
The sender cannot connect to site "%1" over RAS.%12 Possible cause: Remote site server "%2" might be down. Solution: Verify ...
The sender cannot install secondary site "%1" on server "%2" because it cannot query the status of the Configuration Manager ...
The sender cannot install secondary site "%1" on server "%2" because it cannot retrieve the encryption public key.%12 Please ...
The sender cannot install secondary site "%1" on server "%2" because it cannot stop the Configuration Manager Bootstrap service ...
The sender cannot install secondary site "%1" on server "%2" because some fatal error occured in Configuration Manager Bootstrap ...