We are about to use BizTalk 2004, which I'm very
comfortable with, but an issue in the "known issue" list
has sparked an argument.

I need an expert opinion on it.

Issue number 1 is this:
BizTalk Server 2004 does not work with Microsoft Windows
NT 4.0-based domains or Microsoft Windows 2000-based
domains that are running in Pre-Windows 2000 Compatible
Access mode. Installation of BizTalk Server 2004 into a
domain is only supported on a Microsoft Active Directory
domain environment that is running in Windows 2000 native
mode or later.

My position is that since we are doing all of our
interfacing with BizTalk through web services installed
locally, and are using a custom
authentication/authorization scheme, we could run BizTalk
on a machine that is not on the domain, and still
operate. I'm catching flack on it. SQL Server will be on
the same box as BizTalk, and all sql authentication is
through SQL authentication, not windows auth.

If by 'standard' all input and output is by web services,
and all message queues we will use will be private queues
on the host machine, why would this not work?

We are not planning any implementation other than
Mapping, and Message Queue routing between local private
queues.

Thanks for any input.

[ Post a follow-up to this message ]

One thing to keep in mind is that all sql authentication in biztalk uses
windows authentication, not sql auth (and this is not changeable).

Otherwise, seems fine if you don't need party resolution or single sign on
in your architecture.

Matt


"Darron Jennings" <anonymous@discussions.microsoft.com> wrote in message
news:37eb01c42971$6b1fb5a0$a501280a@phx.gbl...
> We are about to use BizTalk 2004, which I'm very
> comfortable with, but an issue in the "known issue" list
> has sparked an argument.
>
> I need an expert opinion on it.
>
> Issue number 1 is this:
> BizTalk Server 2004 does not work with Microsoft Windows
> NT 4.0-based domains or Microsoft Windows 2000-based
> domains that are running in Pre-Windows 2000 Compatible
> Access mode. Installation of BizTalk Server 2004 into a
> domain is only supported on a Microsoft Active Directory
> domain environment that is running in Windows 2000 native
> mode or later.
>
> My position is that since we are doing all of our
> interfacing with BizTalk through web services installed
> locally, and are using a custom
> authentication/authorization scheme, we could run BizTalk
> on a machine that is not on the domain, and still
> operate. I'm catching flack on it. SQL Server will be on
> the same box as BizTalk, and all sql authentication is
> through SQL authentication, not windows auth.
>
> If by 'standard' all input and output is by web services,
> and all message queues we will use will be private queues
> on the host machine, why would this not work?
>
> We are not planning any implementation other than
> Mapping, and Message Queue routing between local private
> queues.
>
> Thanks for any input.

[ Post a follow-up to this message ]

Thanks for the reply.

The BizTalk process itself could be set up with Windows
Auth (shouldn't be a problem) all of our "corporate" code
will be done from the web services, and COM+ objects we
use. (and they all use SQL auth).

This is also temporary, as we will have moved off our NT4
domain by november or so.


>-----Original Message-----
>One thing to keep in mind is that all sql authentication
in biztalk uses
>windows authentication, not sql auth (and this is not
changeable).
>
>Otherwise, seems fine if you don't need party resolution
or single sign on
>in your architecture.
>
>Matt
>

[ Post a follow-up to this message ]