When you run a script or a command against multiple servers in Microsoft Office 365 Dedicated/ITAR, you may receive an error message that indicates that a service is not available or is not running. For example, when you search for message-tracking logs on all transport servers, you may receive the following error message:
Failed to connect to the RPC server on computer TransportServerName. Verify that a valid computer name was used.
On the ANSI-D platform, Office 365 typically upgrades each customer’s Office 365 environment on a 2–4-week cadence. During the upgrade period, computers are pulled from rotation, upgraded, and then reintroduced through an automated rolling process. Computers that undergo an upgrade are not available during the process because the upgrade includes a full operating system reinstall and a reconfiguration of the computer's Exchange Server installation.
Customers should be made aware of this process, as it may cause frequent service failovers that make individual servers are temporarily unavailable. By updating customer-side tooling such as custom scripts, you can minimize customer dependencies on any specific server and, in turn, minimize any potential effects on their businesses. In a high availability design, customers should be able to access mailboxes from alternative servers.