View Complete Post
I have one environment where the Client and Server are part of a workgroup. The Client can access SQL Server 2008 as long as the Client has the same local account (same username and password) on both the Client and and Server.
At home I have a physical SBS 2k3 Server acting as my domain controller. I have a virtual Win7 Client and virtual Win2k8 R2 Server which are both part of my domain. While connected to the domain, I can access the SQL Server 2008 R2 instance on
the virtual Win2k8 Server from the virtual Win7 Client with no problem. I log on to both virtual machines using the same domain account. What I want to know is if there's a way I can set things up so that I can connect to SQL Server on the virtual Win2k8
Server even when my domain controller is unavailable. (Sometimes due to noise and heat issues I don't have my SBS 2k3 server booted up). Ideally I'd like to be able to do this with domain accounts. I can log into the Client and Server machines
even if the DC isn't available it's just connecting to SQL Server that becomes a problem.
I failed to login to my SharePoint Server 2007 since the virtual image is cloned. The trust relationship between the MOSS and DC failed since the duplication of SID occurred. I tried to unjoin and re-join the Windows Server 2008 but the server just stays at
"Applying Computer Setting..." after server reboot.
Thank you for your advice in advance!
We are migrating from Windows Server 2003 domain controllers to Server 2008 Domain controllers. I want to be able to know which domain controller a SQL server is using for authentication, so I can verify that the 2008 Domain Controllers are working,
before we take down the 2003 domain controllers permanently.
I also read something about possibly setting a preferred DC?