Great article once again! I am currently installing the Exchange 2010 SP2 tools on a Server 2008R2 box in preparation for O365 integration. I am on the Readiness Checks portion of the install and had a quick question. If I already have an Exchange 2003 organization, will the setup /prepareAD have any effect on my current server if I choose to go ahead with this install? I have already introduced two 2008 Domain Controllers to my 2003 Fully Functional environment.
I am in a public school district and connect to a statewide Exchange server on which I have local rights. The statewide Exchange server connects to Office 365. I am trying to find where the install process looks for the name of the Exchange server, since it never asks for the domain during installation. Another Technician I work with has this working on his desktop and we both support the same functions.
Or will I have to install the entire server 2008 with AD in order to have a successfull restore? The original Internal Name consisted of over 15 characters so installing with same name is unsuccesful and using the Answer file is unsuccesful because its looking for the Source Server which does not exist anymore.
I have been searching around for informatio and found your article. Thanks for writing this, I have a question regarding the poerating systems.Do you have information/experience installing Exchange Management Tools 2010 on a Windows 2003 64 server? The Exchange server is 2008R2, Exchange 2010R2. Our backup software is requiring the tools but I am concerned they do not function on a 2003 server.
I check and see this service is running on all 4 of our exchange servers. I have no problem running the management tools on any of the exchange servers, but several tries reinstalling the management tools on my system all resulted in this error.
This service is an optional component that can be installed on Windows Server 2008 R2 or Windows 7 as part of the IIS Web Server package. If the World Wide Web Publishing Service stops, the operating system cannot serve any form of web request.
There is no difference with the firewall disabled on the HV/NAT server. On the guest/website server, I get the following message when I try to access Windows Firewall: "Windows Firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)." (This is a Windows 2003 SP2 guest running IIS 6.0 and RRAS, but NAT is not installed/enabled. The website itself runs from Apache Tomcat.)
I gave this a shot and did an in place upgrade on our site server thats running wds, iis, and wsus. I followed the steps to re enable wsus services and go through the post installation tasks. When I click on the post installation tasks to finish it up, it errors out and disables the W3SVC service. Any ideas?
Group Managed Service Accounts superseded MSAs, which in Windows 7 and Windows Server 2008 R2 (both no longer supported). Please use this updated link for more current information: -us/windows-server/security/group-managed-service-accounts/group-manage...
Warning:If ArcGIS Server is already installed and running on the same Web site where ArcIMS is to be installed, then IIS is being run in 32-bit mode. Follow the steps for 32-bit installation. Uninstall any unsupported versions of Java, Web Server, or Servlet Engine. For more information, refer to How To: Uninstall ArcIMS-related third-party software on Windows.Install Java 2 Standard Edition Development Kit version 6 Update 16. A. Click J2SE Development Kit (JDK) 6 Update 16 to download Sun Java 2 SDK, Standard Edition, version 6 Update 16.B. Click Download JDK.C. Select a platform, and accept the license agreement.D. Click the download link for Java SE Development Kit 6u16. The file jdk-6u16-windows-i586.exe is downloaded.E. Run the installer after it has finished downloading.F. Accept all of the default installation options, unless changes are required. This installs both the Java Runtime Environment (JRE) and the Development Kit. Note:Registration of Java is optional.G. Navigate to Start > Settings > Control Panel > Java. On 64-bit machines, from the Control Panel select the View x86 Control Panel Icons folder.H. Click the Update tab, and uncheck Check for Updates Automatically.I. Click Apply, and close the Java Control Panel. Install Microsoft IIS if it is not already installed.A. Navigate to Start > Control Panel > Programs and Features. B. On the left, click Turn Windows features on or off. C. On the left, Click Features. D. Scroll down and under Features Summary, click Add Features.E. In the Add Features Wizard, expand Remote Server Administration Tools, expand Role Administration Tools, and check Web Server (IIS) Tools. Click Next.F. Click Install.G. Once complete, click Roles on the left.H. Click Add Roles.I. In the Add Roles Wizard, click Next, check Web Server (IIS), and click Next twice.J. In the Select Role Services window under Web Server > Application Development, checkASPISAPI ExtensionsISAPI FiltersK. Scroll down, and under Management Tools > IIS 6 Management Compatibility, check IIS 6 Metabase Compatibility. Click Next. L. In the Confirm Installation Selection window, click Install. M. In the Installation Results window, verify that the installation was successful, and click Close.N. Once complete, restart IIS by clicking Start and typing IISRESET in the Search box. Or go to Administrative Tools > Services and restart the IIS Admin Service and World Wide Web Publishing Service.O. Open the IIS Manager by navigating to Start > Programs > Administrative Tools > Internet Information Services (IIS) Manager.P. Expand the server host name and Sites on the left. Select the Default Web Site.Q. Under Default Web Site Home, right-click on MIME Types, and select Open Feature. R. In the Actions panel, click Add to open the Add Mime Type dialog box.S. Type 'axl' in the File name extension field. Type 'text/xml' in the Mime Type field. Click OK. Warning:The version of Tomcat used in this article is 32-bit, thus the 32-bit version of Java must also be used (including 64-bit machines). Install Tomcat 6.0.18. INSTALL TOMCATA. Go to the Apache Tomcat 6.0.18 Download Site.B. Click apache-tomcat-6.0.18.exe to download the file. Save it on the local machine.C. Navigate to the download folder, and double-click apache-tomcat-6.0.18.exe.D. Click Next.E. Read the License Agreement, and click I Agree.F. In the Choose Components dialog box, change the type to Full install, or alternatively, only select the Service and Examples features.G. Click Next.H. Select the preferred installation location; for example, the default C:\Program Files\Apache Software Foundation\Tomcat 6.0 or C:\Tomcat6.0.I. Select the default settings in the Configuration dialog box. Create a new password for the Tomcat Administrator. Click Next.J. If the path is not set automatically, map the path of the installed JVM to the location of the Java Standard Development Kit; for example, C:\Program Files\Java\jdk1.6.0_16. Click OK. Note:If a path to an older SDK version is listed, cancel the Tomcat installation. Make sure that a Java SDK is installed, and make sure that the environment variables, JAVA_HOME and PATH, do not include any old entries regarding the Java Runtime Environment and that they are pointing to the J2SDK location correctly. K. Click Install to continue. Click Finish.SETUP OF ENVIRONMENT VARIABLESL. Right-click My Computer, and click Properties > Advanced tab > Environment Variables button.M. Under System Variables, click New. When prompted for Variable Name, type JAVA_HOME, this is case sensitive. For the Variable value, type the path where Java 2 SDK is installed; for example, C:\Program Files\Java\jdk1.6.0_16. Click OK.N. In the System variables list, scroll to the Path variable, select it, and click Edit. In the Variable Value text box, add the following to the end of the text, including the semicolon to separate it from previous entries:;%JAVA_HOME%\bin.O. Verify that old references to JAVA_HOME in the path variable have been removed; for example, \jdk1.3.1. P. Click OK twice to close the Properties window.Configure Tomcat for IIS. DOWNLOAD CONFIGURATION FILESA. Download the configuration files for Tomcat: 6.0.13:Tomcat6013_IIS_IMS93_win.zip. INSTALL IIS REDIRECTOR FOR TOMCATB. Extract the downloaded .zip file to a location on the hard drive.C. Navigate to \bin in Windows Explorer.D. Create a new folder, and name it 'win32' in the bin folder. Note:Important: If using a 64-bit machine, create a folder 'win64' instead.E. Copy the isapi_redirect.dll from the location where it was originally extracted, to the newly created win32 folder; for example, \win32. Note:If using a 64-bit machine, copy the file isapi_redirect_1.2.27_amd64bit.dll to the 'win64' folder and rename it isapi_redirect.dll.CONFIGURE PROPERTIES FILES Note:Important: If using a 64-bit machine, replace any paths referencing the /win32 directory with /win64 in the steps below.F. Copy the files 'workers.properties.minimal' and 'uriworkermap.properties' from the temporary location, from step A, to \conf.MODIFY WEB.XML FILE G. Navigate to \conf, and open the file 'web.xml' in a text editor.H. Search for the following text: Delete the comment lines ',' so the code appears as shown below: invoker/servlet/*I. Search for the following text: --> Delete the comment lines '', so the code appears as shown below: invoker org.apache.catalina.servlets.InvokerServletdebug02 J. Save and close the file. K. Edit the file 'context.xml.'Find the file 'context.xml' in \conf, and open it in a text editor.Add the parameter privileged="true" into the tag at the beginning of the file. The first two lines of the file should look like this:Save and close the file.CONFIGURE THE REGISTRY Warning: It is recommended that you backup your operating system and files, including the registry, before proceeding. The instructions below include making changes to essential parts of your operating system. Consult with a qualified computer systems professional if necessary.Esri cannot guarantee results from incorrect modifications while following these instructions. Therefore, use caution and proceed at your own risk.The registry file Win_IMS93_IIS_Tomcat60.reg is configured for Tomcat 6.0.13 installation at the location C:\Program Files\Apache Software Foundation\Tomcat 6.0. If Tomcat was installed to C:\Program Files (x86)\... or a custom location, open the file in Notepad, and make the appropriate changes to reflect the installation location. Note:If ArcGIS Server is installed on the same machine as ArcIMS, then IIS is being run in 32-bit mode. In this case, it is necessary to adjust the second line in the registry file to read:[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Jakarta Isapi Redirector\1.0] L. Double-click the registry file Win_IMS93_IIS_Tomcat60.reg in the location where it was extracted to execute it.M. Click Yes and OK. This creates the necessary registry keys for Tomcat.CONFIGURE IISN. Open Internet Services Manager.O. Under Internet Information Services, expand the contents of the host machine name.P. If a Jakarta virtual directory already exists in IIS, delete it.Q. Create, or re-create, a Jakarta virtual directory as follows:Right-click Default Web Site, and select Add Virtual Directory. This opens the Virtual Directory wizard.In the Alias box, type Jakarta.3. For Physical Path, browse to \bin\win32. Click OK.R. Add Jakarta ISASPI filters as follows:Click Default Web Site, and from the list on the right, double-click ISAPI Filters.In the top right of the screen, select Add.Type Jakarta for the Filter name.For the Executable, navigate to \bin\win32\isapi_redirect.dll.Click OK.INTEGRATED WINDOWS AUTHENTICATIONS. In IIS Manager on the left, navigate to and click Default Website, double-click Authentication, and click Anonymous Authentication. Verify that it is enabled.T. Navigate back to Default Website, expand it, and select Jakarta. Double-click Authentication from the middle panel. Click Anonymous Authentication. Verify that it is enabled.U. Click Jakarta. Double-click Handler Mappings. If ISAPI.dll is disabled, select Edit Feature permissions, and enable Execute.ADD ISAPI RESTRICTION Note:This is equivalent to setting up a Web Service Extension in IIS 6.V. Add an ISAPI restriction as follows:Under Connections on the top left, click the host name of the machine.From the IIS list on the right, double-click ISAPI and CGI Restrictions.In the top right of the screen, select Add.For Description, type Jakarta.For the ISAPI path, navigate to \bin\win32\isapi_redirect.dll.Check the box to Allow extension path to execute.Click OK.Configure the directory permissions for IIS and Tomcat.A. Open Windows Explorer.B. Navigate to :\.C. Right-click the directory, and select Properties.D. Select the Security tab.E. Add the following accounts:Authenticated UsersIUSR_ or IUSRF. Set the following permissions for the above accounts:Read & ExecuteReadWriteG. Navigate to the :\\bin\win32 folder. H. Right-click the *.dll file. Select Properties.I. Select the Security tab.J. Add the following accounts:Authenticated UsersIUSR_ or IUSRK. Set the following permissions for the above accounts:Read & ExecuteReadWriteRestart IIS and Tomcat. A. Go to Start > Settings > Control Panel > Administrative Tools > Services.B. Right-click the Apache Tomcat service, and select Restart.C. Right-click the IIS Admin service, and select Restart. Click Yes if asked to restart the other services.D. Verify that WWW Publishing Service is started. If not, start it. Verify IIS and Tomcat were installed successfully. A. Open the Windows Services panel. Select the Apache Tomcat service from the list and start it.B. Enter this case-sensitive URL into a browser: page that says 'Hello World' displays if the test is successful. Warning: If this test fails, check the URL carefully for case or spelling issues. Retrace the installation steps. The URL may work if 'http://:8080/...' is specified. This only indicates that the Tomcat Web server is working on port 8080; the required redirect to IIS is failing.C. Return to the IIS Management Console > Default Web Site > Properties. Check the ISAPI Filters tab. Verify that there is a green, upward arrow next to the Jakarta filter.Note:This only applies to IIS 6; IIS 7 does not have a way to check if the ISAPI filter is working. Warning:If there is not a green arrow next to the Jakarta filter, stop and re-start the IIS Admin Service, including the WWW Publishing Service, from the Services panel. If that does not work, open a browser, and type ' ' to re-initialize IIS. If the Jakarta filter still fails, do not proceed further. Go back and verify the settings created in the previous steps.D. Return to the IIS Management Console > Default Web Site > Jakarta. Verify that the Jakarta virtual directory is pointing to the correct location on the hard drive, the location of the isapi_redirect.dll.Install ArcIMS from the installation DVD/download. Refer to 'Step 3a: Installing ArcIMS' in the ArcIMS Installation Guide.To configure ArcIMS and run the ArcIMS Post Installation, see 'Step 3b: ArcIMS post installation setup' in the ArcIMS Installation Guide.Verify that the ArcIMS installation was successful. A. Navigate to Start > Programs > ArcGIS > ArcIMS > ArcIMS Diagnostics.B. Verify that the Web server protocol and the Web server name are correct, including the domain and port number. The default is port 80. Note:On Windows XP/2003 machines, Internet Explorer sometimes does not show the host name and port number. If this is the case, right-click near the top of the window, and select Allow Blocked Content.C. Test both components. The results for Test 1 should be:IMS v10.0.0Build_Number=183.1916Version=10.0.0Test successful The results for Test 2 should be:Version=10.0.0Build_Number=183.2159Test successfulIf these tests are successful, the ArcIMS Application Server and ArcIMS Servlet Connector are configured correctly. If an error message is received, select the error number from the drop-down list, and click View. The error number and a description appear. Follow the instructions in the description to fix the problem, and run the Diagnostics tool again.For additional steps in ArcIMS, refer to Steps 4 and 5 in the ArcIMS Installation Guide.To get the ArcIMS Web ADF for the Java Platform or for the .NET Framework setup, refer to the following Installation Guides: ArcIMS Web ADF for the Java Platform ArcIMS Web ADF for the Microsoft .NET Framework 2b1af7f3a8