Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Re-installation of RPC HTTP proxy feature leads to big problem in

363 views

Skip to first unread message

It's me again

unread,

Feb 22, 2010, 7:44:07 PM2/22/10

SBS 2008, being the odd duck that it is, moves certain virtual directories
from the Default Web Site to the SBS Web Applications site during
installation. Among the vdirs moved are the RPC and RPCwithCert vdirs that
are critical to Outlook Anywhere. These vdirs are associated with the RPC
HTTP proxy feature. Now, if the RPC HTTP proxy feature is removed and then
added again in SBS 2008 using Windows Server Manager (which the last time I
looked was part of SBS 2008), the RPC and RPCwithCert vdirs are put in the
Default Web Site and Outlook Anywhere in a one cert installation is broken. I
have examined the script in the CAS role repair of Exchange Server (SBS
version) and do not see how the RPC and RPCwithCert vdirs are being moved.
Absent a cookbook procedure it would be nice if the RPC and RPCwithCert apps
were fully documented which would at least provide a way to recreate them in
the proper IIS 7 site. Somebody tell me there is an easy way to fix my broken
SBS 2008.

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 22, 2010, 7:56:32 PM2/22/10

I'm unsure on what You've done.
You've Uninstalled RPC HTTP For a reason?
Was it not working or did you manually move a web directory or something?
and re installed it (How did you reinstall it?)

And you say one CERT Installation is Broken?
(More Details please.)

Errors in Logs etc.
Symptoms

Have you run the Configure network and network fix wizard?
or Run the Best Practices Analyzer and see what you can see.

Not to sound harsh but if you want the easiest way to fix this,
is to call someone and have them do it.

Be it Microsoft or your SBS Specialist guy.

Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Microsoft Certified Small Business Specialist
SBS2003 SBS2008 Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message
news:924AFA22-B832-4898...@microsoft.com...

It's me again

unread,

Feb 22, 2010, 8:55:01 PM2/22/10

Hi Russ,

As you know, in SBS 2008 there is a Server Manager application where one can
add or remove roles and features, as well as perform other tasks. If the RPC
HTTP proxy feature is removed (using Server Manager), upon reinstalling RPC
HTTP proxy (again with Server Manager) one finds that the RPC and RPCwithCert
Apps that were originally in the SBS Web Applications site (cf IIS 7) are now
in the Default Web Site. One of the benefits of having RPC and RPCwithCert
being in the SBS Web Applications site is that a single SSL connection
listening on port 443 can be used for several web applications, as well as
Outlook Anywhere.

It came as a surprise to me that by simply removing and reinstalling a
feature I could break part of the customization that is small business
server. I have been looking high and low for a way to recover the original
configuration and can find no discussion of this problem anywhere. I did come
across a few people who said this happened to them, but it's going on two
years with SBS 2008 and not a peep from anyone connected with Microsoft.
Please tell me I am just confused and/or there is a simple solution to fix
the problem I have described.

- Rob

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 22, 2010, 9:05:32 PM2/22/10

Well if it just recent
Restore your OS Drive from backup
That's the easiest
Russ

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message

news:45E291EA-6FFD-4646...@microsoft.com...

It's me again

unread,

Feb 22, 2010, 9:21:01 PM2/22/10

Well Russ, that is not the kind of solution I was looking for. I was hoping
to get some insight into the mechanism employed in this bit of customization
to achieve the odd duck known as SBS.

Have you ever looked at the script that changes the IIS configuration when
Exchange is installed in SBS? In that script you can see all the apps being
moved from Default Web Site to SBS Web Applications site, except for the RPC
and RPCwithCert apps. What I would like to know first is where the move of
those apps takes place during installation and secondly how the two apps
should be configured for SBS purposes. With the latter information I can
recreate them. But, as I said earlier, nobody at Microsoft wants to talk
about this detail.

Anyway, thanks for trying to help.

Cliff Galiher - MVP

unread,

Feb 22, 2010, 9:36:07 PM2/22/10

Since SBS 2008 is "built" on Windows Server 2008, it has the windows server
tools, including ADUC, ADSI, and the server manager snap-in.

That doesn't mean you should *use* these tools. If there isn't a wizard to
do something, that means one of two things:

1) It should not be done in SBS because of licensing or technology
restrictions.
2) It should only be done if there is a business need and a *very*
experienced Windows professional familiar with SBS is making those changes.

In this case, you used a tool that was not SBS aware to try and install
something and now things are very shuffled.

Depending on the extent of the damage, you have several options:

1) Restore a backup. Yes, this will re-introduce the problem you were
trying to fix, but chances are we can walk you through that and resolve the
issue more easily than the state you are in now.

2) Try the SBS wizards. In particular the FNCW and CTIW could be useful. I
doubt the IAMW wizard will do much in this instance, but it can't hurt
either. These wizards are interlaced, so the "I doubt" is literal; they've
surprised me by rebuilding stuff internally that I didn't expect them to
more than once.

3) Rebuild the exchange roles. There is a technet article on this. It is
very risky, very difficult, and step #1 would be MUCH more preferencial at
this point, but if you have somehow gotten yourself past the point of
return, it is an option. It is *SO* far out of the realm of a good option
though that I won't post the link until we've exhausted all other options.
Sorry, I just feel that strongly about it.

Hope that helps,

-Cliff

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message
news:924AFA22-B832-4898...@microsoft.com...

It's me again

unread,

Feb 23, 2010, 12:09:01 AM2/23/10

Hi Cliff,

Thank you for taking the time to offer your observations concerning SBS.

As for not using the tools that are provided with the product, don't you
find such a practice to be just a little strange? If Microsoft knew that
using a particular tool would break the product, do you not imagine they
would disable that tool? Yes, it is true that uninformed choice of settings
will often lead to unintended consequences, but in this case we are talking
about enabling or disabling a feature. There are no explicit settings to get
wrong.

In general I am not a fan of black box computing. Running wizards without
knowing what the wizard is doing is not very appealing, even if it leads to a
workable solution. Indeed, what happens the next time something breaks,
should one begin blindling running wizards one by one, with hope and a
prayer? Besides, there is nothing being done in any SBS wizard that cannot
easily be done using the tools given. So the advice to "try" the various
wizards you list is not very helpful to me.

Your item 3 is exactly what I was referring to in my original post. The
script I mentioned is given in the reference that you are reluctant to
provide. To wit,
http://technet.microsoft.com/en-us/library/dd767439(WS.10).aspx . The repair
instructions found therein are not particularly difficult in any sense, but
the whole procedure smacks of the black box approach. My conclusion, so far
or at least until someone with real knowledge of the code sets me straight,
is that the relocation of the RPC and RPCwithCert apps in IIS 7 is taking
place during the running of the CAS repair process on the Component
Technologies for Server Repair disk. Clearly, the script given in the
reference just deals with the apps that were added to SBS, the ones not found
in other Windows Server 2008 editions.

So in summary, if you know anybody who really knows his or her way around
this topic, please point them to this thread because I know that there are
other people who have fallen into the same trap as I did.

Regards,
Rob

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 23, 2010, 12:46:43 AM2/23/10

Rob
No offense,
But actually not running the wizards are probably where it went wrong.
Microsoft doesn't disable snap-ins because they are a integrated part of the
OS
SBS is a Module on top of Server2008 not a rebuild of OS from ground up.
(And you can not separate the two.)

The three Rules of SBS are:
1. Use the wizards.
2. Use the wizards.
3. Use the wizards, and if no wizards then the snap ins.

yes these are "RULES" not guidelines...

SBS2008 Requires you to use the wizards to run effectively.
As it seems now, you are finding out the hard way.

Sorry to say but your phrase:

" there is nothing being done in any SBS wizard that cannot easily be done
using the tools given."

I totally disagree with, and as a result, is probably why you are in the
state you are.

If you have added users and done other tweaks
and not used the SBS wizards, which I suspect.

You may have already put your server in a "Unsupported" Position.
In which case you have to bring your server into SBS standards.
(not the standards you used to.)

These "Standards" are different for SBS which is why Microsoft
has created a new Certification Just for the SBS Products
They are called "Small Business Specialists"
Which is a group that Cliff and I are Members of.

If you have avoided Wizards like I suspect you may have to call Microsoft.
In which case you will get the "Why didn't you use wizards" from them also.
(Sorry but you will hear it from them also.)

This Document written for SBS2003 however the rules stills applies
Introduction to Windows Small Business Server 2003 for Enterprise IT Pros
http://www.microsoft.com/downloads/details.aspx?familyid=71211053-CCD6-4F2B-BBD9-5E7B97C232EC&displaylang=en

If you are still Determined to not use wizards
Be aware you will fight SBS2008 every step of the way. and you will not be
happy with it.

Rob you can try to save this server by running the wizards that cliff
mentions.
however I suspect at this point I think you should call Microsoft.
or flatten the box and start over using wizards.

However if you do not ever want to run a wizard
I suggest another Microsoft product as you will not be happy with SBS2008

Here are some books that I highly suggest if you want to learn about SBS2008

Windows® Small Business Server 2008 Administrator's Companion
http://www.amazon.com/Windows%C2%AE-Business-Server-Administrators-Companion/dp/0735620709/ref=sr_1_3?ie=UTF8&s=books&qid=1241297332&sr=1-3
And OR
Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1

