Search results for query: *

If you wish to to use Server A as a backup or standby system you will need to rebuild the server with the exact same name and settings as Server B is now. You will keep Server A in the closet, or a safe place, until the day comes that you would require an immediate restoration of the Exchange...

As long as you have moved all of the mailboxes off of the old server you should be ok when you power down the old server. The only way to achieve a set of 'fault tolerant' Exchange Servers is to cluster them using an external and mutual raid array where both servers feed off of the same...

You'll need to manually move mailboxes as needed, the old server won't be much of a backup to the new server unless you rebuild it to the identical setup as the new server. Restoring an IS to another server is very very bad. I'm not sure if restoring mailboxes from the new server to the old...

You'll have to provide more details than "strange error". My "jiggy whutz" doesn't work either. On your PDC, the User Manager for Domains has an "Exchange" option on the toolbar. I would remove the options to auto create and delete accounts when doing so with...

It is my understanding that a Palm will only sync to a local storage folder such as PST or OST. Not aware that it can use the Exchange Store. Free and Busy data should be publishing to the Exchange server as is, regardless of where the emails are delivered. That would give others the ability...

my guess would be in the dialing properties of your modem.

do you only want a single exchange server when you are done? want to keep it the same name? Taking the old server offline? There are Q articles to assist you in Technet with this. But in a nutshell, you take the old server offline, backup the stores, then shut it down. Bring the new server...

I hope someone can share some advanced insight into this issue.... I recently took over the admin of our Internet domain. Our primary DNS is provided by a Tier 1 provider. We switched our company's Internet connection to a direct T1 from a 128k line we shared thru a sister company. Obviously...

You will need to apply the Exchange service pack to the PDC, it will update the admin components... Did you actually install the Admin component on the PDC? Or are you attempting to run the Admin utility (the program itself) over the network like say via a shortcut to the BDC? (Obviously you...

you will also need to have admin rights on all servers involved with the connectors...

thru the exchange administrator tool which should have loaded with Exchange on the server, then within each site's "connections" container you should see the site connectors listed..... make sure you have IP and Netbios name resolution to and from all servers involved...

find the connection in all servers involved... you will have to remove the connectors to the old site, recalculate routing, re-establish the site connectors with the new exchange server and the existing sites. recalc routing again... If I understand your problem then that should work for...

I have been asked to add an updated domain name to our Exchange site. We recently purchased another company and want to move to another stmp address for email purposes. How do I add this new/additional smtp domain to my existing site and have that address scheme available to existing and new...

I'm attempting to solve the ghost mailbox and resource issues that everyone else is... BUT... When I run from the command prompt, all I can get to happen is that the ISINTEG syntax options scroll thru the screen. I've been up and down technet and even across the web looking for a clue...

NT domain... less than 10 users... Win 95 PC clients... RDR 3013, RDR timed out request on server, error shows in NT event log... Only seems to occur when users open my computer, windows explorer or attempt to open a drive thru an application, clients have 4-6 drives mapped to the server... 4...

the file is on the PC... the user attempts to complete a function and it randomly gives this error... it does not have a pattern at all.. say ok the error message and the function is able to be completed... there is only one system with this problem, all systems are running access 97.<br> the...

access user... local network access database.. occasionally recv's

I have a set of remote users attempting to access a database via a 56k dedicated frame relay..<br> <br> upon attempting to open the file, access will open but then times out waiting for data, or so I assume.. <br> <br> the files are 60 to 160mb... <br> <br> anybody have info on how far we need...