BizTalk Server General - Problems with using domain groups instead of local

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > August 2004 > Problems with using domain groups instead of local





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Problems with using domain groups instead of local
Gary

2004-06-28, 7:29 pm

After looking at other posts found issue to be because I
have an NT 4.0 domain which is not supported. Is there any
way BizTalk 2004 can work in an NT 4.0 domain with SQL
Server on seperate box and by using windows integrated
authentication?
Jayaram Mulupuru [MSFT]

2004-06-28, 7:29 pm

Gary,
Per
http://msdn.microsoft.com/library/d...-us/deploying/h
tm/ebiz_depl_install_sbzy.asp, Windows 2000 SP4 is the minimum operating
system required to run BizTalk 2004 in a supported manner.

--jayaram.

--------------------[vbcol=seagreen]

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

hopchouinard

2004-08-11, 5:52 pm

We got the same problem and what we found out is that it would be possible
to have BTS 2004 and SQL server on 2 different servers, in a NT4 domain
environment, IF your SQL server is a W2K server, in which case you can create
local accounts and groups on your BTS 2004 box than manually create the same
local accounts and groups on your SQL server. This works because W2K allow
passtrough security but it is a none supported installation method, so it's
at your own risk.

BTW this does not work if both server are W2K3, since W2K3 doesn't allow
passtrough security.

"Gary" wrote:

> After looking at other posts found issue to be because I
> have an NT 4.0 domain which is not supported. Is there any
> way BizTalk 2004 can work in an NT 4.0 domain with SQL
> Server on seperate box and by using windows integrated
> authentication?
>

Johann Höchtl

2004-08-13, 5:51 pm

I can confirm that, we had the same issues, solved it the same way, and
we're not experiencing any problems yet.

However be warned, if your SQL Server actually is a cluster. In that
scenario everything get's incredible complicated ...

hopchouinard wrote:
[vbcol=seagreen]
> We got the same problem and what we found out is that it would be possible
> to have BTS 2004 and SQL server on 2 different servers, in a NT4 domain
> environment, IF your SQL server is a W2K server, in which case you can create
> local accounts and groups on your BTS 2004 box than manually create the same
> local accounts and groups on your SQL server. This works because W2K allow
> passtrough security but it is a none supported installation method, so it's
> at your own risk.
>
> BTW this does not work if both server are W2K3, since W2K3 doesn't allow
> passtrough security.
>
> "Gary" wrote:
>
>
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com