none
What is the OU? RRS feed

  • Question

  • I use batch files to install and setup SQL Server 2005.  One of the first things done is to use dsquery to check that the computer is in the correct OU - other OUs have policy that remove rights from local groups.  I need to install SQL 2005 on a Windows 2008, but I get an error running dsquery.  Should I manually add the AD DS server role to enable dsquery?  (This seems to be as much work as just manually checking the OU from my desktop.)  Can anybody recommend a good and quick way to test the OU from a command file?  Is there a registry setting or such I can read?  Thanks. 

    Thursday, September 25, 2008 6:00 PM

Answers

All replies

  • Hi,

     

    Have you tried installing SQL Server 2005 SP2 on Windows Server 2008. You may want to visit the link below which might be helpful for you -

     

    http://support.microsoft.com/kb/936302

    http://msdn.microsoft.com/en-us/library/ms143506.aspx

    http://www.microsoft.com/sql/howtobuy/windowsvistasupport.mspx

     

    Hope above helps.

     

    Thanks.

    Thursday, October 9, 2008 3:21 PM
  • SQL Server 2005 is installed on Windows 2008.  I manually checked the OU in this case.  The issue is not with the SQL Server install, but a prior step to insure the OU is correct.  As a DBA, I'm looking for an easy way to check the OU - read only - of the machine I'm logged directly into as an administrator without opening a security hole.  I want this method to work for other DBAs that don't have the Windows Server Administration Tools Pack. 

     

    Because of the short lifecycle of our servers, DBA finds itself building new SQL Servers all the time.  To make it easier on us, I created series of batch files to install and configure the servers.  We must first check the OU make sure we don't end up with a corrupt server.  If an install takes place while the machine is in the incorrect OU, group policy will remove critical permissions created during the SQL Server install - requiring later reinstall or a repair.  The old dsquery method to check the OU does not work out of the box on Windows 2008. 

     

    If the SQL server install had a warning that domian policy will eventually remove the rights installed, I would not need to check the OU.  Until this is a feature, I want my script to error until the server team corrects the OU. 

     

     

    Thursday, October 9, 2008 4:03 PM