PDA

View Full Version : Exchange 2007 on win 2008


gabi_cavaller
05-13-2009, 01:03 PM
Hi,

Exchange 2007 standard on windows 2008 standard,

Just going the HTTP redirect as this article explains (unfortunately Dave's article does not have IIS7, and it's a bit different )

http://technet.microsoft.com/en-us/l.../aa998359.aspx

I am now removing the redirect from the directories that don't need it.

bottom of article.

I am getting the following error message

The erm 'appcmd' is not recognized as a cmdlet, function, operable program, or script file..........................

This is really annoying me.

Tried the following scripts

appcmd set config "default web site/Exchange" /section:httpredirect /enabled:false -commit:apphost

appcmd set config "default web site/Exchange" /section:httpredirect /enabled:false /commit:apphost

No luck sadly.

Any thoughts?

Thanks ever so much,

Gabi.

gabi_cavaller
05-19-2009, 04:44 AM
Any idea?

:)

No luck this end, I am definitely in the correct directory and still having the same issue.

Thanks in advanced,

Gabi.

DShack
06-01-2009, 09:46 AM
Gabi, are you trying to run this within a PowerShell window, or are you opening up a command-line and navigating down to the inetsrv directory? Did you verify that 'appcmd.exe' is present in the inetsrv directory or in one of the paths that the "path" variable defines?

gabi_cavaller
06-10-2009, 05:25 AM
Hi,

Thanks for taking your time to reply.

I am running this within powershell and making sure I am in the right directory.

The appcmd.exe is present.

I have not checked this again for a while but everything seems to be functioning..........

Strange product this is.

Glad it's pretty much all up and running.

Just need to configure postinin and fingers crossed.

You're tutorials were very clear and handy, thanks again for taking your time to do them, really appreciate it :)

DShack
06-18-2009, 11:41 AM
I think for appcmd to work properly, you don't want to be in PowerShell. It's not a PowerShell cmdlet, so you'd want to be at a regular (ESCALATED!) command-line. Sometimes normal command-line stuff works fine in a PowerShell session, but occasionally it doesn't.

Probably the main day-to-day thing you need to watch out for on Windows 2008 is to make sure that when you open a command-line or PowerShell, that you've chosen "Run as Administrator" when you clicked the icon to fire it up.

If you like to just type "cmd" at the bottom search box to fire off a command-line, hold down Shift+Ctrl when you hit Enter, and it will automatically escalate it for you. Shft+Ctrl will escalate anything that you run from the Run or Search fields.

Best,

Dave Shackelford

r0kIT
07-24-2009, 06:07 AM
the method in http://technet.microsoft.com/en-us/library/aa998359.aspx does include IIS7 and it works great... just remmeber to double check the redirect rule for the subdirectorys... that's a tricky part.