Prepare Exchange 2010 Test Environment with Hyper V

Hi
We are preparing a test environment to check the migration from Exchange 2010 to 2013 and to get familiarized with 2013. Created the VMs of existing Domain Controllers using D2V tool, looking for suggestion on how to prepare the Exchange 2010 servers
( 2 X MB servers in 1 DAG and 2 X Hub/CAS servers in WNLB) in VM environment - either by creating VMs of existing physical servers using D2V without DB storage LUNs (Dial tone DBs) or prepare the Exchange 2010 servers from DCs created in test lab.
Thanks in advance

There's got to be a question in here somewhere. How about a guide to setting up Exchange 2010 that you can then use for a test environment:
http://technet.microsoft.com/en-us/library/ff709381(v=EXCHG.141).aspx
Now, if you are asking how to configure your test environment to mimic production, you should probably get directory exports of your users, groups, and contacts (rather than trying to remove a production domain controller to use as the initial domain controller
in your test environment), since it allows you to connect between the two environments without jumping through huge numbers of hoops - it also allows you to send email between them, which can be useful when testing external connectors.

Similar Messages

SSL-Problems when setting up a test environment with Exchange

Hello everyone,
I am trying to set up a test environment with Exchange 2013 to learn how the stuff works. However, I am facing some problems due to the fact that Exchange is designed for use with SSL certificates. The main thing that makes problems is the connection with
RPC over HTTP. I've used the MS remote connectivity analyzer to find out why it is not working and as I thought it is because of a missing SSL certificate (it seems the self signed doesn't work here). Now in order to get this working I just bought a certificate
for "mydomain.com". Now here is the first problem: This certificate is NOT a wildcard certificate. So if I understood correctly it works for mydomain.com but it won't work for subdomain.mydomain.com. Is this correct? (First question)
If this is correct I will probably another problem: As I said this is a learning-environment so the server is at home behind a router. This means: Only one WAN-IP. I think could get this working by forwarding everything to the Exchange Server (like mydomain.com
goes to the WAN-IP where the router is forwarding everything like port 25 or 443 directly to the exchange Server). This way I wouldn't have any problems I think: mydomain.com has a valid SSL cert, it resolves to my WAN-IP which forwards everything to the internal
Exchange Server. Now here is the problem: I plan to setup a SharePoint Server as well. I thought about using ARR (IIS) to make both available behind the same WAN-IP without using ports inside the url. Ideally the Exchange Server should then be available via
"mail.mydomain.com". This will work fine with ARR but then I probably have SSL problems again? (second question)
Do you have any ideas what I can do to solve such problems? Should I buy another certificate for mail.mydomain.com? But then I would need to buy several certificates (e.g. for autodiscover.mydomain.com to get this working as well). This can become very expensive...
Thanks!
Regards
Christian

Hi,
For your first question, if there is a single certificate just for “mydomain.com”, it cannot work for subdomain.mydomain.com.
Generally, antodiscover.domain.com is used to access the autodiscover service for external users. If you just need test users to access Exchange server from internal environment, it is not necessary to get a certificate for autodiscover.domain.com.
Therefore, for your second question what I can ensure is that if all URLs that used to connect Exchange from internal and external are configured to mail.mydomain.com with all services(IIS,SMTP,POP,IMAP), there will be no certificate problems in Exchange
side.
Best Regards,
Winnie Liang
TechNet Community Support

ISA 2006 publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation

Hi,
I have two Exchange 2010 Sp1 CAS with Windows Network Loadbalancing. I set up an alternate Serviceaccount and mapped the http,ExchangeMDB,PRF and ExchangeAB SPNs.
Then i published the Exchange Services via ISA 2006. OWA is working using Internet -> via NTLM -> ISA(webmail.domain.com) -> via KCD -> CAS-Array(ex2010.domain.com)
I tried the same with Outlook Anywhere (RPC over HTTP) without success.
Authentication to the ISA via NTLM works fine, but i think the isa server cannot delegate the Credentials successfully to the CAS-Server.
The ISA Log looks like:
Allowed Connection ISA 24.11.2011 15:50:40
Log type: Web Proxy (Reverse)
Status: 403 Forbidden
Rule: Exchange 2010 RPC
Source: Internal (172.16.251.33)
Destination: (172.18.10.182:443)
Request: RPC_OUT_DATA
http://webmail.domain.com/rpc/rpcproxy.dll?ex2010.domain.com:6001
Filter information: Req ID: 108b89d8; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: https
So i always get a 403 Forbidden from the CAS.
I the IIS logfile from the cas server i see this entry:
2011-11-24 15:51:37 172.18.10.182 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.domain.com:6001 443 - <ISA IP> MSRPC 401 1 2148074254 203
I use the same Listener for OWA and Outlook Anywhere. Authentication Methods are Basic and Integrated. I forward the request to a webfarm which exists of the two physical CAS. Internal Site Name is set to the NLB name ex2010.domain.com, SPN is set to http/ex2010.domain.com
Thanks for your support

