Ready to watch this entire course?
Become a member and get unlimited access to the entire skills library of over 4,900 courses, including more IT and personalized recommendations.Start Your Free Trial Now
- View Offline
Learn how to choose an edition that's right for your setup, install Windows Server 2012 and the VirtualBox drivers, and then configure the services and roles on your new server. Timothy also shows how to set up local storage and manage Windows Server in one of two ways: through the command line or with the simple admin interface that ships with Windows Server.
- Installing Windows Server 2012
- Installing VirtualBox drivers
- Configuring server roles
- Configuring services
- Configuring disk and file systems
- Using alternative administration methods
Skill Level Beginner
Let's go ahead and take a closer look at services. If you remember, we can go to our Local Server tile and we can get a general overview of what's happening with our services right here in this screen. However, also if you remember, from this screen all we are able to do is start and stop services. We are not able to do anything else with them. To get more detail about a service, and to be able to do more to a service, we need to go up here to the Tools menu, and click the Computer Management, and then click the Services and Applications, and finally click the Services.
This brings up our Service Manager. As you can see in our Service Manager, if we click a service we can get a lot more information about that service. We can get a detailed description of the service, we can also find out the status of the service, what the startup type for the service is, and what component of a system turned it on. In this case, it was Network Sources that turned on the service. Once we have the service up, we can actually stop a running service or start a service that is not running.
We also have the option to restart, that is shut off and then bring back up a service that is currently running. We can start and stop a service by right-clicking on the service and then clicking either the Stop, Restart options, or we can go to Properties where we can get even more detail about it. This Properties will also allow us to change the startup type of the service. In this case, this service is set to run automatically. That means that the server will automatically turn on the service every time it boots up. However, other options are Asaurus maybe turned on manually. That means that this service will only come up when the application that depends on that service is opened. You can also disable a service, which means that it will not come up at all. You may ask, why would I want to do this? Well there are a couple of situations where you may want to manage your services closely like that.
One example is in the process of hardening your server. That means making your server more secure. Microsoft will load and run a lot of services that are not absolutely needed for most functions of Microsoft Server. By referencing information on TechNet and other locations, you can go in and find out exactly which services are needed and which services are not. Once you have determined what services are not needed but are running, you can go in and disable that service, making your server more secure and also more stable.
Another situation where you may want to come into this screen and manage your services is if an application hangs. Many times a hung application will actually be because a service that application depends on has actually stopped working. When that happens, you need to restart the service, and more often than not that will actually solve the problem with your application. Now, example of a, how we would stop a service is we just click on the service, in this case Cryptographic Services. And we either stop it up here from this link, or, we can click Restart, which would actually go through and stop the service automatically, and then restart it automatically.
If you use just the Stop option, you will then have to go through and start it up manually. A service that is very common to cause problems for you on your network is the Print Spooler service. Often times if you have a network printer that stops printing, and the problem is not because of a paper jam or something like that, the problem will often be because this Print Spooler has locked up. So when that happens you just come here find the Print Spooler, right-click it, and restart it.
And, a significant percentage of the time, that will solve your printer issues. However, you'll need to remind any of your end users who have attempted to print something when the Print Spooler failed, that they will need to reprint their document after you have restarted the Print Spooler.