As for the both server being dns server make sure you have the following.
Windows 2000.
DNS server A will need to have DNS server B as its primary DNS server and its self as a secondary..
and Vice versa Server B will have Server A and its primary DNS..
The reason for this is that you can...
The first thing here is, do you have the exchange 2k server running as a DC?. Exchange and AD will run on the same server but it is not best practice as both are memory hungry... If not never mind the FSMO roles..
If this is a DC.. you will have to run adprep /forestprep and adprep/domainprep...
After you apply SP2 for the forst time the storage is defaulted to 18gb.. to have to set the registry to increase to 75gb (or to 20gb, 30gb etc...) it also increase the size of the public folder store...
Installed IMF v2 (you have to remove IMF first if you have it installed and the new sender...
Need more info.. here..
When you removed the policy from the Domain.. were the clients logged out!! default refresh time is 90 minutes..
Check the path in the registry for the my documents as well as the properties of the my documents folder..
Are you using roaming profiles on the clients...
That would be a good design and departmental setting via GPO will be easier to customise.. if this is a new domain.. do they have an existing domain?.. if so a migration would be best for the user and computer accounts..
are you able to ping the DC's in each others domain?..
is the domain being picked up in network neighbour hood.
try using the domains FQDN name to set up the trusts
if you use ADMT (active directory migration tool) available for download from Mircosoft's website.
you have the option of migration password as well as the account.
If you have new account and old account in the new domain, you can use Active Directory account cleanup wizard to merge the...
check under My Computer>Properties on the remote tab.. make sure that remote desktop is ticked and also make sure that the windows firewall that is installed with sp1 in disabled under Control Panel>Security Centre and select firewall.
there is a patch that you have to install after...
on both servers, flush and register your dns and reload your table..
from the command prompt.
ipconfig /flushdns
then
ipconfig /registerdns
then
nbtstat -R
make sure you use the captial R and not lower case..
then try and resolve. if not..
in the tcp/ip properties of your NIC
make sure...
Exchange migration tool only moves the mailbox..
What I would have done is to installed ADC for windows AD between both domains and then installed ADC for exchange between both Exchange servers. and move the user accounts via ADMT and mailboxes via exchange migration tool
Are the exchange...
why not install the new DC first with the adprep command run. this will fully extent the schema to 2003 ad standard (not native mode 2003 i know that comes later) and then install exchange 2003..
this would be better
make sure that you sites and service has the correct IP subnet address assigned to the correct sites.
In dns under your _msdcs the GC folder you will see the global catalog entry for each site.
make sure that the DC's have to correct settings under the NIC config. If you are using WINS then...
If SP1 you applied is for windows 2003 server you will need to installed a patch.. this is a known issue. if the patch is not applied it can affect IIS..
http://support.microsoft.com/kb/841561
Does the server now have a different IP address. And if so have to configured your firewall to pass port 25 and 443 if you are using a cert to the new ip..
Have you got the smtp connector configured correctly within exchange
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.