Introduction
If you encounter "Google Instances Unavailable" errors upon logging into the CAS admin portal, it signifies that your core infrastructure servers are offline or the WinRM certificate on the servers has expired. This KB article provides steps to resolve this issue by updating the WinRM certificate and ensuring the availability of the core infrastructure servers.
Issue: Google Instances Unavailable Errors
When you log into the CAS admin portal and encounter the "Google Instances Unavailable" error message, it suggests issues with your core infrastructure servers or an expired WinRM certificate.
Resolution Steps
Follow the steps below to resolve the "Google Instances Unavailable" errors:
1. Restart your primary domain controller (PDC or Bastion server for Managed AD deployments):
At times an instance virtual memory can get full causing CAS to fail executing commands via Remote PowerShell. A quick solution to free up this memory is by restarting your instance.
2. Update WinRM certificate via PowerShell(admin session):
Launch PowerShell as an administrator and run the following script below:
Remove-WSManInstance -ResourceUri winrm/config/Listener -SelectorSet @{Transport='HTTPS'; Address='*'}
$FQDN = (Get-WmiObject win32_computersystem).DNSHostName+"."+(Get-WmiObject win32_computersystem).Domain;
$Certificate = New-selfsignedcertificate -dnsname "$FQDN" -certstorelocation "cert:localmachine\my" -notafter (get-date).addyears(3);
New-WSManInstance winrm/config/Listener -SelectorSet @{Transport='HTTPS'; Address='*'} -ValueSet @{Hostname=$FQDN; CertificateThumbprint=$Certificate.ThumbPrint}
- Wait for about 5 minutes.
- Refresh your CAS admin portal.
3. Verify the Issue is Resolved:
- Check if the "Google Instances Unavailable" errors persist.
- If the errors continue, proceed to the next step.
4. Run the Script on Additional Servers:
- If the issue persists after 5 minutes, run the provided script on all your domain controllers, file servers, RD gateway, and broker servers on the CAS side.
- Ensure you follow the same process for each server.
- If the issue still persists, proceed to the next step.
5. Contact Support:
- If the "Google Instances Unavailable" errors persist even after running the scripts on all necessary servers, contact support at support@itopia.com.
- Provide detailed information about the issue, the steps you've taken, and any error messages you're encountering.
6. Alternative Script for Windows 2012 R2:
- If you're using Windows Server 2012 R2, use the following script instead:
Get-WSManInstance winrm/config/listener -Enumerate
NetSh Advfirewall set allprofiles state off
Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private;
& winrm quickconfig -quiet -force;
Set-ExecutionPolicy Bypass -Force;
Enable-PsRemoting -Force;
Enable-Wsmancredssp server -Force;
Set-Item wsman:\\localhost\\client\\trustedhosts * -Force;
Enable-wsmancredssp -role client -delegatecomputer * -Force;
Restart-Service WinRM
#CERTIFICATE RENOVATION
Remove-WSManInstance -ResourceUri winrm/config/Listener -SelectorSet @{Transport='HTTPS'; Address='*'}
$FQDN = (Get-WmiObject win32_computersystem).DNSHostName+"."+(Get-WmiObject win32_computersystem).Domain;
$certificate = New-selfsignedcertificate -dnsname "$FQDN" -certstorelocation "cert:localmachine\my";
New-WSManInstance winrm/config/Listener -SelectorSet @{Transport='HTTPS'; Address='*'} -ValueSet @{Hostname=$FQDN; CertificateThumbprint=$certificate.ThumbPrint}
#END CERTIFICATE RENOVATION
Conclusion
By following these steps, you can address the "Google Instances Unavailable" errors in your CAS admin portal. Ensure that you execute the provided scripts on the appropriate servers and domains as outlined. If the issue persists after completing these steps, reach out to support at support@itopia.com for further assistance.