- CRM on Windows 2003 Server, in SBS 2003 domain?
- Posted by Stephen Rogers on June 29th, 2004
From the implementation guide, I cannot tell if it is possible to
successfully configure MS CRM v1.2 on a Win2003 server PC within a
domain that is controlled by a separate Small Business Server 2003
system. I am running Exchange Server and Sharepoint on the SBS
system, and things run fine. But this system is maxed out and cannot
handle another large application, so I would like to set up MS CRM on
a separate PC. I would also like to set up the required SQL Server on
the CRM box (not the SBS server).
Is this practical/supported?
Secondly, can I use SBS to rout WAN HTTP accesses to the MS CRM web
site, or should I plan to allocate a separate static IP address.? I
use a separate dedicated firewall (not the SBS router) and currently
the only static IP address on my LAN is the SBS server.
Thanks - Stephen Rogers
- Posted by John O'Donnell on June 29th, 2004
You can install CRM on a server which uses another server as the domain
controller.
"Stephen Rogers" <sarogers@optema.com> wrote in message
news:3ae3b38f.0406291045.4cbca536@posting.google.c om...
- Posted by Edwin Garst on June 30th, 2004
Stephen,
The two server setup is ideal in the situation you describe. The
implementation guidelines are 25/40 users recommended/supported on a single
server and 50/100 on three servers. I think the SBS solution of choice for
more than a few users is CRM/SQL on a member server. This is similar to the
current situation with terminal server (application mode) setup for SBS2003.
You should be able to run CRM on a separate SSL port. I will be trying this
out soon and let you know how well it works. I don't expect remote Sales
For Outlook replication and playback function except using VPN.
Edwin Garst
www.epconsystems.com
"Stephen Rogers" <sarogers@optema.com> wrote in message
news:3ae3b38f.0406291045.4cbca536@posting.google.c om...
- Posted by Edwin Garst on June 30th, 2004
Stephan,
See inline
"Stephen Rogers" <sarogers@optema.com> wrote in message
news:3ae3b38f.0406291045.4cbca536@posting.google.c om...
Very practical. But the supported SBS solution is SBS2003 Premium which
includes SQL and ISA. You should determine the expected load from CRM,
perhaps with a Virtual Machine pilot install, and go from there.
If SBS has two nics you can certainly route the incoming CRM traffic through
it's firewall. You should always assign static IP addresses to servers.
You should use SSL for CRM internet access. SBS uses port 443 for Exchange
and remote web workplace. I have succeeded in setting up CRM to listen on
an SSL port (not 443) in CRM 1.2. SSL doesn't work with Crystal in 1.0.
Crystal initially refused to list reports, indicating a signon error
instead. I checked the Knowledge Base and determined that the fully
qualified name of the server (server.domain.local) needs to be added as a
WCS host to the web connector in the Crystal Configuration Manager. It
still uses port 6401. The default WCS name is the netbios name of the
server.
Edwin Garst
www.epconsystems.com