Browsed by
Category: windows

windows stuff

error connecting to EMS on exchange server – The WinRM client cannot process the request

error connecting to EMS on exchange server – The WinRM client cannot process the request

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.     + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc    eption     + FullyQualifiedErrorId : PSSessionOpenFailed

 

check: https://localhost/powershell

if it says module WinRM not found, edit C:WindowsSystem32InetsrvconfigApplicationHost.config file.

insert         <add name=”WSMan” image=”C:Windowssystem32wsmsvc.dll” />

under <globalmodules> section

may need to restart iis (iisreset in commandline). When running EMS it may take a while before finally connecting, then it’s plain sailing.

dns fails registration in windows 2008r2 cluster

dns fails registration in windows 2008r2 cluster

taken from: http://jaminquimby.com/joomla253/servers/81-windows-server/windows-server-2008-r2/473-cluster-name-resource-failed-registeration-in-dns

 

In DNS Management (dnsmgmt.msc):

  1. Find the VirtualClusterName that is failing to register.
  2. Right-Click Properties.
  3. Select Security Tab.
  4. Click Add.
  5. Click Object Types.
  6. Check off “Computers“; uncheck other options selected.
  7. Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
  8. Click Check Names; Verify that the entry has been found.
  9. Click OK.
  10. Give the CNO FULL Control over this record.
  11. Click OK.
loading and unloading peformance counter in Exchange 2010

loading and unloading peformance counter in Exchange 2010

To unload performance counters for ESE, perform the following steps:

  • Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
  • Open the Exchange Management Shell
  • Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
  • Type remove-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
    Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

To reload performance counters for ESE, perform the following steps

  • Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
  • Open the Exchange Management Shell
  • Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
  • Type new-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
    Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx

Windows System Image Manager – Windows 2012 server – GB gotchas

Windows System Image Manager – Windows 2012 server – GB gotchas

WSIM is used to create an xml file which can be used to automate installations of Windows 2012 servers.
The default settings (the ones that you may find in official documentation) are heavily biased towards US.
Here there are the settings that will get you going if you need to use the GB locales:

