Script: Exchange Server 2013 SP1 Prerequisites (Exchange2013SP1Prerequisites_W2008R2SP1_v1.0)

This script automate execute steps for installing the necessary Windows Server 2008 R2 SP1 operating system prerequisites for the Microsoft Exchange 2013 Mailbox, Client Access, Multirole and Edge Transport server roles. The prerequisites that are needed to install Exchange 2013 on a Windows Server 2008 R2 SP1 computer depends on which Exchange roles you want to install.

What do you need to know before you begin?

  • The Edge Transport server role is available starting with Exchange 2013 SP1.
  • Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003 with Service Pack 2 or later.
  • The full installation option of Windows Server 2008 R2 SP1 must be used for all servers running Exchange 2013 server roles or management tools.
  • You must first join the computer to the appropriate internal Active Directory forest and domain.
  • You must check and be sure your server has access to the internet
  • Some prerequisites require you to reboot the server to complete installation.

Let’s have a quick look how to execute the script Exchange2013SP1Prerequisites_W2008R2SP1_v1.0 on Windows PowerShell and what this script do for us.

  1. Login to Windows Server 2008 R2 SP1 with Enterprise Administrator credentials
  2. Start Windows PowerShell “As Administrator”


  1. Next step, copy the script Exchange2013SP1Prerequisites_W2008R2SP1_v1.0 on (C:\) drive
  1. Let’s start with running scripts from within Windows PowerShell itself.
    In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
    Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted


Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.

Windows PowerShell has four different execution policies:

  • Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
  • AllSigned – Only scripts signed by a trusted publisher can be run.
  • RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
  • Unrestricted – No restrictions; all Windows PowerShell scripts can be run.
  1. The most common (default) way to run a script is by calling it:

PS C:\> & “C:\Admin\My first Script.ps1”

If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator

PS C:\> C:\Admin\Myscript.ps1

If the script is in the current directory, you must indicate this using .\ (or ./ will also work)

PS C:\> .\Myscript.ps1

In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter


  1. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 3 (E2013 Multirole installation) and click Enter


  1. As you can easy check bellow, my Multirole Prerequisites are in progress to be download and install


  1. After the Prerequisites successfully installed, we have to choose the option 10 in order to restart our server


  1. After restart your server, login as EA and proceed to install your Microsoft Exchange Server 2013 SP1


You can download the script from TechNet Gallery Script Center Capture


Microsoft Exchange User Monitor (Exmon) tool – Updated Version

I am pleased to announce that there is a new version of this tool that the Exchange performance, development, and operations teams at Microsoft have used for quite some time called Exchange User Monitor (Exmon) and can be downloaded here.

Exmon for the first time allows an Exchange administrator the ability to see in amazing detail the performance of an Exchange server. Shown on a user by user basis, Exmon allows you to see how much CPU, latency, network traffic, and disk each user on an Exchange server consumes. It can be run in almost realtime (minute by minute analysis) or over longer (multiple-hour) capture periods. Exmon also ‘bubbles’ up data sent back to the Exchange server from Outlook 2003 and higher about the user’s actual experience, showing the actual RPC (network+server) latency and even the name of the process talking to the Exchange server (so you can see ActiveSync usage and other 3rd party MAPI applications).

The data Exmon exposes is the ‘raw’ data that many of the Exchange Performance counters use in calculating the running averages.

Internally, this tool was used to help understand the performance of Outlook 2003 and other MAPI applications during the development of Exchange Server 2003. We use it to understand the broad impact of performance across a server, but also to troubleshoot specific performance problems with individual users. The impact to the server being ‘traced’ is minimal, allowing it to be run on very large servers.

I’d love for you to download the tool, give it a whirl, and tell us what you think. We’d love to see what use you can come up with for this data, problems you’re able to solve, and conclusions you’re able to make.

It is also now available the ExPerfwiz that can enable the Exmon on a time interval basis and automation.

Kind Regards
Catastrophic Failure “JV”

Exchange Server 2010 SP1 VHD

This download comes as a pre-configured VHD. This download enables you evaluate Microsoft Exchange Server 2010 SP1 for 180 days.

