SQL Server 2005 can't be added Active Directory, but the documentation says it can.
Hi,
I've installed SQL Server 2005 on Windows Server 2003 SP1 Standard Edition. Before I install SQL Server 2005, I've configured Windows to be an domain controller with Active Directory. As the documentation said that using Object Explorer and then selecting Properties, I have the property page of Server Properties. But I still can't find the Active Directory page.
When I try to run the system stored proceduresp_ActiveDirectory_SCP, I can't either register or update. Is this an error or bug? Using SQL Server 2000, I can easily add it to Active Directory. Now I can't do it in 2005 version.
Please help!
Eriawan
[676 byte] By [
eriawan] at [2008-2-17]
The Active Directory page was present during a beta version but was removed before SQL Server was shipped. You are correct to use
sp_ActiveDirectory_SCP which should work if you have sufficient permissions. Permissions can easly get messed up. As the topic says, Active Directory registration can only be modified by the account that created it. When you change the security account used by the SQL Server service, delete the Active Directory registration, change the service account, and then create the Active Directory registration again. Thanks. Why MS didn't mention the fact that it was removed before release? This matter should be clarified, and I can't find it on the documentation.
Currently I'm an Administrator of Windows Server 2003, and I also installed SQL Server 2005 using Administrator account. Still, I can't change it! How to delete the Active Directory registration first but I have't register it yet because I can't register it.
I had also change the service account, but maybe I was wrong. Can you explain to me which service account to change?
best regards,
Eriawan
Please answer my questions... I still can't register Sql Server 2005 to my Active Directory domain.
Can somebody help me and also explain to me which service account to change?
best regards,
Eriawan
hi, it's been more than 3 weeks but my question hasn't been answered. Is the updated SQL Server 2005 mention this? I need to know it before I download. I have checked other SQL Server 2005 forums, but still I got no answer.
MS or MCP guys, please answer the question.. I'm getting nowhere...
Or are there any other views?
It's been more than 1 month and I still can't get a satisfactory answers. I have downloaded the SQL Server BOL June 2006, and it's still confusing to me. In fact, it's still a confusing matter on SQL Server 2005 SP1!
Can I get real answer and explanation about this? Otherwise almost all of my clients will get angry and be forced back to SQL Server 2000, since SQL Server 2000 has been nicely integrated into Active Directory either Windows 2000 Server family or Windows Server 2003. Is this really a bug? On the MS connect website, there's also no satisfactory explanation about this.
Am I alone in this thread? Seeting the total viewers of this thread, this thread should prove to me that I'm not alone...
Please help! 
I'll try to check that. Thanks for your kind reply!
I'll inform you whether it's succeeded or not.
Many thanks for your kind reply!
I'll inform you whether it's failed or not.
Eriawan Kusumawardhono
RX Communica
Hi Buck. I've tried and it doesn't work at all! Can you explain it to me step by step? Maybe I was missing something... 
I begin to think this is definitely a BUG, since It's been tested on many machines, also using your suggestions. 
Eriawan K.
It looks like there have been others with this same issue. Check out this thread:
http://dbforums.com/t442597.html
If that doesn't work, I'd recommend contacting Microsoft support. You may have another issue.
Buck
Thanks Buck. It seems there are still many unsolved issues. I've tried to contact Microsoft support but they haven't got the clue yet.
I'm still investigating this with my local MVP in Indonesia for 2 months, and they're able to reproduce the results on many server machines, even after installing Windows 2003 SP1. This is bad, since it's also not documented.
Have you gotten a resolution on this yet? If not, let's revisit the problem and see what we can find out.
Buck
Hi Buck,
I still hasn't been able to solve this problem. Have you tried to reproduce the situation? I have upgraded my Windows Server 2003 SP1 to Windows Server 2003 R2, and it's still the same. I have also upgraded to MS SQL Server 2005 SP1, and it's also out of luck.
Many other forums have said this, and somehow I have to install my old SQL Server 2000 SP3a back since my clients also asked for the good old SQL Server 2000. I know, they won't get fancy things such as native .NET SQLCLR from SQL Server 2005 and also many other new things, but they need to integrate SQL Server to their existing Active Directory infrastructure just like before SQL Server 2005 came in, and I did this too.
I have decided to delay the upgrade to SQL Server 2005 until further Active Directory integration has been solved and clarified. If I insist of upgrading to SQL Server 2005, then I still have to provide evidence that the integration works well, just like SQL Server 200. I've been using and sending feedbacks system on Microsoft Connect website, and I'm out of luck!
.
Do you have any other suggestions? My mind have gone blank about this.
Eriawan
RX Communica
Read this: 