Re: The same old Ex07 32 bit questions
- From: "David Chadwick" <david@xxxxxxxxxxxxxxx>
- Date: Sun, 31 Dec 2006 01:44:18 +1100
Hi,
This isn't a complete answer, but it's what I have found so far.
The evaluation versions available for download appear to be EXACTLY the same
as the full blown retail media. In other words, unlike previous versions of
Exchange, there is actually no such thing as "evaluation media"
specifically. I have done a complete binary file comparison between the
64-bit media from the VLK licensing website and the 64-bit evaluation
download, and they are exactly the same. Not one single file is different.
The only difference is that the VLK media contains every Unified Messaging
langauge pack (making it 5.5Gb) whereas the "eval" download only contains
the UM language for US. You can then download each UM langauge pack
individually. This is just to keep the download size down, rather than
actually being a binary difference between the two sources.
The way Microsoft seem to be doing it now is based on entering the product
key instead. When you install Exchange 2007, you can do it without a
product key. After installation you are now in evaluation mode for 120
days. At any time after installation you can enter your key which will
"unlock" it. It's not like in the past where you would have to install the
retail version over the top of the evaluation install to "upgrade" to a full
copy. Having a single media source makes a lot of sense. I would guess
that there will no longer be the pain that a service pack or hotfix can't be
installed on the eval edition and all that sort of hassle (because now the
eval edition is just normal retail media without a key entered yet).
There is now just one media which covers eval, standard and enterprise
editions, and entering the product key is what makes the distinction. A
much better way of doing it in my opinion. Incidentally, SharePoint 2007
seems to be the same from what I can tell, so I assume this is an overall
change in policy for Microsoft for new products rather than something only
the Exchange 2007 team has done.
The difference between the 32-bit and 64-bit media is that the 32-bit media
doesn't have an option to enter a key. It appears that it can never be
anything other than a 120 day evaluation. I've even tried using the
Powershell cmdlet to enter the key and it complains about the key being
invalid (even though the 64-bit version accepts it).
I would like to see the 32-bit version accept keys and become "unlocked"
too, although I can understand why they haven't enabled this.
Regards,
David
"Mark Arnold [MVP]" <mark@xxxxxxxx> wrote in message
news:hqtap256htt97ptde1n1s91dflirkippmc@xxxxxxxxxx
On Fri, 29 Dec 2006 12:44:04 -0700, "Del" <del@xxxxxxxxxxx> wrote:
yeah we know 64 bit for production and 32 bit not officially supported inWell yes, it's available, it's available for download from MSDN. You
Prod. It seems we still need a 32 bit version though? that won't expire.
1). In lab/test we'd like to run 32 bit Virtual machines
2). In lab/test, until later in 07 we have only 32 bit machines.
3). In Prod, Exchange tools are installed onto many 32 bit machines
4). We have large Forest with many domains, I've read it's best to run
Forest prep on root domain machine. We have no 64 bit machines in our
root
domain.
I know it's difficult to keep 32 bit out of Prod, but will MS make a 32
bit
version of Ex07 available?
could even use it in production. It's just that the second you do
you're unsupported.
I haven't actually seen anything about the expiration of the versions
though (a la Eval editions etc) but given what you have to do and
traces you need to provide then you will have problems as the build
numbers are different.
.
- References:
- The same old Ex07 32 bit questions
- From: Del
- Re: The same old Ex07 32 bit questions
- From: Mark Arnold [MVP]
- The same old Ex07 32 bit questions
- Prev by Date: ldifde HELP
- Next by Date: Re: Issues on warning when logging onto OWA - RPC over HTTP
- Previous by thread: Re: The same old Ex07 32 bit questions
- Next by thread: Re: OWA working outside of network but not inside...sort of.
- Index(es):
Relevant Pages
|
Loading