One VHD with

  • Windows 2008 Domain Controller & Global Catalog

  • Rights Management

  • Exchange Server 2010 SP1

  • DNS

  • Certificate Authority

  • Microsoft Office Professional Plus 2010

  • Office Communications Server Standard Edition

Kind Regards
Catastrophic Failure “JV”

Exchange Management Shell (EMS) missing after applying Exchange 2010 SP1


Problem: After installing Service Pack 1 for Exchange Server 2010, the Exchange Management Shell is missing.

Cause: Missing certain .ps1 scripts from the bin directory, removed during SP1 setup.Resolution: There is no resolution at this time. 


1. Verify that the ConnectFunctions.ps1 , RemoteExchange.ps1 and CommonConnectFunctions.ps1 files are present in the %ExchangeInstallPath%bin directory.

NOTE: If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack 1 installation media to the %ExchangeInstallPath%bin directory.
These files are present in the setupserverrolescommon folder.

2. Right click an open area on the Desktop, click New , click Shortcut .

3. In the Type the location of the item , type in the text below:
%SystemRoot%System32WindowsPowerShellv1.0powershell.exe -noexit -command ". ‘%ExchangeInstallPath%binRemoteExchange.ps1’; Connect-ExchangeServer -auto"

4. Name the shortcut Exchange Management Shell and click Finish .

5. Right click the Exchange Management Shell shortcut, click Properties and remove the text from Start In field on the Shortcut tab.

6. On the Shortcut tab, click Change Icon , click Browse and type in the text below:

7. Select the Exchange icon and click OK .

8. Click Apply and click OK .

9. Copy the new Exchange Management Shell shortcut to this location:
%systemdrive%ProgramDataMicrosoftWindowsStart MenuProgramsMicrosoft Exchange Server 2010

Kind Regards
Catastrophic Failure ”JV” Nerd smile

Configuration Improvements in Outlook Web App / Instant Messenger integration in Exchange Server 2010 SP1


Exchange Server 2010 RTM is the first version of Exchange that allows integration between Outlook Web App and Office Communications Server’s instant message capabilities. The RTM steps to configure the Instant Messenger integration between Office Communications Server and Exchange were as follows:

1. Configure Office Communication Server 2007 R2

  • Add Exchange Server’s name(s) and its certificate info to the Host Authorization tab

2. Configure Exchange Server 2010  Client Access Server

  • a) Configure certificate
  • b) Install Office Communications Server components on to Exchange Server
    • Run  CWAOWASSPMain.msi file to expand the below files:
      • Double-click on vcredist_x64.exe (Visual C++ Redistributable Setup)
      • Double-click on UcmaRedist.msi (Unified Communication Managed API 2.0 Core Redistribution 64-bit package)
      • Open a CMD window with elevated privileges (using an administrator password) and run CWAOWASSP.msi
  • c) Edit web.config file so Exchange Server 2010 Client Access server knows how to communicate with Office Communications Server 2007 R2 server.

3. Office Communication Server 2007 R2 User configuration to confirm that all users are enabled for Instant Messaging.

Problems with Method of Configuring Integration in Exchange Server 2010 RTM

In Exchange Server 2010 RTM, one of the steps (2.c as noted above) to configure the Client Access server requires the editing of the web.config file in the /owa subdirectory and make changes to a specific section of the file:

<add key="IMPoolName" value="" />
<add key="IMCertificateIssuer" value="" />
<add key="IMCertificateSerialNumber" value=""/>

Those values contain the necessary information to allow the Exchange Server 2010 RM Client Access server to connect to the Office Communications Server 2007 R2 server:

<add key="IMPoolName" value="" />
<add key="IMCertificateIssuer" value="CN=ContosoCA, DC=contoso, DC=com" />
<add key="IMCertificateSerialNumber" value="1F 5E DD 03 00 00 00 00 00 05"/>

There are multiple problems with this method:

  1. It was very tedious and not very administrator friendly.
  2. Whenever an upgrade (incl. build to build) occurs, the web.config file is wiped and the administrator must reconfigure all web.config files in the environment. This step is often forgotten so help desk calls come in stating the Instant Messenger functionality is no longer present.
  3. Generally speaking, we want the configuration of components to be as easy as possible and certainly to not involve the editing of configuration files. This can lead to other problems if the edits are not done correctly and no backups of the file are made.
