Office 365 Limitations

The other day I had a quick look at the Office 365 for Enterprise Service Descriptions documents to see what the limitations are with Office 365, mainly with Exchange Online and Lync Online.

I am not going to talk about the advantages or disadvantages of going from an on-premises e-mail solution to the cloud (there are hundreds of pages/documents about that). I am merely mentioning some aspects of this solution that I think might be of an issue for some companies.

Please note that some of them are my interpretation and might be wrong! All of these are purely based on what I read in the Office 365 for Enterprise Service Descriptions documents and what I thought was relevant to my organization!

NOTE: Please do not take this information and 100% accurate as I still need to confirm some of them. I will be testing Exchange Online in the next couple of months, so I might post an update.

Lync Online

1. Lync technology does not support coexistence between Lync Online and Lync Server using a single domain. Therefore, it is not possible to deploy a subset of users in Lync Online and other users on-premises using a single domain name. Lync federation can be used to enable users to communicate between Lync Online and Lync on-premises deployments, however only using different domain names.

2. Federated Lync does not support file transfer;

3. Dial-in audio conferencing (the ability to dial into a scheduled Lync meeting/conference from fixed-line or mobile phones) is not provided in Lync Online, but can be achieved using third-party audio conferencing services;

4. No Lync-to-Lync high definition video;

5. There is no possibility of recording and playback of meetings;

6. No anti-malware scanning for meeting content and file transfers;

7. No privacy mode (which allows users to restrict their presence information so that it is visible only to the contacts listed in their Lync Contacts list);

8. There is no IM/Presence federation with XMPP networks (Jabber, Google Talk);

9. There is no interoperability with on-premises video conferencing systems;

10. Communicator for Mac client and Lync 2010 Phone Edition (for Lync-based IP phones) are not supported. Lync 2010 Mobile client coming soon;

11. No IM Archiving;

12. SharePoint (both Online or on-premise) skill search via Lync is not supported with Lync Online;

Exchange Online

1. Public folders are not available in Exchange Online. The solution would be to migrate data to SharePoint (either on-premise or Online) or to a shared mailbox;

    a. As Outlook 2003 and earlier versions use public folders to share free/busy information, distribute the offline address book (OAB) and set Outlook security settings, these will not be available;

    b. However, Exchange Online does not support Outlook versions before Outlook 2007.

2. When using Active Directory Federation Services 2.0 for single sign-on, users manage their credentials directly in their on-premises Active Directory. Users cannot change their passwords from Outlook Web App. This means that if a user’s password expires when he/she is on leave, the user will not be able to use any services (assuming the user does not have remote access to the internal network so he/she can change the password);

3. The Office 365 Directory Synchronisation tool ignores dynamic distribution groups in on-premises Active Directory, and does not synchronise these to Exchange Online;

4. Hierarchical address lists, Global Address List segmentation, custom Global Address List views, and multiple address lists per organisation are not available in Exchange Online;

5. Administrator-driven import of .pst files, using the new-mailboximportrequest PowerShell commandlet introduced in Exchange Server 2010 SP1, is not available in Exchange Online. However, PST Capture Tool (to be released later this year) will allow to do this;

6. OWA does not support S/MIME;

7. It is not possible to use BlackBerry devices to connect to Exchange Online via Blackberry Enterprise Server (coming later this year). However, it is possible to connect via Blackberry Internet Service. Research in Motion has announced a new hosted BES service for Office 365 customers that they plan to make available later this year;

8. Administrators cannot search Transport Logs, only Delivery Reports;

9. SMTP Relay: Exchange Online can be used as an SMTP delivery service to relay email messages. However, applications or services must authenticate with the username and password of a valid, licensed Exchange Online mailbox, and connect using TLS which a lot of applications still do not support;

10. Custom applications that use the Outlook MAPI library typically can connect to Exchange Online, but those that use the Exchange Server MAPI Client and Collaboration Data Objects (MAPI/CDO) for server-to-server communication with Exchange will not connect;

11. When an Exchange Online mailbox is deleted, its contents are recoverable for 30 days, after which the mailbox is not recoverable. If the user's account was deleted from the Microsoft Online Services Portal, then a call to Office 365 support is required in order to restore the Microsoft Online account so it can be linked to the recovered mailbox. It is not clear if/how a mailbox can be recovered after the 30 days period or for how long;

