Thanks for all of your suggestions. I still haven't been able to get this to work. I have changed approaches and have a script that is scheduled to run on the actual SQL Server which uses the SQLDMO.SQLServer object. If it fails initially, the script relaunches it.
Not allowed to modify the SP. Was looking for an easy way to relaunch the SP without giving the night shift production manager SQL manager. I was hoping just to make a quick script.
I am trying to build a utility to run a stored procedure from a simple VBScript. I believe the SQL procedure is running but I can't figure out how to display the return value that the procedure returns. When in SQL, the procedure returns a 0 if it executes properly. I can't figure out what I...
Can you change email address that Sharepoint use to send the emails? I have it sending the mail okay but it uses my personal email address rather the address I want it to use. Is there a trick to changing it? In the Admin site, I type in the address I want it to use, but it doesn't use it...
We just enabled OWA for outside email access. The URL is supposed to be https://email.company.com. When you access that page to get a site under construction. If you add a /owa to the end of the URL, you get the login page. What do we have to change so you don't have to add the /owa...
Pardon my ignorance as I'm not a DNS expert. I'm assuming that if I own "company.com" that I can create as many subdomains as I need without registering them, correct? So I can add "email.company.com" and "autodiscover.company.com" without any problems?
Mapman04
Great. That's an A record, correct? And I'd need a DNS record for the autodiscover.company.com as well, correct? Anything else that would be needed?
Mapman04
I'm trying to implement OWA and Outlook Anywhere for a new Exchange 2007 install. Purchased an SSL Cert with Subject Alternative Names and have it installed. Can access OWA internally. I'm assuming that I'll need to add an external DNS entry for email.company.com resolving to the firewall IP...
Thanks for everyones input. One final question: If the budget allows, would everyone buy a new low-end box to use as a DC or would you take your chances on the old hardware?
Thanks again,
Mapman04
So is the general recommendation to NOT run DCs on the 64-bit platform? I'm apprehensive to run the DC on such an old piece of hardware. I'd have a better (albeit maybe false) sense of security running on new hardware...or even a used piece of equipment that's not 5 to 6 years old. I don't...
The DC is its own separate box. Would use VMWare and virtualize a redundant DC at corporate on a separate box. Would put a DC at the remote site. I was thinking 64-bit for all of those. The Exchange and SQL boxes would also be separate. So my train of thought was to put in the 64-Bit AD...
So should the DCs be 64-Bit machines/OSs? Doesn't it make sense to put the 64-Bit foundation in place, especially since Exchange 2007 requires 64-Bit? I am trying to put in the proper foundation/network backbone, knowing this is my chance to do so. Another significant upgrade might not take...
Can a 64-Bit DC (serving as the PDC emulator) co-exist with 32-Bit backup/redundant DCs? Does it matter hold old the server is? I want to implement a 64-Bit DC and was asked if an existing 32-Bit DC (a PIII 1.0 GHz box 512 MB Ram) running at the remote site across the WAN can still be used...
Thanks for the insight. So this boils down to do you as the end user want to control your mail hygiene with Exchange or use other services to do those functions? Am I correct with that statement?
Mapman04
Yes, where the mail is stored. I just don't see the advantages of adding the Edge Transport Server. Exchange 2003 didn't have such a thing and it worked fine. I know there are major differences between 2K3 and 2K7. I want to make the proper recommendation and for the size of the...
Thanks for the responses. Having limited resources, does it make sense to implement the Edge box? I have to weigh in on how this should be implemented. The Edge could be added later, correct? Does the Edge box spool inbound mail if it can't reach the "actual" exchange box?
Thanks again...
So if the present firewall/security appliance does those functions, it's just an added expense? Do you have to purchase another exchange license to run they edge transport server?
I am researching Exchange 2007 for implementation. This will be a new implementation. Is an Edge Transport server necessary? It will be a single domain infrastructure with approximately 150 users. I'm getting/finding differing opinions. Any insight will be appreciated.
Regards,
Mapman04
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.