The Improvement

To improve on these areas, Exchange Server 2010 SP1 no longer requires the editing of the web.config file as shown in Step 2.c. above. The step was:

2. c. Edit web.config file so Exchange Server 2010 Client Access server knows how to communicate with Office Communications Server 2007 R2 server.

Now the step is to configure those settings using the Set-OwaVirtualDirectory cmdlet:

2. c. Use Set-OwaVirtualDirectory on the Client Access server(s) to configure the Office Communications Server name (or pool name) and the Client Access server’s certificate thumbprint.

Below we discuss the new method of configuring the information formerly stored in the web.config file.

Important: All other steps are the same as they are in Exchange Server 2010 RTM.

Settings to Configure Instant Messenger integration with Office Communications Server 2007 R2

To simplify the configuration of Instant Messenger integration with Office Communications Server, Exchange Server 2010 SP1 no longer requires the editing of the web.config file.

The information that is stored in the web.config file in Exchange Server 2010 RTM is now stored in Active Directory on the Outlook Web App virtual directory (owa) and can easily be changed by using the, Set-OwaVirtualDirectory cmdlet. The settings can be retrieved by using the Get-OwaVirtualDirectory cmdlet.

The settings are stored in the InstantMessaging* properties.

Default Settings

Before configuring any of the settings on the Outlook Web App virtual directory (owa), the four InstantMessaging settings look as follows in their default configuration:

Get-OwaVirtualDirectory | fl InstantMessage*

Two of the parameters are already familiar to you and have not changed. The InstantMessagingType and InstantMessagingEnabled parameters are the same as they are in Exchange Server 2010 RTM. The two new ones that replace those in the web.config file are InstantMessagingCertificateThumbprint and InstantMessagingServerName.


Configuration is only possible by using the Exchange Management Shell. There is not a way to configure these settings by using the Exchange Management Console or the Exchange Control Panel.

To see what the old settings in Exchange Server 2010 RTM’s web.config file map to in the Set-OwaVirtualDirectory cmdlet please view the following table:

Web.config setting

Set-OwaVirtualDirectory Parameter replacement




None/Not required



Note: This parameter now requires the thumbprint of the certificate and not the serial number.

Note: This parameter now requires the thumbprint of the certificate and not the serial number.

Important: After changing any of the InstantMessage parameters, it is important to always remember to reset IIS by using the following cmdlet:

Iisreset /noforce

After upgrading to Exchange Server 2010 SP1, these parameters must be modified by the administrator. The settings are not transferred from the RTM web.config file. Below we take a look at each of the Instant Message related parameters in detail:


Use the InstantMessagingServerName parameter to configure the name of the Office Communications Server 2007 R2 server, or server pool name that the Exchange Server 2010 SP1 server(s) will communicate with. To set this parameter, use the Set-OwaVirtualDirectory cmdlet and use the FQDN of the Office Communications Server (or pool name of servers) as the value for the InstantMessagingServerName parameter.


Set-OwaVirtualDirectory "owa (default web site)" -InstantMessagingServerName


When you are ready to configure the new values using the Set-OwaVirtualDirectory cmdlet you only have to retrieve the thumbprint value from the certificate on your Exchange Server 2010 SP1 Client Access server. To do this, you can run the following cmdlet on your Client Access server:

Get-ExchangeCertificate | fl thumbprint

If you have more than one certificate and need more information to determine which certificate currently being used for IIS, include the Services field which shows you which certificate is currently set to use IIS.

Get- ExchangeCertificate | fl services,thumbprint

Example result:

Then, copy the thumbprint value onto the clipboard and run the Set-OwaVirtualDirectory cmdlet to configure the thumbprint number on the owa virtual directory. See an example:

Set-OwaVirtualDirectory "owa (default web site)" -InstantMessagingCertificateThumbprint 8210E17393B6E81AD0B3A75DD9161ABE1A93B695

Please note that you do not have to enter any spaces between two digit sets of the number like you have to in Exchange Server 2010 RTM for the certificate serial number stored in the web.config file.