12. If a user wants to recover an e-mail that was deleted 4 months ago, the only option is the Dumpster. No mention of possibility of recovering single items through backup or a mailbox database restore from a specific point in time (which DAGs do not replace);

13. It is possible to configure mailbox capacity alerts for the user’s primary mailbox. However, the personal archive has a separate, non-configurable quota (quota depending on the plan chosen);

14. There is no Public/Private computer logon option in OWA and the default session time-out is 6 hours (configurable up to 24h – not sure is possible to configure for less than 6h);

15. Message size limits (by default 25MB in Exchange Online but 10MB in OWA) cannot be adjusted up or down. This value can only be “changed” by the use of transport rules to limit the maximum size of any individual attachment;

16. Exchange Online has restrictions that prevent users and applications from sending large volumes of email. Each Exchange Online mailbox can send messages to a maximum of 1,500 recipients per day. An email message can be addressed to a maximum of 500 recipients. These limits apply to emails sent within the internal domain as well as to messages delivered to external contacts. However, a distribution group that is stored in the Global Address List counts as one recipient but in a personal distribution group each recipient is counted separately;

17. Users can send only 30 messages per minute. If a user submits messages at a faster rate, Exchange Online will deliver the messages but will queue the messages at the server and throttle the rate of delivery. Not clear if this applies to e-mails sent to distribution lists;

18. Distribution Lists

a. Distribution groups that contain 5,000 or more members must have delivery management (a list of senders who are allowed to send messages to the distribution group) or message approval (one or more moderators who must approve all messages sent to the distribution group) options configured;

b. If a message is sent to 5,000 or more recipients, the message size can't exceed 2MB. If the message size exceeds the limit, the message isn't delivered and the sender receives a non-delivery report. The total recipient count is determined after distribution group expansion.

19. Moderation Lists

a. The maximum size of the arbitration mailbox is 10GB. If the arbitration mailbox exceeds this limit, messages that require moderation are returned to the sender in a non-delivery report;

b. The maximum number moderators that can be assigned to a single moderated distribution group or that can be added to a message using a single transport rule is 10;

c. By default, a message waiting for moderation expires after two days. However, the processing of expired moderated messages runs every seven days. This means that a moderated message can expire at any time between two and nine days.

Exchange Online Migration

1. Send/Receive As and full mailbox permissions are not replicated (might be available in the future);

2. Public folders are not replicated/supported.

3. Outlook Anywhere must be configured properly for RPC over HTTP access, with an SSL certificate issued by a public trusted certification authority.

Get OCS Client Version Script

This script uses the OCS 2007 R2 Resource Kit (didn't test with OCS 2007) to query its database and check the user’s version of the client they are using to connect to OCS.

The script reads a list of users to query from the UsersList.csv file and then queries one by one using the DBAnalyze tool from the Resource Kit (please update the path accordingly).



$users = Get-Content D:\UsersList.csv
cd "C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit"

ForEach ($user in $users)
{
  $strCmd = ".\DBAnalyze.exe"
  $strParams = "/Report:user /User:$user > D:\OCSUserReport.txt"
  $strExec = "$strCmd $strParams"
  Invoke-Expression $strExec

  # Get the user's version
  $strVersion = Select-String -Path D:\OCSUserReport.txt -Pattern "Client version"

  # Print the user's client version
  If ($strVersion -ne $NULL)
  {
    Write-Host "$user $strVersion"
  }
}

cd D:\
Remove-Item D:\OCSUserReport.txt

Attachments visible in OWA but not in Outlook

Today I had a user saying that our e-mail scanners had blocked an attachment sent to him. Upon closer look, I realised that this wasn’t the case and looking at the transport logs I saw that an e-mail with more than 1MB was delivered to the users!
So, with the user’s permission I look into his mailbox. By using OWA I was able to see, open and save both attachments, but when I looked in Outlook (2007 v12.0.6557.5001 with SP2) there just weren’t there! However, the e-mail size in Outlook was showing more than 1MB, so they had to be there...

Tried forwarding the e-mail from Outlook to myself, and nothing... Tried from OWA and I received them with no problems!

I found this post on Microsoft Support which says this sometimes happens with inline attachments in Exchange 2007 SP1 (which is what we are currently using – I know, don’t ask!...).

Basically, for Outlook 2007 the attachment is hidden and it is unavailable for download. In OWA, it is still hidden but you can download and view it.

If you are using Exchange Server 2010:
- Stop the Exchange Transport service;
- Locate the EdgeTransport.exe.config file (located in the following path: :\Program Files\Microsoft\Exchange Server\Bin\);
- In the EdgeTransport.exe.config file, add the following entry between the /appSettings element and the /appSettings element: add key="TreatInlineDispositionAsAttachment" value="true" /
- Restart the Transport service.

(Please note I had to remove the < > tags because of the HTML here...)


With Exchange Server 2007, just install Service Pack 2 and run the following command:
Set-OrganizationConfig –ShowInlineAttachments $True


As soon as I am able to test this, I will post here the results.

Hope this helps!

Lync Monitoring Dashboard Error

If you install the Monitoring server role for Lync and you get the following error message when opening the Dashboard on the reports page:

Report processing stopped because too many rows in summary tables are missing in the call detail recording (CDR) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the LcsCDR database.


But how do we run dbo.RtcGenerateSummaryTables?! Just follow these instructions:   :)