Russ

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message

news:91D13672-83ED-4214...@microsoft.com...

Cliff Galiher - MVP

unread,

Feb 23, 2010, 1:46:27 AM2/23/10

Hello Rob,

Unfortunately, the way I read your post, is that you want to have your cake
and eat it too. On one hand you want MS to disable options that are
"dangerous" but on the other hand you don't want to use the wizards because
they are too "black box" for you and you want the option to do everything
manually. Do you not see the direct contradiction in that?

In short, SBS is designed to allow the *average* office worker do daily
tasks such as adding users, monitor the server for problems, and do basic
maintenance. As such, the wizards have been specifically designed to
automate much of that work. The downside to that approach is that the
wizards *must* make certain assumptions (or the stop becoming "wizards") and
thus are more frail to external changes. So you have a choice, use the
wizards, or accept the responsibility of NOT using them.

But don't kid yourself. This is still a server product. It is automated to
the extent that *BASIC* tasks are automated. Reconfiguration, significant
environmental changes, and feature adjustments will *never* be listed under
basic/daily tasks in any reference on any server. As such, they should only
be done with backups, more backups, a thorough understanding of process and
consequence, and finally ideally in a test environment first. That is how
sysadmins manage servers and keep their job. Not exclusive practices to SBS
here.

So you can ask for someone to help unravel the black box all you want, but
the simple harsh truth is you've gone far enough down the rabbit hole that I
doubt anybody will be able to explain the intricacies to your satisfaction.

So your choices are simple:

1) Leave your server as is and hope/wait for someone to hold your hand.
Each day you wait is a day your backup gets older and the chances of a quick
recovery diminish.

2) Call Microsoft CSS and pay for support. They may not give you the level
of detail you want, but they are skilled at recovering from problems, and
since it is a charge service, response is usually timely and efficient (if
not enlightening.)

3) Proceed with previous recommendations, limit your downtime, and learn
from your mistakes.

Understand that I have no vested interest in which approach you use. I'm
simply trying to give you the *easiest* out I can based on the condition
you've set up. The choice is yours.

Thanks,

-Cliff

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message

news:91D13672-83ED-4214...@microsoft.com...

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 23, 2010, 1:50:52 AM2/23/10

Cliff I should let you write these (use the wizards) next time
You are better at it :)

Russ

"Cliff Galiher - MVP" <cgal...@gmail.com> wrote in message
news:98CAEBD9-9026-4EB9...@microsoft.com...

Cliff Galiher - MVP

unread,

Feb 23, 2010, 1:52:02 AM2/23/10

Aye, and for the record, the link you posted was *NOT* what I'd recommend
doing by the way. Uninstalling (or reinstalling) an entire exchange server
role just to fix an IIS issue is *EXACTLY* going farther down a path of
unistalling things that are best left alone. Exchange (as far as I can tell
from your previous posts) is working, so no, your assumption of what I'd
post was, sadly, wrong. But it does highlight my point of trying too hard
to do something that causes more harm than good, and why I am *NOT* posting
any references to further hard-line repair procedures yet. They could, if
abused, introduce their own set of problems.

-Cliff

"It's me again" <Itsme...@discussions.microsoft.com> wrote in message

news:91D13672-83ED-4214...@microsoft.com...

Leythos

unread,

Feb 23, 2010, 6:43:18 AM2/23/10

In article <91D13672-83ED-4214...@microsoft.com>,
Itsme...@discussions.microsoft.com says...

> As for not using the tools that are provided with the product, don't you
> find such a practice to be just a little strange?
>

For those that have researched, used, built, maintained SBS systems for
any real period of time, we've all learned that the PROPER and BEST
methods to manage a SBS server is to use the Wizards, ALWAYS.

That's not to say that you can't do it the manual way, but you should
not expect the "Manual" way to work as it does using the Wizards.

As an example, I used UDUC in SBS03 to copy users accounts where I was
creating a user with the same permission groups (we normally have 20 odd
NTFS Permission/Security groups related to file structures), so it's
easier to use the SBS 03 ADUC to ensure that new users get the same
permissions as others like them, but, since I didn't use the wizard,
they have to be added to the company web manually and if I was to create
a user from scratch I would have to add them into specific groups for
RWW to work.

With SBS 08, just because you create a User account using ADUC, it
doesn't mean you get an email account, you have to do that manually
too.... I don't use the same process in SBS08, I always use the wizard
in 08.

If you use the Server 03/08 tools instead of the SBS 03/08 tools, "just
because they are there", then you're showing that you don't know much
about SBS and how it's structured.

Removing things are the last thing you want to do.

> If Microsoft knew that
> using a particular tool would break the product, do you not imagine they
> would disable that tool?

If Users researched the product and management before they started using
the product, do you imagine that they would do things that break SBS?

If Users were reasonable, do you imagine they would disable/remove
things without first checking to see what it might impact?

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam9...@rrohio.com (remove 999 for proper email address)

Ace Fekay [MVP-DS, MCT]

unread,

Feb 23, 2010, 12:51:25 PM2/23/10

"Leythos" <spam9...@rrohio.com> wrote in message
news:MPG.25ed895bf...@us.news.astraweb.com...

Honestly, I don't know why you guys are pushing this to Rob (It's Me Again).
He stated he feels flatly against out of box solutions and would rather do
it manually, so IMHO, no matter how many times or how you state it,
apparently he will not follow the SBS rules. Unfortunate, however, this is
the case, for it is simply breaking his instalation.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

Cliff Galiher - MVP

unread,

Feb 23, 2010, 2:33:19 PM2/23/10

FWIW Ace, I'm not randomly pushing back on Rob. What is done is done. But I
did recommend using wizards to try and repair the damage, which, if you read
the entire thread, was rebuffed as "black box" computing. So my reply was
solely an attempt to lay out the realities. You can use a black-box wizard
and hopefully be up and running, or you can stick to your "no wizards"
ideals and stay down. But there is no happy medium.

So I agree, if someone doesn't want to use the wizards then SBS is probably
not the product for them. But the reality right now is that SBS is already
in play, has already been broken, and the wizards may be the easiest way
out, so I wanted to EXPLICITLY lay that framework out with no equivocation.

-Cliff

"Ace Fekay [MVP-DS, MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
news:e0ICTDLt...@TK2MSFTNGP06.phx.gbl...

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 23, 2010, 2:49:41 PM2/23/10

In also support of Cliff
Often when 2 or more professionals in the field give the same advice
it often helps.