Just like in Exchange Server 2010 RTM you must enable Instant Messaging by setting this parameter on the /owa virtual directory to $True:

Set-OwaVirtualDirectory "owa (default web site)" -InstantMessagingEnabled $True

Reminder: This setting is only applied to users who do not have the InstantMessagingEnabled setting set to $False in an Outlook Web App policy on their mailbox.  The owa mailbox policy always overrides the /owa virtual directory setting.


This setting is also the same as it is in Exchange Server 2010 RTM. This value must be set to ocs to allow Instant Messenger integration to function with Office Communications Server 2007 R2.

To set this parameter, run the following cmdlet on the Client Access server:

Set-OwaVirtualDirectory "owa (default web site)" -InstantMessagingType ocs

Applying settings to all /owa virtual directories on multiple servers

In some environments you may want apply all of the settings to all /owa virtual directories on your Exchange Server 2010 SP1 Client Access servers in your environment. To do that you simply pipe the Get-OwaVirtualDirectory cmdlet into the Set-OwaVirtualDirectory cmdlet and include the appropriate syntax as below:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory
-InstantMessagingServerName <OCS Pool FQDN>
-InstantMessagingCertificateThumbprint <Thumbprint>
-InstantMessagingEnabled $true
-InstantMessagingType OCS

Running this type of cmdlet ensures all settings are applied to all Client Access servers. This is critical if you are load balancing your Client Access servers because users may log on to a different server each time they log in to an Outlook Web App session.

Resetting IIS

Always remember to reset IIS after making changes to any of the parameters mentioned in this lesson. To reset IIS run the following command in a regular command shell:

iisreset /noforce

Source: Perry Newman

Kind Regards
Catastrophic Failure “JV”

Microsoft Security Advisory 2416728, the ASP.NET Vulnerability, and Exchange Server


On September 17, Microsoft released Microsoft Security Advisory (2416728), “Vulnerability in ASP.NET Could Allow Information Disclosure.” As stated in the advisory, Microsoft is investigating a new public report of a vulnerability in ASP.NET. Additional information about the issue can also be found in Understanding the ASP.NET Vulnerability on the Microsoft Security Research and Defense blog, and in the following blog posts by Microsoft .NET Developer Platform Vice President Scott Guthrie:

All Microsoft Exchange versions starting with Exchange 2003 use ASP.NET in a manner where potential for this vulnerability exists. However, if you have implemented a default configuration within your environment there are only a handful of files which may contain sensitive data that could be potentially accessed. In addition this sensitive data is only useable if the attacker has managed to penetrate the additional defense layers built into Exchange.

How to detect an attack on Exchange

An attack attempt against Exchange Server should generate warnings in the application event log of your server similar to:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/11/1111 11:11:11 AM
Event time (UTC): 11/11/1111 11:11:11 AM
Event ID: 1309
Event sequence: 133482
Event occurrence: 44273
Event detail code: 0
Application information:
Application domain: c1db5830-1-129291000036654651
Trust level: Full
Application Virtual Path: /
Application Path: C:fooTargetWebApplication
Machine name: FOO
Process information:
Process ID: 3784
Process name: WebDev.WebServer40.exe
Account name: foo
Exception information:
Exception type: CryptographicException
Exception message: Padding is invalid and cannot be removed.

We strongly recommend customers monitor their Application logs for instances of this event and investigate them if seen. These event logs would contain an Event Occurrence field that provides a counter of the number of exceptions triggered.

Note: You may also see this warning event logged due to other reasons (including cases for example where you have mismatched keys on a web-farm, or a search engine is following links incorrectly, etc), so its presence does not necessarily indicate an attack of this nature.

The presence of this ‘Event Occurrence’ also does not indicate that an attack was successful.

If the event is detected and you believe it is the ASP.NET attack, it is possible to use stateful filters in your firewall or intrusion detection systems on your network to detect patterns and block malicious clients.

As indicated in the advisory, Microsoft is currently working to develop a security update to address this vulnerability with details of any fix released in the future being reposted on this blog and the Microsoft Security Advisory (2416728) page.