1. Go to your SQL Server where you installed the reports and start Microsoft SQL Server Management Studio (for the Monitoring Instance)

2. Expand Databases --> LcsCDR --> Programmability and finally Stored Procedures

3. In there, scroll down until you find the stored procedure specified in the error. In this case, dbo.RtcGenerateSummaryTables.

4. Right-Click the stored procedure and select Execute Store Procedure.

5. On the Execute Procedure window, click OK.

6. And hopefully will get a Return Value of zero.
 

Go back to your Dashboard, refresh the page and it should now work!    :)

Microsoft 2011 Scripting Games

Only two days to go!  :)





2011 Scripting Games: All Links on One Page

550 5.7.1 Unable to relay

Due to a change in our Call Logging system (the application the Help Desk uses to log IT service calls for users), I had to allow it to send e-mails as coming from the Help Desk mailbox to external users (similar to Send-As permissions).

So, I create a new receive connector, called Infra, just for the servers hosting that application and allowed for anonymous users to use it as the application doesn’t support authenticated SMTP...

This grants permissions to the anonymous account but it still doesn’t give you the relay permission. If you try to relay using this send connector, you will get the following SMTP error message:

550 5.7.1 Unable to relay


The ACL that controls relay is the ms-Exch-SMTP-Accept-Any-Recipient. To add this ACL to this receive connector, we have to use Exchange Management Shell:

Get-ReceiveConnector "Infra"
Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"


Please, don’t forget to keep relay as restricted as possible, as your domain might get black-listed!

Exchange 2007 and Nortel CS1K Unified Messaging

A lot of administrators out there using Nortel CS1K are experiencing the same issue that I am about to describe.

A few days ago a user complained that when someone phones him the call goes down after being diverted to voicemail. So, I decided to phone him and see if I could reproduce this issue. At first the user picked up and we had a normal conversation, no interruptions, good quality, everything as expected.

When I phoned him again, the call got diverted to voicemail (the user didn’t answer as per my request) and I received the usual “please leave a message for...” message. Approximately 5 seconds into my message I suddenly got the famous “are you still there?” message as if I wasn’t even speaking!


After some discussion with Nortel, they asked me to check the following registry key in our UM servers and report back my findings:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Speech Server\2.0\WireCodecList


Like probably most people on at least Exchange 2007 SP1, that key had the following codec’s list:
- RTAudio16KHz
- RTAudio8KHz
- G.723.1(6.3)
- G.711µ
- G.711A

Nortel then asked me to change it to:
- RTAudio16KHz
- RTAudio8KHz
- G.723.1(6.3)
- G.711A
- G.711µ

and restart the Microsoft Exchange Speech Engine service. So I did, and now it works fine!

My concern is why was it failing just to this user? Although there could have been more users affect that I simply wasn’t aware of...


According to Wikipedia, “G.711 defines two main compression algorithms, the µ-law algorithm (used in North America & Japan) and A-law algorithm (used in Europe and the rest of the world)”. Maybe the fact that our CS1K is in the UK caused this discrepancy and the problem we were experiencing. But still, why was it working for most people?! I am still working with Nortel to figure this out...



In Exchange UM, a codec (that converts an analog voice signal to a digitally encoded version for VoIP or to store it as an audio file) is used to store voicemails. But before that, another codec is used between the PBX and the UM server.

