IIS 7 & IIS 8
UI & Remote Management
IIS7 Remote Admin Manager Connections
Last post May 02, 2011 06:23 AM by HCamper
Apr 30, 2011 05:11 PM|LINK
Well.. Tech Support have told me that they used my Id to login, and have suggested that I uninstall the IIS manager and download again, and then try it. I guess that is a good idea.. however, I can't seem to get rid of the thing!
I went to "programs & features" in the control panel, and removed it from there. But that didn't seem to do anything. (Do you have to reboot for the files to finally disappear, by chance?)
I have the following folder structure at this location (which is where it appears to be downloading the assemblies when I create a connection that isn't working):
And have the following folder structure at this location (where the executable for IIS is found):
<other files with .exe .dll, msc & xml extensions>
<files with .ini extensions>
<files with .ini extensions>
<files with .config extensions>
<files with .config extensions>
<files with .xml extensions>
<files with .xml extensions>
<files with .xml extensions>
<files with .mui, mfl, & .msc extensions>
<files with .mui, mfl, & .msc extensions>
So should I just delete those files/folders manually? I am a bit nervous about doing that in the system32 folder (if I am even allowed.) Otherwise, what should I do to remove what I installed and start again.
Actually I should explain, that after I downloaded the application the first time (via some installer: RemoteManager.exe), it didn't appear to work, so I tried installing it again, and it asked if I wanted to repair it.. so I did. And then later when it
still didn't work, I went to a different location (one recommended by the hosting company) and downloaded the .msi file directly. I am now wondering if this has been the root of my problems. As I look above, it appears that the same .dlls appear in two different
locations (in AppData\Roaming\Microsoft\WebManagement
and Windows\System32\inetsrv). Could this be causing the problems, and explain why one connection works, and the other doesn't?? eg: the connection that works looks in the correct location, and the connection
that doesn't work looks in the other location? Or is this the way it is supposed to work with the files in two different directories?
Anyway, please tell me how to remove it all, so I can start fresh.
Once I get all the files removed, I will use the link that my hosting company provided to download the IIS7 manager (inetmgr_i386.msi), from this location:
Is that OK? (This is the one I downloaded the last time).
Apr 30, 2011 11:03 PM|LINK
Do not remove any of the files in C:\Windows\system32\inetsrv. You can only cause problems in this location.
The IIS Manager will be installed to C:\Program Files\ for X64 program or C:\Program Files (x86) for X86 program.
Your best option maybe using the Windows Installer Version from Microsoft Download Center
which is the location for the inetmge_386.msi.
Yes You should do a restart since they provided a custom package which may still have "inuse" files.
The Roaming Folder is where the Winhost Shared files have been "Parked" and they may go away after the restart.
May 01, 2011 07:07 AM|LINK
Hi HCamper, thanks for the reply.
I have tried absolutely every step I can think of.
I have started off with a fresh reboot.
Uninstalled my previous installation.
Permanently turned off Antivirus, Antispyware, Smart Firewall, Intrusion prevention, etc.
At this location:
clicked on inetmgr_i386.msi download button, and save to PC
double click on the inetmgr_i386.msi just downloaded from PC
Pop-up window asks if I want to run, click on run
IIS7 Manager Setup window displays: click Next, accept agreement & click next, save manager to C:\Program Files\IIS\IIS Manager 7\ & click next, click install, (please wait while the Setup wizard installs IIS7 Manager.), give permission, click
Readme.txt at: C:\Program Files\IIS\IIS Manager 7\ (Note: this is the
only file located at this directory.. which seems strange as you said this is the location where the installation is written to.)
click on run start button, and in the start search field type in
inetmgr.exe (found in system32/inetsrv - Note: can't tell if it has been updated by this installation or left there from previous install).
right click and run as administrator. (thought I would cover my basis!)
The last time I installed, I did optinest.com first. So I thought I would try doing optimation.com first this time. I have documented every step of the way, every keystroke, every pop-up window content, and you can read it here:
www.optinest.com/images/Optimation_Optinest_IIS7_remote_connection_sequence_only.pdf. (Sorry, I don't know how to attach a document to this post!)
You will see that, once again, the optimation.com connection works great, but the optinest.com one does not.. still only showing the one rewrite module.
You will note that when the optinest.com connection occurs that it is trying to download some strange modules that were not included in the optimation.com connection. In addition, these are 'not recognized as Microsoft'.
Please review the whole document, and tell me if you see anything.
The very fact that I have totally re-installed, eliminated firewall issues, ran as administrator, etc, and ended up with the exact same results, where one connection works, and the other doesn't is very strange.
I closed down
the IIS7 Manager, and then did another reboot, and then restarted the IIS7 Manager (via Start Button search for: inetmgr.exe).
This time without executing as admin (so I had to give it permission to execute).
When I clicked on my previous optimation.com connection, it asked for a login, and then displayed fine. However, when I clicked on my previous optinest.com connection, after it asked to verify
the login, it wanted to download those same two strange assembles as it tired before. (See my document). But it doesn't matter if I elect to down load them or don't, the net result is always that I only see the one module for optinest.
What are those modules that optinest.com is trying to download that optimation.com doesn't need, and that don't appear to get installed (even though I try to install them), and thus
don't allow optinest to show any other modules???
Tech Support at my hosting company says they have tried this connection from several different PCs, all using my login, and it works fine.. so they are insistent that it is my PC's installation of the manager that is the problem..
What else can I try?
Also, when I look up system info this is what it says about my PC:
OS Name: Microsoft Windows Vista Business
Version: 6.0.6001 Service Pack 1 Build 6001
System Type: X86-based PC
So am I correct in assuming that means I need to install the x86 version, and not the x64 version? And the
inetmgr_i386.msi is the x86 version?
And can you verify that I did download the correct file from the correct location at Microsoft's website?
May 01, 2011 11:18 AM|LINK
Ok. Then you got the Remote Manager installed.
The Confusion you maybe experiencing is where the IIS Manager(s) are Launched from:
You should not need to use inetmanager from the program files folder.
Instead go to Administrator Tools you may have two IIS Managers shown.
You should be able to open either one IIS Manager and in Left Hand Display you should see
your Local Server for your system as "Default" and then Names for other Servers you have made connections to.
http://learn.iis.net/page.aspx/113/getting-started-with-iis-manager/#New picture helps
for what you should see for IIS Manager.
http://support.winhost.com/KB/a628/using-the-microsoft-iis-70-manager.aspx no pictures
information at Winhost for Site Login and Use helps with getting the Host Name added for Remote
Here is a Winhost setup
In particular for Winhost use their Control Panel for "The IIS Manager user name for your site can be found in the
Site Tools" and use
that for "Site name: Your domain name without "www" Login and Host Name.
May 01, 2011 02:03 PM|LINK
I was away for some time, i usually don't read the forum during weekends.
Anyway, it was great information you gave us. From what i can see, optimation.com runs on an IIS 7 server. optinest.com runs on an IIS 7.5 server. Most likely, you had all the required modules on your machine to administrate IIS 7. But when you try to administer
IIS 7.5, IIS Manager notice that there are other versions of the assemblies, and downloads them from the server. Most likely, this is were it fails.
Unfortunately i don't know where the log file is located, but it would be interesting to see if the installation of the new modules failed or was successfull. It probably fails by some reason, but the question is why.
May 01, 2011 02:46 PM|LINK
I am doing some more testing. Do you connect to optinest.com, or optimati.w05.winhost.com? I am asking because optimation.com has an Apache server as front-end and optinest.com has an IIS 6.0 machine as front-end. I am wondering if this is confusing for
the application, and the files are not stored at the expected location, hence it cannot find them and their modules are not available in the GUI.
May 01, 2011 06:37 PM|LINK
Thank you to both Martin (HCamper) and Kristofer for your continued support.
I will reply to Martin first.
Just to clarify, I have been launching the IIS7 Manager only from
C:\Windows\System32\inetsrv\ (via the start menu's search bar, entering inetmgr.exe), which is the exact same place it gets executed from if I go through Administrator Tools. (Note: My Administrator Tools only has one shortcut
listing for "Internet Information Services [IIS] Manager")
I am unsure if I can see what you were refering to as the "Local Server for your system as "Default"" in the left-hand side for connections. It only says 'start page', and then lists the two
connections I have created.. for optinest.com & optimation.com.
Note: There are no subdirectories listed for either site connections. That is probably because I haven't uploaded any files to the optimaton.com hosting area. I have files in the optinest.com
hosting area.. but obviously can't see them listed yet, since I am not getting a proper module display to optinest.com.
You can see a screen print of what all the pages look like by clicking on these links:
As you can see - I can login, and connect to both sites. That isn't the problem.. it is just the lack of modules being displayed on optinest.com.
Wow.. this is making more sense to me.. I really did feel there was something different on the server side, because it just didn't make sense that I could seem to have a successful install, and
have it proven with my successful connection to optimation.com, but still have problems with optinest.
And the fact that the Tech Support people at WinHost are able to login might have to do with the possibility that they have a newer manager version? If you look at the screen-print they provided
as can be seen here:
www.optinest.com/images/IIS_Host_optinest.png, you will see that they have extra options at the top of their features view page (eg: "filter" & 'show all'). Is that something you can setup as options, or is it indicative of
a different manager version than I have?
Is there some way I can find out where the log files could be located? Although, I never get an error when I try to download those last two groups of assemblies for optinest, so maybe it doesn't
get logged as an error? It just looks like it has completed, and I can see the progress being displayed with messages like: "downloading...", "validating assemblies...", and "validated
I know I have files associated with IIS7 in the directory: C:\Users\xxx\AppData\Roaming\Microsoft\WebManagement\220.127.116.11\Modules\,
and also in the directory:
C:\Windows\System32\inetsrv\. I think I have provided the files structure for these two locations to you before, and have said there appears to be duplicate .dlls between them. There aren't any real files for IIS located in Program
files (ie here: C:\Program Files\IIS\IIS Manager 7\). I am not sure where else to look.
With the IIS7 Manager, I have tried connecting to optinest.com using either "w05.winhost.com" or "optinest.w05.winhost.com" as the server name.. both fail to display all the modules. (Note: conversely,
I have also tried connecting to optimation.com using either "w04.winhost.com" or "optimati.w04.winhost.com" as the server name .. and both work fine either same way.) So I don't think that makes much difference whether you add the extra 'username' node in
front of the server name or not. But I haven't tried using just the domain name as the server name when creating a connection.. mostly because as I said before, the nameservers are not pointing to WinHost yet. (Although I may be changing the nameservers
as early as Monday evening -May 2nd, US time)
Can you just clarify which machine has what:
I think you said this
(but some of it doesn't make sense..):
Optimation.com: has Apache server as front-end and runs on IIS 7 server (this is the one I can connect to with all modules)
Optinest.com: has IIS6 machine as front-end and runs on IIS 7.5 server??? (I am not sure I have gotten your information down correctly here.. but this is the one I only get
the one module!)
Did I answer all your questions? Is there something I can do on my side to help you figure this out? Please let me know.
May 01, 2011 09:54 PM|LINK
Hi Martin & Kristofer:
I have written a long post to both of you, but that was three hours ago, and it still hasn't shown up here. Usually my posts show up straight away, but this time I got a message that it needed to be approved first. So I am not sure how long that will take.
So.. I have posted my reply here:
May 02, 2011 05:14 AM|LINK
Since there does not seem to be much documentation on this application (and it probably shouldn't, we should never have to do our own configurations).
I think this is what should be happening and what is going on:
When you start IIS Manager, or when you connect to either of the sites, it looks for the necessary modules in
I don't think that is correct. I think that it should be looking in the folder:
Both times. This makes most sense, since that is where the files are downloaded. In the system32\inetsrv folder, do you have this file:
If so, download Process Monitor, and set it up to monitor/filter this file. Then start IIS Manager (make sure you have not started it since you rebooted, so we know there is nothing cached somewhere), and connect to the website it works for. Do you have
any acceess on the above file? If so, notice the process(es) that accessed this file. Reboot the computer (again so we know we have nothing cached), set Process Monitor to monitor/filter the(se) process(es) and open IIS Manager. Which files does it access?
I have feeling that they are trying to access a file that does not exist in the system32/inetsrv folder. If this is correct, we can assume that the configuration is wrong somewhere. The question would then be where.
An alternate way would be to monitor the dll-files in the "roaming" folder.
We could again monitor the same process(es) as above, and see which files and registry keys it accesses. Something in those it should be reading the configuration location. Check all files and keys for the location path, but it may not be there (the default
is the insrv folder, and unless there is something else, it has not created any setting, hence we would not see it).
We could also try to uninstall everything related to IIS. That would be the Remote Admin Manager first, then check the installation folder(s) of Remote IIS Manager and see if something is left (if it is, either remove it, or ask here if you are unsure if
you can remove it). Also remove everything in the WebManagement\18.104.22.168
Then uninstall IIS completely following these steps (i assume that you do not use IIS to something important, this will remove everything regarding IIS):
1 ) Remove web server role and reboot
2 ) Uninstall Windows Process Activation (a service)
3 ) Reboot again
Now everything related to IIS should be removed. Reinstall everything in correct order with the correct files (only files from the Microsoft website). Does it work now?
I would expect that the configuration of the path should be written during installation of Remote Admin Manager, and we have already reinstalled that once, but the setting may have been left somewhere.
I would try option 2 first, since there may be a chance that something else is wrong as well. You could do the monitoring, and make sure that all files it tries to access is removed after the uninstallation.
I hope everything of this is understandingly. I have a feeling you got lost somewhere. But the key point is to do this:
- Do the monitoring/filtering of the above files -or-
- Reinstall everything
Then provide us with the results and we can help you to interpret it.
To answer your questions:
Is there some way I can find out where the log files could be located?
Not that i am aware of. And as you say, it might be an error, it may be doing the expected, the problem is that it is not what we want.
I have not used the domain name directly
That is correct, you should not be using this, should be using the name that goes directly to the IIS 7 / 7.5 server.
Regarding front-end servers
Since you are connecting directly to the server to do the administrating, it does not matter what is running as front-end. A front-end is very common to prevent access directly to the webserver (and other reasons), so you should not bother with this. What
could have been a problem whatever was if you used you domain name to the remote administration, because that could cause non-expected results.
My post has not shown up yet
The filter seems to be aggressive at some times. It will show up in a few minutes.
May 02, 2011 06:23 AM|LINK
If you look at the First Screen Shot there is another Connection that I assumed was "default" or "Local".
That is why this comment "Local Server for your system as "Default"" in the left-hand side for connections."
so it maybe with the re-install the connection has been removed?