forcedexposure
asked on
WinRM error message on SBS 2003 server
Hi There,
I am prepping for an SBS 2003 -> SBS 2011 migration. The initial work is fixing problems identified in Event Viewer / System and also by the SBS Server 2003 Best Practices Analyzer.
Here's one I'm having trouble with:
Event Type: Error
Event Source: WinRM
Event Category: None
Event ID: 10119
Date: 1/30/2014
Time: 9:38:57 AM
User: N/A
Computer: ROLLINS
Description:
The WinRM service is unable to start because of a failure during initialization.
Additional Data
The error code is 1300.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Your help is appreciated!
thanks, Kristin
I am prepping for an SBS 2003 -> SBS 2011 migration. The initial work is fixing problems identified in Event Viewer / System and also by the SBS Server 2003 Best Practices Analyzer.
Here's one I'm having trouble with:
Event Type: Error
Event Source: WinRM
Event Category: None
Event ID: 10119
Date: 1/30/2014
Time: 9:38:57 AM
User: N/A
Computer: ROLLINS
Description:
The WinRM service is unable to start because of a failure during initialization.
Additional Data
The error code is 1300.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Your help is appreciated!
thanks, Kristin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
domain controller policy > Computer Configuration > Windows Settings > Security Settings > User Rights Assignment
go to this link scroll to 'Network Service' and make sure all those policies listed have Network Service in them.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx?mfr=true
go to this link scroll to 'Network Service' and make sure all those policies listed have Network Service in them.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx?mfr=true
ASKER
Hi There!
I ended up removing the Windows Remote Management (WinRM) 2.0 application and it seems to have worked.
thanks!!!
I ended up removing the Windows Remote Management (WinRM) 2.0 application and it seems to have worked.
thanks!!!
ASKER
I'd like to try solution #2 since removing the Windows Management Framework Core update might cause too many other things to fail.
so, regarding this instruction:
"add the NETWORK SERVICE account to the aforementioned policies. "
what are the aforementioned policies?
thanks! Kristin