In Exchange 2007 SP1, UM servers can accept the following codecs from a PBX:
- RTAudio16KHz - Microsoft Real-Time audio codec that runs at 16 KHz and is used for wide bandwidth applications of Microsoft Unified Communications platforms;
- RTAudio8KHz - Microsoft Real-Time audio codec that runs at 8 KHz and is used for narrow bandwidth applications of Microsoft Unified Communications platforms;
- G711 µ-law - typically used for telephony in North America and Japan;
- G711 A-law - typically used for telephony in Europe and other parts of the world;
- G723.1 - typically used for VoIP telephony.

RTAudio is available only is UM is integrated with Office Communications Server 2007 (or superior), the UM dial plan configured as a SIP URI-type dial plan and the call answering codec on the dial plan to WMA. If OCS is not deployed, the dial plan is usually set to Telephone Extension and not SIP URI, which is my case.

G.711 is a well know standard developed for use with audio codecs. It uses two main algorithms, the µ-law algorithm (used in North America and Japan) and the A-law algorithm (used in Europe and other countries).

Normally, UM and PBX can offer both the G.711 and G.723.1 codec. However, UM will choose its preferred codec based on the WireCodecList key in the registry, mentioned above. Microsoft recommends to change the configuration on the PBX and not on this file as the UM server will determine the codec that is being used by the PBX and select the appropriate codec from the list.


Then, we have the codec used to store the voicemail message. Here, three codecs can be used:
- WMA – 16 bit compressed file
- GSM 06.10 – 16 bit no compressed file
- G.711 PCM – 8 bit compressed file

Each audio codec has its advantages and disadvantages. Just as a quick overview:
- WMA creates .wma audio files;
- GSM/G.711create .wav audio files;
- WMA is the default due to its sound quality and compression properties;
- GSM/ G.711 were included because of their ability to support other types of messaging systems.

As this wasn’t the issue, I will leave this for a later post. For more information, please check Size of Exchange Server 2007 UM (Unified Messaging) messages or the Microsoft UM documentation.


Hope this information helps!

Exchange 2010 Visio Stencils

Last November (I know, I'm a little bit late...) Microsoft released the November version of the Microsoft Exchange 2010 Visio Stencils, that include:
- Exchange 2010 server roles;
- Features new to Exchange 2010 SP1;
- Networking, telephony, and Unified Messaging objects;
- Active Directory and directory service objects;
- Client computers and devices;
- Other Exchange organization elements.

It works with the Microsoft Office Visio 2003 or later and you can get it here.

Microsoft Forefront Protection Server Script Kit

Just installed Forefront Protection 2010 for Exchange Server in one of my production servers yesterday (more on this in a couple of days) and I am waiting to install the Forefront Protection Server Management Console.
However, today I just found out about the Microsoft Forefront Protection Server Script Kit!
This kit provides multi-server management capabilities for Forefront Protection 2010 for Exchange Server and Forefront Protection 2010 for SharePoint.

"In addition to the ability to manage multiple Forefront Protection Servers from a single location, this Solution Accelerator provides easily extensible command-line scripts that help enable server discovery, configuration deployment, and integration with existing management technologies. It also offers basic reporting capabilities to detect configuration drift and monitor server statistics.

Configuration Management and Reporting
- Capture server configuration snapshots and push snapshots to any number of servers
- Compare configuration of any number of servers or baselines
- Obtain statistics from one or many servers, including information about infected files, detected malware, server health, and more
- See summary and/or server detail views"


Going to try it straight away! :-D

More information here and the download here.

Exchange 2010 - Best Mail Server

According to InfoWorld, Microsoft Exchange 2010 is the best mail server!   :)

"Microsoft Exchange 2010 continues Redmond's longstanding market leadership in mail servers and related software. This release shows why the company's once-reviled product continues to be deployed widely in enterprises: it works, it scales, and it continues to gain important new features. In our tests, we saw improved management, administration, and reliability features plus an enhanced experience for users that includes automatic transcription of voicemails, delivery reports for messages, and extensive self-service options. Although light on wholesale changes and heavy on refinements, Exchange 2010 is nevertheless a major step up from Exchange 2007."

Source: InfoWorld's 2011 Technology of the Year Award winners

Lync Server 2010 Protocol Workloads Poster

"This poster shows each workload in Microsoft Lync Server 2010 communications software, describing relationships, dependencies, flow of information, and certificate requirements."

Explore this poster online using Microsoft Zoom.It.
Download Lync Server 2010 Protocol Workloads poster

