Exchange 2k Ent Install on Win2k Server

1. you need to have sp1 or sp2 installed on the server.
2.you have to run adc setup with the /scemaonly switch. and after install adc.
3.now you can run the /forestprep switch.

I previously had a multitude of problems with the AD Schema Expansion. The culprit was a bad copy of Exchange 2000. The problems occurred repeatedly until I installed from an original cd.
I don't know if this would apply in your case.

You need Win2k SP1 in order to install exchange 2000.

Do make it as a practise,
from the exchange 2000 CD, seperate the installation to:
1) Do a forestprep
2) Apply the domainprep
3) Install Exchange 2000 (with a service acct that have the Enterprise Admin rights)

This is will be easy for you to troubleshoot.

Active Directory is number one prerequisite for successfull installation of Exchange 2000.
Exchange 2000 extends Active Directory Schema before it is installed. For that reason it is necessary that AD configuration is healthy.
I would direct my troubleshooting efforts to try to find what's wrong with AD. From what you describe it apears that AD schema cannot be updated.

I would search event logs and support articles. Some hints:

- Are your Exchange Admin and Exchange Service accountsmembers of Enterprise Admins group?
- Can you access your AD objects using AD Schema snap in (you need to add this snap-in separately to your mmc console).
- Exchange includes utility AD Cleanup Wizard (adclean.exe) that cleans up AD if you decideto remove Exchange from your configuration. Perhaps you can try cleaning AD prior to installation.
- Are all domain operations masters functional? (Domain naming master, PDC emulator, Schema master, RID master, Infrastructure master).
- As a test I'd try to install Exchange on another computer that is part of the same domain. I'd make this computer a domain controller too.
- Check Q271088, Q256184, Q216899.
- Check that you don't have orphaned domains.

Try running the forest prep from a diffent domain controller. Of course make sure you have all the correct permissions (schema admin). You don't have to run the schem extension from the pdc. See if it crashes from another DC - remember each one has its own copy of AD. Also you could try moving the Schema Master Role to another DC (its probably on your PDC)

Good luck

cp

Please give serious consideration to running Exchange 2000 from another machine. Even if your DC is a quad processor running 1 gig procs and a butt load of memory, you are really asking for trouble.

AD is required (this is for the person who saidto shut it down)

Run your Schema changes, MAKE SURE replication between all DC's takes place after the schema update. Then run the install on a new machine.

P.S. Where did you get the schema modification program from? There are two versions and you have to make sure you have the correct one or you can get all kinds of problems.

Good Hunting

Ive just installed everything you listed onto a new machine and it works fine. Its a DELL poweredge 1300.

Your going to hate to hear this, but i think you may have a hardware incompatibility, or you just need to reinstall form the ground up.

My 2cents

here is my input although my attempt was not on in a production enviroment.I did run into the installation problem wher my dc crashes during install.I do not recall the message exactly but bsod.The procedure I followed thereafter is thus,
1)after reboot I went to root dir,deleted the exchange dir created during partial setup before crash & the setup log file.
2)On member server icopied the entire ex2000 cd in dir exch2000.NB I had to buy a 100MB switch because when I attempted with my existing 10MB hub(error & exit)In your case you probably have a hig speed backbone on your DC,Anyways I attached to that dir & ran setup thereafter & it finished successfully.Also I duplicated the same scenario on another machine but this time I ftp'd my member server on another DC on a child domain I created which was attached to the hig speed i mentioned earlier & I was successful as well.In essence try the network or ftp route.In my case I am dedusing perhaps cd reader failure.I will redo this scenario & will pot results.Hope I helped

You mention running /forestprep. Are you also running /domainprep?

You have to run setup /forestprep then setup /domainprep.

Also, what account are you logged in as when you run setup? You have to be an Enterprise admin and you have to make sure that account has permissions to modify the schema.

What is your AD topolgy? Are you installing this in a single domain or a child domain?

Lastly, is there anything logged in the event viewer after the bluescreen?

p.s. I would also recommend that you install Exchange on a member server all by itself.

Hi Dude

I found a Step by step install description in my wanderings and thought it might help you toward resolution of your problem. It's to big to post here but if you would like a copy just drop me and email

I suppose that your replication is working fine and your hardware is full compatible with w2k
Create another account like exch2k and give admin rights, boot & install exchange with this account.
You mention running /forestprep. Are you also running /domainprep?
Also, what account are you logged in as when you run setup? You have to be an Enterprise admin and you have to make sure that account has permissions to modify the schema.

AD topolgy? Are you installing this in a single domain ora child domain?

Anything logged in the event viewer after the bluescreen?

I would also recommend that you install Exchange on a member server ...

Good luck

you have to install the administrative tools
again by runing the adminpak.msi.now you open
mmc choose add snapin and add the active directory schema snap in.do a right click and select operation master and check the
"the schema may be modified on this domain controler.
good luck !!!!

I don't know if this will help. I have found, when things like this crops up, that I overlooked or missed something. If you go to http://www.mrandy.com/pdf, I have put up a couple of documents that may help. I can put up the entire package if youwould like. These documents are right off if Technet cd. If you read through them, you may find a step that you missed, thereby causing the problem. Hope this helps and I'll keep looking.

Mr. Andy :-)

Try doing that with another hardware-architecture. I had exactly the same problem.

Changed the hardware - worked!

format your Xeon's 600 20GB HD, install once again w2k advanced server + SP's, and then e2k enterprise. It will take you maximum a day.
Unless you may wait (ASAP ;)) another 2 weeks
for our guesses.

One of the following is believed to be true:
* a package file (included with the installation) is damaged and one file couldnt be read correctly,
* your disk is screwed up and you should run scandisk and defrag. Fix any errors.
* a dll file that is installed and is being used is either out of date or damaged.
* the program is trying to use an invalid registry key.

You can go to http://www.sysinternals.com to download File Monitor and Registry Monitor to see what files are used and what registry action is taking place. if you dont see "Success" beside an entry in the registry monitor or file monitor, get that file immediately (maybe from MS) and then try again. Those tools are really useful and they should be used to your advantage.

When you installed the Exchange 5.5 connector did you use the one that came with Win2k or the one that came with Exchange 2000? MS says you should definatley use the one that came with Exchange 2000.

cp

OK. Need some more info (email me on peter_ockenden@yahoo.com).

1st Are you at SP2 (ok MS asked the same question).
2. What's the machine config? disk layout memory, pagefile, etc. (run winmsd to a file).
3. Can you do screenshots of the steps up to the crash.

4. What's the dns name of your domain?

5. How many NICs?

6. What services are running when you start setup?

Keep me informed! I'm a bit bored here and I have a spare server to play with!

Defrag is a very "light " utility, it shouldn't crash, unless there may be a hardware error like:
a) bad sector
b) cross link files
c) RAM memory failure
I hardly recomends you to format your HD and issue a defrag after installing Exchange. Yes,I know that this is not the easiest way to fix a problem, but may be a fast one.

Also check:
* a package file (included with the installation) is damaged and one file couldnt be read correctly,
* your disk is screwed up and you should run scandisk and defrag. Fix any errors.
* a dll file that is installed and is being used is either out of date or damaged.
* the program is trying to use an invalid registry key.

Remember this Microsoft Advice: Do not install any application (like exchange) on a machine with AD instaled.(use another w2k server without AD installed)

Again, good luck

The Win2k setup has a bug: When you upgrade the system from other win version, some feautures doesn't work. I have upgrade my system from win 98 and IIS didn't work and the event viewer was dull of error. The solution was: FORMAT THE DISK and install the Win 2k witout upgrade from a prior version. Now IIS is running and I have no errors in event viewer!!
But first doing this, try to upgrade your kernel, go to http://windowsupdate.microsoft.com

If it doesn't work, FORMAT your disk and install the win 2k again!!!

GDisk the hard drive, reset the MBR and do a low level format. This will unfortunately destroy all your data on your hard drive, but it will reinitialize your hard drive and you will be able to install your OS. BTW, if this is a production server,you might consider replacing it with a new hard drive. If it is brand new, send it back to the vender for replacement. It is not wise to depend on a hard drive that crashes your system.

David Powers

It sounds like a hardware/memory problem. Try to test memory and cpu. There is a shareware utility "BurnInTest PRO" that does a good job. Download from www.passmark.com
Make sure to increase duty cycle in configuration to 75-80%

Clearly, something is messed up with the primary OS installation if a defrag crashes the system.

Solution: FDISK, format, reinstall.

Sorry ...

Maybe your HD is not in good shape, get another disk and reinstall everything.

Regards

A couple things that might help.
1. Check to make sure in your DNS settings that you append parent suffixes of the primary DNS suffix. Fill in your domain name in the DNS Suffix box. and check both boxes to register the connection in DNS and use the suffix in registration.

2. Point your DNS primary and alternate resolvers to the same ip address as the machine you are on.

3. Make sure that you are logged in as the account with local admin rights to the server, and the user belongs to the schema admins, enterprise admins, and the domain admins group. (I am sure you have verified this.)

We had problems with our exchange upgrade install. It was all associated with the DNS issues. GOOD LUCK!

Have you built an additional AD server and moved the Schema Master over to it. Try this then /forestprep.
Might bypass the glitch or at least point you in a better direction as too the problem.

