Sun, Sep 25 2011 21:57
When the log files give you a clue
I was installing a SBS Essentials and kept getting an error indicating a problem connecting the computer wouldn't do a trust connection to the server.
In digging out the log files (per http://social.technet.microsoft.com/wiki/contents/articles/3887.aspx)
On XP machines the log files are located in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs and on Vista and later under the hidden ProgramData folder.
 110924.220212.0677: ClientSetup: JoinNetwork had errors: ErrorCatalog:CAError ErrorCode:2
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetCert
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetCert(String serverName, String userName, String password, Boolean bForce)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinNetworkTask.Run(WizData data)
 110924.220212.0677: ClientSetup: Exiting JoinNetworkTask.Run
All the known resolutions talked about machine key permissions (which were set right in my case) or a time situationi on the workstations (also set fine in my case). It wasn't until I opened up the Certificate Authority on the server and remembered that I had shifted the date on the server because it wasn't coming up with the right date... and sure enough after I shifted it back, the workstations installed just fine.
It was in looking at the CA and the failed cert deployments that it reminded me of a sequence that occurred in the deployment that might explain this.
The server was accidentally off in it's time. Bottom line this isn't something that you'd normally see, but just remember to look in unexpected places like the Certificate Authority on a SBS Essentials box that might give you a clue of what's going on.
Filed under: SBS Essentials