I've seen people post here and think, Oh that's just 1 persons opinion
(And I'm Smarter than they are.)

I know when I first Started SBS I too Didn't trust the wizards
And reading More and more People saying the same thing.
Convinced me that "I" was the person who was wrong....

So IMO the more "Professionals" that post
PLEASE don't do this.

The happier He will be, and the happier the client will be.
(Which is the result I'm going for.)

My Goal is to stop IT Companies that #$#@$ over SBS servers...
And it's one company at a time.... :)
Russ

"Cliff Galiher - MVP" <cgal...@gmail.com> wrote in message

news:u5meS8Lt...@TK2MSFTNGP04.phx.gbl...

Ace Fekay [MVP-DS, MCT]

unread,

Feb 23, 2010, 5:46:35 PM2/23/10

"Russ SBITS.Biz [SBS-MVP]" <ru...@REMOVETHIS.sbits.biz> wrote in message
news:uqFTYFMt...@TK2MSFTNGP05.phx.gbl...

>>
>> "Cliff Galiher - MVP" <cgal...@gmail.com> wrote in message
>> news:u5meS8Lt...@TK2MSFTNGP04.phx.gbl...
>> FWIW Ace, I'm not randomly pushing back on Rob. What is done is done.
>> But I did recommend using wizards to try and repair the damage, which, if
>> you read the entire thread, was rebuffed as "black box" computing. So my
>> reply was solely an attempt to lay out the realities. You can use a
>> black-box wizard and hopefully be up and running, or you can stick to
>> your "no wizards" ideals and stay down. But there is no happy medium.
>>
>> So I agree, if someone doesn't want to use the wizards then SBS is
>> probably not the product for them. But the reality right now is that SBS
>> is already in play, has already been broken, and the wizards may be the
>> easiest way out, so I wanted to EXPLICITLY lay that framework out with no
>> equivocation.
>>
>> -Cliff
>>
>>
>

> In also support of Cliff
> Often when 2 or more professionals in the field give the same advice
> it often helps.
>
> I've seen people post here and think, Oh that's just 1 persons opinion
> (And I'm Smarter than they are.)
>
> I know when I first Started SBS I too Didn't trust the wizards
> And reading More and more People saying the same thing.
> Convinced me that "I" was the person who was wrong....
>
> So IMO the more "Professionals" that post
> PLEASE don't do this.
>
> The happier He will be, and the happier the client will be.
> (Which is the result I'm going for.)
>
> My Goal is to stop IT Companies that #$#@$ over SBS servers...
> And it's one company at a time.... :)
> Russ
>

Hey guys, I am not refuting what you are saying. I completely agree. And I
meant to say "black box" computing, which I did read in the thread, and
hence why I commented that if Rob doesn't want to use the wizards, there's
nothing we can say to talk him into or out of it, unfortunately. Apparently
he feels that strong about it. Nonetheless, I hope he can fix his issues
that was brought about from ignoring the wizards.

And I wish you the best of luck to help stop IT companies, or even
individuals, for that matter, from #$#@$ over SBS servers... :-)

Ace

Leythos

unread,

Feb 23, 2010, 6:26:54 PM2/23/10

In article <e0ICTDLt...@TK2MSFTNGP06.phx.gbl>,
ace...@mvps.RemoveThisPart.org says...

> Honestly, I don't know why you guys are pushing this to Rob (It's Me Again).
> He stated he feels flatly against out of box solutions and would rather do
> it manually, so IMHO, no matter how many times or how you state it,
> apparently he will not follow the SBS rules. Unfortunate, however, this is
> the case, for it is simply breaking his instalation.
>

I have older teens, so I'm use to talking to the brick-wall :-)

Ace Fekay [MVP-DS, MCT]

unread,

Feb 23, 2010, 8:13:23 PM2/23/10

"Leythos" <spam9...@rrohio.com> wrote in message

news:MPG.25ee2e4a9...@us.news.astraweb.com...

> In article <e0ICTDLt...@TK2MSFTNGP06.phx.gbl>,
> ace...@mvps.RemoveThisPart.org says...
>> Honestly, I don't know why you guys are pushing this to Rob (It's Me
>> Again).
>> He stated he feels flatly against out of box solutions and would rather
>> do
>> it manually, so IMHO, no matter how many times or how you state it,
>> apparently he will not follow the SBS rules. Unfortunate, however, this
>> is
>> the case, for it is simply breaking his instalation.
>>
>
> I have older teens, so I'm use to talking to the brick-wall :-)
>

LOL!

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 24, 2010, 4:00:15 AM2/24/10

I know it's job security if I Don't tell people to use wizards however, I'd
rather have a server done right

Russ
--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Microsoft Certified Small Business Specialist
SBS2003 SBS2008 Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

"Ace Fekay [MVP-DS, MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message

news:eP0sPoNt...@TK2MSFTNGP04.phx.gbl...

Ace Fekay [MVP-DS, MCT]

unread,

Feb 24, 2010, 9:03:44 AM2/24/10

"Russ SBITS.Biz [SBS-MVP]" <ru...@REMOVETHIS.sbits.biz> wrote in message

news:1B7A999D-A248-4F2E...@microsoft.com...

>I know it's job security if I Don't tell people to use wizards however, I'd
>rather have a server done right
> Russ

Well, yea, I agree. That is the ultimate goal. :-)

Ace

John

unread,

Feb 24, 2010, 7:31:01 PM2/24/10

I dont know why you guys are badgering Rob - but there should be a simple solution to properly register the RPC directory in IIS - what is it??

I have a kind of mirrored problem of this issue - my RPC directory exists in the proper SBS Web Applications vdir(never changed or removed it), but several Exchange Power Shell tests show that RPC is broken, and the tests think the directory is missing from the "Default Website" vdir - DUH! of course its missing - cause its in SBS Web Applications - not many issues from this - somehow remote Outlooks still work fine - but TS Gateway features are broke.

My gut feeling is to NOT run the wizards as they failed to setup the ssl cert with SANs properly configured with autodiscover in the first place. I feel deciphering that nasty guide that Rob posted that is loaded with Power Shell commands may be the only real solution. Working with SBS since Backoffice 4.0, I think I know my way around the block, and I have done my due diligence to research this - if I call MS support (which has crossed my mind) and they cant fix this in 15 minutes - where am I left?? - Means they tried the wizard and it didnt work. My last call to the Exchange department took 2 months to solve a problem, and the resolution was never known, except that its working again. Surely I respect these techs as being quite proficient, my hats are off to you guys, but sometimes it feels like you are thumping your MCSE bible at me.

Point being - MS should definitely better document RPC and how its tied to IIS - something tells me part of that script Rob linked to has the 3-4 lines that fix this hidden in there somewhere.

---
frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl

Ace Fekay [MVP-DS, MCT]

unread,

Feb 24, 2010, 8:14:29 PM2/24/10

John,

In Rob's case, I think the operative word is "re-register" or
"re-install" RPC, which falls under the Exchange 2007 CAS role.

I myself, have been curious from the beginning of this thread, as to
why Rob had to removed RPC to begin with. Was there a problem that
prompted hinm? I don't know. I was trying to read through the rhetoric,
but I cannot ascertain or find any stated reason, even after he was
asked as to why.

Nontheless, the deed has been done, for whatever reason, and he's
trying to repair it. He mentioned the CAS repair link, but he didn't
mention if he followed it, and if so, if it worked. I am also curious
if he followed the KB, if it worked or not.

And btw John, the link you provided at the bottom of your post, is
actually a link to this thread. I don't know if you are aware of that
or not, or if it was automatically placed by the web-based newsgroup
access method or site that you used to access this group.

John

unread,

Feb 24, 2010, 8:35:21 PM2/24/10

That link is placed there by the msgroups list.

Some further research leads me to this kb:
http://support.microsoft.com/default.aspx/kb/970259/EN-US

relevant commands being:
3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/Rpc" -applicationPool:RpcAppPool

4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/RpcWithCert" -applicationPool:RpcAppPool

One would think you could simply change the paths to say:
appcmd.exe set app "SBS Web Applications/RpcWithCert" -applicationPool:RpcAppPool

but - tried it, and nothing changes in the output of get-outlookanywhere |fl

WARNING: IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc was not found.
Please make sure you have typed it correctly.

ServerName : EXCH1
SSLOffloading : False
ExternalHostname : remote.acme.com
ClientAuthenticationMethod : Basic
IISAuthenticationMethods : {Basic, Ntlm}
MetabasePath : IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc
Path :
Server : EXCH1
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acme,DC=local
Identity : EXCH1\Rpc (Default Web Site)
Guid : 5b2ba1c6-936-41d3-9998-1d1c14be8e98
ObjectCategory : acme.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 1/3/2010 3:42:08 PM
WhenCreated : 1/3/2010 3:42:08 PM
OriginatingServer : EXCH1.acme.local
IsValid : True

silly server should not even mention the Default Website since its SBS.

-John

---
frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 24, 2010, 9:07:39 PM2/24/10

John,
The reason as you put it We Thump our MSCE Bible
is because SBS requires you to follow RULES!

People don't want to follow the rules with SBS
and when they don't and "assume" they know what they are doing and it
breaks.
They then complain that the product sucks, lacks documentation etc...

So when they call Microsoft for support and you don't use the rules for SBS
You definitely get a BIG Delay in support.

Why? Because they have to try and UNDO all you've done to break your server.

We are not after Rob to be "mean"
but to guide him in the best way to do things...

Using the wizards with SBS puts your server in a Supported Configuration
not using wizards puts SBS in a NON Supported Configuration.

You are free to do what you wish, however people need to realize the
consequences of their actions.

And that is the purpose of our many posts.
Not to harass, but to guide them so they may enjoy SBS not hate it!
Russ

PS John, if you avoid msgroups.net website
and post directly to msnews.microsoft.com with your favorite NNTP Reader
You will avoid broken links people not understanding your posts and reading
excessive ad's

"John" <us...@msgroups.net/> wrote in message
news:OzhoPHbt...@TK2MSFTNGP04.phx.gbl...

John

unread,

Feb 25, 2010, 1:45:39 AM2/25/10

so - following the rules of SBS - used the Fix Network wizard, and Setup
your Internet address wizard - things are worse then before, this is a
relatively fresh server (2-3 months old). What happens after you installl
SBS - you fill out the Wizards to complete setup of your domain - this is
how it was done, and several features of SBS were disfunctional out of the
box.

Some settings needed to be adjusted in IIS and some ps commands were
performed to correct ssl certs - pretty simple and standard fixes which
the wizards have now broke again.

The Fix network wizard keeps going on about a TS Gateway issue, click fix
it, says it has resolved the problem, but if you run the wizard again it
identifies the same issue - it doesnt give any details, but most likely it
is not correcting the RPC issue.

Not to hijack a thread, but my issue is quite similar and hopefully
collaboration can aide in resolution, Rob may not have the symptom of
broken TS gateway, simply because he hasnt used it yet - he does have the
underlying disease of misconfigured RPC in IIS - this is the cause of the
symptom.

I definitely know that MS support has unfathomable resources, I have seen
a tech edit 20-30 deep reg keys to fix a problem for me, but sometimes I
see them just as stumped as I, running through the wizards takes about 5
minutes - give them 15 for good measure, talking to you guys gives me a
good feel for what I will get when I call MS.

So for the moment I will correct all the problems the wizards have made to
get basic remote features working again, in the morning we will open an
incident to see where it leads - any other advice?

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Russ SBITS.Biz [SBS-MVP]

unread,

Feb 25, 2010, 2:13:01 AM2/25/10

John,
Sorry you are having Problems with your SBS Server
I've had great success using the wizards and they are all running fine.
And RPC over HTTPS works fine in all my SBS servers
(I have never had to make any Changes in IIS to "FIX" things)

Wizards will not Break things but bring things in line with SBS standards.
If it breaks things usually this means that the server is not set to SBS
standards.

If you wish support on this issue,
Which seems different in Topic of the original thread,
I suggest a new thread or you may
Contact your SBS Specialist, or contact Microsoft.
Thanks
Russ

"John" <j...@dot.com> wrote in message news:op.u8n7qdgpvul11g@eee...

>> ite/Rpc" -applicationPool:RpcAppPool
>>
>> 4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
>> Site/RpcWithCert" -applicationPool:RpcAppPool
>>
>> One would think you could simply change the paths to say:
>> appcmd.exe set app "SBS Web

Cliff Galiher - MVP

unread,

Feb 25, 2010, 2:48:15 AM2/25/10

John:

As with my previous reply, I will *STRONGLY* suggest you open a new thread.
If the symptoms end up pointing to the same cause, then we can always add
that information back here. But here is my short list:

1) You've "decided" that this is caused by RPC, but have given us no
information why. So I'll repeat my initial request. Start a new thread and
describe IN DETAIL the problem you are having.