Get Mailbox Database Mount Status

Wondering why when you run the Get-MailboxDatabase you don’t see if the database is Mounted or not? This value might be especially useful when writing a monitoring script, for example. And yes, I was also wondering for a while...

All we have to do is add –status to the cmdlet:

and voila!   :)
Don't ask me why though...

Exchange 2010 Architecture Poster

The Exchange 2010 version of the Exchange 2007 Component Architecture poster has just been released!

“The poster [.pdf file, 36" x 24"] helps you understand how the major components of Exchange 2010 work and serves as a quick reminder and a learning tool.”

The poster can be found in the Download Center.

Exchange opens the door for hackers

"FIRMS RUNNING Microsoft's Exchange mail server could find that users of its Outlook Web Access (OWA) software have their sessions hijacked.

A security vulnerability in Exchange Server 2003 SP2 and Exchange Server 2007 SP1 and SP2 means that attackers can take control of a user's OWA session and issue commands up to the level permitted by security controls without the user knowing. OWA is a rich 'web mail' client that is offered by Exchange Server and has the look and feel of Microsoft's standalone Outlook software.

Microsoft's proposed solution to the problem might raise the ire of it customers. In the security advisory the Vole says, "Microsoft recommends that customers running affected editions of Microsoft Exchange Server upgrade to a non-affected version of Microsoft Exchange Server to address the vulnerability." Of course system administrators have nothing better to do than upgrade the version of Exchange on all of their mail servers and shift thousands of mailboxes to a new version of Exchange.

Microsoft does give a helping hand, though, by providing a handy list of the Exchange versions that are not affected, and those include Exchange 2000 SP3, 2007 SP3, 2010 and 2010 SP1.

The Vole also recommends segmenting user rights in OWA to limit the potential for damage by hackers. If you feel like implementing a particularly useless 'fix', then Microsoft also offers a way of hiding the display of the OWA options panel, which should flummox only the most novice of script kiddies.

Now all that's left is for Microsoft email system administrators to pick which day to come in at 3AM in order to overcome yet another security hole in Exchange."


By Lawrence Latif on the Inquirer
Wed Sep 15 2010

Exchange Server 2010 SP1 Is Now Available

Been on holidays for a couple of weeks and far away from the IT world...
That's why this news come a little bit out dated   :)

You probably already know most of the new features, so no point in telling them all here.

Just get it now here at the Download Center and try it!

PFDAVADMIN – “Could Not Expand” Error

Description
“Use the Exchange Server Public Folder Distributed Authoring and Versioning (DAV)-based Administration tool (PFDAVAdmin) to perform various management tasks related to public folders and mailboxes. The tool checks the permissions status of each public and mailbox folder and corrects any problems found. The ability to bulk export/import the permissions and replica lists make this tool invaluable in achieving greater productivity in managing public folders. The program can also report content information of each public folder and mailbox folder such as the number of items in each folder, size of folder and most recent modification date of any item in the folder.”

PFDAVADMIN can be found here.


If you try no run this tool directly for you Exchange 2007 Server (not advisable!), you will probably get the following error:

"Could not expand https://localhost/exadmin/admin/mydomain.com/public%20folders/ : Name cannot begin with the '0' character, hexadecimal value 0x30. Line 1, position 386"


You will always get this error message if the server/workstation you are running PFDAVADMIN does not have Microsoft .NET Framework v1.1 installed (Exchange 2007 uses the v2.0 Framework).

I had .Net Framework 2.0, 3.0, 3.5 and 4 on my workstation and it didn’t work. As soon as I installed 1.1, it worked perfectly.

So, don’t install v1.1 on your Exchange server, but on a workstation and run the tool from there!

Exchange SP1 Interviews

During Microsoft TechEd 2010 in New Orleans, Harold Wong interviewed a few of the Exchange Server Program Managers and Technical Managers regarding Exchange 2010 SP1 functionalities.

Check them all at Video Interviews From TechEd 2010.

You can find Exchange Server 2010 SP1 Beta, you can download it from here.

Exchange 2007 SP3

Since last week that Exchange Server 2007 SP3 is available for download here.
This third service pack enables Exchange 2007 to be installed on a Windows Server 2008 R2 server.

Don’t forget to check What's New in Exchange Server 2007 SP3.

2010 Scripting Games - Post Games

