Hello,
I wont blog here anymore, you can follow up my new blogs on
http://blogs.technet.com/b/nawar/
Friday, May 28, 2010
Monday, May 03, 2010
HUB Routing in a DAG Scenario
Nice one :)
When the Hub Transport server is co-located with a Mailbox server that's a member of a DAG, there are changes in routing behavior to ensure that the resiliency features in both server roles will provide the necessary protection for messages sent to and received by users on that server. The Hub Transport server role was modified so that it now attempts to reroute a message for a local Mailbox server to another Hub Transport server in the same site if the Hub Transport server is also a DAG member and it has a copy of the mailbox database mounted locally. This extra hop was added to put the message in the transport dumpster on a different Hub Transport server.
For example, EX1 hosts the Hub Transport server role and Mailbox server role and is a member of a DAG. When a message arrives in transport for EX1 destined for a recipient whose mailbox is also on EX1, transport will reroute the message to another Hub Transport server in the site (for example, EX2), and that server will deliver the message to the mailbox on EX1.
There's a second, similar behavior change related to the Microsoft Exchange Mail Submission service. This service was modified so that it would not submit messages to a local Hub Transport server role when the Mailbox server or Hub Transport server is a member of a DAG. In this scenario, the behavior of transport is to load balance submission requests across other Hub Transport servers in the same Active Directory site, and fall back to a local Hub Transport server if there are no other available Hub Transport servers in the same site.
http://technet.microsoft.com/en-us/library/dd638137.aspx#CT
When the Hub Transport server is co-located with a Mailbox server that's a member of a DAG, there are changes in routing behavior to ensure that the resiliency features in both server roles will provide the necessary protection for messages sent to and received by users on that server. The Hub Transport server role was modified so that it now attempts to reroute a message for a local Mailbox server to another Hub Transport server in the same site if the Hub Transport server is also a DAG member and it has a copy of the mailbox database mounted locally. This extra hop was added to put the message in the transport dumpster on a different Hub Transport server.
For example, EX1 hosts the Hub Transport server role and Mailbox server role and is a member of a DAG. When a message arrives in transport for EX1 destined for a recipient whose mailbox is also on EX1, transport will reroute the message to another Hub Transport server in the site (for example, EX2), and that server will deliver the message to the mailbox on EX1.
There's a second, similar behavior change related to the Microsoft Exchange Mail Submission service. This service was modified so that it would not submit messages to a local Hub Transport server role when the Mailbox server or Hub Transport server is a member of a DAG. In this scenario, the behavior of transport is to load balance submission requests across other Hub Transport servers in the same Active Directory site, and fall back to a local Hub Transport server if there are no other available Hub Transport servers in the same site.
http://technet.microsoft.com/en-us/library/dd638137.aspx#CT
Tuesday, April 20, 2010
CAS Static ports and what to LB
from http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part2.html
On the CAS servers, for Mailbox connections, you need to use add a DWORD registry key named “TCP/IP Port” under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem
Set the value to the port number to be assigned. In this article we use port 55000, but you are free to choose whatever port you want to use, just remember it should not conflict with other applications using the port. It is recommend you choose a port within the dynamic RPC ranger (1024-65535).
To use a static port for public folder access, you need to do the same on the mailbox servers:
First open the registry editor. Then add a DWORD key named “TCP/IP Port” under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem
It’s fine to use the same port that you specified on the CAS server
Finally you need to limit the port usage for clients that connect to the NSPI endpoint for directory access. Unlike MAPI access to mailboxes and public folders this is done by modifying a file more specifically the Microsoft.exchange.addressbook.service.exe.config configuration file located in the Exchange Bin folder
Open the file in Notepad and then change the “RpcTcpPort” value from the default assignment of “0” to the port you want Outlook clients and Exchange to use for the directory access via the NSPI EndPoint. In this article we use port 55001.
When you have done the above changes, you should reboot the Mailbox and Client Access on which you performed the above changes.
from the installation guides:
The values used in NLB must be the same across all nodes in the NLB cluster. The values specified here will ensure that the Windows Network Load Balancing array can load-balance HTTPS (TCP443), IMAP4 (TCP143 and TCP993), POP3 (TCP110 and TCP995), RPC Endpoint Mapper (TCP135), Address Book service (TCP55000), and RPC Client Access (TCP55001).
On the CAS servers, for Mailbox connections, you need to use add a DWORD registry key named “TCP/IP Port” under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem
Set the value to the port number to be assigned. In this article we use port 55000, but you are free to choose whatever port you want to use, just remember it should not conflict with other applications using the port. It is recommend you choose a port within the dynamic RPC ranger (1024-65535).
To use a static port for public folder access, you need to do the same on the mailbox servers:
First open the registry editor. Then add a DWORD key named “TCP/IP Port” under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem
It’s fine to use the same port that you specified on the CAS server
Finally you need to limit the port usage for clients that connect to the NSPI endpoint for directory access. Unlike MAPI access to mailboxes and public folders this is done by modifying a file more specifically the Microsoft.exchange.addressbook.service.exe.config configuration file located in the Exchange Bin folder
Open the file in Notepad and then change the “RpcTcpPort” value from the default assignment of “0” to the port you want Outlook clients and Exchange to use for the directory access via the NSPI EndPoint. In this article we use port 55001.
When you have done the above changes, you should reboot the Mailbox and Client Access on which you performed the above changes.
from the installation guides:
The values used in NLB must be the same across all nodes in the NLB cluster. The values specified here will ensure that the Windows Network Load Balancing array can load-balance HTTPS (TCP443), IMAP4 (TCP143 and TCP993), POP3 (TCP110 and TCP995), RPC Endpoint Mapper (TCP135), Address Book service (TCP55000), and RPC Client Access (TCP55001).
Monday, April 19, 2010
"Warning: Failed to cleanup the source mailbox after the move"
In Exchange 2010 when a source mailbox is moved from Exchange 2003 to Exchange 2010 using the Mailbox Replication Service there is a potential issue can arise that source mailbox is not removed at the end of the move.
All of the content in the mailbox is moved from the source Exchange 2003 mailbox to the Exchange 2010 destination mailbox. All the user mailbox attributes are updated to point to the new Exchange 2010 mailbox
This issue can be caused by problems within the search folders that are located in the source mailbox
This issue will be mainly encountered in Exchange 2003 servers. This issue currently resolved in the Exchange 2007 mailbox servers that have been upgraded to Service Pack 2.
When you try to purge the mailboxes you will get the following error:
"The Operation cannot be performed because this mailbox was already reconnected to an existing user"
The solution is : http://support.microsoft.com/default.aspx?scid=kb;EN-US;930363
All of the content in the mailbox is moved from the source Exchange 2003 mailbox to the Exchange 2010 destination mailbox. All the user mailbox attributes are updated to point to the new Exchange 2010 mailbox
This issue can be caused by problems within the search folders that are located in the source mailbox
This issue will be mainly encountered in Exchange 2003 servers. This issue currently resolved in the Exchange 2007 mailbox servers that have been upgraded to Service Pack 2.
When you try to purge the mailboxes you will get the following error:
"The Operation cannot be performed because this mailbox was already reconnected to an existing user"
The solution is : http://support.microsoft.com/default.aspx?scid=kb;EN-US;930363
Thursday, April 15, 2010
DAG witness on non exchange server
If the witness server you specify isn't an Exchange 2010 server, you must add the "Exchange Trusted Subsystem" universal security group to the "local Administrators" group on the witness server. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. If the proper permissions aren't configured, the following error is returned:
Error: An error occurred during discovery of the database availability group topology. Error: An error occurred while attempting a cluster operation. Error: Cluster API "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied."
Error: An error occurred during discovery of the database availability group topology. Error: An error occurred while attempting a cluster operation. Error: Cluster API "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied."
Wednesday, April 07, 2010
What happened to –ConfigurationOnly?
In many of the disaster recovery scenarios in Exchange 2007, one of the most useful cmdlets is the “Move-mailbox” with the “ConfigurationOnly” parameter.
With the “ConfigurationOnly” parameter the mailbox content is not physically moved but instead mailbox configurations gets changed “mailbox location”, for example we could direct the mailbox(s) to a functioning server and create a dialtone database or if we have a database with clean shutdown state (from a failed server or backup) we could mount this database on a different functioning server and redirect users to that database (Database Portability) .
In Exchange Server 2010 the “Move-Mailbox” cmdlet is now replaced with the “New-MoveRequest” cmdlet and the “ConfigurationOnly” parameter is no longer available.
So in Exchange 2010 to maintain this powerful functionality and to allow a configuration only move of mailboxes, we will be using the “Set-Mailbox” cmdlet with the “Database” parameter, for example to move all the users whose mailboxes is on database DB1 to DB5 we will use:
Get-Mailbox -Database DB1 | Set-Mailbox –Database DB5
The example above shows how powerful the Set-Mailbox cmdlet in Exchange 2010 and care should be taken when working with this cmdlet.
With the “ConfigurationOnly” parameter the mailbox content is not physically moved but instead mailbox configurations gets changed “mailbox location”, for example we could direct the mailbox(s) to a functioning server and create a dialtone database or if we have a database with clean shutdown state (from a failed server or backup) we could mount this database on a different functioning server and redirect users to that database (Database Portability) .
In Exchange Server 2010 the “Move-Mailbox” cmdlet is now replaced with the “New-MoveRequest” cmdlet and the “ConfigurationOnly” parameter is no longer available.
So in Exchange 2010 to maintain this powerful functionality and to allow a configuration only move of mailboxes, we will be using the “Set-Mailbox” cmdlet with the “Database” parameter, for example to move all the users whose mailboxes is on database DB1 to DB5 we will use:
Get-Mailbox -Database DB1 | Set-Mailbox –Database DB5
The example above shows how powerful the Set-Mailbox cmdlet in Exchange 2010 and care should be taken when working with this cmdlet.
Thursday, April 01, 2010
Update Rollup 3 for Exchange Server 2007 Service Pack 2
Update Rollup 3 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers.
For a list of changes that are included in this update rollup, see KB979784.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.
This is a cumulative update rollup and replaces the following:
KB971534 Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)
KB972076 Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB972076)
http://www.microsoft.com/downloads/details.aspx?FamilyID=c781326a-7b81-444d-9836-760fa1e3a28a&displaylang=en
For a list of changes that are included in this update rollup, see KB979784.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.
This is a cumulative update rollup and replaces the following:
KB971534 Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)
KB972076 Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB972076)
http://www.microsoft.com/downloads/details.aspx?FamilyID=c781326a-7b81-444d-9836-760fa1e3a28a&displaylang=en
Wednesday, March 24, 2010
versions versions versions !
Run on PS: GCM exsetup | %{$_.Fileversioninfo}
then follow
http://support.microsoft.com/kb/158530
http://technet.microsoft.com/en-us/library/bb232170(EXCHG.80).aspx
then follow
http://support.microsoft.com/kb/158530
http://technet.microsoft.com/en-us/library/bb232170(EXCHG.80).aspx
Tuesday, March 23, 2010
Outlook 2003: E-mail messages take a long time to send and receive when you use an Exchange 2010 mailbox
This problem occurs because Exchange Server 2010 does not issue UDP notifications to Outlook 2003. Therefore, Outlook 2003 cannot register to receive UDP notifications from Exchange Server 2010. Additionally, Outlook 2003 is not notified about changes that are made to a folder until Outlook 2003 polls the server for these changes. The default polling interval for Outlook 2003 is about 60 seconds. This is why you see delays that last approximately 1 minute in these folder actions
http://support.microsoft.com/default.aspx?scid=kb;en-us;2009942
http://support.microsoft.com/default.aspx?scid=kb;en-us;2009942
Friday, March 05, 2010
Latest Exchnage Updates
Exchange 2010: Release Date: February 18, 2010 Update Rollup 2 for Exchange Server 2010 resolves issues that were found in Exchange Server 2010 since the software was released. This update rollup is highly recommended for all Exchange Server 2010 customers. For a list of changes that are included in this update rollup, see KB979611. This is a cumulative update rollup and replaces the following: KB976573 Update Rollup 1 for Exchange Server 2010 (KB976573) | Exchange 2007: Release Date: January 21, 2010 For a list of changes that are included in this update rollup, see KB972076. This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052. This is a cumulative update rollup and replaces the following: KB971534 Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534 |
Helpful Notes: · For detailed steps about how to install update rollups on a clustered mailbox server in Exchange 2007, see the following: · For detailed steps about how to install update rollups on Exchange 2010 on DAG server, see the following: | |
Friday, November 20, 2009
EXCHANGE BUILDS NUMBERS
E2000 ("Platinium"): 6.0.4417 RTM 11/2000
SP3: .6249 07/2002
“Aug rollup” v2: .6603.1 (KB870540) 08/2004
E2003 ("Titanium"): 6.5.6944 RTM 06/2003
SP1: .7226 (TI SP1) 04/2004
SP2: .7638.2 (TI SP2) 10/2005
Post SP2 GDR: .7650.28 01/2006
KB 916160 : includes ALL E2003 PFDs tracing
E2007 ("E12"): 8.0.685 RTM 12/2006
…
8.0.783.2 RU6 KB942846 02/21/2008
8.1.240.6 SP1 11/29/2007
…
8.1.336.1 SP1 RU5 KB953467 11/20/2008
MS09-003 <- 8.1.340.1 SP1 RU6 KB959241 02/10/2009
8.1.359.2 SP1 RU7 KB960384 03/18/2009
8.1.375.2 SP1 RU8 KB968012 05/19/2009
8.1.393.1 SP1 RU9 KB970162 07/17/2009
8.2.176.2 SP2 08/24/2009
8.2.217.3 SP2 RU1 KB971534 11/19/2009
E2010 ("E14”): 14.0.639.21 RTM 10/2009
SP3: .6249 07/2002
“Aug rollup” v2: .6603.1 (KB870540) 08/2004
E2003 ("Titanium"): 6.5.6944 RTM 06/2003
SP1: .7226 (TI SP1) 04/2004
SP2: .7638.2 (TI SP2) 10/2005
Post SP2 GDR: .7650.28 01/2006
KB 916160 : includes ALL E2003 PFDs tracing
E2007 ("E12"): 8.0.685 RTM 12/2006
…
8.0.783.2 RU6 KB942846 02/21/2008
8.1.240.6 SP1 11/29/2007
…
8.1.336.1 SP1 RU5 KB953467 11/20/2008
MS09-003 <- 8.1.340.1 SP1 RU6 KB959241 02/10/2009
8.1.359.2 SP1 RU7 KB960384 03/18/2009
8.1.375.2 SP1 RU8 KB968012 05/19/2009
8.1.393.1 SP1 RU9 KB970162 07/17/2009
8.2.176.2 SP2 08/24/2009
8.2.217.3 SP2 RU1 KB971534 11/19/2009
E2010 ("E14”): 14.0.639.21 RTM 10/2009
Tuesday, July 28, 2009
Exchange 2010 trainings
Some cool new trainings for the upcoming Exchange 2010 are available now FREE for a while, enjoy !
Clinic 6901: Exchange Server 2010 in an Enterprise
This one-hour clinic describes Exchange Server 2010 features that are useful in an enterprise. It covers features such mailbox server configurations, unified messaging, and high availability.
Clinic 6900: Introduction to Exchange Server 2010
This one-hour clinic describes Exchange Server 2010 features, deployment scenarios, and development platform options. It also contains descriptions of tools used for managing Exchange Server 2010.
Collection 6899: Exploring Features of Exchange Server 2010
This two-hour collection provides you with an overview of the new features in Exchange Server 2010. It also describes the enhancements made over Exchange Server 2007.
Clinic 6901: Exchange Server 2010 in an Enterprise
This one-hour clinic describes Exchange Server 2010 features that are useful in an enterprise. It covers features such mailbox server configurations, unified messaging, and high availability.
Clinic 6900: Introduction to Exchange Server 2010
This one-hour clinic describes Exchange Server 2010 features, deployment scenarios, and development platform options. It also contains descriptions of tools used for managing Exchange Server 2010.
Collection 6899: Exploring Features of Exchange Server 2010
This two-hour collection provides you with an overview of the new features in Exchange Server 2010. It also describes the enhancements made over Exchange Server 2007.
Wednesday, December 24, 2008
Thursday, October 23, 2008
Information about Interim updates
If you experience a critical problem with Exchange 2007, the fix process resembles the fix process of earlier versions of Exchange. We use the following process to help resolve the problem:
1.You work with a Customer Support Specialist or with the Microsoft Escalation Services personnel to troubleshoot the problem.
2.The Customer Support Specialist or the Microsoft Escalation Services person escalates the fix request to the Exchange Customer Experience Team.
3.The Exchange Customer Experience Team creates an interim fix to resolve the problem.
4.The Exchange Customer Experience Team offers this fix to help resolve the problem until the next scheduled update rollup package that contains the fix is released.
Note: We deliver the interim fix under the same service-level agreement that is currently used. However, an additional agreement states that you must remove the fix when an update rollup package that contains the fix is released. Then, you must reinstall the fix by using the appropriate update rollup package. This agreement helps guarantee that the Exchange installation is restored to a known and quantifiable state as soon as possible.
Interim fixes (interim updates) and cumulative update rollup packages benefit from much of the same testing. However, an interim fix does not receive the comprehensive testing that we perform for an update rollup package. Additionally, an interim update is specific to a particular update rollup. For example, an interim update that we create to fix a problem in the release version of Exchange 2007 may not function correctly on an Update Rollup 2 for Exchange Server 2007 installation. Therefore, if you receive an error message when you try to install an interim update, you may be experiencing one of the following problems:
•You have another interim update installed.
•You are trying to install an interim update that was designed for a different update rollup package.
Interim update interaction with update rollup packages
If you have an interim update installed in Exchange 2007, you must remove the interim update before you apply the next update rollup package. To remove the interim update, use Add or Remove Programs in Control Panel. If you do not remove the interim update before you install an update rollup package, you may receive an error message when you try to install the update rollup package. You may also receive an error message when you try to install an earlier update rollup package after a later update rollup package has been installed.The main technical reason why only one interim update installation is allowed is that all interim updates for a particular rollup package share the same build version. This means that if you have an interim update installed, and if you enable a second interim update to be installed, any files that are common to both interim updates will not be installed when the second interim update is installed. Therefore, the fix may not be installed when the second interim update is installed. The seemingly obvious alternative is for each interim update to have a unique build version. However, this condition would cause currently installed changes to be overwritten. This means that a previously installed fix would no longer function. To avoid these conditions, we have implemented a blocking strategy. This strategy lets only a single interim update be installed. The fact that all interim updates for a particular rollup package share the same build version is also the technical reason for the following requirements:
•You must uninstall an interim update before you install an update rollup.
•You must install the correct update rollup before you install an interim update.
1.You work with a Customer Support Specialist or with the Microsoft Escalation Services personnel to troubleshoot the problem.
2.The Customer Support Specialist or the Microsoft Escalation Services person escalates the fix request to the Exchange Customer Experience Team.
3.The Exchange Customer Experience Team creates an interim fix to resolve the problem.
4.The Exchange Customer Experience Team offers this fix to help resolve the problem until the next scheduled update rollup package that contains the fix is released.
Note: We deliver the interim fix under the same service-level agreement that is currently used. However, an additional agreement states that you must remove the fix when an update rollup package that contains the fix is released. Then, you must reinstall the fix by using the appropriate update rollup package. This agreement helps guarantee that the Exchange installation is restored to a known and quantifiable state as soon as possible.
Interim fixes (interim updates) and cumulative update rollup packages benefit from much of the same testing. However, an interim fix does not receive the comprehensive testing that we perform for an update rollup package. Additionally, an interim update is specific to a particular update rollup. For example, an interim update that we create to fix a problem in the release version of Exchange 2007 may not function correctly on an Update Rollup 2 for Exchange Server 2007 installation. Therefore, if you receive an error message when you try to install an interim update, you may be experiencing one of the following problems:
•You have another interim update installed.
•You are trying to install an interim update that was designed for a different update rollup package.
Interim update interaction with update rollup packages
If you have an interim update installed in Exchange 2007, you must remove the interim update before you apply the next update rollup package. To remove the interim update, use Add or Remove Programs in Control Panel. If you do not remove the interim update before you install an update rollup package, you may receive an error message when you try to install the update rollup package. You may also receive an error message when you try to install an earlier update rollup package after a later update rollup package has been installed.The main technical reason why only one interim update installation is allowed is that all interim updates for a particular rollup package share the same build version. This means that if you have an interim update installed, and if you enable a second interim update to be installed, any files that are common to both interim updates will not be installed when the second interim update is installed. Therefore, the fix may not be installed when the second interim update is installed. The seemingly obvious alternative is for each interim update to have a unique build version. However, this condition would cause currently installed changes to be overwritten. This means that a previously installed fix would no longer function. To avoid these conditions, we have implemented a blocking strategy. This strategy lets only a single interim update be installed. The fact that all interim updates for a particular rollup package share the same build version is also the technical reason for the following requirements:
•You must uninstall an interim update before you install an update rollup.
•You must install the correct update rollup before you install an interim update.
Update Rollup 4 for Exchange Server 2007 SP1 has been released
Final version of Update Rollup 4 for Exchange Server 2007 SP1
Download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8B492ED2-EA92-412F-A852-3AA1C58D9499&displaylang=en
Related KB article: http://support.microsoft.com/?kbid=952580
The rollup is available via the download center. It will be available via Microsoft Update starting with 11/4/2008.
Download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8B492ED2-EA92-412F-A852-3AA1C58D9499&displaylang=en
Related KB article: http://support.microsoft.com/?kbid=952580
The rollup is available via the download center. It will be available via Microsoft Update starting with 11/4/2008.
Wednesday, November 07, 2007
Friday, November 02, 2007
Licensing Advisor and Virtual Licensing Calculators
Here are some great licensing resources I wanted to share to help you understand some of the licensing challenges that you face from time to time.
Let me start with “The Microsoft Product Licensing Advisor” an online tool that will help you figure out what licensing program is best for you based on your requirements. This online tool has been updated recently and can be reach from the following link. please note that you can review your report offline and save your quote to send to someone later.
http://www.microsoft.com/licensing/mplahome.mspx
In the virtualization world there are 2 calculators which would help you figure out what you need based on your virtualization strategy. Calculator 1 lets you interactively build virtual machines running multiple Microsoft server products to estimate the licenses and costs for Windows Server by edition (Standard, Enterprise and DataCenter) and many Microsoft server products. It starts with configuring your server based on virtualization technology, sockets and clustering requirements, and then builds the virtual machines.
Calculator 2 provides two ways to estimate the number and cost of Windows Server Standard Edition, Enterprise Edition and DataCenter Edition licenses needed for your virtualization scenarios to help you determine the most cost-effective edition of Windows Server.
You can find both calculators at
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/calculator.mspx
In addition the licensing team has also produced this video that explains virtualization licensing in depth. It is a long video but well worth the time as there are plenty of examples and scenarios covering Windows, SQL, multi-core, multi-CPU and more...Video: Licensing Microsoft Servers for Virtualization
Wednesday, September 19, 2007
SCR
Very interesting SCR blog from the exchange team
http://msexchangeteam.com/archive/2007/09/13/447006.aspx
download and make sure to watch maximized.
I have asked Scott for a list of commands used and here is the link "thanks Scott"
http://blogs.technet.com/scottschnoll/archive/2007/09/19/cmdlets-and-commands-used-in-scr-blogcast.aspx
http://msexchangeteam.com/archive/2007/09/13/447006.aspx
download and make sure to watch maximized.
I have asked Scott for a list of commands used and here is the link "thanks Scott"
http://blogs.technet.com/scottschnoll/archive/2007/09/19/cmdlets-and-commands-used-in-scr-blogcast.aspx
List of all Microsoft Team Blogs
Thanks to Brandon LeBlanc for the list of Microsoft Team blogs
http://windowsvistablog.com/blogs/windowsexperience/pages/microsoft-blogs.aspx
http://windowsvistablog.com/blogs/windowsexperience/pages/microsoft-blogs.aspx
Subscribe to:
Posts (Atom)