2) It is rare that the wizards break something unless other things are
out-of-line as well. This is a good sign that you need to address the
underlying issues that are out of line with what the wizard expects.

3) Download and use the SBS BPA.

4) You mention changes to IIS *and* ps scripts, but again give no details.
It is possible that these changes are, in fact, more harmful than not.
There are many ways to disguise symptoms, but it doesn't make the process
correct. For example, I've seen people "fix" the outlook repeatedly asking
for authentication issue that appeared in December by loosening IIS
authentication rules. Does that work? Sure. But it also exposes OWA to
several security vulnerabilities. The correct fix is to apply Exchange SP1
rollup 9, which alters exchange appropriately so this becomes a non-issue.
Two ways to fix the symptoms, but only one is a real *FIX* for the
underlying problem. I *STRONGLY* suspect that the changes you made are part
of the cause, not the cure, based on the many SBS boxes I've set up that
have never required a single powershell command be run. Take that
experience for what is worth.

In short, there are plenty of people here that are willing to help you.
And, of course, you can open an incident with MS as well. I just want to
prepare you for what you may be in for when you call them. This box sounds
like it has been adjusted enough that they may take more than 5 or 15
minutes to fix this issue.

-Cliff

"John" <j...@dot.com> wrote in message news:op.u8n7qdgpvul11g@eee...

Leythos

unread,

Feb 25, 2010, 6:19:42 AM2/25/10

In article <op.u8n7qdgpvul11g@eee>, j...@dot.com says...

> What happens after you installl
> SBS - you fill out the Wizards to complete setup of your domain - this is
> how it was done, and several features of SBS were disfunctional out of the
> box.
>

Wrong, if you followed the wizards and didn't screw around, all of the
features of SBS would be FUNCTIONAL out of the box.

I just did a Dell 610 server yesterday, brand new, out of the box,
followed the Wizards, everything works perfectly - this is just under
40 SBS 08 systems for me, not including all the times I've installed it
in our QA areas for testing issues with third party apps....

The only issue I have ever run into on SBS 08 is the fragging MS
ForeFront crap that blocks all inbound email by default - I never use
the MS virus crap, but it comes installed by default.

Ace Fekay [MVP-DS, MCT]

unread,

Feb 25, 2010, 9:26:04 AM2/25/10

"Leythos" <spam9...@rrohio.com> wrote in message

news:MPG.25f026d66...@us.news.astraweb.com...

On that note, I have a new small customer that I help order a new Dell 410,
and talked him into SBS 2008. I'm installing it on Monday. It's my first SBS
2008 installation. I'll post back with my success or failure, but I feel
that if I just follow the rules, I should be ok. :-)

Ace

John

unread,

Feb 25, 2010, 9:33:38 PM2/25/10

So Rob - not sure if you have gotten anywhere, but my luck with the wizards was on the down side - I did however find this post on the sbs2008 forum that may aide you in properly fixing your Rpc dir:
------------------------------
"If rpc and rpcwithcert are not there, the Rpc Over HTTP Proxy component has either been uninstalled or they were recreated under the Default Web Site.

Try reinstalling Rpc Over HTTP Proxy again, using the following steps:

Remove Rpc Over HTTP Proxy and reinstall it. Here are the steps:

1. Open Server Manager and go to Features > Remove Features > Uncheck Rpc over HTTP Proxy -- this will also ask you to remove TS Gateway role.

2. Make sure we don't have Rpc and RpcwithCert Virtual Directories anywhere in IIS.

3. Open registry editor and browse through HKLM\SOFTWARE\MICROSOFT\RPC\RpcProxy and create a string 'Website' -- Assign 'SBS Web Application' as the value to this key.

4. Install Rpc over HTTP Proxy feature through server manager again. You should have Rpc and RpcWithCert VDirs under SBS Web Applications website.
Make sure you can browse rpcproxy.dll with a blank page.

5. Run these commands to make sure Outlook Anywhere is working:

Disable-OutlookAnywhere -Server:<servername>

Enable-OutlookAnywhere -Server:<servername> -ExternalHostname:<ExternalFQDN> -ExternalAuthenticationMethod:NTLM -SSLOffloading:$true

--
Chris Puckett"
-------------------------------
Good luck - John

---
frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl

Mark Jones

unread,

Nov 26, 2010, 6:11:24 AM11/26/10

Hey Chris,

I will just in here to provide feedback.

To many people get on their high horse and this that "Wizards" solve everything.

In this case, they didnt for me. Yes, I have 20+ years supporting Microsoft stuff.

The details that you provded though were perfect.

The registry key fixed my issue when reinstalling.

Pity people just wanted to debate crap, rather than use some knowledge to provide actual useful advice.

> On Monday, February 22, 2010 7:44 PM It's me again wrote:

> SBS 2008, being the odd duck that it is, moves certain virtual directories
> from the Default Web Site to the SBS Web Applications site during
> installation. Among the vdirs moved are the RPC and RPCwithCert vdirs that
> are critical to Outlook Anywhere. These vdirs are associated with the RPC
> HTTP proxy feature. Now, if the RPC HTTP proxy feature is removed and then
> added again in SBS 2008 using Windows Server Manager (which the last time I
> looked was part of SBS 2008), the RPC and RPCwithCert vdirs are put in the
> Default Web Site and Outlook Anywhere in a one cert installation is broken. I
> have examined the script in the CAS role repair of Exchange Server (SBS
> version) and do not see how the RPC and RPCwithCert vdirs are being moved.
> Absent a cookbook procedure it would be nice if the RPC and RPCwithCert apps
> were fully documented which would at least provide a way to recreate them in
> the proper IIS 7 site. Somebody tell me there is an easy way to fix my broken
> SBS 2008.

>> On Monday, February 22, 2010 7:56 PM Russ SBITS.Biz [SBS-MVP] wrote:

>> I am unsure on what You've done.
>> You've Uninstalled RPC HTTP For a reason?
>> Was it not working or did you manually move a web directory or something?
>> and re installed it (How did you reinstall it?)
>>
>> And you say one CERT Installation is Broken?
>> (More Details please.)
>>
>> Errors in Logs etc.
>> Symptoms
>>
>> Have you run the Configure network and network fix wizard?
>> or Run the Best Practices Analyzer and see what you can see.
>>
>> Not to sound harsh but if you want the easiest way to fix this,
>> is to call someone and have them do it.
>>
>> Be it Microsoft or your SBS Specialist guy.

>>
>> Russ
>>
>> --
>> Russell Grover - SBITS.Biz [SBS-MVP]
>> MCP, MCPS, MCNPS, SBSC
>> Microsoft Certified Small Business Specialist
>> SBS2003 SBS2008 Support - www.SBITS.Biz
>> Question or Second Opinion - www.PersonalITConsultant.com
>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>> On Monday, February 22, 2010 8:55 PM It's me again wrote:

>>> Hi Russ,
>>>
>>> As you know, in SBS 2008 there is a Server Manager application where one can
>>> add or remove roles and features, as well as perform other tasks. If the RPC
>>> HTTP proxy feature is removed (using Server Manager), upon reinstalling RPC
>>> HTTP proxy (again with Server Manager) one finds that the RPC and RPCwithCert
>>> Apps that were originally in the SBS Web Applications site (cf IIS 7) are now
>>> in the Default Web Site. One of the benefits of having RPC and RPCwithCert
>>> being in the SBS Web Applications site is that a single SSL connection
>>> listening on port 443 can be used for several web applications, as well as
>>> Outlook Anywhere.
>>>
>>> It came as a surprise to me that by simply removing and reinstalling a
>>> feature I could break part of the customization that is small business
>>> server. I have been looking high and low for a way to recover the original
>>> configuration and can find no discussion of this problem anywhere. I did come
>>> across a few people who said this happened to them, but it is going on two
>>> years with SBS 2008 and not a peep from anyone connected with Microsoft.
>>> Please tell me I am just confused and/or there is a simple solution to fix
>>> the problem I have described.
>>>
>>> - Rob
>>>
>>> "Russ SBITS.Biz [SBS-MVP]" wrote:

>>>> On Monday, February 22, 2010 9:05 PM Russ SBITS.Biz [SBS-MVP] wrote:

