![]() Get-Service -Name 'NetLogon' -ComputerName computernameĪlso, be sure to try the Get-Service cmdlet locally and remotely, as well. Get-Service -Name 'Dnscache' -ComputerName computername Get-Service -Name 'eventlog' -ComputerName computername Get-Service -Name 'Winmgmt' -ComputerName computername Get-Service -Name 'IISADMIN' -ComputerName computername Get-WmiObject Win32_Service -Filter "Name='Netlogon'" -ComputerName computernameĪlso, be sure to try the Get-Service cmdlet locally and remotely, as well. Get-WmiObject Win32_Service -Filter "Name='Dnscache'" -ComputerName computername Get-WmiObject Win32_Service -Filter "Name='eventlog'" -ComputerName computername Get-WmiObject Win32_Service -Filter "Name='Winmgmt'" -ComputerName computername Get-WmiObject Win32_Service -Filter "Name='Netlogon'" Get-WmiObject Win32_Service -Filter "Name='Dnscache'" Get-WmiObject Win32_Service -Filter "Name='eventlog'" Get-WmiObject Win32_Service -Filter "Name='Winmgmt'" Log on to your server and run the first four examples - do you get any results? Then try the following four from a remote computer changing 'computername' to the name of your IIS computer. ![]() Verify IIS configuration on the machine on which you installed the. This could be enough to make some people think it is not working. This appendix describes how to configure and verify IIS to support the Exchange. Get-WMIObject returns nothing when a filter is not met regardless of if it is run against a remote computer, or on the local computer. I get the feeling that IIS is not installed on the server. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |