Showing posts with label password. Show all posts
Showing posts with label password. Show all posts

Sunday, March 11, 2012

double click SQL Server Express and install with sa password

Hi!

Is it possible to double click the sql server express installer, it will install sql server 2005 in silent mode, set sa password..

Just want alternative of command installation on double click

setup.exe /qb INSTANCENAME=<InstanceName> SAPWD=<StrongPassword>

is it possible

thanks in advance

No, double-clicking the installer will always launch in UI mode, not quite mode.

Mike

|||

Thanks for your answer

Is there any way, the installer automatically checks the settings file while installation. On double click it reads instructions from the ini file and continue installation...

Asif Mahboob

|||

Perhaps these will help.

SQL Server 2005 UnAttended Installations
http://msdn2.microsoft.com/en-us/library/ms144259.aspx
http://www.devx.com/dbzone/Article/31648

Friday, February 24, 2012

domain password policy on 2005

Hi! How do we enforce Sql authenticated logins, the domain password policy?
It looks like by default (once you check the enforce policy box during new
login creation) it uses password policy of local machine, not the domain
policy. My server is in the domain and its running Windows 2003 sp1 and has
sql 2005 sp1 installed and not sure how to enforce the domain policy rather
than local machine policy.
Thanks in advance.the feature is not available at this time.
--
-oj
"james" <kush@.brandes.com> wrote in message
news:%235TtLS4mGHA.4208@.TK2MSFTNGP04.phx.gbl...
> Hi! How do we enforce Sql authenticated logins, the domain password
> policy?
> It looks like by default (once you check the enforce policy box during new
> login creation) it uses password policy of local machine, not the domain
> policy. My server is in the domain and its running Windows 2003 sp1 and
> has sql 2005 sp1 installed and not sure how to enforce the domain policy
> rather than local machine policy.
> Thanks in advance.
>

domain password policy on 2005

Hi! How do we enforce Sql authenticated logins, the domain password policy?
It looks like by default (once you check the enforce policy box during new
login creation) it uses password policy of local machine, not the domain
policy. My server is in the domain and its running Windows 2003 sp1 and has
sql 2005 sp1 installed and not sure how to enforce the domain policy rather
than local machine policy.
Thanks in advance.the feature is not available at this time.
-oj
"james" <kush@.brandes.com> wrote in message
news:%235TtLS4mGHA.4208@.TK2MSFTNGP04.phx.gbl...
> Hi! How do we enforce Sql authenticated logins, the domain password
> policy?
> It looks like by default (once you check the enforce policy box during new
> login creation) it uses password policy of local machine, not the domain
> policy. My server is in the domain and its running Windows 2003 sp1 and
> has sql 2005 sp1 installed and not sure how to enforce the domain policy
> rather than local machine policy.
> Thanks in advance.
>

Sunday, February 19, 2012

Domain Administrator Password Change Fails File output

Windows 2003 Ent.
RS 2000
SQLSERVER 2000 Ent.
The networking group changed the domain administrator password. I have
changed the RS serverice in the control panel. I have changed all the
subscriptions to use the new password. I have used the RSCONFIG with the -e
and -u to supply the domain administrator password change but they still do
not export to the file share. Any responses would be helpfull!!Are the reports rendering correctly? I'd like to view the log files first.
You can zip and email them to me at v-rxwang@.microsoft.com.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Scott,
I've received the log files. From the ReportServerService__<datetime> logs
I can see:
ReportingServicesService!crypto!1114!8/3/2005-20:03:48:: i INFO:
Initializing crypto as user: INTERINTRA\Administrator
ReportingServicesService!crypto!1114!8/3/2005-20:03:48:: i INFO: Exporting
public key
ReportingServicesService!library!1114!8/3/2005-20:03:48:: Exception caught
while starting service. Error: System.Runtime.InteropServices.COMException
(0x8009000B): Key not valid for use in specified state.
This indicates a encryption key and Reporting Services Windows Service
account problem. I suggest that you follow these steps:
1. Backed up ReportServer and ReportServerTempdb
2. Run rskeymgmt -e -f <name> -p <password>
3. Run rskeymgmt -d
4. Restarted the ReportServerservice and access the reportserver via
http://servername/reportserver to activate it.
5. Test and see if the subscriptions still have the problem. If the problem
still exists, zip and email the log files to me again please.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for all your help!
Scott
"William Wang[MSFT]" wrote:
> Hi Scott,
> I've received the log files. From the ReportServerService__<datetime> logs
> I can see:
> ReportingServicesService!crypto!1114!8/3/2005-20:03:48:: i INFO:
> Initializing crypto as user: INTERINTRA\Administrator
> ReportingServicesService!crypto!1114!8/3/2005-20:03:48:: i INFO: Exporting
> public key
> ReportingServicesService!library!1114!8/3/2005-20:03:48:: Exception caught
> while starting service. Error: System.Runtime.InteropServices.COMException
> (0x8009000B): Key not valid for use in specified state.
> This indicates a encryption key and Reporting Services Windows Service
> account problem. I suggest that you follow these steps:
> 1. Backed up ReportServer and ReportServerTempdb
> 2. Run rskeymgmt -e -f <name> -p <password>
> 3. Run rskeymgmt -d
> 4. Restarted the ReportServerservice and access the reportserver via
> http://servername/reportserver to activate it.
> 5. Test and see if the subscriptions still have the problem. If the problem
> still exists, zip and email the log files to me again please.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||It's my pleasure!
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Domain administrator password change

Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
I've just taken over responsability for some servers and I need to
change the domain administrator password.
I was wondering if changing this will have any adverse affects on SQL.
The SQL server is a domain controller. Only the SQLSERVERAGENT service
uses the administrator account.
Will I have any problems "internal" to SQL after the password is changed?
Thanks for any tips.

Hi,
After the change you need to change the password for SQLServer Agent with
new password.
How to change the startup account:-
1. Control Panel - Admin tools -- Services
2. Double click above the SQLSERVERAGENT service
3. In the Log on tab, change the OS user name and enter the password, Click
ok and restart the service.
Thanks
Hari
SQL Server MVP
"David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
> Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
> I've just taken over responsability for some servers and I need to change
> the domain administrator password.
> I was wondering if changing this will have any adverse affects on SQL.
> The SQL server is a domain controller. Only the SQLSERVERAGENT service
> uses the administrator account.
> Will I have any problems "internal" to SQL after the password is changed?
> Thanks for any tips.
>
|||Nice one - thought that was it but always good to check.
Thank you.
Hari Prasad wrote:
> Hi,
> After the change you need to change the password for SQLServer Agent with
> new password.
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the SQLSERVERAGENT service
> 3. In the Log on tab, change the OS user name and enter the password, Click
> ok and restart the service.
> Thanks
> Hari
> SQL Server MVP
> "David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
> news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
>
>

Domain administrator password change

Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
I've just taken over responsability for some servers and I need to
change the domain administrator password.
I was wondering if changing this will have any adverse affects on SQL.
The SQL server is a domain controller. Only the SQLSERVERAGENT service
uses the administrator account.
Will I have any problems "internal" to SQL after the password is changed?
Thanks for any tips.
:)Hi,
After the change you need to change the password for SQLServer Agent with
new password.
How to change the startup account:-
1. Control Panel - Admin tools -- Services
2. Double click above the SQLSERVERAGENT service
3. In the Log on tab, change the OS user name and enter the password, Click
ok and restart the service.
Thanks
Hari
SQL Server MVP
"David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
> Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
> I've just taken over responsability for some servers and I need to change
> the domain administrator password.
> I was wondering if changing this will have any adverse affects on SQL.
> The SQL server is a domain controller. Only the SQLSERVERAGENT service
> uses the administrator account.
> Will I have any problems "internal" to SQL after the password is changed?
> Thanks for any tips.
> :)|||Nice one - thought that was it but always good to check.
Thank you.
Hari Prasad wrote:
> Hi,
> After the change you need to change the password for SQLServer Agent with
> new password.
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the SQLSERVERAGENT service
> 3. In the Log on tab, change the OS user name and enter the password, Click
> ok and restart the service.
> Thanks
> Hari
> SQL Server MVP
> "David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
> news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
>>Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
>>I've just taken over responsability for some servers and I need to change
>>the domain administrator password.
>>I was wondering if changing this will have any adverse affects on SQL.
>>The SQL server is a domain controller. Only the SQLSERVERAGENT service
>>uses the administrator account.
>>Will I have any problems "internal" to SQL after the password is changed?
>>Thanks for any tips.
>>:)
>
>