>>>> Well if it just recent
>>>> Restore your OS Drive from backup
>>>> That's the easiest

>>>> Russ
>>>>
>>>> --
>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>> MCP, MCPS, MCNPS, SBSC
>>>> Microsoft Certified Small Business Specialist
>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>> On Monday, February 22, 2010 9:36 PM Cliff Galiher - MVP wrote:

>>>>> Since SBS 2008 is "built" on Windows Server 2008, it has the windows server
>>>>> tools, including ADUC, ADSI, and the server manager snap-in.
>>>>>

>>>>> That does not mean you should *use* these tools. If there is not a wizard to

>>>>> do something, that means one of two things:
>>>>>
>>>>> 1) It should not be done in SBS because of licensing or technology
>>>>> restrictions.
>>>>> 2) It should only be done if there is a business need and a *very*
>>>>> experienced Windows professional familiar with SBS is making those changes.
>>>>>
>>>>> In this case, you used a tool that was not SBS aware to try and install
>>>>> something and now things are very shuffled.
>>>>>
>>>>> Depending on the extent of the damage, you have several options:
>>>>>
>>>>> 1) Restore a backup. Yes, this will re-introduce the problem you were
>>>>> trying to fix, but chances are we can walk you through that and resolve the
>>>>> issue more easily than the state you are in now.
>>>>>
>>>>> 2) Try the SBS wizards. In particular the FNCW and CTIW could be useful. I

>>>>> doubt the IAMW wizard will do much in this instance, but it cannot hurt
>>>>> either. These wizards are interlaced, so the "I doubt" is literal; they have
>>>>> surprised me by rebuilding stuff internally that I did not expect them to

>>>>> more than once.
>>>>>
>>>>> 3) Rebuild the exchange roles. There is a technet article on this. It is
>>>>> very risky, very difficult, and step #1 would be MUCH more preferencial at
>>>>> this point, but if you have somehow gotten yourself past the point of
>>>>> return, it is an option. It is *SO* far out of the realm of a good option

>>>>> though that I will not post the link until we have exhausted all other options.

>>>>> Sorry, I just feel that strongly about it.
>>>>>
>>>>> Hope that helps,
>>>>>
>>>>> -Cliff

>>>>>> On Tuesday, February 23, 2010 12:09 AM It's me again wrote:

>>>>>> Hi Cliff,
>>>>>>
>>>>>> Thank you for taking the time to offer your observations concerning SBS.
>>>>>>

>>>>>> As for not using the tools that are provided with the product, do not you
>>>>>> find such a practice to be just a little strange? If Microsoft knew that

>>>>>> using a particular tool would break the product, do you not imagine they

>>>>>>> On Tuesday, February 23, 2010 12:46 AM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>> Rob
>>>>>>> No offense,
>>>>>>> But actually not running the wizards are probably where it went wrong.

>>>>>>> Microsoft does not disable snap-ins because they are a integrated part of the

>>>>>>> OS
>>>>>>> SBS is a Module on top of Server2008 not a rebuild of OS from ground up.
>>>>>>> (And you can not separate the two.)
>>>>>>>
>>>>>>> The three Rules of SBS are:
>>>>>>> 1. Use the wizards.
>>>>>>> 2. Use the wizards.
>>>>>>> 3. Use the wizards, and if no wizards then the snap ins.
>>>>>>>
>>>>>>> yes these are "RULES" not guidelines...
>>>>>>>
>>>>>>> SBS2008 Requires you to use the wizards to run effectively.
>>>>>>> As it seems now, you are finding out the hard way.
>>>>>>>
>>>>>>> Sorry to say but your phrase:

>>>>>>> " there is nothing being done in any SBS wizard that cannot easily be done
>>>>>>> using the tools given."

>>>>>>> I totally disagree with, and as a result, is probably why you are in the
>>>>>>> state you are.
>>>>>>>
>>>>>>> If you have added users and done other tweaks
>>>>>>> and not used the SBS wizards, which I suspect.
>>>>>>>
>>>>>>> You may have already put your server in a "Unsupported" Position.
>>>>>>> In which case you have to bring your server into SBS standards.
>>>>>>> (not the standards you used to.)
>>>>>>>
>>>>>>> These "Standards" are different for SBS which is why Microsoft
>>>>>>> has created a new Certification Just for the SBS Products
>>>>>>> They are called "Small Business Specialists"
>>>>>>> Which is a group that Cliff and I are Members of.
>>>>>>>
>>>>>>> If you have avoided Wizards like I suspect you may have to call Microsoft.

>>>>>>> In which case you will get the "Why did not you use wizards" from them also.

>>>>>>> (Sorry but you will hear it from them also.)
>>>>>>>
>>>>>>> This Document written for SBS2003 however the rules stills applies
>>>>>>> Introduction to Windows Small Business Server 2003 for Enterprise IT Pros
>>>>>>> http://www.microsoft.com/downloads/details.aspx?familyid=71211053-CCD6-4F2B-BBD9-5E7B97C232EC&displaylang=en
>>>>>>>
>>>>>>> If you are still Determined to not use wizards
>>>>>>> Be aware you will fight SBS2008 every step of the way. and you will not be
>>>>>>> happy with it.
>>>>>>>
>>>>>>> Rob you can try to save this server by running the wizards that cliff
>>>>>>> mentions.
>>>>>>> however I suspect at this point I think you should call Microsoft.
>>>>>>> or flatten the box and start over using wizards.
>>>>>>>
>>>>>>> However if you do not ever want to run a wizard
>>>>>>> I suggest another Microsoft product as you will not be happy with SBS2008
>>>>>>>
>>>>>>> Here are some books that I highly suggest if you want to learn about SBS2008
>>>>>>>

>>>>>>> Windows?? Small Business Server 2008 Administrator's Companion

>>>>>>> http://www.amazon.com/Windows%C2%AE-Business-Server-Administrators-Companion/dp/0735620709/ref=sr_1_3?ie=UTF8&s=books&qid=1241297332&sr=1-3
>>>>>>> And OR
>>>>>>> Windows Small Business Server 2008 Unleashed
>>>>>>> http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
>>>>>>>

>>>>>>> Russ
>>>>>>>
>>>>>>> --
>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>> On Tuesday, February 23, 2010 1:46 AM Cliff Galiher - MVP wrote:

>>>>>>>> Hello Rob,
>>>>>>>>
>>>>>>>> Unfortunately, the way I read your post, is that you want to have your cake
>>>>>>>> and eat it too. On one hand you want MS to disable options that are

>>>>>>>> "dangerous" but on the other hand you do not want to use the wizards because

>>>>>>>> they are too "black box" for you and you want the option to do everything
>>>>>>>> manually. Do you not see the direct contradiction in that?
>>>>>>>>
>>>>>>>> In short, SBS is designed to allow the *average* office worker do daily
>>>>>>>> tasks such as adding users, monitor the server for problems, and do basic
>>>>>>>> maintenance. As such, the wizards have been specifically designed to
>>>>>>>> automate much of that work. The downside to that approach is that the
>>>>>>>> wizards *must* make certain assumptions (or the stop becoming "wizards") and
>>>>>>>> thus are more frail to external changes. So you have a choice, use the
>>>>>>>> wizards, or accept the responsibility of NOT using them.
>>>>>>>>

>>>>>>>> But do not kid yourself. This is still a server product. It is automated to

>>>>>>>> the extent that *BASIC* tasks are automated. Reconfiguration, significant
>>>>>>>> environmental changes, and feature adjustments will *never* be listed under
>>>>>>>> basic/daily tasks in any reference on any server. As such, they should only
>>>>>>>> be done with backups, more backups, a thorough understanding of process and
>>>>>>>> consequence, and finally ideally in a test environment first. That is how
>>>>>>>> sysadmins manage servers and keep their job. Not exclusive practices to SBS
>>>>>>>> here.
>>>>>>>>
>>>>>>>> So you can ask for someone to help unravel the black box all you want, but

>>>>>>>> the simple harsh truth is you have gone far enough down the rabbit hole that I

>>>>>>>> doubt anybody will be able to explain the intricacies to your satisfaction.
>>>>>>>>
>>>>>>>> So your choices are simple:
>>>>>>>>
>>>>>>>> 1) Leave your server as is and hope/wait for someone to hold your hand.
>>>>>>>> Each day you wait is a day your backup gets older and the chances of a quick
>>>>>>>> recovery diminish.
>>>>>>>>
>>>>>>>> 2) Call Microsoft CSS and pay for support. They may not give you the level
>>>>>>>> of detail you want, but they are skilled at recovering from problems, and
>>>>>>>> since it is a charge service, response is usually timely and efficient (if
>>>>>>>> not enlightening.)
>>>>>>>>
>>>>>>>> 3) Proceed with previous recommendations, limit your downtime, and learn
>>>>>>>> from your mistakes.
>>>>>>>>

>>>>>>>> Understand that I have no vested interest in which approach you use. I am

>>>>>>>> simply trying to give you the *easiest* out I can based on the condition

>>>>>>>> you have set up. The choice is yours.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> -Cliff

>>>>>>>>> On Tuesday, February 23, 2010 1:50 AM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>>>> Cliff I should let you write these (use the wizards) next time
>>>>>>>>> You are better at it :)
>>>>>>>>>

