I'm testing the implementation of roaming profiles into my Windows infrastructure and testing on a clean workstation. After adding the workstation to the domain and logging in, I receive the error that the roaming profile could not be loaded, and a temporary local profile is being used. Event Viewer shows error ID 1058, and in the details under EventData, the value for DCName is my secondary (backup) domain controller, not the primary. I logged in to the backup domain controller and successfully verified that the PDC is indeed set as the operations master. All other AD functions on the workstation are operating normally -- DNS, file replication, etc. -- even the path to gpt.ini linked in the event viewer's general details when clicked open right up to the GPT.ini file without issue.
Additionally, the RODC configured at a remote location loses all access to the PDC when I shut down the backup domain controller. Again, operations master is the the PDC. DNS on all workstations, and the RODC, is pointing to the PDC.
Seems like I'm overlooking something relatively simple here. Any thoughts?
EDIT: After re-reading this, perhaps it's pertinent to note that the PDC is indeed online and accessible.