|
Home > Archive > BizTalk Server Setup > June 2004 > anonymous
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]
|
|
| BizTalk 2004 a great software, but :-( 2004-03-11, 10:43 pm |
| Can’t you invest a little bit more time and resources to test the BizTalk installer?
BizTalk server 2004 is a great product, but the installer is terrible, I don’t believe that this installer was ever tested in a real environment; I even can’t install that product probably in the testing environments.
Try to create a testing environment, Windows 2003 Server, with Active Directory installed (local DNS), SQL Server 2000 SP3, VS.NET 2003, Office 2003, WSS, and with a domain name abc.xyz (yes this domain name) (a simple testing environment)
Then install BizTalk server 2004 and see if it can recognize the xyz extension of the domain, you will run in all kind of problems, and then see if you can configure it.
It will be very nice if you hire a real Q.A. to test the installer with the most common setup combinations, to simulate a real environment, and then to fix that installer.
from 4 different installations, in 4 different environments and software combinations, only 2 of them succeeded. and you can imagine how much time and effort was spent to get those 2 installations working.
Otherwise, if I should be fixing the configuration manually after the installer, what is the point of using BizTalk 2004? I can’t see it saving me any time, if the installation is that complicated, I’ll probably code the project manually; it may take
less time and resources.
Some of the problems:
The installer is not creating the BizTalk groups.
The installer is mixing the windows groups with the domain groups, but the domain controller does not have any windows groups.
The installer requires you manually to create users, and then argues that some of those users are not in the proper groups, like the user is not in the EDI group, when in reality the user is there.
Etc etc etc etc.
I won’t talk about the documentations, I will leave that for someone else :-(
| |
| Ari Ridwan [MSFT] 2004-06-29, 5:51 pm |
|
I understand your frustrations. You made a good point about scenario
testing and I will forward your feedback to the team who is responsible for
the scenario testing.
Regards,
ari.- (MS)
--------------------
Thread-Topic: anonymous
thread-index: AcQHea97Pkkm77hEQHO4AkAvTU3Y7w==
X-Tomcat-NG: microsoft.public.biztalk.setup
From: "=?Utf-8?B? Qml6VGFsayAyMDA0IGEgZ3JlYXQgc29mdHdhcmUs
IGJ1dCA6LSg=?="
<anonymous@discussions.microsoft.com>
Subject: anonymous
Date: Thu, 11 Mar 2004 07:01:08 -0800
Lines: 23
Message-ID: <4CD38314-07A4-455A-8C02-528E64180A22@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.biztalk.setup
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.setup:3253
NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
X-Tomcat-NG: microsoft.public.biztalk.setup
Can’t you invest a little bit more time and resources to test the BizTalk
installer?
BizTalk server 2004 is a great product, but the installer is terrible, I
don’t believe that this installer was ever tested in a real environment;
I even can’t install that product probably in the testing environments.
Try to create a testing environment, Windows 2003 Server, with Active
Directory installed (local DNS), SQL Server 2000 SP3, VS.NET 2003, Office
2003, WSS, and with a domain name abc.xyz (yes this domain name) (a simple
testing environment)
Then install BizTalk server 2004 and see if it can recognize the xyz
extension of the domain, you will run in all kind of problems, and then see
if you can configure it.
It will be very nice if you hire a real Q.A. to test the installer with the
most common setup combinations, to simulate a real environment, and then to
fix that installer.
from 4 different installations, in 4 different environments and software
combinations, only 2 of them succeeded. and you can imagine how much time
and effort was spent to get those 2 installations working.
Otherwise, if I should be fixing the configuration manually after the
installer, what is the point of using BizTalk 2004? I can’t see it saving
me any time, if the installation is that complicated, I’ll probably code
the project manually; it may take less time and resources.
Some of the problems:
The installer is not creating the BizTalk groups.
The installer is mixing the windows groups with the domain groups, but the
domain controller does not have any windows groups.
The installer requires you manually to create users, and then argues that
some of those users are not in the proper groups, like the user is not in
the EDI group, when in reality the user is there.
Etc etc etc etc.
I won’t talk about the documentations, I will leave that for someone else
:-(
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
| Ari Ridwan [MSFT] 2004-06-29, 5:51 pm |
|
--------------------
Newsgroups: microsoft.public.biztalk.setup
From: ariridwan@online.microsoft.com (Ari Ridwan [MSFT])
Organization: Microsoft
Date: Tue, 29 Jun 2004 23:07:54 GMT
Subject: RE: anonymous
X-Tomcat-NG: microsoft.public.biztalk.setup
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="--Next.Tomcat.Message.With.ASCII.and.RTF.8973497230230"
Content-Transfer-Encoding: 7bit
I understand your frustrations. You made a good point about scenario
testing and I will forward your feedback to the team who is responsible for
the scenario testing.
Regards,
ari.- (MS)
--------------------
Thread-Topic: anonymous
thread-index: AcQHea97Pkkm77hEQHO4AkAvTU3Y7w==
X-Tomcat-NG: microsoft.public.biztalk.setup
From: "=?Utf-8?B? Qml6VGFsayAyMDA0IGEgZ3JlYXQgc29mdHdhcmUs
IGJ1dCA6LSg=?="
<anonymous@discussions.microsoft.com>
Subject: anonymous
Date: Thu, 11 Mar 2004 07:01:08 -0800
Lines: 23
Message-ID: <4CD38314-07A4-455A-8C02-528E64180A22@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.biztalk.setup
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.setup:3253
NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
X-Tomcat-NG: microsoft.public.biztalk.setup
Can’t you invest a little bit more time and resources to test the BizTalk
installer?
BizTalk server 2004 is a great product, but the installer is terrible, I
don’t believe that this installer was ever tested in a real environment;
I even can’t install that product probably in the testing environments.
Try to create a testing environment, Windows 2003 Server, with Active
Directory installed (local DNS), SQL Server 2000 SP3, VS.NET 2003, Office
2003, WSS, and with a domain name abc.xyz (yes this domain name) (a simple
testing environment)
Then install BizTalk server 2004 and see if it can recognize the xyz
extension of the domain, you will run in all kind of problems, and then see
if you can configure it.
It will be very nice if you hire a real Q.A. to test the installer with the
most common setup combinations, to simulate a real environment, and then to
fix that installer.
from 4 different installations, in 4 different environments and software
combinations, only 2 of them succeeded. and you can imagine how much time
and effort was spent to get those 2 installations working.
Otherwise, if I should be fixing the configuration manually after the
installer, what is the point of using BizTalk 2004? I can’t see it saving
me any time, if the installation is that complicated, I’ll probably code
the project manually; it may take less time and resources.
Some of the problems:
The installer is not creating the BizTalk groups.
The installer is mixing the windows groups with the domain groups, but the
domain controller does not have any windows groups.
The installer requires you manually to create users, and then argues that
some of those users are not in the proper groups, like the user is not in
the EDI group, when in reality the user is there.
Etc etc etc etc.
I won’t talk about the documentations, I will leave that for someone else
:-(
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
|
|
|
|
|