Rajiv K Khandelwal replied to Mark Arnold [MVP]
13-Sep-09 02:20 AM
As Mark rightly mentioned there must be some wizard in SBS 2003. SBS 2008
certainly has wizard configuration. I am marking this post in the SBS group
for some expert in SBS 2003 to respond.

Rajiv K Khandelwal
Rightly
(1)
Mentioned
(1)
Wizard
(1)
Configuration
(1)
Marking
(1)
Group
(1)
Expert
(1)
Respond
(1)
  Larry Struckmeyer [SBS-MVP] replied to Rajiv K Khandelwal
13-Sep-09 06:18 AM
Hi Rajiv, Roger, and Mark:

This is a duplicate post of that three posts below this one.  Below is the
answer.  If there are further questions, it would be good to confine the
thread to the SBS group.

To set the default external email address you run the CEICW (second item on
the page, cannot ever remember what it stands for) from the to do list in
Server Management.

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com
  Charlie Russel - MVP replied to Larry Struckmeyer [SBS-MVP]
13-Sep-09 11:27 AM
Configure E-Mail and Internet Connectivy Wizard.

--
Charlie.
http:/msmvps.com/blogs/xperts64

Windows Server - How can I change the default external email address

Asked By Roger
12-Sep-09 04:57 AM
We use Outlook 2003 sp2 and have a small LAN with 3 workstations using a
Server SBS 2003. We are set up to send emails via Microsoft Exchange Server
and never send email to ourselves, only to "external" addresses in the
outside world ! When we send emails to outside the LAN they always show the
local email address, ie roger@ournetwork.local so anyone replying to our
emails will get an "address unknown" message. How can I change the return
address on our emails so that it shows our external address and not the
internal local address. I have been told it can be done, but I cannot figure
it out ... Roger
  Mark Arnold [MVP] replied to Roger
