![]() In the results pane, right-click SMS_SITE_COMPONENT_MANAGER. Expand System Status and right-click Component Status. The Preview pane displays the site roles, including the Management Point role, for the site system server. Since IIS is a requirement for the Management Point role, we now have an opportunity to observe how Configuration Manager will behave. However, I failed to install IIS on RKO-SVR1. RKO-SVR1 is configured with the Management Point role on RKO-PS1. In the Configuration Manager console, the new site system displays in the results pane.The Progress page displays and closes upon completion.On the Management Point Database, accept the defaults and click Next.On the Management Point page, accept the defaults and click Next.In the Site code: list, select the site code, RKO. The Select Computer Name dialog box displays.The Create Site System Server Wizard displays.In the context menu, select Create Site System Server.Expand Site Configuration and right-click Servers and Site System Roles.In the Configuration Manager console, select the Administration workspace.Ping the site system server and verify communications is enabled. Verify communications with the site system server.Add RKO-PS1 as member of the local Administrators group on RKO-SRV1.This is the procedure I will follow to configure RKO-SRV1 as a Management Point on RKO-PS1: ![]() You can stand up a similar Hyper-V environment and follow along with me as I discuss the results presented in the post. The machines are configured as Hyper-V VMs. The Configuration Manager version is CM 2012 RTM. The operating system on all servers is Windows Server 2008 R2 SP1. The name of the site server is RKO-PS1, the name of the site system server is RKO-SVR1, and the name of the domain controller is RKO-DC1. In this article, we will examine the situation that occurs when we fail to install IIS on the site system server. This post, and other posts titled “MP Install Failed”, looks at the behavior of Configuration Manager when the target site system server for a Management Point is not properly configured to meet the above requirements. What happens if the site system server you’ve specified as a Management Point does not meet these requirements? BITS Server Extensions (and automatically selected options), or Background Intelligent Transfer Services (BITS) (and automatically selected options.Application Development: ISAPI Extensions.If you use a custom IIS configuration, you must enable the following options for IIS: You can use either the default IIS configuration or a custom configuration. CD into the Exchange setup dir and do the following in an admin prompt: Setup.exe /Role:ManagementTools /IAcceptExchangeServerLicenseTermsĪfter that, everything should be fine and the tools will be available.MP Install Failed-Part 1- IIS Error Code 101Īccording to Supported Configurations for Configuration Manager,, Configuration Manager System Requirements, Site System Requirements, Prerequisites for Site System Roles, the prerequisites for installing a Management Point are listed as follows:ġ) Configure Role Services for the web server (IIS) role. Once that's complete, install the management tools from an admin shell. ![]() So, to get around it, install the required IIS management tools by going to Start > Turn Windows features on or off > Internet Information ServicesWeb Management ToolsIIS 6 Management Compatibility and install IIS 6 Management Console and IIS Metabase and IIS 6 configuration compatibility. It'd make sense if we were installing Exchange, proper, for it to be picky, but this is just the management tools. ![]() Which doesn't tell you anything about the actual issue that's preventing installation which is that this is an insanely picky install. The exact error message is: Error:The target of the specified cmdlet cannot be a Windows client-based operating system. Update : The below process also reportedly works with Windows 10. Unless you've already installed the IIS components required by Exchange you'll get an extremely unhelpful error message when trying to install, saying that it cannot be installed on a client-based OS. Trying to install Exchange 2013 Management tools on Windows 8.1 is likely to present some problems by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |