32-bit DCs, not ready to move to x64, now what?
The only "supported" production-quality E2K7 is the x64 version, right? Since AD needs to be extended for E2K7, and the preparation/extensions need to be done on the Schema master, is moving the Schema master to x64 an absolute requirement?
If the client is not ready for x64, and Virtual Server does not yet support x64 guests (so we can temporarily putup an x64 virtual DC), and there is no 32-bit version of setup.com, does this mean that the client is SOL as far as going to E2K7 is concerned?
If not, does anyone know a work-around?
Réponses
I've just been reading more about this in the help files:
Run the following command:
setup /PrepareSchema
Note the following:- This command connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2007 specific attributes.
It definitely suggests that this will run and connect to the schema master.
I would be intersted to read the bits you mentioned about the reasons for running on the schema master.
Could you point me in the right direction!
Thanks
Nathan
Toutes les réponses
We seem to be in the same situation. We need a workaround or Ex07 32 bit for:
1). Run Forest prep on 32 bit root DC
2). Run Ex07 VM's (32 bit) in our Lab
3). Install Ex07 Admin Tools onto 32 bit machines
Others have suggested that the eval of Ex07 is available in 32 bit, but Eval will time expire.
I got around this by using the 32-bit Beta2 version to run the extension/preparation process. Got E2K7 installed and working now.
Not an optimal situation, IMO.
Hi,
Not 100% sure on this, but I believe that there are changes in the schema extensions from beta2 to RTM. Therefore although you have Exchange running you may not be in the optimal solution and likely also not supported?
If Exchange 2007 is the same as 2003 (I haven't tested this yet) then there should be no problem with running the schema extensions on the first Exchange box you will install.
Hope this makes some sense, with a little luck I will test some of this in the next few days!
Happy New Year
Cheers
Nathan
Well, I looked through the reference docs that I could find and didn't see any mention of changes between B2 and RTM. I may have been looking at the wrong docs.
I also would like to think that you should be able to run the prep on the first E2K7 server, but that's not what the docs are saying. The help files state that you MUST run it on the Schema master, and it went into some details as to WHY this is a requirement. Given the points raised in the help file, I can also see where running it on the first E2K7 server may not be optimal, and I can understand why they are asking for it to be run on the Schema master.
It's just funny that MS is assuming that the Schema master will be x64.
- Nice job MS, look what you've created! Sounds like Deji just Prep'd his Production Forest with Beta Bits. Get us 32 bit or a workaround, come on.
Hi,
Fair enough, sorry for adding confusion to the thread! (Still I mentioned I hadn't tested it)
Anyway, in that case I totally agree with you, assuming the Schema Master is 64bit is a big leap. No doubt they will be gradually, but for now this is just not what is out there!
About the schema changes, I read here the post from Henrik:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1002583&SiteID=17
He mentioned that before upgrading from the beta you should upgrade the schema and domain. That suggested to me that there were changes.
Del; agreed we need a work around althought not a 32bit version of Exchange, a way of doing 32bit schema modifications is a must!
Cheers
Nathan
I've just been reading more about this in the help files:
Run the following command:
setup /PrepareSchema
Note the following:- This command connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2007 specific attributes.
It definitely suggests that this will run and connect to the schema master.
I would be intersted to read the bits you mentioned about the reasons for running on the schema master.
Could you point me in the right direction!
Thanks
Nathan
If you hold my feet to the fire, I will scream loudly and claim that I "think" I read the "justification" for running the commands on a Schema master either in the Help file that I downloaded on MS site, or on the Msexchangeteam blog site. If you insist that i tell the truth, I will limply confess that I am not so sure about where I got the information anymore.
But I did read it somewhere. That doesn't matter now, because I've gone back and read some more, and I can see that you just need to be able to talk to the Schema master during installation in order to have a successful schema extension and AD preparatio.
I apologize for the confusion, and take back some of the bad things I've said about MS :)
Please review this Q/A of this article from very Good Exchange resources KC Lemson and Paul Bowden.
Q I've heard that Exchange 2007 is "64-bit only for production purposes." What does that mean?
A Exchange 2007 is available in both 32-bit and 64-bit flavors.....
http://www.microsoft.com/technet/technetmag/issues/2007/01/ExchangeQA/
Right now the only Ex07 32 bit I'm aware of is part of the Evaluation download, is MS suggesting we Forest Prep, Install Ex07 Admin tools and run 32 bit VM's from Evaluation bits?
Thanks
Hi,
Edit: I realise now that I didn't fully read your post. I see what you mean about the article on the TechNet site.
Right now the only Ex07 32 bit I'm aware of is part of the Evaluation download, is MS suggesting we Forest Prep, Install Ex07 Admin tools and run 32 bit VM's from Evaluation bits?
It seems that where there is not a 64 bit server in the domain (as the command must be run from a 64 bit server) that yes they are suggesting that we prepare AD from the 32 bit code.
The 32 bit version of Exchange is, as you say only for demo and test and is not supported in production. However, it is exactly the same as the 64 bit version so althought it is for eval only it will still perform the same schema extensions. The only difference is that it will run on 32 bit. So for the specific scenario where the Exchange install you a doing is not in the root domain then it would seem that this is the only way currently.
For more info about the reasons for 64 bit see here:
http://msexchangeteam.com/archive/2005/12/29/416613.aspx
Cheers
Nathan
As of this writing, I am unable to locate a 32-bit version of E2K7 on Technet download. The only available version is x64.
I have also tested the scenario of prepping the domain/forest (single forest/domain, 2 DCs), NOT from a DC, but from the Exchange server itself, and the schema/AD/Domain/Legacypermission stuff completed successfully (for me). So, it does appear that there is no reason to look for the 32-bit version at all. Can anyone verify this?
Hi,
Looking at the above posts and the help file, it would seem that if you have a multi-domain forest and you are not installing Exchange in the root domain, you would need to run the Prepare steps on a 64bit machine in the Root domain.
If that isn't possible because one is not available, then you could use the 32 bit download eval version here:
Cheers
Nathan
That pretty much describes the environment we have here. we have 14 domains, in a single forest. and our Exchange servers aren’t going to be going into the root.
Since all of our DCs are 32 bit and not 64, we had to follow the following steps to install Exchange 2007.
First. Build out the server that the new Exchange server will reside on (since Exchange 2007 needs 64 bit. that server is a 64 bit OS).
Next. Join that server to the Root Domain.
From that server Run the Schema Prep, Forest Prep and Domain Prep. on the root domain (you don't have to actually run these tools on the DC, they can contact the Schema Master just fine).
Next Remove the "soon to be exchange server" from the Root domain, and join it to the domain you wish the Exchange servers to live in.
Then simply Prep that domain and install exchange.
You don't actually have to be in the Domain you want to prep. the Domain prep tool can take the name of the domain you wish to prepare. you can also prep All the domains. We didn't do this because of how our security is step on those domains.
One important thing to note:
Make sure that as you move the Computer between domains that your remember to update the DNS entries on the server to point to the right DNS. We set this right for when we had the server in the Root domain. But forgot to do this when we moved it into the Sub Domain. Because of how we do DNS here (which is very weird) things got "interesting".
I would still like to see 32 bit versions of the Admin tools.
right now, we are having to Remote into the Exchange server when ever we want to administrate the Exchange environment.
I am also curious about what’s going to happen with the Users and Computers MMC. is the past. there was the 2003 Exchange plug-in and this was how people enabled and managed there Exchange Users and groups. I think we will need something similar for the Exchange 2007 environment. as it stands right now, it looks like all of our administration will have to happen from the server.
- So I just ran the 32 bit version right on the DC. Got a smaller network with a DC on the Forest Root and 3 sub domains, each of them has an Exchange Server 2003. However I am getting errors when I try to do the Domain preps.
Any advice?
Peter
Peterand
