A new robot is installed on a Windows server. It comes up and is visible in Infrastructure Manager. However, newly installed probes are not starting and the configurations are blank. Checking the folders for these probe, they are blank as well.
Robot was installed to the root of the D:\ drive and not into a folder on the D:\ drive. To access configurations or install probes, the hub probe must navigate from the hub folder, up to the root of the D:\ drive, and then back into another folder. By design, Windows security is preventing file access through the D:\ root.
To resolve, follow the below steps:
After redeployment to a folder, the robot is able to function normally to allow probe deployment and configuration.