Can Io swap an existin sql server with iis running an intranet to another domain
we recently acquired a company that has a 2003 with sql 2008 r2 installed and hosting their intranet. we would like to see what can be done about maintaining the functionality of the server but moving it over to domain. what is the best way to make this happen. the sql servers database is heavily integrated into the intranet. We realize that it is not ideal, but need to make it happen quickly. I understand that their will be permission issues that we will need to work through as it pertains to iis and sql. So, how do we go about it? Any help would be appreciated.
Imtiaz Hasham
Is the server a DC? If not, please disjoin the server from their domain to your domain, presuming the IIS is on the same server
ASKER
It is not a dc. Do I need to prep sql in any fashion before disjoining. How about iis
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it for the first part of your answer. What is the easiest way to enable the permissions for the users
Under logins, add DOMAIN\Authenticated Users to allow them permissions to the required Databases
As Imtaz Hasham said... change the domain membership.
If SQL is using service accounts in the previous domain, then create new service accounts in the new domain and us the SQL Configuration Manager console to change the service accounts in question.
About the database permissions - really depends on how the web application is using the database. i.e. could be one account that logs onto the database on behalf of users (proxy account). Bottom line you need to look at current security settings on the databases and see if you need to create new accounts. If the user accounts are based on sql authentication then no changes may be necessary. If based on ntlm authentication, then you would need to create the accounts in AD and SQL.
If SQL is using service accounts in the previous domain, then create new service accounts in the new domain and us the SQL Configuration Manager console to change the service accounts in question.
About the database permissions - really depends on how the web application is using the database. i.e. could be one account that logs onto the database on behalf of users (proxy account). Bottom line you need to look at current security settings on the databases and see if you need to create new accounts. If the user accounts are based on sql authentication then no changes may be necessary. If based on ntlm authentication, then you would need to create the accounts in AD and SQL.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
David, you are right, however, in my opinion, you would need to bring the DC which I believe he doesn't want to do as he wants to move to a his own domain
HI,
>> bring the DC
Or create a new one for the new domain. Kinda gotta do one or the other as its really difficult to have a domain without a domain controller.
Regards
David
>> bring the DC
Or create a new one for the new domain. Kinda gotta do one or the other as its really difficult to have a domain without a domain controller.
Regards
David
They have an existing domain, however, these are two options for them to choose from :)
ASKER
Thanks guys. This gives me several options in my planning.