Components->[windowsPE->amd64_Microsoft-Windows-International-Core-WinPE__neutral

InputLocale: 0809:00000809
SystemLocale: en-GB
UILanguage: en-US
UserLocale: en-GB

Components->[windowsPE->amd64_Microsoft-Windows-International-Core-WinPE__neutral->SetupUILanguage
UILanguage: en-GB

Components->Specialize->amd64_Microsoft-Windows-Shell-Setup__neutral
TimeZone: GMT Standard Time

Capture1

“Exchange HTTP Virtual Server Instance” cluster resource keeps failing

“Exchange HTTP Virtual Server Instance” cluster resource keeps failing

Event Type:    Error
Event Source:    MSExchangeCluster
Event Category:    Services
Event ID:    1005
Date:        06/03/2013
Time:        15:00:06
User:        N/A
Computer:
Description:
Exchange HTTP Virtual Server Instance 100 : The IsAlive check for this resource failed.

 

I have Exchange 2003 running in a Windows 2003 cluster. One of the cluster resources, “Exchange HTTP Virtual Server Instance” kept failing sometimes immediately after bringing it online (even description given above). The problem was intermitent, so it was difficult to replicate it in a production environment.

I have logged a call with Microsoft and their engineer was happy to observe that “it’s working now” and leave it like that. As I pushed him to give me a proper root cause, he declined by saying that I need to have “premium” support as opposed to the “professional” one that I had.

Anyway, enough of the perils of scripted support provision, which most of you reading this will already know about.

From what I was able to work out, the cause to this is lack of kernel memory and the solution is given here:

http://support.microsoft.com/?id=934878

In short go to registry

Click Start, click Run, type regedit in the Open box, and then click OK.

Click the following registry subkey:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHTTPParameters

On the Edit menu, point to New, and then click DWORD Value.

Type EnableAggressiveMemoryUsage, and then press ENTER.

On the Edit menu, click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

You will need to (re)start HTTP.

 

Windows Server 2012 – converting between core, gui and minimal interface versions

Windows Server 2012 – converting between core, gui and minimal interface versions

In Windows Server 2012 is now possible to switch between various install options (Gui, Core) through simple PoweSshell commands, installing/uninstalling features.

Core Minimal GUI Desktop Experience
File And Storage Services
FileAndStorage-Services
File And Storage Services
FileAndStorage-Services
File And Storage Services
FileAndStorage-Services
File And Storage Services
FileAndStorage-Services
Storage Services
Storage-Services
Storage Services
Storage-Services
Storage Services
Storage-Services
Storage Services
Storage-Services
.NET Framework 4.5 Features
NET-Framework-45-Features
.NET Framework 4.5 Features
NET-Framework-45-Features
.NET Framework 4.5 Features
NET-Framework-45-Features
.NET Framework 4.5 Features
NET-Framework-45-Features
.NET Framework 4.5
NET-Framework-45-Core
.NET Framework 4.5
NET-Framework-45-Core
.NET Framework 4.5
NET-Framework-45-Core
.NET Framework 4.5
NET-Framework-45-Core
WCF Services
NET-WCF-Services42
WCF Services
NET-WCF-Services43
WCF Services
NET-WCF-Services44
WCF Services
NET-WCF-Services45
TCP Port Sharing
NET-WCF-TCP-PortSharing42
TCP Port Sharing
NET-WCF-TCP-PortSharing43
TCP Port Sharing
NET-WCF-TCP-PortSharing44
TCP Port Sharing
NET-WCF-TCP-PortSharing45
Ink and Handwriting Services
InkAndHandwritingServices
Media Foundation
Server-Media-Foundation
Media Foundation
Server-Media-Foundation
Media Foundation
Server-Media-Foundation
Media Foundation
Server-Media-Foundation
User Interfaces and Infrastructure
User-Interfaces-Infra
User Interfaces and Infrastructure
User-Interfaces-Infra
User Interfaces and Infrastructure
User-Interfaces-Infra
Graphical Management Tools and Infrastructure
Server-Gui-Mgmt-Infra
Graphical Management Tools and Infrastructure
Server-Gui-Mgmt-Infra
Graphical Management Tools and Infrastructure
Server-Gui-Mgmt-Infra
Desktop Experience
Desktop-Experience
Server Graphical Shell
Server-Gui-Shell
Server Graphical Shell
Server-Gui-Shell
Windows Powershell
PowerShellRoot
Windows Powershell
PowerShellRoot
Windows Powershell
PowerShellRoot
Windows Powershell
PowerShellRoot
Windows Powershell 3.0
PowerShell
Windows Powershell 3.0
PowerShell
Windows Powershell 3.0
PowerShell
Windows Powershell 3.0
PowerShell
Windows PowerShell ISE
PowerShell-ISE
Windows PowerShell ISE
PowerShell-ISE
Windows PowerShell ISE
PowerShell-ISE
WoW64 Support
WoW64-Support
WoW64 Support
WoW64-Support
WoW64 Support
WoW64-Support
WoW64 Support
WoW64-Support

(Click here for a nicer version of the above in .pdf format)

I couldn’t find a command for checking the current install option on the server, so I used this:
# list all INSTALLED Windows Server features
Get-WindowsFeature | where {$_.Installed -eq "True"} | ft DisplayName, Name, Installed
credit goes here

the presence of [-Source] variable determines if local binaries are to be used or if they will be downlodaded from ‘Windows Update’

In order to convert between the install options of Windows Server 2012 run one of the following in PowerShell as appropriate:

Core -> Gui
Install-WindowsFeature Server-Gui-Shell -Restart -Source C:mountdirwindowswinsxs
or
Install-WindowsFeature Server-Gui-Shell -Restart

Core -> Minimal Interface
Install-WindowsFeature Server-Gui-Mgmt-Infra -Restart -Source C:mountdirwindowswinsxs
or
Install-WindowsFeature Server-Gui-Mgmt-Infra -Restart

Gui -> Core
Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -Restart

Gui -> Minimal Interface
Uninstall-WindowsFeature Server-Gui-Shell -Restart

Minimal Interface -> Core
Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -Restart

Minimal Interface -> Gui
Install-WindowsFeature Server-Gui-Shell -Restart -Source C:mountdirwindowswinsxs
or
Install-WindowsFeature Server-Gui-Shell -Restart

This is how technet recommends moving between install options, however I found that the above is sufficient.

To reach the installation state in each row… Run the Windows PowerShell install/uninstall commands with these values for the Name parameter: Or, select these features in Server Manager:
Server Core installation option none none
Minimal Server Interface Server-Gui-Mgmt-Infra Graphical Management Tools and Infrastructure
Server with a GUI installation option Server-Gui-Mgmt-Infra,
Server-Gui-Shell
Graphical Management Tools and Infrastructure,
Server Graphical Shell
Desktop Experience feature installed Server-Gui-Mgmt-Infra,
Server-Gui-Shell,
Desktop-Experience
Graphical Management Tools and Infrastructure,
Server Graphical Shell,
Desktop Experience

http://technet.microsoft.com/en-us/library/hh831786.aspx

 

UPDATE (08/04/2013) – install-windows-feature may give errors talking about non-existing sources. Hence the DVD source may need mounting (see http://p0w3rsh3ll.wordpress.com/2012/10/10/switch-from-windows-2012-core-to-gui-mode-hands-on/)

# 1. Create an empty directory             
mkdir c:mount            
# 2. Mount the Standard image            
Mount-WindowsImage -Path C:mount -ImagePath D:sourcesinstall.wim -Index 2 -ReadOnly
HP Sistem Management Homepage timeout

HP Sistem Management Homepage timeout

the timeout errors in windows (error 1053) can be addressed by adjusting the UI timeout (default 60 seconds).
Check for the SMH log for entries such as this:
MAJOR 11/19/2012 2:19:24 PM
UI Timeout (limit: 120s) — vcagent(HPVersionControlAgent):359s||vcrepository(HPVersionControlRepositoryManager):0s||elm(backwardscompatibility):0s

which indicates that the one of the agents needed more time than that specified by the UI Timeout limit.