[monkkey]

Воспользуйтесь runas с ключом /savecredentials

[menpavel]

а какие службы не стартанули? У меня было такое с апачем на винде, пока в зависимость от нужных служб не поставил (уже забыл какие), не работало от имени доменных учетных записей.

[dihlof0s]

Проблема повторилась(

порывшисть в логах нашел вот это:

Код:

Event Type:	Failure Audit
Event Source:	Security
Event Category:	Logon/Logoff 
Event ID:	534
Date:		20.08.2010
Time:		7:40:27
User:		NT AUTHORITY\SYSTEM
Computer:	ural
Description:
Logon Failure:
 	Reason:	The user has not been granted the requested
 		logon type at this machine
 	User Name:	USR1CV81
 	Domain:		ural
 	Logon Type:	5
 	Logon Process:	Advapi  
 	Authentication Package:	Negotiate
 	Workstation Name:	ural
 	Caller User Name:	ural$
 	Caller Domain:	l_ural
 	Caller Logon ID:	(0x0,0x3E7)
 	Caller Process ID:	432
 	Transited Services:	-
 	Source Network Address:	-
 	Source Port:	-


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________________________________________________
Event Type:	Failure Audit
Event Source:	Security
Event Category:	Logon/Logoff 
Event ID:	534
Date:		20.08.2010
Time:		7:40:28
User:		NT AUTHORITY\SYSTEM
Computer:	ural
Description:
Logon Failure:
 	Reason:	The user has not been granted the requested
 		logon type at this machine
 	User Name:	ILSSRV
 	Domain:		ural
 	Logon Type:	5
 	Logon Process:	Advapi  
 	Authentication Package:	Negotiate
 	Workstation Name:	ural
 	Caller User Name:	ural$
 	Caller Domain:	l_ural
 	Caller Logon ID:	(0x0,0x3E7)
 	Caller Process ID:	432
 	Transited Services:	-
 	Source Network Address:	-
 	Source Port:	-


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________________________________________________
Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7041
Date:		20.08.2010
Time:		7:46:43
User:		N/A
Computer:	ural
Description:
The ILS Integration Service service was unable to log on as .\ILSSRV with the currently configured password due to the following error: 
Logon failure: the user has not been granted the requested logon type at this computer.
 
Service: ILS Integration Service 
Domain and account: .\ILSSRV
 
This service account does not have the necessary user right "Log on as a service."
 
User Action
 
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
 
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
_______________________________________________________________________________________________________________________________
Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7041
Date:		20.08.2010
Time:		7:42:07
User:		N/A
Computer:	ural
Description:
The ILS Monitor Service service was unable to log on as .\ILSSRV with the currently configured password due to the following error: 
Logon failure: the user has not been granted the requested logon type at this computer.
 
Service: ILS Monitor Service 
Domain and account: .\ILSSRV
 
This service account does not have the necessary user right "Log on as a service."
 
User Action
 
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
 
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
__________________________________________________________________________________________________________________
Event Type:	Error
Event Source:	Kerberos
Event Category:	None
Event ID:	5
Date:		20.08.2010
Time:		7:40:33
User:		N/A
Computer:	ural
Description:
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server LOUR5$.  This indicates that the ticket used against that server is not yet valid (in relationship to that server time).  Contact your system administrator  to make sure the client and server times are in sync, and that the KDC in realm l_ural.LOCAL is  in sync with the KDC in the client realm.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________________________

и вчера блы проблема у обычных пользователей.
Нескольким юзерам при входе в систему писало "Интерактивный вход в систему на данном компьютере запрещен локальной политикой"
Есть у меня подозрения что всё это связано

а какие службы не стартанули? У меня было такое с апачем на винде, пока в зависимость от нужных служб не поставил (уже забыл какие), не работало от имени доменных учетных записей. »

Служба 1СV8 и Manhattan`a. Серв на котором запускаются службы в домене, но пользователи, под которыми стартуют службы локальные.
После повторного сбоя в домере создал пользователей аналогичных локальным(для запуска служб) на сервере и в политике безопастности домена разрешил им вход в качестве службы.

[monkkey]

пользователи, под которыми стартуют службы - локальные »

Как Вы собираетесь пустить локального пользователя в домен?

The user has not been granted the requested logon type at this machine »

Возможно, у Вас указаны в свойствах учетной записи машины, разрешенные пользователям для входа.

[dihlof0s]

Возможно, у Вас указаны в свойствах учетной записи машины, разрешенные пользователям для входа. »

нее не указаны.
Тут выяснил что Windows "забыл пароль" и для пользователей из под которых делается бэкап в шедулере(пользователи доменные).

Код:

Event Type:	Failure Audit
Event Source:	Security
Event Category:	Logon/Logoff 
Event ID:	534
Date:		20.08.2010
Time:		17:16:55
User:		NT AUTHORITY\SYSTEM
Computer:	URAL
Description:
Logon Failure:
 	Reason:	The user has not been granted the requested
 		logon type at this machine
 	User Name:	myeliseykina
 	Domain:		L_URAL
 	Logon Type:	4
 	Logon Process:	Advapi  
 	Authentication Package:	Negotiate
 	Workstation Name:	URAL
 	Caller User Name:	URAL$
 	Caller Domain:	L_URAL
 	Caller Logon ID:	(0x0,0x3E7)
 	Caller Process ID:	848
 	Transited Services:	-
 	Source Network Address:	-
 	Source Port:	-

пароль в настройках задания шедулера перебиваеш и всё реботает.

[monkkey]

Windows "забыл пароль" »

При смене пароля пользователя в Диспетчере задач необходимо менять пароль вручную.