Microsoft will release the security update once it has reached an appropriate level of quality for broad distribution. We will post again to inform Exchange customers once this security update has been released to resolve the ASP.Net issue. We do not have an ETA for this fix being available at the time of writing. Microsoft Security Advisory 2416728, the ASP.NET Vulnerability, and Exchange Server

Posted by Kevin Bellinger 

TechNet Subscription Offerings

TechNet Subscriptions is tailored to fit the needs of your IT environment for every organization. There are three different products that are geared towards different roles and organizational needs whether you are evaluating, testing, or deploying Microsoft software.

Microsoft® TechNet Subscription Standard: Tailored to help IT Professionals evaluate, test, and troubleshoot Microsoft software for desktop environments. TechNet Standard does not include some enterprise editions of Microsoft software.

Microsoft® TechNet Subscription Professional: Geared towards IT Professionals who need a more comprehensive subscription and are primarily focused on supporting enterprise wide environments such as the following scenarios: server consolidation, interoperability, network management and more.

Microsoft® TechNet Subscription Professional with Media: Offers the same benefits as TechNet Professional, but is geared towards those organizations with bandwidth constraints and/or prefer a DVD copy of software.

Find out which TechNet Subscription is right for you :


Continue at

Kind Regards,
Catastrophic Failure “JV”Nerd smile

Ενημερωθείτε, εκπαιδευτείτε, ανταλλάξτε απόψεις.

7 ημέρες έμειναν ακόμη μέχρι την λήξη της προσφοράς του Super Early Bird των 135 euro για την Συμμετοχή στο IT Pro | Dev Connections 2010

Υπενθυμίζουμε ότι για όσους δηλώσουν συμμετοχή κάνοντας χρήση αυτής της προσφοράς, θα υπάρξει κλήρωση δύο MSDN Ultimate Subscriptions αξίας 12500 ευρώ η κάθε μία.

Από την 1η Οκτωβρίου και για άλλες 20 ημέρες η συμμετοχή θα κοστίζει 150 ευρώ. Ενώ για τις τελευταίες ημέρες πριν το event η τιμή θα είναι 230 ευρώ.

Και φυσικά εδώ θα βρείτε το πρόγραμμα του event.

2 μέρες, 4 παράλληλα tracks γεμάτα με 29 ομιλίες από 30 ομιλητές.

Εδώ δεν θα βαρεθείτε με ανιαρές παρουσιάσεις γεμάτες θεωρία για μια …παράλληλη πραγματικότητα. Αν και κάποιες ομιλίες αναφέρονται στο  … cloud, το περιεχόμενο είναι προσγειωμένο και έχει άμεση πρακτική εφαρμογή.

Και επειδή έχει περάσει η εποχή που βασιζόμασταν σε άλλους, σε θαύματα, σε επιχειρήσεις που δεν κλείνουν ποτέ από τις οποίες θα παίρναμε και σύνταξη (!?), σε ένα …τυρί που δεν τελειώνει, ΠΡΕΠΕΙ ΝΑ ΔΡΑΣΟΥΜΕ.

Η νέα γενιά εκ πεποιθήσεως και οι παλιότερες από ανάγκη, πλέον στηρίζονται στα προσόντα, στις γνώσεις και στην προσωπική τους αξία, που θα τους ακολουθεί όπου κι αν βρεθούν.

To IT Pro | Dev Connections 2010 φιλοδοξεί να βοηθήσει σε αυτή την κατεύθυνση.

Ενημερωθείτε, εκπαιδευτείτε, ανταλλάξτε απόψεις, μοιραστείτε την ενέργεια της κοινότητας που όλοι ανήκουμε.

Σας περιμένουμε.

Source: Θανάσης Κλαδάκης

After installing an Exchange 2007 or Exchange 2010 server in to a mixed site the OAB generation fails with error 9342 and Outlook clients fail to download the OAB with error 0x8004010f

After setting up a mixed org with exchange 2007 and or Exchange 2010 the OAB generation fails with error 9342.

Public folders are widely used with all version of Exchange. For the OAB public folders are a must. With the introduction of Exchange 2007 public folders are an option. During the setup you will be asked whether you want to setup legacy support or not. If you do not opt for legacy support public folders will not be installed. From this point on you will need to create a Web Distribution enabled OAB for your Outlook 2007 clients to download.

