与Server 2008 R2上的Internet Explorer ComObject交互时出现问题

Question

Ok, so I have written a pretty intense PowerShell script that installs and configures SharePoint 2007 and SQL 2008. That is what it is, please don't judge me. After finishing all of that up, because the script is supposed to be user friendly, I developed a web form to gather inputs and display task progress. Stupidly, I wrote all the code for the web form on Windows 8.1 without even testing the basic functions on Server 2008 R2 where the script will be executed. When I took the code over to the server, it malfunctioned pretty much immediately. When I then tested it on Windows 7, it worked fine.

Here is the behavior on Windows 8.1 (w/ IE 11) and Windows 7 (w/ IE 9):

>$ie = New-Object -ComObject InternetExplorer.Application
>$ie.Navigate('about:blank')
>$ie.visible = $true #Internet explorer is now displayed with a blank page
>$ie.document


Script                            : System.__ComObject
all                               : System.__ComObject
body                              : System.__ComObject
activeElement                     : System.__ComObject
images                            : System.__ComObject
applets                           : System.__ComObject
links                             : System.__ComObject
forms                             : System.__ComObject
anchors                           : System.__ComObject
title                             :
scripts                           : System.__ComObject
designMode                        : Inherit
selection                         : System.__ComObject
readyState                        : complete

The list goes on for a while....

Now when I run the same code on Server 2008 R2:

>$ie = New-Object -ComObject InternetExplorer.Application
>$ie.Navigate('about:blank')
>$ie.visible = $true #Internet explorer is now displayed with a blank page
>$ie.document
System.__ComObject

This is a little bit of a problem as the script pretty heavily relies on writing to and reading from the IE Document object and none of the classes I need are available. Rather no classes are available, even the ones I don't need.

So is there any way to access the document object on Server 2008 R2? I have gone through everything that I can think of with the security zone settings (although I may have missed something there), and I have disabled the enhanced security configuration and the IE protected mode. Nothing I have done seems to give me access to the document. Any advice?

Answer 1

One thing that may allow you to still have an HTML but not use if in PowerShell is write an HTA, and export all of the required values from the .hta to a .csv file, and then import those values from the .csv to your Windows PowerShell prompt. Not the cleanest solution by any means, but it's much easier than XAML / WPF, and is available on more platforms. The only draw back may be that I don't know if Windows Server supports HTA. If it doesn't, a simple workaround might be to run the parameter export piece on a client computer, with the actual installation on the server.

Another route might be using the PowerShell script to run the commands against the server, while running the front-end on a client computer. I know that Invoke-Command will let you run against the server, but simultaneously grant you the ability to use IE.

Sorry I can't give more advice, but I've never tried doing this on Windows Server before.

Answer 2

通过使用gacutil.exe将Windows 8.1计算机上的Microsoft.mshtml.dll程序集部署到Server 2008 R2计算机上的GAC并重新启动PowerShell实例来解决。