Hi, i ran into the same Problem.
the steps above solved mine too (Creating a custom AppPool which runs under LocalSystem).
I wonder why they included only the Script: convertoabtovdir.ps1
http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/thread/dc24ccd3-378a-47cc-bbbf-48236f8fe5b0
Ist this a supported configuration (changing AppPool of RPC)?

ISA 2006 publish Exchange 2010 Outlook Anywhere with KCD/NTLM and IPSEC - Problem

Hi
I have setup ISA 2006 to publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation and IPSEC.
The clients have an IPSEC policy pushed to them via GPO. The clients are windows 7 laptops and the ISA server is server 2003, so the IPSEC connection is IKE not AuthIP.
However, it seems that the connection will work for a while, then all of a sudden stop working with zero trace of why. I cant get the Oakley log to work and I cant see any traffic on the ISA.
I am wondering if I need to publish the CRL's externally? Currently we don't, and the Outlook Anywhere uses private certificates (as the whole point of IPSEC is to validate the internal certificate, there is no point in using
public certificates).
I have tried using the StrongCRLCheck=0 registry key in the IPsec Policy Agent on the windows 7 machine but it doesn't seem to make a difference.
Any advice would be appreciated.
Steven

Hi,
Firstly, have you received any related error messages in ISA server or on the clients' side? Besides, as you mentioned IPsec, did you have a VPN connection?
In addition,
While ISA 2006 only includes a Client Access Web Publishing Wizard for both Exchange 2003 and Exchange 2007. Which Exchange version you have chosen when publishing Exchange 2010?
Please also make sure that you have selected the
External interface for the web listener to listen on.
Besides, the link below would be helpful to you:
OWA publishing using Kerberos Constrained Delegation
method for authentication delegation
Best regards,
Susie

Exchange 2010 - Report NDRs with powershell

Hi all,
I would like to analyze all internal NDRs within my exchange environment. For example we have systems which are hard coded with email addresses of internal recipients and people leave the business and their mailbox and associated email address will be removed
from exchange but not from a third party system that has a list of addresses to send notifications out to or home grown scripts. In order to keep the email pipeline clean and follow best practices I would like to catch these NDRs and remove them from the relevant
systems.
Is there anyway I can do this with powershell, my environment Exchange 2010 SP2 and all the roles are on a single server.

Hi Niko,
I have just performed the following test:
sent an email to an internal recipient were the address does not exist, example
[email protected]
The NDR does not come from [email protected]
The headers for the NDR I got as listed below:
MIME-Version: 1.0
From: Microsoft Outlook
<[email protected]>
To: <[email protected]>
Date: Thu, 11 Dec 2014 08:55:54 +0000
Content-Type: multipart/report; report-type=delivery-status;
boundary="129b7383-6632-4979-ab4a-e5742a33ae6b"
X-MS-Exchange-Organization-SCL: -1
Content-Language: en-GB
Message-ID: <[email protected]>
In-Reply-To: <[email protected]com>
References: <[email protected]com>
Thread-Topic: test
Thread-Index: AdAVIEZfXlpAxeICRk2Dg71q+Amr/wAAADyf
Subject: Undeliverable: test
X-MS-Exchange-Organization-AuthSource: exchangeserver.mydomain.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 05

Exchange 2010 SP3 OWA with certificate based authentication

Hi,
I have a bizarre problem in my customer’s environment. Maybe someone has an idea.
Exchange 2010 with SP3, latest cumulative Update installed.
The problem I’m having is that when I enable Certificate based authentication (require client certificate option in IIS) on OWA and ECP virtual directories in conjunction with forms based authentication (this is the requirement – the user
must have a client certificate and type in username and password to log in to OWA), the result is that after the user selects the certificate he wants to use, he is logged into OWA automatically, but cannot use the website, because it’s being constantly automatically
refreshed (or redirected to itself or something like that). The behavior occurs with all users, with any browser. If client certificate is on required, forms based authentication works just fine. If I switch to “Basic Authentication” and enable client certificate
requirement, then OWA act’s as it should be – so no problems. The problem only occurs when authentication type is forms based and client certificates are required.
I have tried the exact same settings (as far as I can tell) on one other production server and one test server, and encountered no such problems.
Anyone – any ideas?

