Archive

Posts Tagged ‘Windows Server 2003’

Level Platforms install does it all, but must add MWService to admin groups

March 7th, 2012 No comments

Summary:
While installing Level Platforms (LPI) Onsite Manager onto a Windows Server 2003 (a member server running on as and ESXi guest and added to a SBS 2003 domain) all went well, but one service would not start. Final, solution was that the MWService account did not have sufficient permissions. LPI tech support said to add that account to Administrators, Domain Administrators and Enterprise Administrators. This solved the problem.

Details:
After installation and during the registrationI entered my VAR domain and clicked Register, I received the message, “Unable to start Windows Service OMNetworkService.” When I ran services.msc and tried to start the OMNetworkService service, it attempted to, but then reported: “Could not start the OMNetworkService service on Local Computer. Error 1053 The service did not respond to start in a timely fashion.

Located the other LPI service, MWExpertSystem.  That service was running, but I restarted it and the started OMNetworkService. I still received the same error that it could not be started.

I consulted the LPI forums and found some suggestions that I make sure the MWService account be flagged as “Password never expires.” It already was.

I also checked the Local Security Policy and found that the MWService account WAS listed under the “Log on as a service” right.

I rebooted the Onsite Manager as a test and it came up with the message you’ve seen at server rebooting saying that some serices could not be started.

I attempted to use the OMTools – Stop OM Services + Start OM Services. Didn’t work.

I attempted stopping MWExpertSystem and starting OMNetworkService first. Didn’t work.

When I checked the Application log I found a .net error:

Event Type:    Error
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:    None
Event ID:    5000
Date:        12/17/2008
Time:        8:15:36 AM
User:        N/A
Computer:    MEMBER1
Description:
EventType clr20r3, P1 omnetworkservice.exe, P2 6.0.4.492, P3 48ca784e, P4 mscorlib, P5 2.0.0.0, P6 471ebc5b, P7 e4, P8 10, P9 system.security.security, P10 NIL.

An issue with .net. Considered working down that line, but eNerd Chris Polis, contacted LPI support.
LPI support tech Paul Savoie wrote:

Event ID 5000 is usually indicative of a rights issue with the account used for the services. Can you please have your tech confirm that the MWSERVICE account is a member of Domain Admin, Enterprise Admin, and Administrators groups.
A quick test to confirm this is the use the domain admin account for the service and see if it starts up correctly.

I did not try the latter, but made changes to the MWService account. Rebooted the server for good measure and the services fired right up.

Other comments from LPI (Jocelyn Sirois) regarding SBS setup:

Make sure the MWService account is added to the SBS group that is allowed access to the Internet. The LPI installation cannot do this. This is a default group created by the SBS default installation.
Verify that the logon credentials for the OMNetworkService  are the correct one.
If using ISA there are other considerations for some of the protocols.
The File and Print services on the SBS server must be enabled.

How to copy folders and keep NTFS and Share Permissions

February 3rd, 2011 2 comments

I have a client that has created a template folder structure for their client files that has the required permissions set up on them.

What the client wants to do is copy this template structure to a new folder whenever they get another client and keep the folder security that they have applied to their template folder structure.

And here is how it can be done.

Read more…

Remote Desktop suddenly stops accepting connections

February 1st, 2011 No comments

I came across a problem at one of my clients today where remote desktop stopped working on a Windows 2003 Server. (Although this also affects Windows 2000 Server)

I have searched the internet for causes, and the most likely reason is due to an update that is installed.

Further investigation led to a solution in Microsoft KB555382.

Read more…