The Microsoft 2010 Scripting Games ended a couple weeks ago, and how fun it was! The scripts were constructive, creative and sometimes tricky.

I finished in 10th place. Honestly, was expecting a little bit more from myself... Got more stars in 9 advanced scripts than in 10 beginner scripts! :-S Shame on me...

But like most scripters that entered the games, it was all about sharing knowledge, learning new “tricks and techniques” and improving our programming skills. And it did just that! I’m fairly new to PowerShell (1+ year) and I mostly use it to manage Microsoft Exchange Server. So, I learned a lot of new things from other scripters and now I know how to do certain things better, like parameters in functions or splatting. Bottom line, I got what I wanted from these games, more knowledge!


PoshCode
It was the first time I used the excellent PoshCode. There were a few issues with it during the first few days, but they were fixed right away and there were no problems at all after that. To the responsible for PoshCode: very nice work!


Ratings
I really liked the fact that we would get 2 stars by meeting the basic requirements for the script, and had 3 more stars that we could earn if we completed extra design tasks. And these extra design tasks made all the difference and made the scripts very, very interesting.

Obviously, ratings will vary from judge to judge. As long as one judge remains constant across all the scripts he analyzes, I don’t see a problem with that. What would be really good is to know why I got 2 stars in this script, or 4 in this one and not 5. I know it was more than 1200 scripts submitted (can’t remember the exact number) and it would be very time consuming for the judges to give their opinion for every scripts, but some feedback would be really, really useful.

A lot of scripters, including myself, don’t understand why we got only 2 or 3 stars in some scripts and it would be great if we could know why. Mainly so we can rectify our errors and do better the next time! What could I have done better? What did I miss? Did I do too much and all you guys wanted was a simple script?

One problem I had with the beginner scripts was the fact that I never knew if I should write a basic 1 or 2 lines script that would do the job, or a more complex one, also with error handling and stuff like that. Please, make that clear next year :)

As Glenn said in his PostGame Roundup post, I also agree that a PowerShell script that is basically a “translation” from VBScript should never get more than 2 or stars. Like I said before, the games are about learning and sharing knowledge, and translating from VB to PS is not learning and is not doing any good to the scripter.



Prizes
It was all about the learning and sharing, but it is always good to win something! :) I won a copy of SoftwareFX PowerGadgets which I’m loving and will cover in my next post. I think I also won a copy of Idera PowerShell Plus Professional Edition, but haven’t received any e-mail about it so far.

Prizes are always a good motivation, and I think the prizes offered by these games were really good! Thank you to the Scripting Guys and to all the Sponsors!


Dates of Submission
The games had 10 events (20 in total considering advanced and beginner divisions), one each day with 1 week to submit each of them.

I think the number and divisions of the events are ok. At first I suggested that a new event should be announced every two days instead of every day. This was mainly due to people that work full time. In my case, I didn’t have enough time to deliver all the scripts: missed one and could have improved some scripts a little bit. However, this would make the games last for 4 weeks, which I don’t know if it is a good idea...


Twitter & All Links on One Page
The Scriting Guys did an excellent job in keeping everyone updated by using Twitter and a webpage with all links and info on it: All Links on One Page, and I loved the idea!
However, for some reason, after the first week of the games or by the end of the second week the webpage was not getting updated as frequently as it normally was... I would see something on Twitter (like a new leaderboard or prize winners) and only after 2 or 3 days it would get posted on the webpage... I don’t know why, but I think this shouldn’t have happened...


Overall, and as always, it was time well spent! I can’t thank enough to the Scripting Guys for organizing another amazing Scripting Games and to all the Sponsors that sponsored the games this year. An honest thank you!

See you all next year!   ;-)

2010 Scripting Games

The 2010 Scripting Games (fifth edition) are almost here and will begin on April 26 and continue through May 7!

Due to many requests from participants, this year the element of competition was reintroduced. There will be a leader board where everyone can keep track of the contestant rankings (updated daily). And yes, there will be prizes! They haven’t been revealed, but apparently “there is some really cool stuff that any scripter or budding scripter would love to have”.

This year, just as it has been for the last two years, there are 10 events for 2 divisions. A VBScript division and a Windows PowerShell division. There are two levels of participation in each of the two divisions: Beginner and Advanced. We are free to participate in both divisions and to participate at both levels if we wish. Of course, that would entail writing forty scripts!

For more information click on the badge or go to: 2010 Scripting Games