>>>>>>>>> Russ
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>>>> On Tuesday, February 23, 2010 1:52 AM Cliff Galiher - MVP wrote:

>>>>>>>>>> Aye, and for the record, the link you posted was *NOT* what I'd recommend
>>>>>>>>>> doing by the way. Uninstalling (or reinstalling) an entire exchange server
>>>>>>>>>> role just to fix an IIS issue is *EXACTLY* going farther down a path of
>>>>>>>>>> unistalling things that are best left alone. Exchange (as far as I can tell
>>>>>>>>>> from your previous posts) is working, so no, your assumption of what I'd
>>>>>>>>>> post was, sadly, wrong. But it does highlight my point of trying too hard
>>>>>>>>>> to do something that causes more harm than good, and why I am *NOT* posting
>>>>>>>>>> any references to further hard-line repair procedures yet. They could, if
>>>>>>>>>> abused, introduce their own set of problems.
>>>>>>>>>>
>>>>>>>>>> -Cliff

>>>>>>>>>>> On Tuesday, February 23, 2010 6:43 AM Leythos wrote:

>>>>>>>>>>> Itsme...@discussions.microsoft.com says...

>>>>>>>>>>>
>>>>>>>>>>> For those that have researched, used, built, maintained SBS systems for

>>>>>>>>>>> any real period of time, we have all learned that the PROPER and BEST

>>>>>>>>>>> methods to manage a SBS server is to use the Wizards, ALWAYS.
>>>>>>>>>>>

>>>>>>>>>>> That's not to say that you cannot do it the manual way, but you should

>>>>>>>>>>> not expect the "Manual" way to work as it does using the Wizards.
>>>>>>>>>>>
>>>>>>>>>>> As an example, I used UDUC in SBS03 to copy users accounts where I was
>>>>>>>>>>> creating a user with the same permission groups (we normally have 20 odd

>>>>>>>>>>> NTFS Permission/Security groups related to file structures), so it is

>>>>>>>>>>> easier to use the SBS 03 ADUC to ensure that new users get the same

>>>>>>>>>>> permissions as others like them, but, since I did not use the wizard,

>>>>>>>>>>> they have to be added to the company web manually and if I was to create
>>>>>>>>>>> a user from scratch I would have to add them into specific groups for
>>>>>>>>>>> RWW to work.
>>>>>>>>>>>
>>>>>>>>>>> With SBS 08, just because you create a User account using ADUC, it

>>>>>>>>>>> does not mean you get an email account, you have to do that manually
>>>>>>>>>>> too.... I do not use the same process in SBS08, I always use the wizard

>>>>>>>>>>> in 08.
>>>>>>>>>>>
>>>>>>>>>>> If you use the Server 03/08 tools instead of the SBS 03/08 tools, "just

>>>>>>>>>>> because they are there", then you are showing that you do not know much
>>>>>>>>>>> about SBS and how it is structured.

>>>>>>>>>>>
>>>>>>>>>>> Removing things are the last thing you want to do.
>>>>>>>>>>>
>>>>>>>>>>>

>>>>>>>>>>> If Users researched the product and management before they started using
>>>>>>>>>>> the product, do you imagine that they would do things that break SBS?
>>>>>>>>>>>
>>>>>>>>>>> If Users were reasonable, do you imagine they would disable/remove
>>>>>>>>>>> things without first checking to see what it might impact?
>>>>>>>>>>>
>>>>>>>>>>> --

>>>>>>>>>>> You cannot trust your best friends, your five senses, only the little
>>>>>>>>>>> voice inside you that most civilians do not even hear -- Listen to that.

>>>>>>>>>>> Trust yourself.
>>>>>>>>>>> spam9...@rrohio.com (remove 999 for proper email address)

>>>>>>>>>>>> On Tuesday, February 23, 2010 12:51 PM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>> Honestly, I do not know why you guys are pushing this to Rob (it is Me Again).

>>>>>>>>>>>> He stated he feels flatly against out of box solutions and would rather do
>>>>>>>>>>>> it manually, so IMHO, no matter how many times or how you state it,
>>>>>>>>>>>> apparently he will not follow the SBS rules. Unfortunate, however, this is
>>>>>>>>>>>> the case, for it is simply breaking his instalation.
>>>>>>>>>>>>

>>>>>>>>>>>> --
>>>>>>>>>>>> Ace
>>>>>>>>>>>>
>>>>>>>>>>>> This posting is provided "AS-IS" with no warranties or guarantees and
>>>>>>>>>>>> confers no rights.
>>>>>>>>>>>>
>>>>>>>>>>>> Please reply back to the newsgroup or forum for collaboration benefit among
>>>>>>>>>>>> responding engineers, and to help others benefit from your resolution.
>>>>>>>>>>>>
>>>>>>>>>>>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
>>>>>>>>>>>> MCSA 2003/2000, MCSA Messaging 2003
>>>>>>>>>>>> Microsoft Certified Trainer
>>>>>>>>>>>> Microsoft MVP - Directory Services
>>>>>>>>>>>>
>>>>>>>>>>>> If you feel this is an urgent issue and require immediate assistance, please
>>>>>>>>>>>> contact Microsoft PSS directly. Please check http://support.microsoft.com
>>>>>>>>>>>> for regional support phone numbers.

>>>>>>>>>>>>> On Tuesday, February 23, 2010 2:33 PM Cliff Galiher - MVP wrote:

>>>>>>>>>>>>> FWIW Ace, I am not randomly pushing back on Rob. What is done is done. But I

>>>>>>>>>>>>> did recommend using wizards to try and repair the damage, which, if you read
>>>>>>>>>>>>> the entire thread, was rebuffed as "black box" computing. So my reply was
>>>>>>>>>>>>> solely an attempt to lay out the realities. You can use a black-box wizard
>>>>>>>>>>>>> and hopefully be up and running, or you can stick to your "no wizards"
>>>>>>>>>>>>> ideals and stay down. But there is no happy medium.
>>>>>>>>>>>>>

>>>>>>>>>>>>> So I agree, if someone does not want to use the wizards then SBS is probably

>>>>>>>>>>>>> not the product for them. But the reality right now is that SBS is already
>>>>>>>>>>>>> in play, has already been broken, and the wizards may be the easiest way
>>>>>>>>>>>>> out, so I wanted to EXPLICITLY lay that framework out with no equivocation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Cliff

>>>>>>>>>>>>>> On Tuesday, February 23, 2010 2:49 PM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>>>>>>>>> In also support of Cliff
>>>>>>>>>>>>>> Often when 2 or more professionals in the field give the same advice
>>>>>>>>>>>>>> it often helps.
>>>>>>>>>>>>>>

>>>>>>>>>>>>>> I have seen people post here and think, Oh that is just 1 persons opinion
>>>>>>>>>>>>>> (And I am Smarter than they are.)

>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I know when I first Started SBS I too Didn't trust the wizards
>>>>>>>>>>>>>> And reading More and more People saying the same thing.
>>>>>>>>>>>>>> Convinced me that "I" was the person who was wrong....
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So IMO the more "Professionals" that post

>>>>>>>>>>>>>> PLEASE do not do this.

>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The happier He will be, and the happier the client will be.

>>>>>>>>>>>>>> (Which is the result I am going for.)

>>>>>>>>>>>>>>
>>>>>>>>>>>>>> My Goal is to stop IT Companies that #$#@$ over SBS servers...

>>>>>>>>>>>>>> And it is one company at a time.... :)

>>>>>>>>>>>>>> Russ
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>>>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>>>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>>>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>>>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>>>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>>>>>>>>> On Tuesday, February 23, 2010 5:46 PM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>>>>> Hey guys, I am not refuting what you are saying. I completely agree. And I
>>>>>>>>>>>>>>> meant to say "black box" computing, which I did read in the thread, and

>>>>>>>>>>>>>>> hence why I commented that if Rob does not want to use the wizards, there is

>>>>>>>>>>>>>>> nothing we can say to talk him into or out of it, unfortunately. Apparently
>>>>>>>>>>>>>>> he feels that strong about it. Nonetheless, I hope he can fix his issues
>>>>>>>>>>>>>>> that was brought about from ignoring the wizards.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And I wish you the best of luck to help stop IT companies, or even
>>>>>>>>>>>>>>> individuals, for that matter, from #$#@$ over SBS servers... :-)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Ace

>>>>>>>>>>>>>>>> On Tuesday, February 23, 2010 6:26 PM Leythos wrote:

>>>>>>>>>>>>>>>> ace...@mvps.RemoveThisPart.org says...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have older teens, so I am use to talking to the brick-wall :-)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> You cannot trust your best friends, your five senses, only the little
>>>>>>>>>>>>>>>> voice inside you that most civilians do not even hear -- Listen to that.

>>>>>>>>>>>>>>>> Trust yourself.
>>>>>>>>>>>>>>>> spam9...@rrohio.com (remove 999 for proper email address)

>>>>>>>>>>>>>>>>> On Tuesday, February 23, 2010 8:13 PM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>>>>>>> LOL!

>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 4:00 AM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>>>>>>>>>>>>> I know it is job security if I Don't tell people to use wizards however, I'd

