Pavan is right. You will need SQL because the router/logger processes are on the server. If you install the AW/HDS service on a different host, that will require SQL as well. You will need separate server(s) for the AD/DNS. It isn't supported as a function installed on the IPCC servers.
It doesn't matter if you have a sprawler or a multi-server production setup, these rules apply. Hope it helps, Chris From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan Burtch Sent: Wednesday, March 05, 2014 12:41 PM To: Pavan K Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Setting up ICM Sprawler 8.x This is for a Sprawler. Do you have any experience setting one of these up? Sincerely, Ryan Burtch On Wed, Mar 5, 2014 at 1:38 PM, Pavan K <pav.c...@gmail.com<mailto:pav.c...@gmail.com>> wrote: AD /DNS is usually on a separate box You need SQL anywhere on the logger / aw/HDS/dds boxes. So yes you will need SQL. On Mar 5, 2014 1:03 AM, "Ryan Burtch" <rburt...@gmail.com<mailto:rburt...@gmail.com>> wrote: I have a couple questions on the ICM Sprawler setup. 1. Does SQL need to be installed on the Sprawler? 2. Can AD/DNS be installed on the Sprawler? Sincerely, Ryan Burtch _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip Confidentiality Notice: This email is intended for the sole use of the intended recipient(s) and may contain confidential, proprietary or privileged information. If you are not the intended recipient, you are notified that any use, review, dissemination, copying or action taken based on this message or its attachments, if any, is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy or delete all copies of the original message and any attachments. Thank you.
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip