Well done Mark. That sounds like a smart way around it. A good thing you didn't listen to my advice lol.
Goodluck
"Assumption is the mother of all f#%kups!
Hi guys,
Any issues installing on R2 (win2003)? I have done some research and not come across any issues related to this, wanted to hear from your experiences.
Cheers.
"Assumption is the mother of all f#%kups!
Sorry for lack of reply,
It sounds like a bit of a mess. If you want to start again, i would perform the remove exchange manually option. This will clean out all of the bad stuff. Then reinstall.
Of coarse, i would export all mail and re-import it again.
I don't know much about your site as...
You should only have 1 instance of TS licensing on your domain / forest.
TS licensing is important to the management of Terminal Server access on your network. You have the 90-120 day grace period if this becomes corrupted but having it installed on the box that you general users will use (and...
yes, this should resolve any errors that you have within exchange. Here is some research for you first though:
http://www.msexchange.org/tutorials/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html
Cheers.
"Assumption is the mother of all f#%kups!
No problem Mike, just following my signature at the bottom ;)
Did you try the setup.exe /disatrerrecovery option? May be worth a go. It seems you are pretty close.
"Assumption is the mother of all f#%kups!
Don't install the TS licensing on the same server as the TS. Install this on the DC with FSMO roles. Install the Enterprise version of licensing, not the domain version. You will need to redo what you have already done on the licensing, but this is a good practice.
Even though this is just 10...
If you have rebuilt your domain, and not modified the permissions of the files on this other drive then you will not be able to access these and the result you get is what you should.
Even if you build your domain with the same name, same users and groups this is not going to work. Because all...
Did you restore in 'Directory Services Restore mode'? When recovering AD, you need to use this method.
I have recovered DC's with FSMO roles and without successfully before. Exchange just adds onto this.
I would test the restored server for AD issues using DCDIAG.exe (c:\dcdiag /v...
This server that you are restoring, are you adding it to your network or is it stand alone? And just a general question about your network, is this server the only DC in your domain and if not does it contain and FSMO roles? These are more general understanding questions of how your network is...
Did you perform all of the required tasks when removing 'The first Exchange server in an org'? There are some things you need to do before you can remove. If these weren't done, you have an issue.
"Assumption is the mother of all f#%kups!
Do you want the users to log onto the DC as the terminal server? Or, do you have another server that is your terminal server? This wasn't that clear.
To allow terminal services to service users, you need to install Terminal Services in +/- programs in Win2k3, not just TS licensing.
There is...
I prefer CBTNuggets video training. You can watch it anytime you want and rewind the bits you are unsure on.
http://www.cbtnuggets.com/
I also use Selftest software practice tests (excellent) and books. Getting a couple of opinions is always good. I usually aim to take about a month of study...
High available solutions are not cheap at all. You get what you pay for. Great solution mrdenny. What sort of budget do you have in mind ilceres?
"Assumption is the mother of all f#%kups!
You will need to prepare you current AD for the migration. It is similar to preparing AD for Exchange (/Forestprep and /Domainprep).
Below is a great website that has many great pieces of information with the like to what you need:
https://www.petri.co.il/windows_2003_adprep.htm
This will be...
I second Citrix also, but if you can't justify purchasing W2k3 then Citrix will be even harder to swallow. For me, 100 users wanting to use an app such as this I know it is likely to be much more stable on Citrix.
"Assumption is the mother of all f#%kups!
Create the sites in AD Sites and Services before you create the local DC's for each site. Then promote the servers to DC's locally following the below. This way, when you create the DC's in their relevant IP range, they will automatically be placed in their established site. Then it is a matter...
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.