Domain administrator password change

Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
I've just taken over responsability for some servers and I need to
change the domain administrator password.
I was wondering if changing this will have any adverse affects on SQL.
The SQL server is a domain controller. Only the SQLSERVERAGENT service
uses the administrator account.
Will I have any problems "internal" to SQL after the password is changed?
Thanks for any tips.
Hi,
After the change you need to change the password for SQLServer Agent with
new password.
How to change the startup account:-
1. Control Panel - Admin tools -- Services
2. Double click above the SQLSERVERAGENT service
3. In the Log on tab, change the OS user name and enter the password, Click
ok and restart the service.
Thanks
Hari
SQL Server MVP
"David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
> Hi folks. Sorry if this one's a bit basic, but I'm a SQL 2000 novice.
> I've just taken over responsability for some servers and I need to change
> the domain administrator password.
> I was wondering if changing this will have any adverse affects on SQL.
> The SQL server is a domain controller. Only the SQLSERVERAGENT service
> uses the administrator account.
> Will I have any problems "internal" to SQL after the password is changed?
> Thanks for any tips.
> |||Nice one - thought that was it but always good to check.
Thank you.
Hari Prasad wrote:
> Hi,
> After the change you need to change the password for SQLServer Agent with
> new password.
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the SQLSERVERAGENT service
> 3. In the Log on tab, change the OS user name and enter the password, Clic
k
> ok and restart the service.
> Thanks
> Hari
> SQL Server MVP
> "David Pounds" <david.pounds@.hohohohohohahahahahah.bum> wrote in message
> news:Oaib5H5VFHA.132@.TK2MSFTNGP14.phx.gbl...
>
>
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
Hello,
Yes, if the Windows account used by the SQL Server services has a new
password you should update it here or by using Enterprise Manager.
Also, it would be better if you use a dedicated Windows account for SQL
Server instead of the domain administrator account.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
Are you saying that your SQL Server service is running under domain admin
user account? That is bad, that means SQL Server service can do anything
with the domain, which is really needed.
If the SQL Server service has to access something in the domain (say, you
added some extended procedures that require access files on other
computers), you can use a domain account that is only given proper
permission for just that purpose, using a domain admin account is an
overkill and dangerous.
With that said, the change you described should not affect how SQL Server is
accessed, as long as it still runs.
<bntgoogle@.yahoo.com> wrote in message
news:1194626641.221081.264340@.e34g2000pro.googlegr oups.com...
>A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>
|||Have both servers been rebooted since the domain name and password change?
Regards,
Jamie
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>
|||Jamie
No, the SQL servers were not rebooted, a realization I had only after
we backed off and returned to the previous pwd. That seems to the
other likely reason why it breaks after this.
Put another way, my question is whether the username\password for the
account responsible for the server startup needs to be changed
*separately* after having changed the AD user password...
And oh yeah, I certainly know that is a bad user to use. That is why I
need to change it...
B
On Nov 9, 12:02 pm, thejamie <theja...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Have both servers been rebooted since the domain name and password change?
> --
> Regards,
> Jamie
> "bntgoo...@.yahoo.com" wrote:
>
>
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)Are you saying that your SQL Server service is running under domain admin
user account? That is bad, that means SQL Server service can do anything
with the domain, which is really needed.
If the SQL Server service has to access something in the domain (say, you
added some extended procedures that require access files on other
computers), you can use a domain account that is only given proper
permission for just that purpose, using a domain admin account is an
overkill and dangerous.
With that said, the change you described should not affect how SQL Server is
accessed, as long as it still runs.
<bntgoogle@.yahoo.com> wrote in message
news:1194626641.221081.264340@.e34g2000pro.googlegroups.com...
>A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>|||Have both servers been rebooted since the domain name and password change?
--
Regards,
Jamie
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>|||Jamie
No, the SQL servers were not rebooted, a realization I had only after
we backed off and returned to the previous pwd. That seems to the
other likely reason why it breaks after this.
Put another way, my question is whether the username\password for the
account responsible for the server startup needs to be changed
*separately* after having changed the AD user password...
And oh yeah, I certainly know that is a bad user to use. That is why I
need to change it...
B
On Nov 9, 12:02 pm, thejamie <theja...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Have both servers been rebooted since the domain name and password change?
> --
> Regards,
> Jamie
> "bntgoo...@.yahoo.com" wrote:
>
>
>
>
>
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)Hello,
Yes, if the Windows account used by the SQL Server services has a new
password you should update it here or by using Enterprise Manager.
Also, it would be better if you use a dedicated Windows account for SQL
Server instead of the domain administrator account.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
Hello,
Yes, if the Windows account used by the SQL Server services has a new
password you should update it here or by using Enterprise Manager.
Also, it would be better if you use a dedicated Windows account for SQL
Server instead of the domain administrator account.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
Are you saying that your SQL Server service is running under domain admin
user account? That is bad, that means SQL Server service can do anything
with the domain, which is really needed.
If the SQL Server service has to access something in the domain (say, you
added some extended procedures that require access files on other
computers), you can use a domain account that is only given proper
permission for just that purpose, using a domain admin account is an
overkill and dangerous.
With that said, the change you described should not affect how SQL Server is
accessed, as long as it still runs.
<bntgoogle@.yahoo.com> wrote in message
news:1194626641.221081.264340@.e34g2000pro.googlegr oups.com...
>A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>
|||Have both servers been rebooted since the domain name and password change?
Regards,
Jamie
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>
|||Jamie
No, the SQL servers were not rebooted, a realization I had only after
we backed off and returned to the previous pwd. That seems to the
other likely reason why it breaks after this.
Put another way, my question is whether the username\password for the
account responsible for the server startup needs to be changed
*separately* after having changed the AD user password...
And oh yeah, I certainly know that is a bad user to use. That is why I
need to change it...
B
On Nov 9, 12:02 pm, thejamie <theja...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Have both servers been rebooted since the domain name and password change?
> --
> Regards,
> Jamie
> "bntgoo...@.yahoo.com" wrote:
>
>
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)Hello,
Yes, if the Windows account used by the SQL Server services has a new
password you should update it here or by using Enterprise Manager.
Also, it would be better if you use a dedicated Windows account for SQL
Server instead of the domain administrator account.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"bntgoogle@.yahoo.com" wrote:
> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>