If you are going to maintain a mixed organization for a little while (Exchange 2003 / Exchange 2007, Exchange 2007 / Exchange 2010) you need to know a few things.

  1. By default the Default Offline Address List resides on the first server in the site, which is your Exchange 2003 or 2007 server.
  2. The OAB generation server by default is your Exchange 2003 server for a mixed (2003 / 2007) org. It will be the 2007 server if it is a (2007 / 2010) org.
  3. Before your users on the Exchange 2007 server can download the OAB Version 2, 3 and 4 files from the public folder store, a local replica for the OAB folders must exists on the Exchange 2007 store.
  4. If you did not create a public folder store on the Exchange 2007 or Exchange 2010 server, you will need to create one before clients can download the legacy OAB.
  5. Now if you have installed your Exchange 2007 or Exchange 2010 server and you want your clients to download the OAB, you will need to do a few things otherwise you might get the following errors:

Outlook client“Outlook clients receive error 0x8004010f when downloading the Offline Address Book” issue.

If you turn up diagnostic logging for the OAB Generation process on the Exchange 2007 server you might see the following event:

Event Type: Warning
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9342
Date: 5/1/2007
Time: 10:31:28 AM
User: N/A
Computer: OAB-Server
No previous version of an offline address list for ‘Global Address List’ can be found. No differential update file will be produced. This is expected if this is the first time this offline address list has been generated. – Default Offline Address List

If you follow this blog to turn up diagnostic logging for the OAB Generation process on your Exchange 2007 server and rebuild you might see this event:

Event Type: Warning
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9335
Date: 5/1/2007
Time: 10:31:28 AM
User: N/A
Computer: OAB-Server
OALGen encountered error 80040115 while cleaning the offline address list public folders under /o=org/cn=addrlists/cn=oabs/cn=Default Offline Address List. Please make sure the public folder store is mounted and replicas exist of the offline address list folders. No offline address lists have been generated. Please check the event log for more information. – Default Offline Address List

What this means is that the local replicas on the Exchange 2007 server do not exist. The hierarchy will reflect that they do but the contents need to also be replicate over for the folders to exist. So you will need to do the following:

1. Move the OAB from the Exchange 2003 server to the Exchange 2007 server, or from Exchange 2007 to the Exchange 2010 server.
2. Make sure you have local replicas of the OAB on the correct Exchange server and they have *successfully* replicated over.
3. Make sure all of the mailbox stores on the Exchange 2007 and Exchange 2010 server under the Client Settings tab have the Default Offline Address Book associated.
4. Follow this blog [
How to work with Exchange 2007 / 2010 OAB Event Logging] on how to turn up diagnostic logging on an Exchange 2007 or 2010 server.
5. Rebuild the OAB.
6. Check the application log again to make sure that the OAB has generated successfully.

As long as replicas exist on the Exchange 2003 / 2007 or 2007 / 2010 server you should have no problem generating and downloading the OAB.

Additional Info:

Source: Dgoldman

Kind Regards
Catastrophic Failure “JV”Nerd smile

Κλήρωση απίστευτων δώρων σε όσους κάνουν χρήση του super early bird στο ITPro|Dev Connections 2010…

Κάνουμε την αρχή με μια απίστευτη κλήρωση δώρων για όσους θα δηλώσουν συμμετοχή στο event μέχρι τις 30 Σεπτεμβρίου, εκμεταλλευόμενοι την προσφορά super early bird.

Τα δώρα που θα κληρωθούν ξεπερνούν κάθε προσδοκία.

Πρόκειται για δύο ULTIMATE MSDN SUBSCRIPTIONS, αξίας 11.000$ η κάθε μία. !!!!!!!

Η απίστευτη αυτή κλήρωση γίνεται δυνατή χάρις την ευγενική προσφορά των subscriptions από μέλη της ελληνικής κοινότητας των Microsoft MVPs.

Για όσους θέλετε να μάθετε ποια προϊόντα περιλαμβάνει το subscription δείτε εδώ (μην κάνεις τον κόπο τα έχει όλα)

Και για όσους θέλουν να …τσεκάρουν την τιμή δείτε εδώ.

Κάντε register τώρα….