Purpose: You get this system event errors: “The Diagnostic Service Host service failed to start.” To start client services of the following:
- Diagnostic Policy Service
- Diagnostic Service Host
- Diagnostic System Host
The above services wouldn’t start because they’re controlled by the domain group policy. Create GPO or edit your Domain Group Policy.
Group Policy Name: Default Domain Policy
Computer Configuration: Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment
Policy Settings: Profile system performance
- Check the Define these policy settings
- Add User or Group: LOCAL SERVICE, Administrators (Administrators is default)
GPO: Default Domain Policy
Link Enabled: Yes
GPO Status: Enabled
WMI Filter: None
An hour later into phone support troubleshooting why users are getting IP addresses of 169.254.193.x at one of our remote sites.
The small business router we have is strictly private network with no internet access. I discovered that the Ethernet cable was plugged in the router’s WAN port. So we have the cable plug in the any of the router’s Ethernet ports, users are getting the router’s DHCP private IP addresses (192.168.0.x).
It’s hard to troubleshoot if you’re not physically there to have the visual of the network setup. Simple network setup we can’t afford to neglect. So trace it down everything! LOL.
The Getmac command with the /s switch to specify a remote computer, and then pipe the output into the clipboard to avoid having to type out the MAC address manually.
getmac /s 192.168.0.1 | clip
Open notepad and press the keystroke Ctrl+V. This operation pastes the output from the previous Getmac operation.
When you create the forest root domain with its first domain controller, all five operations master roles are performed by the domain controller. As you add domain controllers to the domain, you can transfer the operations master role assignments to other domain controllers to balance the load among domain controllers or to optimize placement of a single master operation. The best practices for the placement of operations master roles are as follows:
- Co-locate the schema master and domain naming master – The schema master and domain naming master roles should be placed on a single domain controller that is a GC server. These roles are rarely used, and the domain controller hosting them should be tightly secured. The domain naming master must be hosted on a GC server because when a new domain is added, the master must ensure that there is no object of any type with the same name as the new domain. The GC’s partial replica contains the name of every object in the forest. The load of these operations master roles is very light unless schema modifications are being made.
- Co-locate the RID master and PDC Emulator roles – Place the RID and PDC Emulator roles on a single domain controller. If the load mandates that the roles be placed on two separate domain controllers, those two systems should be physically well connected and have explicit connection objects created in Active Directory so that they are direct replication partners. They should also be direct replication partners with domain controllers that you have selected as standby operations masters.
- Place the infrastructure master on a DC that is not a GC – The infrastructure master should be placed on a domain controller that is not a GC server but is physically well connected to a GC server. The infrastructure master should have explicit connection objects in Active Directory to that GC server so that they are direct replication partners. The infrastructure master can be placed on the same domain controller that acts as the RID master and PDC Emulator.
*The infrastructure master can be placed on the same domain controller that acts as the RID master and PDC emulator.
*It doesn’t matter if they’re all GCs – If all DCs in a domain are GC servers – which indeed is a best practices recommendation, “Sites and Replication” – you do not need to worry about which DC is the infrastructure master. When all DCs are GCs, all DCs have up-to-date information about every object in the forest, which eliminates the need for the infrastructure master role.
by: Dan Holme, Nelson Ruest, and Danielle Ruest
Choose the server type
You can install the following configurations:
Complete – Install all components. Can add server to form a SharePoint farm.
The Complete option installs a Web server and configures the computer to provide application server functionality. It does not provide database functionality. You must provide connectivity and credentials settings to connect to an existing SQL Server instance. Although SQL Server can be installed on this same computer, it is recommended that you install SQL Server on a separate computer.
Note You can also install Microsoft SharePoint Server 2010 for a front-end Web server rather than Complete, but you must use the command line to do so.
Stand-alone – Install all components on a single computer (including SQL Server Express 2008). Cannot add servers to create a SharePoint farm.
A Stand-alone installation configures a single computer with all the necessary files and settings to create a fully functioning SharePoint implementation, including Web server, application server, and database. SQL Server Express is installed and configured to provide data storage capability. Although SQL Server Express is based on the Microsoft SQL Server architecture, it has the following limitations:
- Lack of enterprise features support.
- Limited to one CPU.
- One gigabyte (GB) memory limit for the buffer pool.
- Databases have a 4 GB maximum size.
SQL Server Express will not support a server farm configuration or a multi-processor computer. If you anticipate the need to scale up to a larger or more robust installation, choose the Complete option.
Note You can perform a stand-alone installation either by selecting Stand-alone on this screen or by clicking Standalone on the previous screen. The difference is that by clicking Stand-alone on this screen, you can choose the installation path and define feedback options. After this screen, both options follow the same steps and result in the same outcome.
Switch(config)#line vty 0 15
Switch(config)#enable secret cisco