I had more or less the same problem with a W2k-server install. It kept blue-screening me during the install AND WHEN I RAN SPINRITE FROM DOS. It turned out to be some sort of overheating problem (either the CPU or the HD). I managed to do the install by removing the cover and reattaching it after the completed install.

Just my 0.02$

Kim S. Lohse

Well now, since you've chosen to ignore the obviously correct answer of fdisk-format-reinstall, even though your system is pooched, don't expect much further assistance. And don't give me that line about "all the software is fine" when that obviously cannot be the case.

All this tells me your certifications mean nothing.

Paper MCSE, anyone?

First we need to address the defrag problem. If that gets solved, the Exchange install will probably work.

When I have had problems with defrag, it always relates to disk/controller problems. You say you ran scandisk, so I would guess hardware or the way W2K is handling the hardware. Most of the time I find the problem to be with the drives (easiest to corrupt), so try this:

Buy one additional drive.

If you are running Raid-5:
Replace one drive with the new drive and try the installagain. If it still does not work return the original drive to that location and try the next one. Do this until you have tried all drives. If one of the drives is not setup properly, the install should work when that drive is out.

If you are using one drive:
install the new drive, and mirror the two drives. remove the original drive and test.

If one of these methods solves your problem, great. If not, you can call the reseller and tell him you don't want the drive, return it, and reject my answer.

If nothing else, this will test your fault tolerance setup and provide you with the comfort that it is working properly.
Good luck!

Hello Jeremy. I wonder if you ever got an answer to this problem? I would like to make a few suggestions, if you haven't.

STEVE.

move swapfile to raid set. Remove exchange.
rebuild or repair active directory. should only have default users. reinstall exchange and extend schema. please tell me this is not a produciton box and if so why not buy a compaq better deal/better warranty, and if you are an engineer level person your time is more valuble than messing with a homebuilt system you should understand the difference. all systems that are not built by a tier1 vender are 3rd rate because you also have second rate tier1 vendors like dell, who puts pc parts in their low end servers. compaq designs their servers for performance reliability and lower total cost of ownership wich if you are messing with homebuilts you also would'nt understand. so your more the type that should be running linux and sqweezing the pimples on your face in this industry and not asking complex exchange questions.

Wixdem333 said:

"DNS runs fine, domain logins run fine, IIS runs fine, file sharing runs fine. OBVIOUSLY YOUR THE PAPER MCSE if you think that the solution to every problem is to f$%%ing fdisk it. Any paper mcse can fdisk, it takes a talented MCSE to find the source of the problem and fix it."

First, I am not an MCSE, and never claimed to be one, you however do claim to be one, therefore since you're the MCSE, you should have been able to figure it out, but you failed and came here, we offer suggestions, and I only offered my suggestion after all the other intelligent options were either rejected or exhausted.

Secondly, only a fool places all those on one server. Think like a submarine: compartmentalise. The DNS server should be on one machine; the IIS should be on one machine; the Exchange should be on one machine; and the PDC should be on its own machine as well. Putting all that on a single system is asking for trouble, which is exactly what you got. Whomever set that system up that way should be shaved, sterilized, and destroyed.

Thirdly, I never recommend fdisk-format-reinstall unless it is needed to fix a fubar system, which this clearly is since defrag is hosing your system. Undoing all the damage created by pig-piling all the services and software on one machine would take forever, wheras the procedure to wipe and reinstall is faster, cheaper, and easier. Why continue to waste your (presumably valuable) time?

Fourthly, since you're an MCSE, and you haven't found the source of the problem, nor have you been able to fix it, you clearly are not, in your own words, "talented." Thus the previous reference to "paper MCSE" must stick.

And, finally, using insulting comments or masked words (of the off-color kind) are not appreciated here or anywhere else where intelligent people reside. If you can't communicate without using insult or vulgarity, then you need to go away.

Just a thought...
Depending on the size of your network I would think that the problem is memory related.
DHCP and DNS are light applications. Exchange on the other hand is extreamly weighty. I would recommend installing as much RAM as the machine can hold. Then try the expand the active directory. Remember that the expand HAS to happen on the PDC as to accomidate Exchange. Also, remember that AD takes a LOT of disk space. Expecially the Global Catalog which you are expanding.
I think there is also another PREP such as DOMAIN prep you must on top of the forest prep tool.

Are those scsi drives western digital??
I had a similiar defrag problem with w2k adaptec 2100s and wd scsi drives. ended up being the firmware on the drives.

have you tried the /All switch? i had a similar problem with my install and that seemed to fix it (although i dont use lotus or novell, i had to install everything for the install to work)

You might want to check the schema permissions aswell.drewk~

Maybe you have too much running on that machine. I have encountered strange issues on a server of ours, that was resolved once I dedicated each server to a specific service, such as a stand alone IIS server.

You never want to much crap running on one machine, maybe that's where you shoud start.