Jerry
Fri Jan 23 02:14:02 CST 2004
Why would the installed random identifier be the same on all systems? If you
know each Windows installation has its own, random security identifier -
according to you that would be exactly the same on all Windows
installations. I don't understand why it would be difficult to assign a
random id to a default installation. At least the users would not expect the
other identifiers to be sequential, as they do now (and I think it's easy to
see why, the first has an id 1, so the second would be?).
Jerry
"Jonathan Maltz [MS-MVP]" <jmaltz@mvps.org> wrote in message
news:OtMThuU4DHA.2700@tk2msftngp13.phx.gbl...
> Not to mention the fact that the default website is very easy to delete,
as
> we learnt in this thread.
>
> Also think about the way that random identifiers work:
> If you have 2 websites on different IIS 6 servers with the name "second
> server" then they will both have the same "random" identifier. The idea
is
> that a user on another system doesn't know the website's friendly name and
> therefore doesn't know the identifier. What was the point of me bringing
> that up? Well, even if Microsoft _did_ implement their random identifiers
> on the default site, every installation would have the same identifier
> anyway, even if it weren't "1"
>
> Just my $.02 USD
>
> --
> --Jonathan Maltz [Microsoft MVP - Windows Server]
>
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
> tutorial site :-)
>
http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find
out
> here
> Only reply by newsgroup. Any emails I have not authorized are deleted
> before I see them.
>
>
> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> news:%23kSTmYU4DHA.2428@tk2msftngp13.phx.gbl...
> > The point is to not break legacy code. It's called "backwards
> compatibility"
> >
> > Personally I don't understand your thinking. First you complain that "x"
> > product simply won't work with IIS6 because IIS6 uses random
identifiers.
> > When corrected, you complain that IIS6 should be using random
identifiers.
> >
> > Which one do you want?
> >
> > Cheers
> > Ken
> >
> >
> > "Jerry III" <jerryiii@hotmail.com> wrote in message
> > news:OyeG9SN4DHA.1632@TK2MSFTNGP12.phx.gbl...
> > : You may be right in which case Microsoft does a half-*** job again.
What
> > : good are random IDs if they do not use them... Typical...
> > :
> > : Jerry
> > :
> > : "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> > : news:OjedK8J4DHA.2380@TK2MSFTNGP11.phx.gbl...
> > : > "Jerry III" <jerryiii@hotmail.com> wrote in message
> > : > news:uGDlZ1G4DHA.2384@TK2MSFTNGP10.phx.gbl...
> > : > : The same code will fail completely on IIS 6,
> > : > : where even the default web site has a random identifier.
> > : >
> > : > I don't think this is true. As far as I can tell (just checked 2
> Windows
> > : > 2003 Server boxes) the Default website should have 1 as the
> identifier,
> > : and
> > : > the Sharepoint admin site should be 2. All user created sites will
> have
> > : > random identifiers.
> > : >
> > : > Cheers
> > : > Ken
> > : >
> > : >
> > : > "Jerry III" <jerryiii@hotmail.com> wrote in message
> > : > news:uGDlZ1G4DHA.2384@TK2MSFTNGP10.phx.gbl...
> > : > : It looks like they hardcoded 1 as a web site identifier and expect
> it
> > to
> > : > : exist on all IIS installations. The same code will fail completely
> on
> > : IIS
> > : > 6,
> > : > : where even the default web site has a random identifier. There's a
> way
> > : to
> > : > : recreate web site with id 1, just create the key in metabase and
> copy
> > an
> > : > : existing web site's key into it to recreate the structure. Then
> change
> > : the
> > : > : name, address, port and home directory (and whatever else you need
> to
> > : > : change) using ISM.
> > : > :
> > : > : Jerry
> > : > :
> > : > : "EricT" <anonymous@discussions.microsoft.com> wrote in message
> > : > : news:20a701c3e069$8e48a7e0$a501280a@phx.gbl...
> > : > : > Yes, Reporting Services install runs a "System
> > : > : > prerequisites check" which shows has the following info:
> > : > : >
> > : > : > Report Server component requirement
> > : > : > Explanation: Internet Information Services 5.0 (IIS) or
> > : > : > later is not installed or the default Web Site is
> > : > : > disabled. IIS is required for Report Server and Report
> > : > : > Manager.
> > : > : >
> > : > : > Action: To install Report Server and Report Manager, first
> > : > : > install Internet Information Services 5.0 (IIS) or later
> > : > : > and ensure the default Web site is enabled. Or, continue
> > : > : > Setup to complete the installation without these
> > : > : > components. For more information, see the Reporting
> > : > : > Services readme file.
> > : > : >
> > : > : >
> > : > : > What is confusing is that I already have a site running on
> > : > : > port 80. Why isn't it being detected and used as the
> > : > : > default site?
> > : > : >
> > : > : > >-----Original Message-----
> > : > : > >On Wed, 21 Jan 2004 12:24:02 -0800, "EricT"
> > : > : > ><anonymous@discussions.microsoft.com> wrote:
> > : > : > >
> > : > : > >>When I set up my Windows 2003 machine, I deleted the
> > : > : > >>default web site. It's standard practice in our company;
> > : > : > I
> > : > : > >>think we do it for security reasons.
> > : > : > >>
> > : > : > >>Now I'd like to try out SQL Server Reporting Services
> > : > : > >>(RS). But RS requires the default web site be enabled in
> > : > : > >>order to install.
> > : > : > >>
> > : > : > >>How do I re-install or re-create the default web site?
> > : > : > >>Does it need to be on port 80?
> > : > : > >
> > : > : > >There is nothing special about the default web site.
> > : > : > Simply create it
> > : > : > >in the IIS MMC and point it to a folder.
> > : > : > >
> > : > : > >Are you getting an error from the install of Reporting
> > : > : > Services?
> > : > : > >
> > : > : > >Jeff
> > : > : > >.
> > : > : > >
> > : > :
> > : > :
> > : >
> > : >
> > :
> > :
> >
> >
>
>