>>>>>>>>>>>>>>>>>> rather have a server done right

>>>>>>>>>>>>>>>>>> Russ
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>>>>>>>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>>>>>>>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>>>>>>>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>>>>>>>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>>>>>>>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 9:03 AM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>>>>>>>>> Well, yea, I agree. That is the ultimate goal. :-)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Ace

>>>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 7:31 PM John wrote:

>>>>>>>>>>>>>>>>>>>> I dont know why you guys are badgering Rob - but there should be a simple solution to properly register the RPC directory in IIS - what is it??
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I have a kind of mirrored problem of this issue - my RPC directory exists in the proper SBS Web Applications vdir(never changed or removed it), but several Exchange Power Shell tests show that RPC is broken, and the tests think the directory is missing from the "Default Website" vdir - DUH! of course its missing - cause its in SBS Web Applications - not many issues from this - somehow remote Outlooks still work fine - but TS Gateway features are broke.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> My gut feeling is to NOT run the wizards as they failed to setup the ssl cert with SANs properly configured with autodiscover in the first place. I feel deciphering that nasty guide that Rob posted that is loaded with Power Shell commands may be the only real solution. Working with SBS since Backoffice 4.0, I think I know my way around the block, and I have done my due diligence to research this - if I call MS support (which has crossed my mind) and they cant fix this in 15 minutes - where am I left?? - Means they tried the wizard and it didnt work. My last call to the Exchange department took 2 months to solve a problem, and the resolution was never known, except that its working again. Surely I respect these techs as being quite proficient, my hats are off to you guys, but sometimes it feels like you are thumping your MCSE bible at me.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Point being - MS should definitely better document RPC and how its tied to IIS - something tells me part of that script Rob linked to has the 3-4 lines that fix this hidden in there somewhere.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ---

>>>>>>>>>>>>>>>>>>>> frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl

>>>>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 8:14 PM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>>>>>>>>>>> John,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> In Rob's case, I think the operative word is "re-register" or
>>>>>>>>>>>>>>>>>>>>> "re-install" RPC, which falls under the Exchange 2007 CAS role.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I myself, have been curious from the beginning of this thread, as to
>>>>>>>>>>>>>>>>>>>>> why Rob had to removed RPC to begin with. Was there a problem that

>>>>>>>>>>>>>>>>>>>>> prompted hinm? I do not know. I was trying to read through the rhetoric,

>>>>>>>>>>>>>>>>>>>>> but I cannot ascertain or find any stated reason, even after he was
>>>>>>>>>>>>>>>>>>>>> asked as to why.
>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>> Nontheless, the deed has been done, for whatever reason, and he is
>>>>>>>>>>>>>>>>>>>>> trying to repair it. He mentioned the CAS repair link, but he did not

>>>>>>>>>>>>>>>>>>>>> mention if he followed it, and if so, if it worked. I am also curious
>>>>>>>>>>>>>>>>>>>>> if he followed the KB, if it worked or not.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> And btw John, the link you provided at the bottom of your post, is

>>>>>>>>>>>>>>>>>>>>> actually a link to this thread. I do not know if you are aware of that

>>>>>>>>>>>>>>>>>>>>> or not, or if it was automatically placed by the web-based newsgroup
>>>>>>>>>>>>>>>>>>>>> access method or site that you used to access this group.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Ace
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> This posting is provided "AS-IS" with no warranties or guarantees and
>>>>>>>>>>>>>>>>>>>>> confers no rights.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Please reply back to the newsgroup or forum for collaboration benefit
>>>>>>>>>>>>>>>>>>>>> among responding engineers, and to help others benefit from your
>>>>>>>>>>>>>>>>>>>>> resolution.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
>>>>>>>>>>>>>>>>>>>>> & MCSA 2003/2000, MCSA Messaging 2003
>>>>>>>>>>>>>>>>>>>>> Microsoft Certified Trainer
>>>>>>>>>>>>>>>>>>>>> Microsoft MVP - Directory Services
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> If you feel this is an urgent issue and require immediate assistance,
>>>>>>>>>>>>>>>>>>>>> please contact Microsoft PSS directly. Please check
>>>>>>>>>>>>>>>>>>>>> http://support.microsoft.com for regional support phone numbers.

>>>>>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 8:35 PM John wrote:

>>>>>>>>>>>>>>>>>>>>>> That link is placed there by the msgroups list.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Some further research leads me to this kb:
>>>>>>>>>>>>>>>>>>>>>> http://support.microsoft.com/default.aspx/kb/970259/EN-US
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> relevant commands being:

>>>>>>>>>>>>>>>>>>>>>> 3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/Rpc" -applicationPool:RpcAppPool

>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> 4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/RpcWithCert" -applicationPool:RpcAppPool
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> One would think you could simply change the paths to say:

>>>>>>>>>>>>>>>>>>>>>> appcmd.exe set app "SBS Web Applications/RpcWithCert" -applicationPool:RpcAppPool

>>>>>>>>>>>>>>>>>>>>>>> On Wednesday, February 24, 2010 9:07 PM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>>>>>>>>>>>>>>>>>> John,
>>>>>>>>>>>>>>>>>>>>>>> The reason as you put it We Thump our MSCE Bible
>>>>>>>>>>>>>>>>>>>>>>> is because SBS requires you to follow RULES!
>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>> People do not want to follow the rules with SBS
>>>>>>>>>>>>>>>>>>>>>>> and when they do not and "assume" they know what they are doing and it

>>>>>>>>>>>>>>>>>>>>>>> breaks.
>>>>>>>>>>>>>>>>>>>>>>> They then complain that the product sucks, lacks documentation etc...
>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>> So when they call Microsoft for support and you do not use the rules for SBS

>>>>>>>>>>>>>>>>>>>>>>> You definitely get a BIG Delay in support.
>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>> Why? Because they have to try and UNDO all you have done to break your server.

>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> We are not after Rob to be "mean"
>>>>>>>>>>>>>>>>>>>>>>> but to guide him in the best way to do things...
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Using the wizards with SBS puts your server in a Supported Configuration
>>>>>>>>>>>>>>>>>>>>>>> not using wizards puts SBS in a NON Supported Configuration.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> You are free to do what you wish, however people need to realize the
>>>>>>>>>>>>>>>>>>>>>>> consequences of their actions.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> And that is the purpose of our many posts.
>>>>>>>>>>>>>>>>>>>>>>> Not to harass, but to guide them so they may enjoy SBS not hate it!
>>>>>>>>>>>>>>>>>>>>>>> Russ
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> PS John, if you avoid msgroups.net website
>>>>>>>>>>>>>>>>>>>>>>> and post directly to msnews.microsoft.com with your favorite NNTP Reader
>>>>>>>>>>>>>>>>>>>>>>> You will avoid broken links people not understanding your posts and reading
>>>>>>>>>>>>>>>>>>>>>>> excessive ad's
>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>>>>>>>>>>>>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>>>>>>>>>>>>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>>>>>>>>>>>>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>>>>>>>>>>>>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>>>>>>>>>>>>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 1:45 AM John wrote:

>>>>>>>>>>>>>>>>>>>>>>>> so - following the rules of SBS - used the Fix Network wizard, and Setup
>>>>>>>>>>>>>>>>>>>>>>>> your Internet address wizard - things are worse then before, this is a

>>>>>>>>>>>>>>>>>>>>>>>> relatively fresh server (2-3 months old). What happens after you installl

>>>>>>>>>>>>>>>>>>>>>>>> SBS - you fill out the Wizards to complete setup of your domain - this is
>>>>>>>>>>>>>>>>>>>>>>>> how it was done, and several features of SBS were disfunctional out of the
>>>>>>>>>>>>>>>>>>>>>>>> box.
>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>> Some settings needed to be adjusted in IIS and some ps commands were
>>>>>>>>>>>>>>>>>>>>>>>> performed to correct ssl certs - pretty simple and standard fixes which
>>>>>>>>>>>>>>>>>>>>>>>> the wizards have now broke again.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> The Fix network wizard keeps going on about a TS Gateway issue, click fix
>>>>>>>>>>>>>>>>>>>>>>>> it, says it has resolved the problem, but if you run the wizard again it
>>>>>>>>>>>>>>>>>>>>>>>> identifies the same issue - it doesnt give any details, but most likely it
>>>>>>>>>>>>>>>>>>>>>>>> is not correcting the RPC issue.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Not to hijack a thread, but my issue is quite similar and hopefully
>>>>>>>>>>>>>>>>>>>>>>>> collaboration can aide in resolution, Rob may not have the symptom of
>>>>>>>>>>>>>>>>>>>>>>>> broken TS gateway, simply because he hasnt used it yet - he does have the
>>>>>>>>>>>>>>>>>>>>>>>> underlying disease of misconfigured RPC in IIS - this is the cause of the
>>>>>>>>>>>>>>>>>>>>>>>> symptom.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I definitely know that MS support has unfathomable resources, I have seen
>>>>>>>>>>>>>>>>>>>>>>>> a tech edit 20-30 deep reg keys to fix a problem for me, but sometimes I
>>>>>>>>>>>>>>>>>>>>>>>> see them just as stumped as I, running through the wizards takes about 5
>>>>>>>>>>>>>>>>>>>>>>>> minutes - give them 15 for good measure, talking to you guys gives me a
>>>>>>>>>>>>>>>>>>>>>>>> good feel for what I will get when I call MS.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> So for the moment I will correct all the problems the wizards have made to
>>>>>>>>>>>>>>>>>>>>>>>> get basic remote features working again, in the morning we will open an
>>>>>>>>>>>>>>>>>>>>>>>> incident to see where it leads - any other advice?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