Hi McWax,
According to your description and test, I understand that all accounts cannot login OWA when select require client certificate.
Is there any error message when open OWA or login? For example, return error ”HTTP error: 403 - Forbidden”. Please post relative error for further troubleshooting.
I want to confirm which authentication methods are used for OWA, Integrated Windows authentication or Digest authentication? More details about it, for your reference:
http://technet.microsoft.com/en-us/library/bb430796(v=exchg.141).aspx
If you select another authentication method, please check whether Client Certificate Mapping Authentication services is installed, and also enabled in IIS, please refer to:
http://www.iis.net/configreference/system.webserver/security/authentication/clientcertificatemappingauthentication
To prevent firewall factor, please try to sign in OWA at CAS server. Besides, I find a FAQ about certificate:
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Best Regards,
Allen Wang

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Prepare Exchange 2010 for a Major Network Outage

We are planning to replace our Core networking switch in our production environment. I am looking for a best practice option for Exchange to be placed into during this outage. This will be an approximate four hour outage.
Our current environment for Exchange is this:
Exchange 2010 SP3 rollup 8v2 two CAS servers and Three MBX/HT servers.
I read a few articles and they recommended different things, one was to just power down all of the exchange servers before the outage and then bring them back up after the outage. To me this just seems like a bad idea. The other was to put the MBX servers
into maintenance mode prior to shutting them down. This seemed more practical.
Can anyone provide feedback, insight, and guidance in this case? Has anyone gone through this type of outage and if so how did you handle your exchange environment and what was your success or failures with the scenario you used?
Thank you

When the server is in maintenance mode it moves all the active databases to other DAG members. It pauses the node in the cluster, and sets the DatabaseCopyAutoActivationPolicy mailbox server setting to Blocked. The Suspend-MailboxDatabaseCopy cmdlet is run
for each database hosted by the DAG member, and the cluster core resources will be moved to another server in the DAG if needed. This prevents data bases from auto activating in the case of a server failure. Just powering down an exchange MBX server would
cause the active data bases to failover to the alternate server, but once Quorum is lost due to more than half of the servers being shut down, I am not sure how the data bases would react after being brought back on line. Based on
this it seems to me that putting the servers in maintenance mode prior to powering them down would be the safest bet.
TL;DR What I am really looking for is advice or experience from an Admin who has already gone through a similar exercise.
Thanks for your input.

Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

Here is our current scenario,
Exchange 2007
2 - Hub Transport Servers
2 - CAS servers (cluster NLB)
2 - Mailbox servers (clustered)
Exchange 2010
2 - Huib Transport Servers
3 - CAS servers (array NLB)
2 - Mailbox servers (1 DAG)
We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

Hi,
As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
For more information, you can refer to the following article:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 logon statistics with powershell

I am trying to get some logon statistics from a Exchange server 2010, I am using the following command,
Get-MailboxServer | Get-LogonStatistics | Select UserName,ClientVersion,LastAccessTime,ServerName, but it returns this, 3587.0.32963.1, as a version
number.
I have read that it is af bug in Exchange 2010. Does anyone have a workaround?

Right, I guess along with IP address Outlook doesn't send version information either back via Get-LogonStatistics...
The client IP address for an Outlook 2010 client is not logged in Exchange when you use the Get-LogonStatistics command -
http://support.microsoft.com/kb/2292750
However you can get Version information from RPC Client Access Logs located in below folder...
\Program Files\Microsoft\Exchange Server\v14\Logging\RPC Client Access

Exchange 2010 health-checks with encryption and ntlm auth

Hi everybody,
I will be forced to implement extended health-ckecks for Exchange 2010 CAS Servers. So the cisco design guide does not help
Exchange2010 CAS Service needs ntlm auth for many services by default. http://technet.microsoft.com/en-us/library/bb331973.aspx
Now with SP1 also for pop3 and imap4. I have not found any option to use ntlm by default.
The next problem is encryption.
Health-checks with encryption are not integrated in cisco ace 4710 by default.
As an alternative to try a scripted health-check with tcl script is an option but needs more investigation and is timeconsuming.
I watched for other vendors solution, they use e.g. external imported shell scripts with curl (curl -s --ntlm -k -X POST ...) to do a health-check with ntlm. That would be fine at the moment to beat the requirement of extendet health-checks.
But maybe it is only ntlm verion 1, I do not know what happens if it comes to ntlm version 2.
Kerberos authentication is a much bigger problem, but at the moment not a requirement.
Does anybody has some hints or also a tcl script for exchange health-checks ?
Best Regards
Alois

Hi everybody,
I will be forced to implement extended health-ckecks for Exchange 2010 CAS Servers. So the cisco design guide does not help
Exchange2010 CAS Service needs ntlm auth for many services by default. http://technet.microsoft.com/en-us/library/bb331973.aspx
Now with SP1 also for pop3 and imap4. I have not found any option to use ntlm by default.
The next problem is encryption.
Health-checks with encryption are not integrated in cisco ace 4710 by default.
As an alternative to try a scripted health-check with tcl script is an option but needs more investigation and is timeconsuming.
I watched for other vendors solution, they use e.g. external imported shell scripts with curl (curl -s --ntlm -k -X POST ...) to do a health-check with ntlm. That would be fine at the moment to beat the requirement of extendet health-checks.
But maybe it is only ntlm verion 1, I do not know what happens if it comes to ntlm version 2.
Kerberos authentication is a much bigger problem, but at the moment not a requirement.
Does anybody has some hints or also a tcl script for exchange health-checks ?
Best Regards
Alois

