Re: c:\inetpub -> d:\newname ??
From: root (postmaster_at_buchanangc.com)
Date: 07/04/04
- Next message: Wilco van der Lugt: "Re: No remote acces to OMA or exchange"
- Previous message: keith: "Re: 9x printing on SBS2003"
- In reply to: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Next in thread: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Reply: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 3 Jul 2004 23:26:03 -0700
"Tony Su" <anonymous@discussions.microsoft.com> wrote in message
news:256d901c46185$52ac3a60$a601280a@phx.gbl...
> This is an issue with Win2K3, not just SBS2K3.
>
> Within seconds after I first saw this in the Win2K3 betas,
> I yelled loudly and often about this everywhere I could,
> but no one commented.
>
> Technically speaking, although it's a bother it's actually
> not a particularly big deal to move a website as it's
> first being set up, you simply define a new path for the
> Home Directory.
>
> But, if you're running Services like SharePoint and
> FrontPage, I don't know of an easy "one click" solution
> for moving... You have to reconfigure that from the ground
> up.
>
> So, with SBS that's probably the biggest problem/issue
> likely to discourage anyone from moving the default file
> locations... You'll probably have to go into the
> SharePoint Administrator and manually configure the new
> location with the settings automatically setup by the SBS
> Companyweb/SharePoint Services Setup wizards.
>
> The other possible gotcha is how Companyweb is written. I
> assume that it was written anc configured using relative
> and virtual paths throughout but it's not a certainty and
> can't be tested unless the website and/or database paths
> actually were changed.
>
> And yes, you are very correct that modifying the hardpath
> location can be an important security measure. So many
> attacks don't assume that they have access/permissions to
> be able to reference a relative path, so you usually see
> hardpaths.
I've been playing with it and I simply tried to setup the default website
c:\inetpub\wwwroot as a virtual dir(SBS) under our real public company
website that I'd setup on d:. Then to get the "SBS2003 Welcome" & RWW link
page, all one would have to do is www.companysite.com/sbs That doesn't
work. Although the first "Welcome SBS2003" page shows up fine, all the
links like RWW are dead(401 page not found or somesuch). I don't think it's
permissions but relative links like /Remote which I don't fully understand.
AND some of the filters running/loaded at the default site that aren't at
www.companysite.com and who knows what else.
I'm gonna figure all this out in detail later for SBS2003. I assumed that
somebody else already had. Right now www.companysite.com goes to the our
company's regular public website using host header and simply
companysite.com defaults to the original default site(as will direct IP
entry) so that's how our remote folks will get in for now to the "Welcome
SBS2003" page.
Thanks.
> Tony Su
>
>
>
>
>
> >-----Original Message-----
> >
> >"Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote
> in message
> >news:O1AEP6WYEHA.996@TK2MSFTNGP12.phx.gbl...
> >> See if there's any help here:
> >>
> >> Moving Data Folders for Windows Small Business Server
> 2003
> >>
> >http://www.microsoft.com/technet/prodtechnol/sbs/2003/main
> tain/movedata.mspx
> >
> >I did a full google search including web,
> microsof....sbs, microsof.....iis
> >and www.microsoft.com and the www sites of the locals and
> I can't seem to
> >find much more than....just drag it and drop it and make
> sure you hand
> >change all the home dirs(many are virtual with odd
> implicit linkages) and
> >permissions etc. Then I find stuff about sharepoint that
> seems much more
> >complicated. It's all the special SBS stuff that appears
> to be the problem.
> >I've already installed a real website and (2nd non-
> company but same IP one
> >using host header) to d:\inetpub. Now the rest and the
> new root dir name is
> >the goal.
> >
> >Given that the security freaks agree that one shouldn't
> leave it on c: and
> >also not named inetpub and there being no default way to
> change it, I
> >ASSUMED that someone had worked out the easiest way and
> posted it somewhere.
> >In an older post one of the folks in .IIS when talking
> about CompanyWeb &
> >OWA and all the rest of the special SBS stuff said go
> here and ask...so I
> >did/am.
> >
> >Are there any gotchas here...is that the reason for the
> apparent lack of a
> >wizard or tool/script or install option or good articles?
> >
> >Is everyone still runin c:\inetpub? If not then how are
> most doing
> >otherwise?
> >
> >> "root" <postmaster@buchanangc.com> wrote in message
> >> news:u1RW9ZWYEHA.3596@tk2msftngp13.phx.gbl...
> >> > What's the easiest way to move the whole inet/website
> structure built on
> >a
> >> > default SBS2003 install to a different drive and
> directory. I believe
> >> that
> >> > not having it on C: is optimal for security. As I
> recall install didn't
> >> > offer other than the default install location
> (C:\inetpub).
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >
- Next message: Wilco van der Lugt: "Re: No remote acces to OMA or exchange"
- Previous message: keith: "Re: 9x printing on SBS2003"
- In reply to: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Next in thread: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Reply: Tony Su: "Re: c:\inetpub -> d:\newname ??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