domain administrator password and sql services startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This account:DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
(Cross-posted to microsoft.public.sqlserver.server,
microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)Are you saying that your SQL Server service is running under domain admin
user account? That is bad, that means SQL Server service can do anything
with the domain, which is really needed.
If the SQL Server service has to access something in the domain (say, you
added some extended procedures that require access files on other
computers), you can use a domain account that is only given proper
permission for just that purpose, using a domain admin account is an
overkill and dangerous.
With that said, the change you described should not affect how SQL Server is
accessed, as long as it still runs.
<bntgoogle@.yahoo.com> wrote in message
news:1194626641.221081.264340@.e34g2000pro.googlegroups.com...
>A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>|||Have both servers been rebooted since the domain name and password change?
--
Regards,
Jamie
"bntgoogle@.yahoo.com" wrote:
> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This account:DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
> (Cross-posted to microsoft.public.sqlserver.server,
> microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)
>|||Jamie
No, the SQL servers were not rebooted, a realization I had only after
we backed off and returned to the previous pwd. That seems to the
other likely reason why it breaks after this.
Put another way, my question is whether the username\password for the
account responsible for the server startup needs to be changed
*separately* after having changed the AD user password...
And oh yeah, I certainly know that is a bad user to use. That is why I
need to change it... :)
B
On Nov 9, 12:02 pm, thejamie <theja...@.discussions.microsoft.com>
wrote:
> Have both servers been rebooted since the domain name and password change?
> --
> Regards,
> Jamie
> "bntgoo...@.yahoo.com" wrote:
> > A reality check please...
> > After changing the domain administrator password, we are no longer
> > able to connect to databases on a MS SQL Server 2000 server when
> > attempting to use ODBC drivers from W2K workstations.
> > The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> > \Administrator under the "Logon under This Account" in the 'Logon' tab
> > in services.msc. The server name inside the SQL server are set to
> > mixed mode.
> > Am I correct in thinking that changing the password field shown in the
> > "Login under This account:DomainName\Administrator to match the new
> > domain administrator password will bring Joy?
> > Thanks!
> > Benoit
> > (Cross-posted to microsoft.public.sqlserver.server,
> > microsoft.public.sqlserver.setup, microsoft.public.sqlserver.odbc)