IOS 4.3.1 + Exchange 2010 "was" fine with the mailbox on Ex2007 server

Hi,
i had used my iphone with ios 4.3.1 and active sync.
The mailbox was hosted on the old exchange 2007 server.
A new exchange 2010 server was running the last 4 weeks and the iphone was connection with activesync against the new exchange 2010 through local wlan and over internet.
After i moved my profile to the new server i can´t connect anymore to the new server!
Any idea what happend?

It was working fine the last weeks with my mail account sitting on exchange 2007.
Today i moved several mailboxes from exchange 2007 to 2010 SP1.
I have some domain accounts that are created new and had their mailbox created on the exchange 2010 sp1 system.
With these accounts i can connect and retrieve mails.
But with my account (moved from 2007 to 2010) i can´t.
All i get is a blank mailbox on my iphone.
I even removed the mail account from my iphone and recreated the account.
But it won´t retrieve mails.
I refresh the offline addressbook at the exchange 2010 but nothing will help.
Message was edited by: juergenb52

EXCHANGE 2010 - Edge server with forefront FULL OF SPAM

Hi there.
We have recieved on Exchange 2010 EDGE server a lot of spam 200k messages in queue.
We have stoped inboud SMTP traffic on firewall to stop the attack.
Any suggestion how to empty the queue? I've heard there is a way to rename the "Exchange queue folder" but forget the procedure.
How to stop the attacker?
bostjanc

Hi There,
Use the KB below to find the Queue DB, then stop the service listed In the KB, rename the old DB and create a new one with the same name, than start the Service.
http://www.ntweekly.com/?p=653
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Getting BEA-000337 error in a TEST environment with no load at all.

Hi,
We're currently experiencing an unknown issue regarding the key BEA-000337. We've looked on the internet to understand what happens, but we are completely stuck.
<Jan 30, 2009 3:23:29 PM CET> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "712" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@cc1102", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.lang.Object.wait(Native Method)
weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:81)
weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:108)
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:335)
weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
xxx.yyy.sas.SASConnectorService_37hpy3_EOImpl_922_WLStub.getRoutingInfo(Unknown Source)
xxx.yyy.tp.manager.SASManager.getRouting(SASManager.java:1071)
xxx.yyy.tp.ccb.RetrievalOperatorProcess.execute(RetrievalOperatorProcess.java:139)
xxx.yyy.tp.Process.baseExecute(Process.java:598)
xxx.yyy.tp.Process.execute(Process.java:683)
xxx.yyy.tp.TransactionService.execute(TransactionService.java:291)
xxx.yyy.tp.TransactionService.executeProcess(TransactionService.java:241)
xxx.yyy.tp.TransactionService.handleAction(TransactionService.java:476)
xxx.yyy.tp.TransactionService.handleMessage(TransactionService.java:431)
xxx.yyy.tp.mdb.TransactionManagerMDBBean.onMessage(TransactionManagerMDBBean.java:126)
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
weblogic.ejb.container.internal.MDListener.run(MDListener.java:674)
weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
On the internet everybody tells that the best thing to do is to extend the StuckThreadMaxTime. But we are executing only one single process on our own, on a test environment. So this can't be because WL is overloaded. When checking memory it is quite low (regarding its usual load), and there is a lot of available CPU.
The strangest thing is that this error occurs as follow:
An EJB is created correctly (we don't see issues in the logs), but this error occurs when we try to access it for the first time. I guess the SASConnectorService_37hpy3_EOImpl_922_WLStub class is our client proxy, that needs to call our real EJB on another instance of Weblogic. But we see no trace of that EJB on our distant server. It is fully reproducible, since everytime we launch it, we get that error.
If anybody has a lead, or at least a clue, I take it.

My guess -
1) Networking issue
2) A long transaction(could be global or your EJB transaction) that you do really need more than 10 mins to finish it.
I would check netstat output for 1) and time the EJB transaction.
If your server is not hang and still accepting request, you can actually ignore it. Or you can tune stuck thread max time higher(longer time allow for stuck warning) so this message will stop bugging.

External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
the Exchange 2010 all incoming external mails were not received. What could be the cause?

Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
Sniff the traffic to ensure that it is hitting 2013 directly.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Prepare Exchange 2010 Test Environment with Hyper V

Similar Messages

Maybe you are looking for