12-Sep-09 09:55 AM
There will probably some wizard for this and someone with better
(some) knowledge of SBS may come in and give you guidance but.... In
normal Exchange land you can start Exchange System Manager and drill
down to Recipients then Recipient Policies. Edit the one that is there
(there ishould be only one).
Change the domain to what you want it to read and you are done. The
addresses will be re-written.
The .local is not needed at all, even if you guys do choose to send
internally at some point so do not worry about it. If you are thinking
help
EMC is Refresh: In Progress. Anyone has any ideas? Thanks. Exchange Admin Discussions Microsoft.Exchange.Configuration.Tasks.GetTaskBase (1) System.Management.Automation.Cmdlet.WriteObject (1) Outlook (1) CASArray (1) MSExchange (1 by an entry ion the eventviewer. See below for contents. Log Name: Application Source: MSExchange Configuration Cmdlet - Remote Management Date: 4 / 1 / 2010 12:16:34 PM Event ID: 8 Task MshCommandRuntime.WriteObject(Object sendToPipeline) at System.Management.Automation.Cmdlet.WriteObject(Object sendToPipeline) at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult(IConfigurable dataObject) at Microsoft.Exchange.Management.SystemConfigurationTasks.GetVirtualDirectory`1.WriteResult(IConfigurable dataObject) at Microsoft.Exchange.Management.SystemConfigurationTasks.GetExchangeVirtualDirectory`1.WriteResult(IConfigurable dataObject) at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult[T](IEnumerable`1 dataObjects) at Microsoft.Exchange Configuration.Tasks.GetTaskBase`1.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() Event Xml: pipeline has been stopped. at System.Management.Automation.MshCommandRuntime.ThrowIfStopping MshCommandRuntime.WriteObject(Object sendToPipeline) at System.Management.Automation.Cmdlet.WriteObject(Object sendToPipeline) at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult(IConfigurable dataObject) at Microsoft.Exchange.Management.SystemConfigurationTasks.GetVirtualDirectory`1.WriteResult(IConfigurable
know that btw :) This step and process is done long before running the actual Migration Wizard process which is the actual migration. If you are using the proper document the mode the issues and proceed with the migration. I am curious. In your original post you mentioned "The error on Exchange is what stuns us though. SP2 has been on it for the same dialog the OP posted) and cannot continue. The log from the migration prep wizard seems to indicate everything is already done, and I have validated that the AD and that is out of sync. Is there any registry setting to fake out the migration wizard having run, or am I stuck doing a manual migration or restoring from backup and server following the MS migration guide and Dave Overtons book and then ran the migration wizard at the end before moving to my new server. The problem appears to be as analyzer tool tells me that it is still mixed. :( then, on destination server the SBS wizard hangs on start and tells me that the preparation tool has not been run on this would have been very easily solved. the sbs 2008 would install fine until the wizard page confirming source name, domain name, dest name, admin account / pwd, etc. At this point my searching. it made troubleshooting the destination server like a pc and not just a Wizard screen that you cannot advance past. - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - Thanks again sharedit :). SOLVED! :) Damn retarded wizards :D Credits
some sort of automation thing going on that is resetting it. Isn't there a "wizard" for what you are doing? Did you use that? Otherwise, that information is kept in Exchange is altering it. - -- Rich Matheisen MCSE+I, Exchange MVP Until you run the backup wizard it will do this. Have you run the backup wizard? That Susan, I did not know. I am curious why it does this? it is log files from growing out of control!), we re-enable it when you run the wizard, and never disable it again (even if you disable the SBS backup tools). So what Exchange logging functionality. How do you do this? Well, you can run the SBS Backup wizard, then run it again and disable it. Or you can modify the setting directly. Simply from the OP on this since I respectfully disagree - I have never run the backup wizard on my SBS03 production server (ShadowProtect), I disabled circular logging in ESM years ago, and it never became re-enabled. I guess there is a small chance I ran the wizard to see some screen or another for some reason, but I am 100% sure that
8063 Could not read the root entry on directory "bc-server.accessguy.local'. Cannont access configuration information. DC = accessguy, DC-local * ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** Any ideas? Exchange Connectivity Discussions Internet Security and Acceleration (1 place in Exchange to change them, but I ran the "Configure Email and Internet Connection Wizard." (One thing I have noticed that seems odd is that the wizard sets the IP address as 99.112.146.98. I do not know where that sone's SOA record is not available on the DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannont be resolved DNS is correct, mail.accessguy.com points to 99.112.146.177. As for running CEICW Wizard in SBS 2003, the 99.112.146.98 address you are receiving is most likely not. My server has two NICs. One goes to the local network hub: (The connect wizard seems to insist on modifying the gateway setting, as you will see in the IPCONFIG 53(ns1.swbell.net)" Could that be an issue?) Here is the IPCONFIG: Windows IP Configuration Host Name . . . . . . . . . . . . : bc-server Primary Dns Suffix . . . . . . . : accessguy Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes
session to directory 'old-DC.corp.local' using local service credentials. Cannot access Address List configuration information. Make sure the server 'old-DC.corp.local' is running. DC = corp, DC = local to the old manual ways of doing things works better. I'd set up the configuration, domain, and global catalog values to use the same DC in the registry. Then see is in DNS in the _msdcs zone. Well, if you remove the organization from the configuration container you remove all of Exchange, not just a single server. That does not sound WINDOWS \ system32 \ inetsrv \ inetinfo.exe ComponentDN: CN = Comapny Name, CN = Microsoft Exchange, CN = Services, CN = Configuration, DC = gb, DC = vo, DC = local Event ID 2078 MSExchangeDSaccess Process INETINFO.EXE (PID = 1244 to use this machine for is recovery work, I'd make careful note of its configuration (location and names of file systrem directories, etc.) and remove the machine using setup.exe. Then reinstall the machine using the same name and configuration. The machine is not used for anything else, right? it is not the OAB server