>>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 2:13 AM Russ SBITS.Biz [SBS-MVP] wrote:

>>>>>>>>>>>>>>>>>>>>>>>>> John,
>>>>>>>>>>>>>>>>>>>>>>>>> Sorry you are having Problems with your SBS Server

>>>>>>>>>>>>>>>>>>>>>>>>> I have had great success using the wizards and they are all running fine.

>>>>>>>>>>>>>>>>>>>>>>>>> And RPC over HTTPS works fine in all my SBS servers
>>>>>>>>>>>>>>>>>>>>>>>>> (I have never had to make any Changes in IIS to "FIX" things)
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Wizards will not Break things but bring things in line with SBS standards.
>>>>>>>>>>>>>>>>>>>>>>>>> If it breaks things usually this means that the server is not set to SBS
>>>>>>>>>>>>>>>>>>>>>>>>> standards.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> If you wish support on this issue,
>>>>>>>>>>>>>>>>>>>>>>>>> Which seems different in Topic of the original thread,
>>>>>>>>>>>>>>>>>>>>>>>>> I suggest a new thread or you may
>>>>>>>>>>>>>>>>>>>>>>>>> Contact your SBS Specialist, or contact Microsoft.
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>> Russ
>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>> Russell Grover - SBITS.Biz [SBS-MVP]
>>>>>>>>>>>>>>>>>>>>>>>>> MCP, MCPS, MCNPS, SBSC
>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft Certified Small Business Specialist
>>>>>>>>>>>>>>>>>>>>>>>>> SBS2003 SBS2008 Support - www.SBITS.Biz
>>>>>>>>>>>>>>>>>>>>>>>>> Question or Second Opinion - www.PersonalITConsultant.com
>>>>>>>>>>>>>>>>>>>>>>>>> Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com

>>>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 2:48 AM Cliff Galiher - MVP wrote:

>>>>>>>>>>>>>>>>>>>>>>>>>> John:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> As with my previous reply, I will *STRONGLY* suggest you open a new thread.
>>>>>>>>>>>>>>>>>>>>>>>>>> If the symptoms end up pointing to the same cause, then we can always add
>>>>>>>>>>>>>>>>>>>>>>>>>> that information back here. But here is my short list:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> 1) You've "decided" that this is caused by RPC, but have given us no

>>>>>>>>>>>>>>>>>>>>>>>>>> information why. So I will repeat my initial request. Start a new thread and

>>>>>>>>>>>>>>>>>>>>>>>>>> describe IN DETAIL the problem you are having.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> 2) It is rare that the wizards break something unless other things are
>>>>>>>>>>>>>>>>>>>>>>>>>> out-of-line as well. This is a good sign that you need to address the
>>>>>>>>>>>>>>>>>>>>>>>>>> underlying issues that are out of line with what the wizard expects.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> 3) Download and use the SBS BPA.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> 4) You mention changes to IIS *and* ps scripts, but again give no details.
>>>>>>>>>>>>>>>>>>>>>>>>>> It is possible that these changes are, in fact, more harmful than not.

>>>>>>>>>>>>>>>>>>>>>>>>>> There are many ways to disguise symptoms, but it does not make the process
>>>>>>>>>>>>>>>>>>>>>>>>>> correct. For example, I have seen people "fix" the outlook repeatedly asking

>>>>>>>>>>>>>>>>>>>>>>>>>> for authentication issue that appeared in December by loosening IIS
>>>>>>>>>>>>>>>>>>>>>>>>>> authentication rules. Does that work? Sure. But it also exposes OWA to
>>>>>>>>>>>>>>>>>>>>>>>>>> several security vulnerabilities. The correct fix is to apply Exchange SP1
>>>>>>>>>>>>>>>>>>>>>>>>>> rollup 9, which alters exchange appropriately so this becomes a non-issue.
>>>>>>>>>>>>>>>>>>>>>>>>>> Two ways to fix the symptoms, but only one is a real *FIX* for the
>>>>>>>>>>>>>>>>>>>>>>>>>> underlying problem. I *STRONGLY* suspect that the changes you made are part

>>>>>>>>>>>>>>>>>>>>>>>>>> of the cause, not the cure, based on the many SBS boxes I have set up that

>>>>>>>>>>>>>>>>>>>>>>>>>> have never required a single powershell command be run. Take that
>>>>>>>>>>>>>>>>>>>>>>>>>> experience for what is worth.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> In short, there are plenty of people here that are willing to help you.
>>>>>>>>>>>>>>>>>>>>>>>>>> And, of course, you can open an incident with MS as well. I just want to
>>>>>>>>>>>>>>>>>>>>>>>>>> prepare you for what you may be in for when you call them. This box sounds
>>>>>>>>>>>>>>>>>>>>>>>>>> like it has been adjusted enough that they may take more than 5 or 15
>>>>>>>>>>>>>>>>>>>>>>>>>> minutes to fix this issue.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> -Cliff

>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 6:19 AM Leythos wrote:

>>>>>>>>>>>>>>>>>>>>>>>>>>> In article <op.u8n7qdgpvul11g@eee>, j...@dot.com says...
>>>>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>> Wrong, if you followed the wizards and did not screw around, all of the

>>>>>>>>>>>>>>>>>>>>>>>>>>> features of SBS would be FUNCTIONAL out of the box.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> I just did a Dell 610 server yesterday, brand new, out of the box,
>>>>>>>>>>>>>>>>>>>>>>>>>>> followed the Wizards, everything works perfectly - this is just under

>>>>>>>>>>>>>>>>>>>>>>>>>>> 40 SBS 08 systems for me, not including all the times I have installed it

>>>>>>>>>>>>>>>>>>>>>>>>>>> in our QA areas for testing issues with third party apps....
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> The only issue I have ever run into on SBS 08 is the fragging MS
>>>>>>>>>>>>>>>>>>>>>>>>>>> ForeFront crap that blocks all inbound email by default - I never use
>>>>>>>>>>>>>>>>>>>>>>>>>>> the MS virus crap, but it comes installed by default.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> --

>>>>>>>>>>>>>>>>>>>>>>>>>>> You cannot trust your best friends, your five senses, only the little
>>>>>>>>>>>>>>>>>>>>>>>>>>> voice inside you that most civilians do not even hear -- Listen to that.

>>>>>>>>>>>>>>>>>>>>>>>>>>> Trust yourself.
>>>>>>>>>>>>>>>>>>>>>>>>>>> spam9...@rrohio.com (remove 999 for proper email address)

>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 9:26 AM Ace Fekay [MVP-DS, MCT] wrote:

>>>>>>>>>>>>>>>>>>>>>>>>>>>> On that note, I have a new small customer that I help order a new Dell 410,

>>>>>>>>>>>>>>>>>>>>>>>>>>>> and talked him into SBS 2008. I am installing it on Monday. it is my first SBS
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2008 installation. I will post back with my success or failure, but I feel

>>>>>>>>>>>>>>>>>>>>>>>>>>>> that if I just follow the rules, I should be ok. :-)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ace

>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thursday, February 25, 2010 9:33 PM John wrote:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So Rob - not sure if you have gotten anywhere, but my luck with the wizards was on the down side - I did however find this post on the sbs2008 forum that may aide you in properly fixing your Rpc dir:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "If rpc and rpcwithcert are not there, the Rpc Over HTTP Proxy component has either been uninstalled or they were recreated under the Default Web Site.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Try reinstalling Rpc Over HTTP Proxy again, using the following steps:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Remove Rpc Over HTTP Proxy and reinstall it. Here are the steps:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. Open Server Manager and go to Features > Remove Features > Uncheck Rpc over HTTP Proxy -- this will also ask you to remove TS Gateway role.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. Make sure we do not have Rpc and RpcwithCert Virtual Directories anywhere in IIS.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3. Open registry editor and browse through HKLM\SOFTWARE\MICROSOFT\RPC\RpcProxy and create a string 'Website' -- Assign 'SBS Web Application' as the value to this key.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 4. Install Rpc over HTTP Proxy feature through server manager again. You should have Rpc and RpcWithCert VDirs under SBS Web Applications website.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Make sure you can browse rpcproxy.dll with a blank page.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 5. Run these commands to make sure Outlook Anywhere is working:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Disable-OutlookAnywhere -Server:<servername>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Enable-OutlookAnywhere -Server:<servername> -ExternalHostname:<ExternalFQDN> -ExternalAuthenticationMethod:NTLM -SSLOffloading:$true
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Chris Puckett"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Good luck - John
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl

>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SharePoint 2010 Visual Web Parts using Visual Studio 2010, Feature Designer and Package Designer
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/aef26be2-b36c-4316-b1b7-e55c8b61646b/sharepoint-2010-visual-web-parts-using-visual-studio-2010-feature-designer-and-package-designer.aspx

0 new messages