Friday, February 17, 2012

Does Windows 2003 Support Multiple Password Policies?

We have a need to enforce a more stringent password policy for IDs that have elevated privileges or have access to sensitive data.

Can more than one policy be created in Windows Server 2003 (one that expires every 90 days and another policy that expires every 180 days and requires more complexity)? If this is possible, can SQL Server 2005 use these policies and how are SQL authenticated IDs tied to a specific policy?

This question was posted originally in a MSSQL 2005 forum (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=718231&SiteID=1) and it was suggested that I check a Windows forum for planned changes in this area.

Thank you for your assistance.

I think the user/replier meant the Windows communities:

www.microsoft.com/communities

|||

You can create different Group Policy's in Active Directory and apply them to the 90 and the 180 group. If these users use Windows login to SQL - password policies are implemented.

If your users use SQL authentication, you can enforce a password policy on each user. I am not that familiar with SQL 2005 password policies but should be ok to ask users for pwd renewal.

Does this help?

|||

As far as I understand, in Windows 2003 it is possible to have only 1 password policy at any time, but I would suggest asking this question on the Windows Active Directory forum, I am sure they will be able to answer it properly.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks for the info.

I originally posted this in the Windows Server forum, but the forum moderator moved it to the MSSQL forum.

I will post this question in the AD forum.

Does Windows 2003 Support Multiple Password Policies?

We have a need to enforce a more stringent password policy for IDs that have elevated privileges or have access to sensitive data.

Can more than one policy be created in Windows Server 2003 (one that expires every 90 days and another policy that expires every 180 days and requires more complexity)? If this is possible, can SQL Server 2005 use these policies and how are SQL authenticated IDs tied to a specific policy?

This question was posted originally in a MSSQL 2005 forum (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=718231&SiteID=1) and it was suggested that I check a Windows forum for planned changes in this area.

Thank you for your assistance.

I think the user/replier meant the Windows communities:

www.microsoft.com/communities

|||

You can create different Group Policy's in Active Directory and apply them to the 90 and the 180 group. If these users use Windows login to SQL - password policies are implemented.

If your users use SQL authentication, you can enforce a password policy on each user. I am not that familiar with SQL 2005 password policies but should be ok to ask users for pwd renewal.

Does this help?

|||

As far as I understand, in Windows 2003 it is possible to have only 1 password policy at any time, but I would suggest asking this question on the Windows Active Directory forum, I am sure they will be able to answer it properly.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks for the info.

I originally posted this in the Windows Server forum, but the forum moderator moved it to the MSSQL forum.

I will post this question in the AD forum.